Rafael Fischmann
Forum Replies Created
-
Great to hear that, @spacetime! Thanks a lot.
I’d rather wait for the official update release, though. 😊
I found the stack trace in our PHP-FPM slow log. The query is being triggered by ai_save_post_hook() on every post save, not only by the transient expiration. The call stack is: ai_get_post_ids_with_blocks() ← ai_save_post_hook() ← wp_insert_post(). This happens on every publish/update, which explains why we see it so frequently given our publishing volume.
Thanks, @spacetime, I really appreciate it.
Forum: Plugins
In reply to: [Relevanssi - A Better Search] Relevanssi in WordPress’ Media Library?Got it, thanks!
- This reply was modified 2 weeks, 4 days ago by Rafael Fischmann.
Forum: Plugins
In reply to: [Relevanssi - A Better Search] Relevanssi in WordPress’ Media Library?You mean searching from /wp-admin/upload.php?mode=list? If so, doesn’t seem to be working for me — and yes, I have Relevanssi enabled for admin search.
But yes, our main usage would be from the modal when selecting a featured image inside Gutenberg.
Thanks, @msaari.
Sure, will do that. Thanks.
I’d more than willing to help, @maybellyne, but we’re actually cutting costs at this moment. I could, for example, swap a specific file from your plugin for debugging purposes.
Should I disable the feature altogether, then?
Hi,
I’ve just browsed my error logs from May 15th (when it was supposed to be updated) and found no entries at all related to Yoast SEO.
I won’t be able to test it with all plugins disabled and the default theme active. We’re a very big and popular site, I can’t run live tests like that and the test would have to be done in the exact date/time the cron job runs again.
I’m running WordPress 6.9.4 and Yoast SEO 27.6, both latest versions.
Hi @maybellyne,
Yes, I can see the
wpseo_llms_txt_populationhook in WP Crontrol, which will run again in about 2 days and 21 hours. I believe the last time it ran was exactly when the file was supposed to be updated, then it wasn’t, and then the warning reappeared in Site Health.Coincidentally, I had to flush Redis a couple of days ago because of some optimizations I made and the warning is still there — so I don’t think it has anything to do with the issue.
And no, the warning itself is correct: the file hasn’t been updated since May 8th.
As expected, the warning is back there.
I didn’t know it was only once a week. Well, it was generated on May 8th, so I believe in 3 days it will try to update it, will fail and the warning will show up in Site Health. I’ll keep my eyes on it. Thanks.
Yeah, but as I said, the file has remained stale since it was generated almost a week ago. Shouldn’t it be updated regularly, especially considering it lists only 5 posts (besides categories and tags)?
For now, the warning hasn’t reappeared in Site Health.
The only local caching I have is Redis’ Object Cache.
Yeah, just checked again and the file hasn’t been updated since I opened this ticket — when I deleted it, turned the feature off and back on in Yoast SEO. It was generated correctly, but it’s been frozen since then. The warning hasn’t reappeared it, but I believe it will soon.
The file is publicly accessible, yes. It’s not cached and I don’t see any firewall/security rules blocking it or anything.
Do you want me to run any specific tests?
Great explanation, @solidwppawel! Thanks a lot, understood.
Forum: Plugins
In reply to: [Lightbox with PhotoSwipe] Still loading WordPress’ native lightboxHi @awelzel, thanks for getting back to me!
WordPress does have a basic lightbox features since version 6.4, yes: https://learn.ww.wp.xz.cn/tutorial/exploring-wordpress-6-4/
I’ve tested disabling my only “script optimizer” plugin, which is Perfmatters, and it doesn’t make any difference.
The conflict seems to be with Imagify [https://ww.wp.xz.cn/plugins/imagify/], as per my testing. When I disable it, Lightbox with PhotoSwipe starts working. Any idea why? Imagify is very important to us.