[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

The most likely cause of the problem is, that the Loop Grid is not yet officially supported, but it highly depends on the exact setup as well.
In one of the upcoming releases this is going to be addressed and the Loop Grid should start working as well. If we run into some issues or limitations I will document that as well.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi Valentina,

It is because after filtering a hook is triggered to initialize the posts element. I guess that somehow interferes with the lightbox in some way. It is hard to tell if this is possible to solve, but some custom code may be needed.

Try adding this code via the Code Snippets plugin or to the functions.php file in your theme/child theme directory – make sure to have a full server back-up first for safety. For more details you can check the safe coding guidelines.

add_action('wp_footer', 'asp_add_footer_script', 99999);
function asp_add_footer_script() {
	?>
	<script>
	window.addEventListener('load', () => {
		WPD.Hooks.addFilter('asp/live_load/start', function(){
			WPD.Hooks.removeFilter('asp/live_load/finished');
		}, 10);
	});
	</script>
	<?php
}

If all goes well, then this may do the trick.

[Ernest Marcinko]

Hi,

You had a very old release installed, I recommend updating a bit more often to maintain the codebase, however this issue would still exist.

There were a few changes in the recent releases, namely the plugin is compiled to native javascript and no longer required jQuery, and some event handlers act a bit differently.

I see there are changes on the results template, I think there is a way to resolve this very easily by adding two additional class names to the template files. I assume you have the custom istopic.php results template in your theme directory, so please open that, and make the following change: https://i.imgur.com/zhXYhrM.png

By adding these two missing classes the event handler will recognize the href attribute and trigger the correct redireciton.

PHP 8.3 will work fine on the recent version, we are currently using that PHP version on the demo site.

[Ernest Marcinko]

It is because those fields are not actually the post description, but custom fields. I have selected them for you in the search settings: https://i.imgur.com/kIwE7Ac.png

I have also made that field as the scondary post description field, in case the actual description field is empty: https://i.imgur.com/T2TeuES.png
Now searching the items will also display the description as expected: https://i.imgur.com/8y8u5pg.png

[Ernest Marcinko]

You are very welcome 🙂

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Thank you, that worked!

I logged in, and I found one major issue, that the primary results ordering was set to Title descending so the relevance was ignored. This way results were not ordered by the relevance and the results were seemingly “missing”, when in fact they been only further down the list.

I changed it back to the default relevance option, now if I search for example “IRE” I get results as expected: https://i.imgur.com/qwtIm5G.png

[Author]

Posts