Zend, Picnik, and 5.4.0 Updating Issues
Permalink
I have a number of issues that I'm starting to feel are all somehow related. I've been wondering if it's permissions-related, but I haven't been able to find anything obliquely unnatural or out of line with my install. I've contacted our hosting company about them (Simplehost), but they claim they don't have any permissions-related restrictions that might be causing these errors.
Here are the issues:
1) When I try to update 5.4.0 to 5.4.0.5 from within the dashboard, I get an error:
The following errors occurred when attempting to process your request:
Concrete was not able to save the package after download.
I am using the Super Administrator account. Is this another permissions-related
issue where the CMS is able to download the file, but then not save it to the file
structure? My first guess was that this was permissions-related, but I haven't changed anything on the file structure's natural permissions. The /updates/ directory is CHMOD'd to 777. Is there something else I'm missing?
2) Since that didn't work, I tried updating manually. Whenever I try to download the file structure to back it up, I get an
error:
Could not download zend_cache---0b45fe6ec846d591d936cd2df6f80705â€. Server said:
Can't open zend_cache---0b45fe6ec846d591d936cd2df6f80705: No such file or directory
Error -160: could not start data transfer
Simplehost says they have Zend Cache enabled.
Why do these files "not exist"? The permissions on them are 600.
Before doing all of this I cleared the site's cache, but I still get this error. Are these files even necessary to download for a backup?
3) I get some weird errors with Picnik—as if it can't write the file to our server after it's done being edited. On trying to save an edited photo from Picnik to the CMS, I get this error:
8231059063_qxM8N.jpg: Invalid file.
(Or something along this line; the file name changes, but the error still states "Invalid file"). This also strikes me as a permissions issue; i.e. not being able to
save files from a third party connection. But again, I haven't changed any of the natural permissions that come with 5.4.0, and Simplehost didn't say they have strange permissions-related restrictions on this stuff.
Any thoughts or pointers?
Here are the issues:
1) When I try to update 5.4.0 to 5.4.0.5 from within the dashboard, I get an error:
The following errors occurred when attempting to process your request:
Concrete was not able to save the package after download.
I am using the Super Administrator account. Is this another permissions-related
issue where the CMS is able to download the file, but then not save it to the file
structure? My first guess was that this was permissions-related, but I haven't changed anything on the file structure's natural permissions. The /updates/ directory is CHMOD'd to 777. Is there something else I'm missing?
2) Since that didn't work, I tried updating manually. Whenever I try to download the file structure to back it up, I get an
error:
Could not download zend_cache---0b45fe6ec846d591d936cd2df6f80705â€. Server said:
Can't open zend_cache---0b45fe6ec846d591d936cd2df6f80705: No such file or directory
Error -160: could not start data transfer
Simplehost says they have Zend Cache enabled.
Why do these files "not exist"? The permissions on them are 600.
Before doing all of this I cleared the site's cache, but I still get this error. Are these files even necessary to download for a backup?
3) I get some weird errors with Picnik—as if it can't write the file to our server after it's done being edited. On trying to save an edited photo from Picnik to the CMS, I get this error:
8231059063_qxM8N.jpg: Invalid file.
(Or something along this line; the file name changes, but the error still states "Invalid file"). This also strikes me as a permissions issue; i.e. not being able to
save files from a third party connection. But again, I haven't changed any of the natural permissions that come with 5.4.0, and Simplehost didn't say they have strange permissions-related restrictions on this stuff.
Any thoughts or pointers?
You may need to chmod 777 the /packages directory. Also check that your /files directory is 777. Then clear your site cache via the Dashboard/Debug tab. That may clear up your Zend Cache issues.
Unfortunately it doesn't. I still get the same error.
Anyone know what these files actually do? I'm a novice at PHP at best, and I don't know what Zend does for C5. It seems like they're just cache files, and in a way I would be tempted to move along with a manual update without keeping them. But my better side says that I shouldn't be working without a *full* backup (this is for a production site).
Are the zend_cache files necessary for keeping your site backed up? What do they do?
These files are located here: /files/cache/
It looks like I can CHMOD them manually to force them to be downloadable, so that may solve things. I'm just interested in knowing more about what they do so I'm not messing around with things I don't understand.
I will try and see if updating works from the dashboard now though. /files/ was already CHMOD 777, I went and changed /packages/ to 777 (was 755). I will see if this cures any of the other errors.
EDIT: The changes appear not to have affected the other errors.
EDIT #2: Successfully manually updated to 5.4.0.5, after skipping the cache files. Thanks for the help nteaviation.
Unfortunately I still get the Picnik Invalid File problem, so no luck there with 5.4.0.5…
Anyone know what these files actually do? I'm a novice at PHP at best, and I don't know what Zend does for C5. It seems like they're just cache files, and in a way I would be tempted to move along with a manual update without keeping them. But my better side says that I shouldn't be working without a *full* backup (this is for a production site).
Are the zend_cache files necessary for keeping your site backed up? What do they do?
These files are located here: /files/cache/
It looks like I can CHMOD them manually to force them to be downloadable, so that may solve things. I'm just interested in knowing more about what they do so I'm not messing around with things I don't understand.
I will try and see if updating works from the dashboard now though. /files/ was already CHMOD 777, I went and changed /packages/ to 777 (was 755). I will see if this cures any of the other errors.
EDIT: The changes appear not to have affected the other errors.
EDIT #2: Successfully manually updated to 5.4.0.5, after skipping the cache files. Thanks for the help nteaviation.
Unfortunately I still get the Picnik Invalid File problem, so no luck there with 5.4.0.5…
Make sure when you chmod 777 a directory, you do so "recursivley". The cache files can be deleted without harm. They will just be rebuilt when required.
