Tagged: 777 dynamic_avia
I scanned my directories for file permissions and was wondering about this one:
I did not set them to 777 by myself and want to ask, why this has 777
would it be an issue to downgrade this one to 755?
Check who owns the file. 755 chmod means that owner can read/write/execute but those in owner’s group (and the rest) can only read and execute. The purpose of that folder is to house a css file holding all the dynamically generated css instead of having this large block of css being housed inline in the theme head section.
So wordpress needs to be able to write there, and if it owns it, then it can. Thus you should check who owns the file , and if the answer is WordPress , then set the 755 chmod. It’s located inside the uploads directory since usually (though not always) WordPress owns it, thus allowing the uploading of media files , for example.
Also please try setting 755 chmod inside the file itself in /framework/php/ function-set-avia-backend.php on line 621. (change 777 to 755). To test if all ok, simply add some fake css to Quick CSS (Replete > Theme Options > Styling) such as
and save Quick CSS. At that point the data should be added to a file housed in that folder. If it’s there then 755 is ok.
Please let us know.
The topic ‘wondering about 777 permissions in dynamic_avia’ is closed to new replies.