Ticket #1763 (closed Feature Requests: fixed)

Opened 5 years ago

Last modified 3 years ago

Online System Updates XML even if changes have not been published

Reported by: wiseoldowl Assigned to: p_lindheimer
Priority: major Milestone: 2.5
Component: FreePBX.org Website Version: 2.3-branch
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description (Last modified by p_lindheimer)

The bug below is a result of this. You should be able to update a module but not publish it. That allows others to pull and test it - forcing proper module installation when manually installed. The publish process should be the trigger to modify the xml blob used by the online system.

In module administration, under Announcements it says: "Online upgrade available (0.6)." If I attempt to install it, it says, "Announcements 0.5 will be upgraded to online version 0.6", but then I get this:

Downloading announcement

Untarring..Done.

Error(s) installing announcement:

  • This module is already installed.

Change History

02/10/07 18:58:38 changed by p_lindheimer

  • owner deleted.
  • component changed from Announcement Module to Installation.
  • description changed.
  • summary changed from Announcement module doesn't upgrade properly (or id's itself as wrong version?) to Online System Updates XML even if changes have not been published.

06/25/07 06:35:25 changed by p_lindheimer

  • version changed from 2.2.0 to 2.3-branch.

given the current infrastructure, this is a bit tough. However, this needs some sort of way to address and catch the errors:

TODO: modify the server side scripts that manage this to detect module.xml files that are out of sync with the tarball files. This can be one of two issues:

  • module's module.xml saved but module not published
  • server side detection of md5 sum errors

Both these error conditions should at least generate alerts to us sysadmins to fix the issues.

06/26/07 16:30:00 changed by p_lindheimer

  • owner set to gregmac.
  • priority changed from minor to major.
  • component changed from Installation to Core - Module Admin.

this really is a feature request

06/30/07 16:37:33 changed by p_lindheimer

  • type changed from Bugs to Feature Requests.

moving to feature request

07/26/07 10:21:11 changed by p_lindheimer

  • milestone changed from 2.2 to 2.3.

07/13/08 01:00:52 changed by p_lindheimer

  • owner changed from gregmac to p_lindheimer.
  • confirmation set to Unreviewed.
  • component changed from Core - Module Admin to FreePBX.org Website.
  • milestone changed from 4.0 to 3.0.

not a Module Admin issue, it's a website issue how the xml is currently handled and managed.

09/08/08 00:17:16 changed by p_lindheimer

  • status changed from new to closed.
  • confirmation changed from Unreviewed to Confirmed.
  • resolution set to fixed.
  • milestone changed from 3.0 to 2.5.

this has been resolved for now with an explicit requirement to publish modules on the website once they have been published through the module process. It also allows for tarballs to be published in advance of general availability for early testing.