Bugtracker of MarioValdez.net http://www.mariovaldez.net/webapps/bugtracker2/ Bugtracker of MarioValdez.netCMS module for Phprojekt: Recently closed tasks 2007-10-13T10:15:06Z FS#49: Java-based multiple-file uploader. http://www.mariovaldez.net/webapps/bugtracker2/task/49 2007-10-13T10:15:06Z Mario A. Valdez-Ramirez This has been dropped in favor of a WebDAV interface. FS#160: Double login. http://www.mariovaldez.net/webapps/bugtracker2/task/160 2005-05-10T02:28:00Z Mario A. Valdez-Ramirez We have two reports of users who have to login twice (one for Phprojekt and another for the CMS). One reported the problem since the security patch of Phprojekt (released by December 2004). The other report is when using the Compact Theme (by Mark Coudriet), but it is unknown the version or patch level of Phprojekt. This bug has not been verified.
This bug has not been verified.]]>
FS#60: Wrong internal version and copyright legends in 0.6.0 release... http://www.mariovaldez.net/webapps/bugtracker2/task/60 2004-07-14T05:26:58Z Mario A. Valdez-Ramirez After 8 days online, I discovered a couple of bugs in 0.6.0 release. The first is a missing copyright legend in the readme.txt and license.txt files about Christian Hartnick (cis@hartnick.de). The second is that the CMS distributed as 0.6.0 thinks it is really 0.6.0b12. That affects (as far as I have checked) the remote checking of new versions availability. Other critical functions of the internal version are configuration consistency (which is not affected in this case) and bug reporting. As of today, only 210 downloads has been done, so I decided to replace the affected packages on the site with fixed versions. Due to a bug in the checkupdates.php script files (which answer the user if there is or not a new version available) beta users of 0.6.0bxx were not being recommended to upgrade. Well, with this change (and the fixing of the checkupdates.php script) those users will be advised to upgrade, but also those 210 users will be advised to upgrade to their current version. Empirical risk analysis suggest that this is the less-colateral damage approach (being the other to do a new release only with two minor changes, although copyright issues are not really minor). Fortunately, most users don't use the "Check for updates" features, so most won't be disturbed. After uploading the new versions, I left the old MD5 checksums with a warning legend, so prior users won't get alarmed by mismatching checksums.
The first is a missing copyright legend in the readme.txt and license.txt files about Christian Hartnick (cis@hartnick.de).

The second is that the CMS distributed as 0.6.0 thinks it is really 0.6.0b12. That affects (as far as I have checked) the remote checking of new versions availability. Other critical functions of the internal version are configuration consistency (which is not affected in this case) and bug reporting.

As of today, only 210 downloads has been done, so I decided to replace the affected packages on the site with fixed versions.

Due to a bug in the checkupdates.php script files (which answer the user if there is or not a new version available) beta users of 0.6.0bxx were not being recommended to upgrade. Well, with this change (and the fixing of the checkupdates.php script) those users will be advised to upgrade, but also those 210 users will be advised to upgrade to their current version.

Empirical risk analysis suggest that this is the less-colateral damage approach (being the other to do a new release only with two minor changes, although copyright issues are not really minor).

Fortunately, most users don't use the "Check for updates" features, so most won't be disturbed.

After uploading the new versions, I left the old MD5 checksums with a warning legend, so prior users won't get alarmed by mismatching checksums.]]>
FS#50: Java-based multiple-file uploader. http://www.mariovaldez.net/webapps/bugtracker2/task/50 2004-07-11T13:16:37Z Mario A. Valdez-Ramirez This has been discarded in favor of a WebDAV interface. FS#48: Add chief user to permission matrix. http://www.mariovaldez.net/webapps/bugtracker2/task/48 2004-07-11T13:09:53Z Mario A. Valdez-Ramirez Currently, the chief user is not an available role for the permissions-restrictions matrix. Let's add it. FS#30: Check compatibility with Phprojekt 4.2 http://www.mariovaldez.net/webapps/bugtracker2/task/30 2004-07-07T17:44:32Z Mario A. Valdez-Ramirez TEst compatibility with Phprojekt 4.2. FS#6: Add skin by Mark/Psymon. http://www.mariovaldez.net/webapps/bugtracker2/task/6 2004-07-06T19:20:21Z Mario A. Valdez-Ramirez Add theme/skin by Mark/Psymon. Finish integration of contributed skin. FS#28: Compact and Mojo themes licensing vs copyright note in files http://www.mariovaldez.net/webapps/bugtracker2/task/28 2004-07-06T08:45:20Z Mario A. Valdez-Ramirez The compact and mojo themes by Mark Coudriet are released under a double-license (GPL and LGPL) but some legends in the source code keep the copyright note of the CMS4P module. The CMS4P module is released only as GPL (because link directly to Phprojekt lib code which is GPL only) and cannot be changed to LGPL. The easier solution is to change the copyright notes so the holder is Mark Coudriet, who can release them under any license he wants. To avoid future copyright claims (not from me, of course, but who knows if I die what will happen) Mark should state "based on code by MAVR... etc". A more complete solution would be to release those files to Mark Coudriet under LGPL so he can tag them with any legend (GPL or LPGL). The CMS4P module is released only as GPL (because link directly to Phprojekt lib code which is GPL only) and cannot be changed to LGPL.
The easier solution is to change the copyright notes so the holder is Mark Coudriet, who can release them under any license he wants.
To avoid future copyright claims (not from me, of course, but who knows if I die what will happen) Mark should state "based on code by MAVR... etc".
A more complete solution would be to release those files to Mark Coudriet under LGPL so he can tag them with any legend (GPL or LPGL).]]>