OK, so this confirms what I suspected.
I can see the comment /* TEST fonts and custom CSS file */ inside the jumbled CSS that is at the end of the @media rule following the /* Weaver Xtreme Plus CSS Styles – Version 7.0.3 */ section.
If I move your custom CSS following /* TEST fonts and custom CSS file */ before the /* Weaver Xtreme Plus CSS Styles – Version 7.0.3 */ section it gets executed .
This means that the section /* Weaver Xtreme Plus CSS Styles – Version 7.0.3 */ inside “weaverx-style-sheet-inline-css ” generated by weaver is corrupted!
The custom CSS that you enter in the global custom CSS rule box being added after that, it never gets executed.
So the question is why is the /* Weaver Xtreme Plus CSS Styles – Version 7.0.3 */ section of the file corrupted (@weaver your help would be appreciated)
If you say your site was hacked, you need to consider that the corruption could come from the hack, and therefore that it may have been hacked way before 2 days ago.
If you can’t restore a much older version because of recent changes, you could try a cleanup with the procedure below
- Save all your weaver settings AND download a copy on your computer for good measure.
- Switch to a default WordPress theme
- Delete Weaver Xtreme and ALL weaver plugins.
- Redo the last WordPress update.
- Redownload a clean new Xtreme theme from Wordpess.org and activate
- redownload the Weaver plugins and activate
- Make sure the /* TEST fonts and custom CSS file */ is still at the top of the Custom CSS rule box
Post back