Bug #2889

CALENDAR EVENT: versioning loses publication

Added by Anonymous about 10 years ago. Updated over 9 years ago.

Bug resolved
Target version:
Start date:
Due date:
% Done:


Estimated time:


On making and publishing a new version of a calendar event, the publication of the first version gets losts.
I'm afraid this might be a general problem of published objects with various versions.



Updated by Anonymous about 10 years ago

  • Priority changed from Normal to Urgent

Updated by Anonymous about 10 years ago

  • Target version set to 21

Updated by Stefaan Vanbillemont about 10 years ago

  • Project changed from Chamilo LCMS Connect to Courses
  • Category deleted (2)

Updated by Stefaan Vanbillemont almost 10 years ago

  • Target version changed from 21 to 2.1.0

Updated by Anonymous almost 10 years ago

  • Status changed from New to Needs more info

You are only able to view versions in the repository at the moment. When you click on an object you get an overview of the versions and you can revert or delete versions. So I think this is not a bug. Are you supposed to be able to manage versions within the courses application?


Updated by Anonymous almost 10 years ago

A new version should never undo the publication of an existing version, otherwise a user would not create a new version but simply change the existing object.
This is the main reason of the introduction of versions: to make it possible to work on new versions of an object without any effect in existing publications (also but not only in the courses application).
An example: it should be possible for version1 of an object published in course xyz2010 to coexist with version2 published in course xyz2011.

I have a question in return: what is the functionality/use of versions in the present implementation? What is the precise relationship with publications?


Updated by Anonymous almost 10 years ago

The use is that you can save several versions of a publication and you can easily revert to an earlier version, this is done via the repository. So the difference with simply editing a publication is that the previous publication version is saved.
The functionality you describe (having several indepedent publications of a same object) is achieved by Publish -> Browse -> select object(s). This way you can create as many publications as you want of an object, in different courses.


Updated by Anonymous almost 10 years ago

If I understand well: a new version of an object saves the previous version, but not the publication?
As far as usability is concerned this is simply unacceptable.


Updated by Anonymous over 9 years ago

  • Status changed from Needs more info to Bug resolved

This feature now works as expected. Old versions remain published.

Also available in: Atom PDF