|
From: Bob S. <bo...@pr...> - 2001-05-08 18:20:04
|
If anyone else has these problems, let me know. -----Original Message----- From: Camden Spiller [mailto:ca...@ar...] Sent: Tuesday, May 08, 2001 1:18 PM To: Bob Schader Subject: Re: [phpGroupWare-developers] Announcing: Phpgwtimtrack test release Hi Bob, I actually havn't had much opportunity to really test it out yet, but I was talking to someone who installed phpgw 0.9.10 from scratch and then installed the .9.10 timetrack test1 release and here's what he found (in his words).... ------------------ snip ---------------- 1. If you are a member of multiple groups, i.e. the "Admin" group and the "Default" group, the setup pages won't display. Once I removed myself from the "Default" group I could see the setup page. Bob's Reply: I have always been a member of both these groups, and never had a problem accessing these pages. Of course, the last few weeks of development was geared towards making sure the upgrade process worked properly, and the main installation was never tested on the final release version of phpgroupware 0.9.10, so it could be something was introduced either by my upgrade coding or changes in the final version of phpgroupware 0.9.10? 2. On my new install of phpgroupware and timetracker the setup page only displayed a table with the phrase "Step 1 - TimeTrack Database Setup Options" in it. The Install and Cancel buttons were not available. It appears that this is because it thought my version of timetrack (as found in the phpgw_applications table) was 0.0.0. Because there was no 'if' statement that matched this in the setup/index.php script, it gave me no options to install. I managed to fix this my manually setting $previous_ttver to "none" after line 176 in the setup/index.php script. Obviously this isn't a permanent solution, but it worked well as a temporary work around. Bob's Reply: This could be an acceptable fix as far as I can tell, but you must have had a really old release of timetrack to have the version set to 0.0.0. Another possible solution would be to manually update the version string before upgrading (via any MySQL client). ------------------ end snip ---------------- I havn't looked in to his statements yet, but I wanted to pass them along to you in case you were looking for feedback. Thanks again, Camden > > P.S. Any feedback on installation, upgrading, use, etc? > |