Jump to content

Recommended Posts

Posted

Where are you developing? On a local host or on a(n) remote/online host(ing) (which one)?

Can we have more details about the platform (Windows, Mac OS X, Linux...), the LAMP setup (WAMP(SERVER), XAMPP, EasyPHP...), etc.?

Posted (edited)

The answer is actually in the error message. Your assets directory seems to be locked down for writing. Does that happen only with Modules Manager or throughout your site? If the former, you might want to ask your question in Modules Manager support forum. There was a similar issue a while back. If the latter, have a read at this as well: https://processwire.com/docs/security/file-permissions/

Edited by kongondo
  • Like 1
Posted

Ok, I changed permissions for assets directory to max (777). The first error message went away (so I guess the directory is PHP writeable now?), but I'm not sure why. I switched it back to 755 and error message is still gone.

The second error message remains. I tried deleting the Modules Manager cache file, but still the same error.

Posted

Yes, it does. It wasn't there when I first looked. Refreshed and it appeared, and Modules Manager started working... :huh:

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...