Currently I have following filters without any success:
add_filter( ‘cornerstone_enqueue_styles’, ‘__return_false’ );
add_filter( ‘cornerstone_customizer_output’, ‘__return_false’ );
add_filter( ‘cornerstone_use_customizer’, ‘__return_false’ );
By the way, if you remove the Cornerstone styles from the head, all of the Cornerstone elements may no longer work or display properly. By the way, what you are trying to do, modifying the features and functions of Cornerstone, requires custom coding and it is already considered custom development. Be advised that this is beyond the scope of our support under our Support Policy. If you are unfamiliar with code and resolving potential conflicts, you may select our One service for further assistance.
I’m developing a custom theme for our client. It is only for one client and not for selling.
I’m using Cornerstone only as a page editor to place and structure site content, with no customization of Cornerstone features or functions. Then on Front-End, I’m serving my own CSS for HTML that Cornerstone generates, which is not cloaked with all the styling for the components the site will not need. At the same time, I’m disabling the client from using any components that are not planned to be used.
In my initial message mentioned filters do not yield the result stated in your documentation.
I was also checking your plugin code and didn’t find an appropriate apply_filter call for ‘cornerstone_enqueue_styles’, ‘cornerstone_customizer_output’ and ‘cornerstone_use_customizer’ hooks handles.
I don’t need support for custom development.
I kindly ask for the information on how to turn on the functionality that it is specified in your documentation, and it seems it’s not working as documented.
I’m using the latest version of WP and Cornerstone: 6.1.4.
The CSS that you want to remove is actually coming from the styles.php file which is in the Cornerstone folder. You may need to check the file in wp-content/plugins/cornerstone/includes/views/frontend/. You can edit this file or delete it from the folder since this is loaded dynamically.
You are suggesting directly modifying the Cornerstone plugin code. I would like to avoid that since we are going to have problems when an update of Cornerstone comes out, and it will overrun our changes.
Isn’t add_filter( ‘cornerstone_enqueue_styles’, ‘__return_false’ ); the filter that should do that?
Why it’s not working?
Why are the other two filters also not working?
I’ve just tried those filters that you’ve posted and they all work. Adding the following codes in the default WordPress theme removes Cornerstone’s Styling.
Please note though that they are for Classic Elements and not for V2 or non-Classic Elements. It’s mentioned in our doc. We don’t have an API yet for the V2 elements.
If you’re working on Classic Elements, there probably is something incorrect with your integration. Regretfully, we do not provide support for custom development so we cannot investigate your custom theme code. I’d just suggest that if you’re using a child theme, do any integration using the after_setup_theme hook like the code below.
It’s most probably an issue with your theme. I used the default WordPress theme, Twenty Twenty-One and no code from Cornerstone was generated.
Please try out the Twenty Twenty-One theme and see if it works. If it does, it’s an issue with your theme.
If it doesn’t work with Twenty Twenty-One theme, please provide the following info so we could check your setup so maybe we can point you to the right direction.
WordPress Login URL
Admin username and password
You can find the Secure Note button at the bottom of your posts.
Upon further testing, I have replicated the issue with the latest Cornerstone version 6.1.4 which is also the version you’re using.
Please uninstall the latest Cornerstone version in your site and install the previous version 6.0.8. You can download the previous version in your license page.
I’ll post this case in our issue tracker so this will be queued to be investigated by our development team.
Not ideal to choose between downgrading 5 versions and not having ETA or staying on the latest version and not having that functionality.
Looking forward to a quick patch of the plugin.
Till then, I came up with this rather hacky workaround that is tested with the latest version of Cornerstone 6.1.4, and it does not include any modification of the plugin.
I’m posting this for the future me or anyone having the same issue.
/**
* Remove Cornerstone's head inline styles
* This is a workaround for not working Cornerstone hooks in versions 6.1.0+ (current version 6.1.4)
*/
function cornerstone_remove_css_scripts() {
if ( !function_exists('CS') ) return;
remove_filters_with_method_name('wp_enqueue_scripts', 'registerStyles', 200);
remove_filters_with_method_name('wp_enqueue_scripts', 'outputStyleTag', 9999);
}
add_action('wp_enqueue_scripts', 'cornerstone_remove_css_scripts');
/**
* Allow to remove method for an hook when, it's a class method used and class don't have global for instanciation !
* @link: http://hookr.io/plugins/search-by-sku-for-woocommerce/0.6.1/files/wp-filters-extra/
*/
function remove_filters_with_method_name( $hook_name = '', $method_name = '', $priority = 0 ) {
global $wp_filter;
// Take only filters on right hook name and priority
if ( ! isset( $wp_filter[ $hook_name ][ $priority ] ) || ! is_array( $wp_filter[ $hook_name ][ $priority ] ) ) {
return false;
}
// Loop on filters registered
foreach ( (array) $wp_filter[ $hook_name ][ $priority ] as $unique_id => $filter_array ) {
// Test if filter is an array ! (always for class/method)
if ( isset( $filter_array['function'] ) && is_array( $filter_array['function'] ) ) {
// Test if object is a class and method is equal to param !
if ( is_object( $filter_array['function'][0] ) && get_class( $filter_array['function'][0] ) && $filter_array['function'][1] == $method_name ) {
// Test for WordPress >= 4.7 WP_Hook class (https://make.wordpress.org/core/2016/09/08/wp_hook-next-generation-actions-and-filters/)
if ( is_a( $wp_filter[ $hook_name ], 'WP_Hook' ) ) {
unset( $wp_filter[ $hook_name ]->callbacks[ $priority ][ $unique_id ] );
} else {
unset( $wp_filter[ $hook_name ][ $priority ][ $unique_id ] );
}
}
}
}
return false;
}
@marc_a do you see any potential problem with that approach or inconsistency with what the problematic Cornerstone hooks should do?
I have checked your solution in my local environment and it does not create any problem with the activated TwentyTwenty theme. Still, I would request you go by the suggestion given by my colleague Christian to avoid any unrecognized problem with the code.
