In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Dependency Graph View Issue ] Relation Graph ] Vertical ]
related to child of duplicate of

Viewing Issue Simple Details
ID Category Type Reproducibility Date Submitted Last Update
0000309 [In-Portal CMS] Install / Upgrages bug report always 2009-09-20 08:32 2009-10-03 07:56
Reporter alex View Status public  
Assigned To alex
Priority normal Resolution fixed  
Status closed      
Summary 0000309: Strange things in modules list (only In-Portal module installed)
Description There are few strange things about how "Modules" section looks now:
1. there are two "Ready to Install" links instead of one;
2. Column "Build Date" shows either "01/01/1970 3:00 AM" (for installed modules) or "NO SUCH FIELD" (for not installed modules).
3. "Order" column doesn't provide any useful information since user can't change order of the installed modules.

Column "Build Date" usually is filled with current date (correct me if I'm mistaken) during time, when module is downloaded from site. In all other cases, like "direct svn checkout", "snapshot being used" this field is empty resulting 1 January of 1970 year to be shown. If this column is really needed, then it should at least "NULL" by default. Also build date is not available for modules, that are not yet installed and that creates the confusion, for ex. when module not installed date not shown, but after it's installed date suddenly appears and it looks-like that date appearance had something to do with module install fact.

If build date is really needed, then I propose to move this date to "module_info.xml" file to be able to show it even before module install. I propose to automatically update this date in "module_info.xml" file for each module during it's release process, not in script, that downloads it from site. This way there always be current release date (for released versions) and previous release date (for versions currently in development).

Same with Order column: if needed, then move module order to module_info.xml (I think something like this is already in "install_order.txt" file for each module).
Additional Information



Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker