[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Perfect, thank you for the feedback.

Yes, keep this one installed, I have already merged this bugfix to the upcoming release.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Oh, I’m sorry, I was confused and thought that was due to the results page.

You are right, that shouldn’t be triggered. I quickly checked, and there seems to be a type coercion issue within the core script, I can replicate this.

Long story short, the script checks if the option is disabled, and the option is sent as either a 0 (if disabled) or 1 (if enabled). However by mistake it’s converted to a string, therefore instead of 0 or 1 the value is “0” or “1”. And in javascript deals with that in a funny way, as 0 is coerced to a boolean false, but “0” is a boolean true – therefore it thinks the option is enabled.

I will get back to you in an hour or so, I think I can patch this real quick and send you a beta copy to test.

[Ernest Marcinko]

Hi,

Thanks for the video, that actually helped a lot.

So in the video you are looking at an event called search_term. However that event is not coming from Ajax Search Pro. As you scrolled through the options on the back-end, the event names were the default: focus, search_start, search_end, magnifier etc..

The event search_term seems to be a core GA4 analytics event parameter. I suspect it is triggered when you view the search results page, when the enhanced measurments are active.
My guess is, that you should be able to test that by visiting the search results page with a couple of different phrases, they should start showing up under the search_terms event.

[Ernest Marcinko]

Hi,

Thank you for the details. When I try to access the website, I’m getting this error message: https://i.imgur.com/Kyeuj2L.png
Can you please check that?

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

If the top level domain name is the same, then nothing will happen, it will be considered to be active. Even better, because the subdomain is “dev.”, the license activation is completely ignored as the plugin recognizes that it is a development environment and skips that.

Even if anything would happen, you can always re-activate the license key.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You are very welcome 🙂

If you don’t mind, I will close this topic soon and mark it as resolved, feel free to open another one if you have other questions or issues.

If you like the plugin and have not rated already, feel free to leave a rating on the wordpress plugin repository, it’s greatly appreciated.

[Ernest Marcinko]

Looks like some extra button side margin coming from somewhere. This custom CSS should remove it:

div.asp_m_1 .probox .promagnifier,.asp_m_1 .probox .prosettings {
    padding: 0 !important;
}

[Author]

Posts