Forum Replies Created
-
Posts
-
Okay, that very likely explains it.
The products are probably created, saved and then the custom fields are added afterwards programmatically. However after adding a custom field
will not trigger the index, as it is bound to the post creation/modification hooks.
I strongly recommend triggering the save_post hook, as it will automatically execute any maintenance related tasks for wordpress after the custom fields were added as well – this is basically a way to tell the system that a post/cpt had been modified.
Alternatively you can enable this option to trigger an index during programmatical custom field changes, however that can be very CPU intensive as it triggers a lot, so definitely monitor the server during imports to make sure it does not time out.Unfortunately the missing custom fields can only be added either by:
– triggering the save_post hook for each of the newly imported posts – probably the easiest solution
– manually removing the newer posts data from the index via IDs from the wp_asp_index table and then “continue index” to refresh the data – this can be also very simple by running an SQL command on the table
– or deleting and recreating the whole index
..as it is not possible to determine which of the posts have missing SKU data from the index.Hi,
Are the products with the SKU issue imported in any way or form, or perhaps the SKU is added in later programmatically/3rd party plugin somehow?
Hi,
Sure! I think you are looking for this input: https://i.imgur.com/e9Lb4V2.png
Hi,
It sounds like a FOUC issue. If you are using a heavy cache plugin or any CDN cache which allows lazy loading of stylesheets, that can cause this problem as the delayed loading of the styles will cause the flash.
Check the cache configuration and make sure to disable any lazy/delayed or “via script” loading of stylesheets, it will resolve the problem. Some CDNs may call it “rocket loader” or similar.
I usually don’t recommend using these advanced techniques of loading assets in general, unless you can gather the critical CSS to prevent the style flash. They usually cause more problems.Let me know if this helps!
Hi,
If you prefer using Elementor Products, then you can simply use that for showing the results.
If it is not neccessary, then for a similar but simpler layout you can also use the horizontal search results, and for that:
– choose any horizontal theme
– turn off the horizontal scroll
– Optionally turn on the load more (if you want to)
– Optionally turn on the auto populate
– change the results display mode to blockThen via the advanced title and content fields you can even display other field contents in the results description/titles.
To place them below the search, use the results shortcode as well.
Yes – there is actually a hard limit set of 400 elements, which we intend to change to 10 000 in the upcoming release.
I have made that tiny tweak on the code editor on your back-end, now it should print all the tags 🙂
Thank you!
I’m afraid I was mistaken, this is not possible via custom CSS, only via major modifications to the template code, I’m sorry.
Hi,
Thanks.
Because that is an archive page, elementor filtering will not work, but I have configured the archive page filtering instead: https://i.imgur.com/LeZPOkx.png
That does the same thing but for the archive pages. It should be okay now.
I see you are using generic filters and the exact matches selector is checked – which means that only exact matches are considered.
You can either remove the generic filter or de-select the exact matches filter by default: https://i.imgur.com/EL1XFDu.png
