- This topic has 9 replies, 2 voices, and was last updated 3 years, 5 months ago by
.
-
Posts
-
Please see attachment. I am running search pro v4.23.3 on WP v6.1. The search box on my site works in Safari with no issue but I am having issues in both Chrome and Firefox displaying correctly. Please advise.
Hi,
If you are using SG optimizer by any chance, it has a bug, where it picks up some CSS files, but then it does not add it back in during the combine method. We already addressed that in the next release with a hacky workaround. I hope they will fix that soon, I see a lot of bypasses in other plugin codes as well just to get around this SG optimizer issue.
Until then, you can resolve it by changing this option: https://i.imgur.com/46DQfwq.png
Thank you. So you are saying this will be address in your next update not SG Optimizer correct? I am currently using that.
Yes – we managed to find a way to get around this issue with the SG optimizer plugin, it will be included in the next release. They are also aware of the problem, hopefully they finally fix it too.
Hello –
I just updated my Ajax Pro to Version 4.24.1 and I am having a similar issue as before. The live staging site at https://staging7.gracei13.sg-host.com/ appears to be unaffected but who I am inside my WP admin editing a page the header is having issues. Please see screen shot. Please advise. Thanks. FYI, I still have the fix in place that you recommended before. I have tried reverting that and it has no impact.
Hi,
Can you pelase add temporary back-end and FTP details? This issue seems unrelated to the previous, but when I try the same with Elementor back-end editor on our local servers it works all right.
Thank you!
Turns out this was a known problem. We recently moved the asset folder for ajax search pro, and for some reason on sg-host staging environments the URL of the wp-content directory is reported with the non secure protocol “http://” instead of “https://”.
It’s not a big deal, usually WordPress auto-corrects that at some point, but here it failed. I had to add a single line of code to force the correct protocol, now it should be fine.
- You must be logged in to reply to this topic.