+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Update/Upgrade (/forum-44.html)
+--- Thread: Update from 1.0.0 to 1.0.2 (/thread-7620.html)
Pages: 1 2
RE: Update from 1.0.0 to 1.0.2 - sci2tech - 08-25-2009 03:54 AM
I did tell only use nightly if the only problem is from gui, not the config files.
@freinhard indeed that was the purpose. But ... squirrel mail security hole forced us to release based on v1.0.0 not on trunk, this way some problem were introduces. My advice was only for Cracknel who replaced reseller-functions.php instead just apply patch based on http://isp-control.net/ispcp/changeset/1924. Another way to fix this is to use version from v1.0.2 then modify according to r1924
RE: Update from 1.0.0 to 1.0.2 - Cracknel - 08-25-2009 04:04 AM
I've modified everything according to r1924, the error I've got was after I've done that.
The automated update script just screwed everything even more.
RE: Update from 1.0.0 to 1.0.2 - sci2tech - 08-25-2009 04:06 AM
Is a development machine or a productive one? I can help you if is productive, if you grant me access to it. This way we can not reach a happy end nearly.
RE: Update from 1.0.0 to 1.0.2 - Cracknel - 08-25-2009 04:24 AM
It's a productive one.
I own 80% of the websites so a did a complete restore of the VPS I'm using for the webserver. I hope my business partner hasn't change any of his websites during the last couple of days
I'll make a copy of the vps tomorrow and I'll test everything in a safe environment.
I can't understand why the developers released this version if it doesn't work!
RE: Update from 1.0.0 to 1.0.2 - BioALIEN - 08-25-2009 09:27 AM
@Cracknel, this was the first time the ispCP Team faced a situation where we had to act quickly to plug a possible security fix that could potentially damage production sites running ispCP v1.0.0. It was a race against time and some areas have been rushed.
We have learnt from our mistakes and a release policy is currently being finalised internally and will be adhered to in future releases to prevent a repeat of such occurrences. We apologise for any inconvenience this may have caused you, but at the same time, we are glad you are able to revert to a backup while you work with us to trace and fix any bugs in the current v1.0.2 release.
RE: Update from 1.0.0 to 1.0.2 - brianhenson - 08-25-2009 02:50 PM
I had the same issue and I tried to use the update listed above and I get this error
Quote:Fatal error: Uncaught exception 'Exception' with message 'Config variable 'COUNT_DEFAULT_EMAIL_ADDRESSES' is missing!' in /var/www/ispcp/gui/include/class.config.php:196 Stack trace: #0 /var/www/ispcp/gui/include/reseller-functions.php(514): Config::get('COUNT_DEFAULT_E...') #1 /var/www/ispcp/gui/include/reseller-functions.php(330): get_user_props('1') #2 /var/www/ispcp/gui/reseller/index.php(149): generate_reseller_user_props('2') #3 /var/www/ispcp/gui/reseller/index.php(316): generate_page_data(Object(pTemplate), '2', 'reseller') #4 {main} thrown in /var/www/ispcp/gui/include/class.config.php on line 196
This is a brand new install with the changeset installed.
RE: Update from 1.0.0 to 1.0.2 - joximu - 08-25-2009 04:36 PM
this const ist set here:
http://www.isp-control.net/ispcp/browser/trunk/gui/include/ispcp-lib.php?rev=#L171
/J
RE: Update from 1.0.0 to 1.0.2 - roadfox - 08-27-2009 01:07 AM
So what should we do? Stay on 1.0.0 with a security risk or upgrade to 1.0.2 and break everithing?
Then i get too:
Warning: Missing argument 4 for records_count(), called in /var/www/ispcp/gui/include/reseller-functions.php on line 529 and defined in /var/www/ispcp/gui/include/admin-functions.php on line 1005
Notice: Undefined variable: value in /var/www/ispcp/gui/include/admin-functions.php on line 1010
after an upgrade from 1.0.0 to 1.0.2
RE: Update from 1.0.0 to 1.0.2 - kurgans - 08-27-2009 01:38 AM
http://www.isp-control.net/forum/thread-7642-post-59843.html#pid59843