Thread

I just upgraded to EE2.3.1 on a Wamp server (PHP 5.2.8 and MySql 5.1.3) to test my site before upgrading the server.  I ran the Server Compatibility Wizard and it says all is well.  My image resizing protocol is set to GD2.

I get the above error in both File Sync and in File Upload.  The directory cannot be write protected, because the _thumb subdirectory is being created, and in the case of File Sync at most 2 files get synced, but I get the error on all the other files (.jpg, .gif, and .png) in the directory.

I saw in a previous thread that it was recommended that GD2 be reloaded. If that is the case, I will need instructions on how to do that! thanks!

Have you confirmed that the image directories are in fact writable (CHMOD 777) with something like FTP? You might also check the ownership. You mentioned reloading GD, can I assume you are on a dedicated server or VPS then?

The server is WAMP on my PC, so I did check that the directories were writable using Windows Explorer.  Since it is on my PC, I assume you could call it dedicated, but I would not have a clue on how to reload GD, if needed (hopefully, that is not the problem since the Compatibility Wizard said that I was ok).

Hi deecee,

Since you are on a localhost with WAMP, is there anyway you can choose a different version of PHP and see if the problem persists? Was everything working normally before the update? Did you experience any errors during the update process? Unfortunately, for support or ideas on how to make changes to WAMP, you’ll have to seek help from the distributors of WAMP.

Thanks!

Yes, everything was fine with EE1.6.9 and the update did not give any errors.  I will upgrade PHP from 5.2.8 to 5.3.8 and see if that helps.  If anyone has any other suggestions, I would appreciate them!

I updated WAMP to the latest version of PHP 5.3.8 (from 5.2.8) and I have the same error.  The directories cannot be write protected because it creates the _thumb subdirectory and puts a couple of thumb files in it.  I get the error on 9 out of 11 files.  In each directory, at least one thumb file is created.

The other weird thing is that an index.html file appears in the thumb directory that says ‘Directory access is forbidden.’  Obviously it was not, or the index.html file would not be there.

I plan to update the webserver on Sunday with the assumption that this error (the only one I have gotten) is specific to PC directories!  Please let me know if you think that is a bad idea!!!!

That error is a bit more inclusive than the response might lead you to believe- and can occur for reasons other than permissions.

Oh- and the index.html page, that’s normal.  It’s created on the fly so nobody going directly to the folder could view the directory contents.

Which means- yes, EE is clearly able to write to the folder.  You do have some files that upload and create thumbs- correct?  Is it the same files each time?  If you upload one of them via file upload in the control panel (or in the file manager) does it work?  How much memory do you have?  Might be worth upping that, as it could make a difference.  And for the files that do get synced (if it’s consistent)- anything seem unique about them compared to the ones that are triggering an error?

And all that said- I wouldn’t be surprised if it was unique to your local windows box.  Did you give it a try on Sunday?

Yes, out of 9 files to be synced, only two thumbs are created.  I did try to upload in the file manager and I got the same error.  I have 4gb of memory on the PC, so not a lot.

I do think it is unique to my PC, and I was not getting a good feeling about doing a good test before I updated the server, so over the weekend I created test directories and database on the server and I got that upgraded to EE2.3.1, so that is now my test environment.  Most everything is working fine there, so I do not plan to work on the PC any further. If I can help resolve the issue for others, I would be glad to send any info or test, but for me you can close the ticket.

Thanks!

😉  Should have been clear- I meant PHP memory.  But that said- yes, sounds like something in the test environment.  Which we should be able to get working but likely so unique that if you can use the server it’s a much better option.

Run into anything else deecee, just give us a yell.