2.24 upgrade to PHP 5.3 OK?
I have PHP 5.2 installed now with no problems is PHP 5.3 a smooth upgrade?
I looked over the recent posts and most people seem fine but I wanted to check again…
Thank you!
No problems here 
Flow,
Thank you - I upgraded and had no problems
I found two challenges with my PHP 5.3 upgrade:
CC as a payment option, it is just staying on Paypal.
When registering for a new account, the Captcha image does not load so I am unable to complete the registration process.
So I reverted back to 5.2 and the problems went away - I wonder why.
I also recently went to fast CGI but that does not seem to be the probem.
@Traveler,
Your apache compile didn't include the gd_library, can't explain payment option issues.
J.
Jesse,
Thank you.
It did include GD. I checked that. It might have been a font problem for the captcha. For the other problem with the credit card I have no idea. CS cart was returning a 302 error.
It's more than likely due to the file cache/compile.
While moving PHP versions typically doesn't make much difference with CS, including new modules like IonCube etc can cause difficulties. In future it's probably best to resolve the issue prior to downgrading (I know you've got an income there) but regardless of that there might be issues affecting your store that only customers are aware of.
J.
I wonder if PHP version 5.3.13 has some type of imcompatability with CS cart?
“it's more than likely due to the file cache/compile.”
No that has been checked - but thanks again for the thoughts.
Are you using PHP version 5.3.13?
[quote name='Traveler' timestamp='1340105734' post='138986']
Are you using PHP version 5.3.13?
[/quote]
I am using 5.3.10, haven't moved to 5.3.13 as I've been developing a new site and haven't the time.
The cache/compile directory is generated by PHP, obviously between versions there will be slight changes for various reasons, different GD library on compile (version changes etc). Much like cookie cache's when people upgrade their carts at times, the information is technically valid but not being parsed correctly from cache.
This is the reason that you need to clear all cache's after most apache recompiles. (Also one reason why webhosts rarely upgrade their PHP versions)
Cache clearing and simple things were not the issue.
It turned out to be a minor bug in some versions of PHP that when matched with another minor design flaw in CS cart caused the problem.
Now we are OK (I hope…) and using fast cgi with PHP version 5.3.13 and we are loading quickly.
Next up we are thinking about a CDN service to load quickly worldwide.
Thank you for your suggestions.
[quote name='Traveler' timestamp='1340236968' post='139113']
It turned out to be a minor bug in some versions of PHP that when matched with another minor design flaw in CS cart caused the problem.
Now we are OK (I hope…) and using fast cgi with PHP version 5.3.13 and we are loading quickly.
[/quote]
I'm having payment issues after upgrading to PHP 5.3.13. How did you fix it? I'm running CSC 2.2.3.
[quote name='grayloon' timestamp='1340395203' post='139278']
I'm having payment issues after upgrading to PHP 5.3.13. How did you fix it? I'm running CSC 2.2.3.
[/quote]
He more than likely recompiled back to 5.3.10
[quote name='grayloon' timestamp='1340395203' post='139278']
I'm having payment issues after upgrading to PHP 5.3.13. How did you fix it? I'm running CSC 2.2.3.
[/quote]
Grayloon,
This solution fixed our problems and we are using PHP 5.3.13 very smoothly now - so far…
With fcgid and APC enabled:
If you're getting an error on AJAX requests it's due to a bug in some versions of PHP.
Please see [url=“PHP :: Bug #58739 :: Fatal Error: Class xxx not found”]PHP :: Bug #58739 :: Fatal Error: Class xxx not found
This bug is easily overcome by calling session_write_close();
in your application.
CS Cart does do this but in AJAX calls (according to ./core/class.ajax.php) it happens in the destructor.
I haven't stepped through all the code but it seems that there are cases where the Ajax class doesn't get a chance to get destroyed properly (perhaps an exit(); call?).
We were able to fix this problem by adding this code:
register_shutdown_function(“session_write_close”);
to the __construct() function in the Ajax class in ./core/class.ajax.php
This way if the destructor never get's called session_write_close(); will still be called.
We're running CS Cart [color=#000000][font=Tahoma, Arial, Verdana,]2.2.4 so I don't know if this has been fixed in 3.x[/font][/color]
we are using PHP 5.3.10, but we are using MySQL 5.0.17 and we want upgrade mysql 5.5. Has anyone tried it?
[quote name='peku' timestamp='1341235137' post='139752']
we are using PHP 5.3.10, but we are using MySQL 5.0.17 and we want upgrade mysql 5.5. Has anyone tried it?
[/quote]
We are using 5.0.95-community what are the advantages of upgrading?
[quote name='Traveler' timestamp='1341394512' post='139890']
We are using 5.0.95-community what are the advantages of upgrading?
[/quote]
Performance improvements
Sounds good -
When upgrade to 3 I will upgrade our SQL to whatever is safe.
So now my question is the same as yours…