Project

General

Profile

Bug #8171

Unreliable versioning

Added by Jurgen Gaeremyn about 5 years ago. Updated about 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
30/03/2016
Due date:
% Done:

0%

Estimated time:
Complexity:
Normal
SCRUM pts - complexity:
?

Description

Embedding the Chamilo version in the configuration file, and relying on the user to manually update the version number, is not reliable. Why not have a separate file containing the version number? (or a different existing file containing it)

For downward compatibility, you could first check if versionnumber.php exists, and if it doesn exist, go fetch the version number in configuration.php.

This looks like a really small patch (even I could write).

History

#1

Updated by Yannick Warnier about 5 years ago

  • Target version set to 2.0

At the moment we're in an intermediate situation. Initially, the version was in another file, but we tried to reduce the number of configuration files (we're still trying but this can only be done between major versions).
There are also recent changes that affected that, whereby in Chamilo 1.10 we do not show the version number in the footer anymore, making the presence of the version in configuration.php less essential.

But yes, I agree with you, having the user change it manually is unreliable and we should change this. I would prefer finishing with the development of 1.11 first (scheduled for June) and then change this, because 2.0 introduces a new configuration.php format.

#2

Updated by Jurgen Gaeremyn about 5 years ago

Hi,

I appreciate your feedback and understand your point. There are other priorities :)

Also available in: Atom PDF