[Ernest Marcinko]

Yea, sure!

It seems like it has something to do with the dialog, perhaps something with the settings, but I’m not sure. It’s part of Elementor, so you probably don’t want to disable that. I can’t tell if it’s the core script or something hooking into it though, most likely hook somewhere, but that’s impossible to find.

What I found though is that this script should get around it, I just tested and it worked from the console:

add_action('wp_footer', function () {
	?>
	<script>
		const f = ( select = false ) => {
			let input = document.querySelector('.dialog-widget .asp_m input.orig');
			if ( input === null ) {
				return;
			}
			input.focus();
			if ( select ) {
				input.setSelectionRange(0, 9999);
			}

		}
		jQuery(document).on('elementor/popup/show', ()=>{
			setTimeout(()=>{f(true);}, 800);
			document.querySelectorAll(".asp_main_container").forEach((el) => {
				el.addEventListener("asp_search_end", () => {
					setTimeout(()=>{f();}, 500);
				});
			});
		});
	</script>
	<?php
}, 999999);

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

My guess is within 2 weeks. This is surely going to be addressed, but it is still very much possible that it can’t be done, live paginations/load more features are generally a huge issue after live queries.

[Ernest Marcinko]

Thanks!

Turns out that is not caused by anything, but it is a recent change in Apple IOS mobile devices. I have found this topic about it.

Basically it is not possible to focus an input box programmatically after a timeout or asynchronous request on any iPhone within the latest IOS versions. I couldn’t find out why is that, but it is limited by the device and not by a script or the browser.

[Ernest Marcinko]

Hi,

Thank you for all the details!

Unfortunately this is not accidental. At the moment there is no way to not reload the page as the event handlers on the pagination can’t be reattached so it defaults back into normal pagination.

I have raised an issue about this on our issue tracker. I’m working on some other features right now, but I marked it to the next release milestone. I think I have a polyfill solution for a similar issue with Elementor, will check if it can be applied to the query loop as well.

• This reply was modified 1 year ago by Ernest Marcinko.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi Dan,

Sure, I can try. Can you please turn off asset minification, as right now every single script is delegated to some sort of a nitro CDN, so I can’t tell what the original source is.
Without that I might be able to pinpoint by blocking scripts one by one and then check the script file source.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Oh, and I forgot to add, the live results (which pop-up when entering something) can be customized, for that use the advanced title and content fields feature.

[Ernest Marcinko]

Hi Stephane!

The results page layout is a theme feature, search plugins can’t change that. Most themes however have wide support for customizing the layout and fields displayed via theme editor features (such as Divi or Avada). The best and easiest way therefore to check the theme builders integrated with your theme, 99% of the time it’s possible.

Another possibility is to use a full featured page editor, such as Elementor. With page editors can replace the whole results page with their own loops that you can customize.

The 3rd possibility is to edit the theme files via a child theme. This I only recommend when none of the options above are available or possible. In your case it shouldn’t be too difficult actually. If I understand correctly you want to only replace the excerpt with an ACF text field of some sort?
If your theme doesn’t support customizations and page building is not available, I can take a look if you want to. For that however I will need temporary sFTP and back-end access as some file edits will be required for sure. Also, don’t forget the field name, I need that too in order to fetch it programmatically 🙂

[Ernest Marcinko]

Oh okay, I will check that.

I tried to open the page, but it’s .htaccess password protected. Can you please let me know?

[Ernest Marcinko]

Oh I see. I’m afraid no.

This is however a borderline bug in my opinion, so just in case I have made an issue request for it. I can see a possibility to try to fix this in some way to perhaps check the adjusted word length. You can expect some sort of an improvement on this for the upcoming release for sure.

[Ernest Marcinko]

You cannot access this content.

[Author]

Posts