Wolfram Kl?ger

Marc, thanks a lot!

Very useful update.

Now, of course, I have to save my past as well and add the 5th star to my rating. Your plugin is my new standard!

Thanks Marc,

you are right. I did another test.

Any changes to headlines are not updated in the TOC. But: the frontend is indeed updated, after reload.

In the backend, I have to re-open the page. This should be improved.

2. to 4. yes, of course, optional. We have to find someone else ??

Johannes, you’re a wizard ??

Thank you so much. Added. Tested. Works.

Thanks again.

Where / how would I add this option to my theme?

The snippet from above can be disabled, after running once. It’s the same as if I had modified options.php.

Thanks.

Yes. “Beitragsbild”, english probably “Featured Image”, appears in my standard Gutenberg block selection. No extra extension or something.

Funny enough. As mentioned, it *has* a link, if the setting is on. If so, of course, it’s linking to itself. I’m too dumb to imagine a useful application but …

For now, I have to add the featured image twice. One for the featured image setting, one in the content, as standard image block. Then, your plugin does its thing. Kind of weird, but not really a problem.

Maybe one day I find a better solution, using GeneratePress and GenerateBlocks.

Regarding the snippet: Probably you’re entirely right. But how would you compose the snippet? I couldn’t find an example for

apply_filters( “option_{$option}”, mixed $value, string $option )

applied to

‘image_default_link_type’, ‘file’

That’s above my head ??

Meanwhile, I discovered the Gutenberg block “Featured Image” (Beitragsbild).

Its settings on the right are:

– Link to post: yes or no (default)
– Additional CSS classes

How could I apply your plugin to this block type, the same as to standard image and gallery blocks?

Of course, I see, I have to promise, I will _never_ activate the link to post switch ??

Hi Johannes,

thanks a lot. That’s a cute trick, setting the image_default_link_type to ‘file’.

Though, instead of editing wp-admin/options.php, I’d prefer adding a little snippet to my functions.php, via the brave plugin

Code Snippets

The idea is “stolen” from writenowdesign.com

This is my version:

add_action( 'after_setup_theme', 'whk_image_defaults' );

function whk_image_defaults() {
	update_option( 'image_default_link_type', 'file' );
	update_option( 'image_default_size', 'large' );
	update_option( 'image_default_align', 'center' );
}

In addition to link_type, this snippet also defines default_size and default_align to my preferences.

Works like a charm.

BUT: featured images, yes, on archives, they are usually linked to full posts, but on single post, they act as the first image below the title. Then, there is no link, and unfortunately no lightbox, as well?!

ahem, just to mark this resolved ??

Thank you so much, until next!

My idea is, I could fix it by CSS.

But, generally, what’s the benefit of wrapping the call in ob_* ?

What’s the disadvantage, if I keep the buffer calls for proper sequence?

Of course ??

Done!

Very interesting result: WP Youtube Lyte works as before. You’re awesome, and you know it, I suppose …

BUT: The GenerateBlock content template gets disturbed. Calling Lyte without ob_*, pushes the video from last to top position.

The template is basically just a post title, consisting of

– Kicker (say headline of the headline)
– Headline
– Post Meta (Author, Date, Date)
– Subline (lead text, 1 or 2 lines)
– Featured Video

With ob_*, everything as expected.

Without ob_*, the video pops before the kicker. Everything else is fine.

Any idea, how I could fix that?

You mean, unbuffered is good enough, like this?

add_shortcode( 'featured_youtube_video', function() {
    // ACF(featured_youtube_id, post_id)
    $youtube_id = get_field('featured_youtube_id', get_the_ID());
    if( $youtube_id ) {
        // WP Youtube Lyte
	echo do_shortcode('[lyte id='.$youtube_id.']');
    }
} );

I actually have no idea, what ob_* is doing here. I thought, this is kind of default, and required for such shortcode snippets.

I’m sorry. I had no direct contact to Tom. His team finished this topic for now. So I have to fall back to the paginated archive, instead of infinite scroll.

Without GPP’s Infinite Scrolling, WP Lyte works like a charm. PageSpeed Insights scores 84. That’s not too bad, for vanilla hosting, no cache, just AutOptimize, so far.

Focussing on my little snippet again: could I further improve the Lyte call?

To me, it looks slightly over-complicated. But maybe, that’s my PHP allergy ??

Thanks again, I’ll try my very best to convince Tom ??

Hey Frank, thanks a lot.

BUT: infinite scroll is a checkbox. I have no idea, what Tom Usborne does with it, which JS he’s calling ??

Or did I get you wrong, and you mean

echo do_shortcode(‘[ly.te id=’.$youtube_id.’]’);

instead of

echo do_shortcode(‘[lyte id=’.$youtube_id.’]’);

in my PHP code snippet, see above?

(yes, the only difference is that little dot between ly and te ??

Where / how else could I get access to this call, using GPP & GB?