[Ernest Marcinko]

Hi Emiel,

Thank you for the details!

There seems to be something wrong with your .htacces mod_rewrite or perlmalink configuration.
When I look at the network tab when loading your site, there are a tons of 301 redirection requests: https://i.imgur.com/VS8L5gC.png

All of them are trying to access the regular ajax handler, but it gets redirected incorrectly to the same URL: https://i.imgur.com/P1TRwha.png
So it ends up in an infinite loop. This only happens when a translation is selected – so my guess is that it’s probably related to a specific cookie or similar.
Make sure the default WordPress ajax url is not added to the translations as it is used across all the website, in your case it’s the https://www.vdvelde.com/wp-admin/admin-ajax.php url. This should always work regardless of the translation and should print 0 to the screen.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

I’m afraid there is no such thing as “night mode” within the plugin. Night mode designs are usually custom coded via custom CSS for every single use case as they all work differently.

I have looked at your case, and put together a baseline custom CSS which should mostly do the trick:

.jnews-dark-mode .asp_m,
.jnews-dark-mode .asp_s,
.jnews-dark-mode .asp_r,
.jnews-dark-mode .asp_r .item {
    background: #1a1a1a !important;
    border: 1px solid #303030 !important;
    box-shadow: none !important;
}

.jnews-dark-mode .probox svg {
    fill: #9E9E9E !important;
}

.jnews-dark-mode .asp_loader>div {
    border: 4px solid #9E9E9E !important;
    border-right-color: transparent !important;
}

.jnews-dark-mode .asp_r .asp_res_text {
    color: #9E9E9E;
}

.jnews-dark-mode .asp_r .asp_showmore {
    background: #1a1a1a !important;
}

.jnews-dark-mode .asp_s legend,
.jnews-dark-mode .asp_s .asp_option_label {
    color: white !important;
}

.jnews-dark-mode .asp_m .probox .orig,
.jnews-dark-mode .asp_m .probox .orig::placeholder {
    color: white !important;
}

.jnews-dark-mode .asp_m .prosettings,
.jnews-dark-mode .asp_m .promagnifier {
    box-shadow: none !important;
}

This is a bit beyond of regular support, so I can’t guarantee anything, but it should be very close to the optimal solution.

[Ernest Marcinko]

Hi,

That deprecation notice is probably not the cause, it is only due to a typo, but has no effect whatsoever, so it’s probably something else. I will fix that nevertheless.

Can you please let me know what the username/pw is fot the .htaccess restriction? I tried the username/pass from the ticket, but that does not work there.

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

Sure!

I see the issues now. Make sure to revert these options back to default:
– Search settings: https://i.imgur.com/o5Vs5X9.png
– Results layout: https://i.imgur.com/wfekcRn.png
These will make sure to have the settings and the results into a floating position, which is much better for a header implementation.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Yes, use this ordering configuration for the primary ordering field: https://i.imgur.com/BVaV5Dh.png
Set the secondary field to Relevance.

This should do the trick 🙂

[Ernest Marcinko]

Hi,

Thank you for the details, I know exactly what is wrong here.

So, in some cases data importing solutions do not trigger the save_post or wp_insert_post hook after a post had been added to the database.
Those hooks are crucial as plugins attach actions to them, in this case Ajax Search Pro triggers the index table update process. If you have access to the import method, then I strongly recommend triggering the save_post hook once all the data, metadata, sku and everything was created. That is a good measure to refresh the data.

If you can’t do that, then there are two alternative methods to try:
1. Enable this option. If by any chance the SKU meta is added after the post object is created, then this could resolve it. However watch the server performance, if you notice anything strange, turn this off.
2. Instead of triggered index, use Cron only. This will trigger the index at intervals to update, and should ensure that only the fully generated products are indexed.

[Ernest Marcinko]

You cannot access this content.

[Author]

Posts