Not even surprised anymore. Updating CS Cart is the bane of my life.
4.3.7 to 4.3.8 getting this error when trying to download the update. [url=https://postimg.org/image/7oztnyo55/][/url]
Suggestions please before I......
Sorted one issue. Got another.
After clicking Install I get this error ErrorUpgrade is impossible due to file integrity check error. Please contact the technical support team.
Please find official answer from CS-Cart team here:
http://forum.cs-cart.com/topic/46503-upgarde-from-435-to-436/
2016-11-15 11:50:48: Starting installation of the "core" upgrade package
2016-11-15 11:50:48: Upgrading version 4.3.7 to 4.3.8
2016-11-15 11:50:48: Running as user "digitalsaveadmin"
2016-11-15 11:50:48: Executing pre-upgrade validators
2016-11-15 11:50:48: Found 0 validators at package
2016-11-15 11:50:48: Executing "collisions" validator
2016-11-15 11:50:48: Executing "permissions" validator
2016-11-15 11:50:49: Executing "restore" validator
2016-11-15 11:50:49: Backup filename is "upg_core_4.3.7-4.3.8_15Nov2016_115046"
2016-11-15 11:50:49: Preparing restore script
2016-11-15 11:50:49: Upgrades directory permissions: drwxr-xr-x digitalsaveadmin:digitalsaveadmin
2016-11-15 11:50:49: Source restore script permissions: -rw-r--r-- digitalsaveadmin:digitalsaveadmin
2016-11-15 11:50:49: Created directory for restore script at "/home/digitalsaveadmin/public_html/upgrades/core_4.3.7-4.3.8/"
2016-11-15 11:50:49: Directory permissions: drwxr-xr-x digitalsaveadmin:digitalsaveadmin
2016-11-15 11:50:49: Created restore script at "/home/digitalsaveadmin/public_html/upgrades/core_4.3.7-4.3.8/restore_2016-11-15_11-50-46.php"
2016-11-15 11:50:49: Restore script permissions: -rw-r--r-- digitalsaveadmin:digitalsaveadmin
2016-11-15 11:50:49: Correcting target restore script directory permissions...
2016-11-15 11:50:49: ----------
2016-11-15 11:50:49: Changing permissions of "/home/digitalsaveadmin/public_html/upgrades/core_4.3.7-4.3.8/" to 755
2016-11-15 11:50:49: Using chmod()... OK
2016-11-15 11:50:49: ----------
2016-11-15 11:50:49: Target restore script directory permissions: drwxr-xr-x digitalsaveadmin:digitalsaveadmin
2016-11-15 11:50:49: Correcting upgrades directory permissions...
2016-11-15 11:50:49: ----------
2016-11-15 11:50:49: Changing permissions of "/home/digitalsaveadmin/public_html/upgrades" to 755
2016-11-15 11:50:49: Using chmod()... OK
2016-11-15 11:50:49: ----------
2016-11-15 11:50:49: Upgrades directory permissions: drwxr-xr-x digitalsaveadmin:digitalsaveadmin
2016-11-15 11:50:49: Checking restore script availability via HTTP
2016-11-15 11:50:49: PHP Notice: Undefined index: transport in /home/digitalsaveadmin/public_html/app/Tygh/Http.php on line 188
2016-11-15 11:50:49: PHP Notice: Undefined index: error_number in /home/digitalsaveadmin/public_html/app/Tygh/Http.php on line 189
2016-11-15 11:50:49: PHP Notice: Undefined index: error_msg in /home/digitalsaveadmin/public_html/app/Tygh/Http.php on line 190
2016-11-15 11:50:49: HTTP error: ():
2016-11-15 11:50:49: Executing pre-upgrade script "/home/digitalsaveadmin/public_html/var/upgrade/packages/core/content/scripts/pre_script.php"
Wheres the timeout!??!?!?!?
Wheres the timeout!??!?!?!?
2016-11-15 11:50:49: Upgrades directory permissions: drwxr-xr-x digitalsaveadmin:digitalsaveadmin
2016-11-15 11:50:49: Checking restore script availability via HTTP
after this you got error.. Script checked if written script was accessible but it was not.. Maybe you got perrmission/ownership problem?
eCom Labs seems to think its this http://forum.cs-cart...rom-435-to-436/ which APPARENTLY is a server side timeout issue. Which it's most definitely not.
I fully believe these issues are overlooked to create more paid work. I've worked with many platforms before, Woocommerce, Magento, Open Cart - none of these other platforms had the same consistent upgrade issues. Not once in the history of this website has an update just worked. Not one single time.
BUMP!!!!
Just to confirm - this had nothing to do with server timeouts or my server. It was again, due to cs cart conflicts and an error with the last upgrade. A lot of time and money wasted.
I fully believe these issues are overlooked to create more paid work.
Not to be disrespectful, but then why are you the only one who seems to be experiencing this problem? Note that a timeout won't show in the logs (because the process go terminated). Instead, the log will just end at the last completed action.
I see your on 4.4.2 now, did you get sorted, if so what was the problem Sean
Not to be disrespectful, but then why are you the only one who seems to be experiencing this problem? Note that a timeout won't show in the logs (because the process go terminated). Instead, the log will just end at the last completed action.
Clearly not the one only one who experiences these problems as the forums will show. If this is a problem only I've experienced, why did you eCom Labs point me to a solution re timeouts?!?!!!?!? Anywhere, here's the evidence that the issue was CS CART UPGRADE RELATED and nothing to do with timeouts or my server. [url=https://postimg.org/image/3ulkkw5f5/][/url]
I see your on 4.4.2 now, did you get sorted, if so what was the problem Sean
The previous upgrade for whatever reason apparently hadn't completed properly. How you're supposed to know this when the upgrade process doesn't actually give you any errors (either works or it doesn't). So after a few weeks of changing every setting on our server/upgrading it I finally gave in and paid CS Cart to investigate. Within minutes they'd discovered this issue. I can't tell you how annoyed I was. But I do recommend the CS Cart Help Desk if anyone has any issues. Support is pretty cheap and you can rest assured its going to get fixed properly.
Clearly not the one only one who experiences these problems as the forums will show. If this is a problem only I've experienced, why did you eCom Labs point me to a solution re timeouts?!?!!!?!? Anywhere, here's the evidence that the issue was CS CART UPGRADE RELATED and nothing to do with timeouts or my server.
The previous upgrade for whatever reason apparently hadn't completed properly. How you're supposed to know this when the upgrade process doesn't actually give you any errors (either works or it doesn't). So after a few weeks of changing every setting on our server/upgrading it I finally gave in and paid CS Cart to investigate. Within minutes they'd discovered this issue. I can't tell you how annoyed I was. But I do recommend the CS Cart Help Desk if anyone has any issues. Support is pretty cheap and you can rest assured its going to get fixed properly.
Yeah, I have relied on CS support many times and they do tend to crack on and do a decent job in my experience.
I had a similar issue going from 2.25 to 3 and same thing , rolled back started again