Question

Can't write Style-custome.css

I upgraded to WordPress 3.8.

Looking around I opened “Apearance --> Customize” and then hit “Close” without making any changes.

Now I get the following… (Website is down)

{“success”:“-1”,“alert”:“Cannot write style-custom.css file, you may try setting the style-custom.css file permission to 755 or 777 to solved this. ( If file does not exists, you have to create it yourself )”}

I didn’t want to make any changes.

I can’t find the “Style-custom.css” file to change ownership.

Has anyone else had this problem?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

<b>“I created the custom-style.css in the var/www/wp-content/css directory…”</b> <br> <br>Why did you do that? A standard WordPress install does not have a <code>./wp-content/css/</code> directory.

I found that I have four themes listed in /var/www/wp-content/themes <br> <br>1) bluediamond-v 1_05 (This is the only one that has the “style-custom.css” file <br>2) twentyfourteen <br>3) twentythirteen <br>4) twentytwelve <br> <br>I still can’t access wp-admin or the website - I get the same alert as in my first post

I created the custom-style.css in the var/www/wp-content/css directory and gave it 777. <br> <br>I then rebooted the server. <br> <br>Website is still down. When I try to access; nameofsite.com or nameofsite.com/wp-admin I still get the same error as above. <br>