Suggestion and help.

Hi,

thanks again ?? Yeah this is a small plugin so it’s expected to have little load on the page.

I’m still thinking, if I should expend this plugin with predefined styles, so I might take you up on that offer in the future.

Off topic:
For your issue with dequeuing the page builder admin styles… The page builder by siteorigin has an action specified right after the admin styles are enqueued, so you can use that to dequeue the styles. The code would look like this:

function remove_so_page_builder_admin_styles() {
	wp_dequeue_style('so-panels-admin');
}
add_action('siteorigin_panel_enqueue_admin_styles', 'remove_so_page_builder_admin_styles');

This works for me…

Take care!

Capuderg,

It worked perfectly for me. Very happy with your help. Millions of gratitudes to you.

However, there is one more thing: Many styles in the Plugin SiteOrigin utliza the style of “SO BUNDLE WIDGETS”:
/wp-content/plugins/so-widgets-bundle/base/css/admin.css
/wp-content/plugins/so-widgets-bundle/admin/admin.css

And I need to take control of these files too. What I would add the code to disable this too?

function remove_so_page_builder_admin_styles() {
	wp_dequeue_style('so-panels-admin');
        wp_dequeue_style('siteorigin-widgets-manage-admin');//It's correct?
        wp_dequeue_style('siteorigin-widget-admin');//It's correct?
}
add_action('siteorigin_panel_enqueue_admin_styles', 'remove_so_page_builder_admin_styles');

add_action(' ? // What we add here?
', 'remove_so_page_builder_admin_styles');

add_action(' ? // What we add here?
', 'remove_so_page_builder_admin_styles');

I looked at the siteorigin-widget-.class.php file and so-widgets-bundle.php and screw me up to record the new styles in my plugin. Once utliza an array. I do not know if it works only for scripts or both (scripts and styles).

If you can help me, showing me to how I can register these new styles, I thank you very much.

And as you always say: “Take care!” ??

Lucas Tolle

Capuderg,

I registered all new files. They are all in place.

However, my doubts mentioned above and the following:

in siteorigin-widget.class.php file are:

function enqueue_scripts(){

		if( !wp_script_is('siteorigin-widget-admin') ) {
			wp_enqueue_style( 'wp-color-picker' );
			wp_enqueue_style( 'siteorigin-widget-admin', plugin_dir_url(SOW_BUNDLE_BASE_FILE).'base/css/admin.css', array( 'media-views' ), SOW_BUNDLE_VERSION );

			wp_enqueue_script( 'wp-color-picker' );
			wp_enqueue_media();
			wp_enqueue_script( 'siteorigin-widget-admin', plugin_dir_url(SOW_BUNDLE_BASE_FILE).'base/js/admin' . SOW_BUNDLE_JS_SUFFIX . '.js', array( 'jquery', 'jquery-ui-sortable', 'jquery-ui-slider' ), SOW_BUNDLE_VERSION, true );

			wp_localize_script( 'siteorigin-widget-admin', 'soWidgets', array(
				'ajaxurl' => wp_nonce_url( admin_url('admin-ajax.php'), 'widgets_action', '_widgets_nonce' ),
				'sure' => __('Are you sure?', 'so-widgets-bundle')
			) );

			global $wp_customize;
			if ( isset( $wp_customize ) ) {
				$this->footer_admin_templates();
			}
			else {
				add_action( 'admin_footer', array( $this, 'footer_admin_templates' ) );
			}
		}

		if( $this->using_posts_selector() ) {
			siteorigin_widget_post_selector_enqueue_admin_scripts();
		}

		// This lets the widget enqueue any specific admin scripts
		$this->enqueue_admin_scripts();
		do_action( 'siteorigin_widgets_enqueue_admin_scripts_' . $this->id_base, $this );
	}

My question is which do_action use for wp_enqueue_style:

-> siteorigin_widgets_enqueue_admin_scripts_
-> footer_admin_templates

One or both. In the case of the two, as I add there?

Hi,

this will disable the CSS for the SO widget bundle settings page inPlugins -> SiteOrigin Widgets, which I think you don’t want to disable:

function remove_so_bundle_settings_page_builder_admin_styles() {
	wp_dequeue_style( 'siteorigin-widgets-manage-admin' );
}
add_action( 'admin_enqueue_scripts', 'remove_so_bundle_settings_page_builder_admin_styles' );

And this will remove the base admin css:

function remove_so_bundle_page_builder_admin_styles() {
	wp_dequeue_style( 'siteorigin-widget-admin' );
}
add_action( 'wp_print_scripts', 'remove_so_bundle_page_builder_admin_styles' );

But this will display an error in the bundle widgets, that the widget needs styles in order to work. So you will have to figure that one out.

Anyway, this is not a topic to discuss this, as this is not related to my Tabs plugin. I wish you luck with your plugin.

Take care!

Hello, Capuderg

I apologize for using your space to address a my plugin. I needed help and did not find another way to do this, since he had sought help everywhere. And unwittingly ended up causing annoyance to you.

But I want you to know that your help was invaluable. I worked for days making the necessary customizations, but thanks to you I managed to complete the plugin, since only need these hooks.

My plugin setting whole area of ??the customize page builder by SiteOrigin, as well as settings pages. The last hook you sent me, saying that error would actually everything worked out as I booked the CSS file also in my plugin. That’s what I needed.

Aware that the next update on the administration page of my plugin, we recommended plugins, and its Tabs plugin will be there, recommended to download. In other words, the idea is that if you need to use the Page Builder SiteOrigin successfully, you must also have your tab plugin installed and enabled.

Anyway, I am grateful for your help. And once again I’m sorry to use your wrongly space. I promise I will not do this anymore. ??

I want to know if there is a very grateful person, that person is me.

Hugs,

Lucas Tolle

Hi,

great ??

It’s ok, I just wanted to point out, that this is not the topic to discuss this issue…

I’m glad you finished your plugin and that you will recommend my tabs widget plugin ??

Have a nice day!