Jetpack's Infinite Scroll not working with lightbox-photoswipe plugin active

[wnuczek]

Jetpack's Infinite Scroll not working with lightbox-photoswipe plugin active

[arnowelzel]

My plugin also uses 2000 for the action priority. Since it works, when lowering the priority for JetPack the easiest fix would be to increase the priority in my plugin to some higher value.

Also see here:
4fb9d96

If this works for you, I will include this for the next update.

[wnuczek]

Actually it's the other way round. I changed the priority in your plugin.
Just did another check and 98 seems to be highest value, anything above that value causes the error.

[arnowelzel]

Hmm - this is bad news. A priority lower than about 200 will cause conflicts with other plugins - that's the reason why I set it to 2000 to be sure to get the output buffer after all other modifications.

As workaround you can keep your modification with a priority of 90. But I'll have to look into this as lowering the priority below 200 is definetly not an option, as this will break many sites.

[wnuczek]

I tinkered with the infinite scroll code and was able to get it to run with your plugin left at 2000 priority.

if ( have_posts() ) {
	// Fire wp_head to ensure that all necessary scripts are enqueued. Output isn't used, but scripts are extracted in self::action_wp_footer.
	ob_start();
	wp_head();
	while ( ob_get_length() ) {
		ob_end_clean();
	}
	ob_end_clean(); //forcing to clean and end the buffer seems to resolve the issue
	$results['type'] = 'success';

It seems to be an issue with output buffer as in case with YoastSEO issue.
Forcing to clean and end the buffer seems to resolve the issue.

I am no PHP expert so I look forward to hear your opinion.

[arnowelzel]

After reviewing the code you mentioned - this translates to:

1. start output buffering (ob_start())
2. output the site header (wp_head())
3. as long as there is anything in the output buffer, delete the buffer content and then end buffering (while ( ob_get_length() ) { ob_end_clean(); })
4. delete the buffer and end buffering (ob_end_clean())

So what this code wants to achive is to actually execute the WordPress header code but supress the output. That is already a very crude hack. But when opening a buffer it must be closed as well - even if there is nothing in it. I don't understand, why they call ob_end_clean() only if there is anything in the buffer. Also after having called ob_end_clean() the buffer is empty - there is no reason to this in conjunction with while( ob_get_length() ). Also see https://www.php.net/manual/en/function.ob-end-clean.php.

I think this is a bug with the infinite scroll code which should be solved there.