alan Posted March 31, 2014 Share Posted March 31, 2014 More fallout from 'rights' problems - Modules Manager is not able to update the first two Modules I tried it with. Had various "cannot write" errors which I fixed with judicious use of 777 and all errors now gone. But still modules report as not being latest and updating them (from Modules Manager at least) just does nothing. FTPing: for me the *only* fly in the PW ointment. I must attract flies :/ Link to comment Share on other sites More sharing options...
heldercervantes Posted April 28, 2016 Share Posted April 28, 2016 I'm going through this problem on my end as well. The Dolce Vita website uses multisite to manage multiple malls under the same PW installation. Now I separated 3 malls to a second installation, basically just downloaded the whole site into my computer, cleaned up, and re-uploaded to a new hosting. Now editing a page I get this error in every image field. Setting permissions to 777 seems to work, but leaving it like that scares me. Seems apache is unable to write over files/folders created by FTP upload. Any way to get around that without nuking the whole thing? Link to comment Share on other sites More sharing options...
LostKobrakai Posted April 28, 2016 Share Posted April 28, 2016 Setting the correct user/group for your files should solve this issue. It sounds like uploading via ftp didn't do that. 1 Link to comment Share on other sites More sharing options...
DaveP Posted April 28, 2016 Share Posted April 28, 2016 @heldercervantes Depends very much on the server setup. Sometimes files/folders are owned by the Apache process, but when you upload via FTP they are owned by your FTP account. One way to sometimes get around this is to upload files via cPanel or whatever rather than FTP. Perhaps your hosting company can chown (change owner) all the site files for you. 1 Link to comment Share on other sites More sharing options...
heldercervantes Posted April 28, 2016 Share Posted April 28, 2016 Thanks for pointing me in the right direction guys. I suck at SSL, never even touched it. Now in my support ticket it looks like I actually know what I'm talking about Link to comment Share on other sites More sharing options...
heldercervantes Posted April 29, 2016 Share Posted April 29, 2016 My hosting provider says they've ran the chown command and that didn't fix it, so... McGyver time! I just duplicated the whole "site" folder with php. I took this script and slapped it in a php file, then temporarily changed public_html permissions to 777 and ran the script copying "site" to "siteB". Every file and folder in siteB got the correct owner/group. Turned permissions on the root folder back to 750 and renamed "siteB" to "site". Done. 1 Link to comment Share on other sites More sharing options...
Troost Posted April 30, 2019 Share Posted April 30, 2019 I'm getting the same problem, the Chmodd 777 on the Site folder works over here... I'm on ProcessWire 3.0.123 © 2019 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now