-
AuthorPosts
-
January 29, 2014 at 3:53 pm #216402
Hello there,
On checking the HTML code of the home page of a test site I found this huge block of CSS.
Is it my mistake?
How can I remove it and retreive the code from the .css file?
Thank you.<edited out by Devin – enfold.css copy>
- This topic was modified 10 years, 10 months ago by Devin.
January 30, 2014 at 12:04 am #216681Hey Cum_Vincere!
Can we see your site live? That css should by default actually already be saved to a custom created file in your uploads folder.
Regards,
DevinJanuary 30, 2014 at 11:08 am #216898This reply has been marked as private.January 30, 2014 at 5:57 pm #217062Looks like the file to write the style options to hasn’t been created. Go to your WordPress uploads folder over FTP or through your server panel and make sure that the chmod permissions allow WordPress to create a new folder and write to it.
Then go to the themes styling tab and make a change, then re-save the options.
January 30, 2014 at 6:38 pm #217079OK Devin, thank you for your suggestion.
I changed permissions of either /wp-content/ and /wp-content/uploads/ even to 777, went to the styling tab, changed a setting and saved, but nothing changed.
January 31, 2014 at 3:10 pm #217449Hello, any other suggestion?
Thank you.
February 1, 2014 at 11:16 am #217759Hi!
Please go to /wp-content/uploads/ and create a new folder called “dynamic_avia” (without the quotes). Then set the folder permission to 777 and go to Enfold > Theme Options and click the “Save” button to regenerate the dynamic stylesheet.
Best regards,
PeterFebruary 4, 2014 at 1:27 pm #219326Hello Peter,
No, unfortunately nothing changed after following your procedure above. No file is created in the new folder “dynamic_avia” and the CSS block remains in the HTML.
Actually, now it comes to my mind what follows. If I remember correctly your Enfold theme does not come with a child-theme folder.
I created a child theme folder and all the rest worked fine.
Can this be the reason of this malfunction?Thanks.
February 4, 2014 at 2:49 pm #219378Hey!
Have you tried selecting a different predefined color scheme on Enfold > Styling options? Change the color scheme then change it back.
Cheers!
IsmaelFebruary 4, 2014 at 3:20 pm #219397Hello Ismael,
I tried changing the colour scheme two times, with no result.
I also tried de-activating the /enfold-child/ theme and activating the basic /enfold/ configuration but nothing changed.
The CSS remains in the HTML.
February 4, 2014 at 4:56 pm #219474February 7, 2014 at 3:27 pm #220875Hello, any news about this question?
Thank you.
February 7, 2014 at 5:36 pm #220957Hi!
mind posting wordpress access data and ftp data in a post that is set as private reply so I can take a look at the backend myself?Best regards,
KriesiFebruary 20, 2014 at 4:26 pm #226853Hello Kriesi,
Thank you for your proposal. Unfortunately our customer does not allow us to give access to his site to other people.
What I can tell you is that the huge block of CSS is the output of / enfold / css / dynamic-css.php
I tried to replace the /enfold/ files with the latest version (today, version 2.5) and use it without the child theme I had created: the block remains.
I also de-activated all plugins, but nothing changed.
What else could I try?
Thank you.
February 21, 2014 at 12:45 am #227142Hi!
This css output is basically the fallback solution if the theme is not allowed to read/write the folder and file that Dude mentioned before. Since the backend needs to save the color and styling rules somewhere it tries to create the file: wp-content/uploads/dynamic_avia/enfold.css
If this file is not located on your server then the theme is probably not allowed to read or write. if it is available make sure to set the file permission of both, folder and css file to 755 or 777
Thats pretty much the only advice I can offer without having access to your server…
Cheers!
KriesiFebruary 21, 2014 at 9:15 am #227309Hello Kriesi,
Thanks for your explaination and suggestions.
I checked the state of the folders and found:1) wp-content/uploads/dynamic_avia/ already exists on the server
2) Permissions for all folders was already set to 777 for the three folders
3) in /dynamic_avia/ I found no enfold.css file
4) I created an enfold.css file and gave it 777 access permissions
5) I went to the theme Options section, changed a styling setting and saved
6) I opened the newly created enfold.css file but nothing was written in there.I believe we are just missing one single step somewhere…
February 21, 2014 at 10:58 am #227360Hi!
Please remove the enfold.css file that you created then try to change the predefined color scheme again. The enfold.css file should be automatically created. Make sure that the dynamic_avia/ folder is writable.
Regards,
IsmaelFebruary 21, 2014 at 11:46 am #227382Hello Ismael,
Thank you for your suggestion.
Unfortunately the enfold.css is not created.
Permission in /wp-content/uploads/dynamic_avia/ are all set to 777.
I also tried deactivating the theme and re-activating it, with no result.February 21, 2014 at 11:53 am #227385Another test I made was giving 777 permissions to /httpdocs/ (never tried before!) but nothing changed.
February 21, 2014 at 12:03 pm #227389Hold on… maybe I got it… just one second.
February 21, 2014 at 12:21 pm #227399OK, I fixed it.
The problem was: in WP dashboard / Settings / Media -> “Save uploads in this folder” we had set, long time ago, a /photo/ folder, in the server root.
Therefore, the /dynamic_avia/ folder was supposed to be created here.
Once I created it all worked.Meanwhile I had made a copy of this WP test installation, just to experiment on it, and that installation contained a child theme.
The child theme did not work properly.
I then understood that the /dynamic_avia/zzzzz.css file for the child theme needed to be named mysite_child_theme.css (where mysite is the site name as specified in WP dashboard / Settings / General -> Site name.Well, I wish to thank the Kriesi staff for the kind support and hope this experience can be useful for other people in this forum.
February 21, 2014 at 12:30 pm #227407 -
AuthorPosts
- The topic ‘A bulk CSS surprise’ is closed to new replies.