[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Okay, thank you for the information.

All right, so if there is nothing in relation in the error log, then those might be bfrom botted/automated requests as they suggested, which have been caught in the firewall but still flagged as “internal server error 500”. There is also a defense try->catch statement around the handler, which will signal an error state when malformed data is sent, so the server doesn’t have to deal with it. However that would be logged in the error log for sure, so I am guessing it is the automated requests.

For now you can safely ignore it in my honest opinion, there is no sign of any serious issue behind it. If it comes back regularly, then let me know. In that case I will have to do an in depth code debugging via (s)FTP to try to re-create the problem.

[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]

Unfortuantely this is unrelated to the plugin settings, the snippet is to do a client side correction on the arguments passed in the results.

In case you will have it somewhere public, I will check it out to see why the snippet isn’t doing it’s thing.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

No worries! I just released an in-depth video on different compact box use-cases, in case you are interested.

[Ernest Marcinko]

Thank you for letting me know!

I can’t replicate this issue though. I have the same layout set, flex with the same parameters, even the numeric values, but all is okay, so I’m not sure what is the cause there. The update should not affect that, it only adds a single line to trigger a module loading, so it shouldn’t change anything related to that.
Can you try clearing all layers of cache, especially the browser cache?

In case you will have this somewhere up where I can test it let me know, I will do a debugging session on it.

[Ernest Marcinko]

Hi Stuart,

I see. I am not sure if this should be patched, as I feel this should be intentional for most cases, but I will definitely consider it.

You can actually fix this through a code snippet, but as you noticed this is on the client side, not on the server side. This should do the trick:

add_action('wp_footer', function () {
	?>
	<script>
	window.addEventListener("load", () => {
		document.querySelectorAll(".asp_main_container").forEach((el) => {
			el.addEventListener("asp_results_show", (event) => {
				// event.detail carries the arguments
				const [id, instance] = event.detail;
				document.querySelectorAll(".asp_r_" + id + '_' + instance + ' .asp_res_url').forEach((el)=>{
					const url = new URL( el.getAttribute('href') );
					let phrase = url.searchParams.get('asp_highlight');
					if ( phrase !== null ) {
						phrase = phrase.replace(/[!?]/g, '');
						url.searchParams.set('asp_highlight', phrase);
						el.setAttribute('href', url.href);
					}
				});
			});
		});
	});
	</script>
	<?php
});

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Yes – through the compact box layout. It is a pop-out search style, good for narrow/navigation areas.

[Ernest Marcinko]

You are welcome!

Correct – The results page design/layout is out of the scope of the search as it is controlled by the theme. Usually it is passed to the search.php and then whatever is required in that file, it varies for every theme. In your case it is very likely the content-search.php as you pointed out.

To get the thumbnail URL you may have to use something like:

wp_get_attachment_image_url( get_the_ID() );

[Ernest Marcinko]

Hi,

Thank you for the details, it helps a lot!

I have logged in to check, and there is indeed something missing as WordPress itself should automatically generate covers for PDF documents during upload. The most likely cause is that ghostscript is not installed, it is not well documented, but WordPress needs that to generate thumbnails.

If those thumbnails are not present, Ajax Search Pro will try alternative methods via ImageMagick, but the extension has to have access to PDF documents. It can be enabled via the policy file. Without that the script has no access to the PDF files. Correcting the policy file will very likely resolve the issue.

[Author]

Posts