-
Posts
-
What are the design thoughts on placing a vital enfold CSS outside the actual theme folder? In case of enfold in the uploads directory…Is there a way to place it inside the theme folder?
The reason I’m asking is because I want to fully protect my uploads folder with an htaccess. Of course one can say to allow a specific subdirectory addAllow from env=allow.
But here is the caveat: I’m using the User Access Manager plugin which always overwrites the htaccess file (in case of a setting change). In other words it’s too risky to have a modified htaccess file knowing it can be overridden (and loose the protection). The simplest way to solve this problem that comes to my mind is to “outsource” (or lets rather say “insource” :-) the enfold.css back into the theme folder. (Well, I could also modify the User Access Manager plugin code to fit my needs but then I would have trouble updating it…)Hi epresley!
You wouldn’t be able to upload images if you disabled writing to the uploads folder either. Its the uploads folder so it stands to reason it over any other should be writable.
Best regards,
DevinDevin,
Thank you for your reply!
I don’t disable writing to the uploads folder (haven’t touchedchmodat all). All I do is set an .htaccess which grants an user read access to the uploads folder. Nobody except me needs to upload data. Maybe my understanding of htaccess is wrong…
My question still stands: why is enfold.css outside the theme folder and can I “insource” it (how)?
- The topic ‘Why is enfold.css outside the theme folder?’ is closed to new replies.