[Ernest Marcinko]

Hi,

I can’t promise anything with the customizations, but it might be doable. What exactly does need to be changed? I can’t quite tell from this custom code. It looks like this ia full implementation of some sort.

[Ernest Marcinko]

Hi,

It could be because of the combination with the custom menu plugin, it may convert the output in some way and that may cause a bit of incompatibility.

In this case you should stick with the legacy shortcode method instead. If the menu supports custom HTML box, Gutenberg block or a shortcode box as a menu item, then definitely use that instead.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Thank you for the details!

It was due to a known issue of Cloudflare’s Rocket Loader. It changes a core window event flow and the plugin can’t initialize because of it. Fortunately a similar issue was already resolved on github in a different project, I can add a similar fix to the plugin as well.

I made a tiny change to the plugin core script file to fix that, this fix will be also included in the upcoming plugin release, so you don’t have to worry about it.

[Ernest Marcinko]

Why is that?

That’s impossible to answer like that. Clouflare looks at the request bodies, and if the heuristics see something suspicious then it blocks it. However sometimes it triggers a false positive – like in this case. I hihgly doubt it is simple to tell which parameter or argument triggers it, as the request is usually checked a million different ways.
For example I have had similar issues with Elementor and Divi builder – even though it’s super rare, it happens regardless of any plugin, as it’s related to the request. Elementor and Divi had nothing to change as it was an isolated case, as they shouldn’t.

I can take a look at the issue directly if you want to – via back-end as well as FTP access and try modifying some of the arguments to see what might be the trigger. It’s a painful process, and it may not work, but I can try if you want to. Make sure to add temporary FTP and back-end access, as I will have to save & modifiy the plugin files.

[Ernest Marcinko]

Hi,

It happens if Cloudflare picks up a false-positive firewall match. Based on the ray ID, you might be able to check what exactly triggered the firewall and make an exception to it.

Unortunately these are extremely rare and it’s never the same exact thing, it’s always something different as their WAF rules update regularly. Sometimes it’s a piece of user input text, a hexadecimal value etc.. It’s not really about the plugin version, WAF blocks requests that seem suspicious.

Another solution is to either decrease the firewall sensitivity, enable development mode or the best of the best is to add your IP address as an exception to the cloudflare firewall.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Sure!

1. This custom CSS will do it:

div.asp_r.asp_r_1.vertical .results .item::after {
    margin-top: 12px !important;
    margin-bottom: 12px !important;
    position: relative !important;
}

2. I think the best is to use the auto-populate feautre. It will display initial results 🙂

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

I think the easiest way to tackle that is via using the shortcodes with HTML, something like:

<h2>Keywords</h2>
[wd_asp id=1]
<h2>Settings</h2>
[wpdreams_asp_settings id=1element='div']

[Author]

Posts