Improvement for removing debug CSS from front end.

Viewing 6 posts - 1 through 6 (of 6 total)

Author

Posts
December 4, 2013 at 1:13 pm #196112

activemind
Participant

Hi,

I followed instruction here given by nuforms https://kriesi.at/support/topic/how-to-disable-dynamic-css-style-on-frontback-end/

Instead of following step n. 2, I suggest to add in functions.php, after line 280:
wp_register_style( ‘avia-debug’, $template_url.”/css/dstyles.css”, array(), ‘1’, ‘screen’ );

Then after line 295:
wp_enqueue_style( ‘avia-debug’);

If it could be implemented as standard feature in the theme it could be really good.

December 4, 2013 at 5:20 pm #196242

Yigit
Keymaster

Hi activemind!

Feel free to post your request here https://kriesi.at/support/topic/enfold-feature-requests/

Cheers!
Yigit

December 4, 2013 at 9:35 pm #196358

Devin
Inactive Moderator

Hey!

If you mean removing the debug information in the source you can add the function shown here: http://kriesi.at/documentation/enfold/remove-avia-framework-debug-information/

Best regards,
Devin

December 4, 2013 at 10:16 pm #196367

activemind
Participant

Hi Devin, I mean removing all the CSS, not only commented headline.

December 5, 2013 at 4:37 am #196479

Devin
Inactive Moderator

There would be no need to do that since the css doesn’t get loaded into the source it gets loaded into the custom file in your uploads folder.

December 5, 2013 at 10:33 am #196577

activemind
Participant

Thanks for you answer, I’ll investigate more and, if needed, I’ll post again.
Author

Posts

Viewing 6 posts - 1 through 6 (of 6 total)

The topic ‘Improvement for removing debug CSS from front end.’ is closed to new replies.