[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Sure!

Please check this documentation: https://documentation.ajaxsearchpro.com/advanced-options/excluding-and-including-results/exclude-by-item-or-id

[Ernest Marcinko]

Yes – back-end access is fine for now. That error could indicate the issue, however I can’t see any problems in the query reported, I suspect the file might be corrupted there, but I will check.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Great, this was very helpful.

Luckily it is possible to set it up, I have changed if for you here: https://i.imgur.com/MG3Q7ef.png

Now the plugin will redirect with the same exact parameters as the theme search, resulting in that page layout.

[Ernest Marcinko]

Hi,

Can you share a relevant URL, back-end access and FTP access so we can debug the issue directl? Thank you!

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

If the migration re-created (export/import) categories/tags or any other taxonomy terms, and if you use any exclusion/inclusion based rules then it’s probably that, because in that case the term IDs change.

Usually the best start off point is to create a new search instance to see if that works, it very likely should if you have any posts/pages by default – and then try to recreate the configuration via that.

If nothing works, you can add temporary back-end details and I will check the configuration.

[Ernest Marcinko]

I think you can actually turn it off after it’s turned on. Once the strings are discovered it’s no longer needed.

[Ernest Marcinko]

Perfect, thank you very much, this all worked. Tried filezilla and other clients as well with no avail, but the updated WinSCP was able to log in.

So aftrer some painstaking testing I found that this is actually a bug in WPML intself. I follwed the instructions in this guide and get it working.
If by any chance you encounter the same issue, just make sure to delete the translation, now that the automatic discover is enabled, it should resolve the problem.

[Ernest Marcinko]

Those screenshots are not the same results page, that looks different from the regular results page.

When I deactivate the Ajax Search Pro plugin and visit the results page I get this layout: https://i.imgur.com/GDPsFK4.png
Which is different from the screenshots.

That looks like either a custom made archive page of some sort or triggered by a URI param. Can you share what the URL is when you are on that modular page?

[Ernest Marcinko]

It still should be okay, maybe there is a delay on the window load and a timeout could actually fix it:

jQuery(function($){
    const load = () => {
        $('.asp_label').on('click', function(){
            $(this).parent().find('.asp_label').removeClass('asp_label_selected');
            $(this).addClass('asp_label_selected');
        });
    }
    load();
    setTimeout(()=>load(), 1500);
});

[Ernest Marcinko]

Hi,

Can you please elaborate the exact nature of the issue with as many details as you can? Thank you!

[Author]

Posts