|
fffunction
|
April 15, 2015 at 9:51 am
Is there anyway to prevent the EE4 CSS from being included in a theme? We’ve got a custom theme already so dont want to have an additional redundant CSS file for users to have to download.
|
|
fffunction
|
April 15, 2015 at 10:13 am
Looks like deregistering the styles works out:
function my_custom_deregister_styles() {
wp_deregister_style( ‘espresso_default’ );
wp_deregister_style( ‘ticket_selector’ );
}
add_action( ‘wp_enqueue_scripts’, ‘my_custom_deregister_styles’, 100 );
|
|
Lorenzo Orlando Caum
|
April 15, 2015 at 11:13 am
Hi, that will work but it does remove the default styling. Are you replacing the included styling with your own?
—
Lorenzo
|
|
fffunction
|
April 16, 2015 at 2:27 am
Yes, we’re implementing EE to replace a custom event system on an existing site, so the styling is already in place.
|
|
Dean
|
April 16, 2015 at 2:42 am
Hi,
Well if you have replacement CSS styles in place then de-registering the CSS is likely the best way forward.
Do you have any other queries regarding this topic that I can help with?
|
|
fffunction
|
April 16, 2015 at 8:43 am
No thanks 🙂
|
