getupworks

i prevent the lightbox stuff from being loaded on archives pages like this:

function my_lbwps_enabled($enabled, $id) {
	if ( is_singular() ) {
		return $enabled;
	}
	return false;
}
add_filter('lbwps_enabled', 'my_lbwps_enabled', 10, 2);

you could further control this with is_page() or is_single().
then there’s the option to exclude specific posts and pages by id in the plugins settings.

from what i understand, you’d like to control it more the other way round. like… the plugin files aren’t loaded by default but only if you tell them to.
i imagine this could be archieved by adding a custom field radio button “use lightbox y/n” for posts or pages to your theme.
so something like this would go to your themes functions.php then:

function my_lbwps_enabled($enabled, $id) {
	if ( <em>custom field radio button has value</em> ) {
		return $enabled;
	}
	return false;
}
add_filter('lbwps_enabled', 'my_lbwps_enabled', 10, 2);

awesome support! thank you!

great! thank you so much for your great support!

i got the same automated response from them, but they actually answered within a few hours.
i just sent you an email as suggested.

I don’t know, what “violate the buffer rules” means.

neither do i.

Google Analytics Dashboard for WP is in the plugin repository, Borlabs Cookie is a paid plugin unfortunately.

i asked the borlabs devs about this, they said you need to make contact with them so they can provide some sort of testing license/environment (i assume).
alternatively i could send you a login to my site if that’s any help.

update: this turned out to be a very specific problem due to my set up where i integrate google analytics dashboard for wp with borlabs cookie, which causes the lightbox to malfunction.
the borlab devs suggest to check if the lightbox plugin violates buffer rules.
my solution for now is to deactivate analytics for dashboard.

ok thank you for your help. i’ll go with the fade-in for the first image then.

hi craig,
thanks for your reply, i’ve sent you a message via your contact form
best

i’ve come across the same issue multiple times and it’s actually not a very particular case: when developing a site for a client on a dev server you usually get to a point when you’d like to let them review the front page and not necessarily other pages.
in another plugin this is possible by excluding the front page with a shortcode, [home] if i remember correct. maybe this solution could be implemented here as well?

hey @craig-at-smash-balloon
perfect, thank you!
i ended up with this:

add_action( 'wp_enqueue_scripts', 'sb_instagram_dequeue', 11 );
function sb_instagram_dequeue() {
	if ( ! is_page('123' ) ) {
		wp_dequeue_style( 'sb_instagram_styles' );
		wp_dequeue_script( 'sb_instagram_scripts' );
		remove_action( 'wp_head', 'sb_instagram_custom_css' ); // remove inline style
		// wp_dequeue_style('sb-font-awesome'); deactivated in plugins options
    }
}

so sad you gave it 5 stars then

why give it 5 stars then?

@buzztone
from the release notes of “disable gutenberg” 1.5.2:

• Adds option to disable frontend Gutenberg styles

i can confirm: with “classic editor” activated,
/wp-includes/css/dist/block-library/style.min.css
is loaded to the front end / theme. this does not happen with “disable gutenberg”.

• This reply was modified 6 years, 3 months ago by getupworks.

glad to hear everything works now.
as “classic editor” loads the gutenberg front end styles – which is pointless if gutenberg is turned off: you have to configure “disable gutenberg” under settings.

gutenberg is part of the core since wp 5.0, it is not a plugin anymore.
you need a plugin to disable it instead. “classic editor” is the most used, but then the gutenberg styles are still loaded into the front-end withouth serving any purpose.
i’d recommend the “disable gutenberg” plugin which completely removes gutenberg.

• This reply was modified 6 years, 3 months ago by getupworks.