imddev

P.S: when I copy the script from /w3tc/pub/js/lazyload.min.js and paste it in to the browser console – lazy loading works as expected.

Reopened ??

Moving conversation to the plugin’s CodeCanyon support page. Marking as resolved here.

Hey, apologies for the delay in responding back to you @maybellyne . This is indeed a CPT, and this particular post at https://parichka.bg/contest/moyataparichka-ese/submission/34123/ is categorized under the term ese2024 and none others.

Perhaps my understanding of the hook is wrong? I want every post that is contained in the excluded term to be excluded for listing in the sitemap. So – posts X, Y and Z with the same CPT (contest_submission) are in 3 different term_ids in the taxonomy submission_category , I want every term in the taxonomy to be listen on the sitemap, with the exception of the term with an id 66 .

How can I accomplish that?

Versions:
WP – 6.4.3
Yoast – 22.6

Edit: error is caused because Yoast relies on REST API to change the logos and the entire WordPress’ REST API was disabled on my site from the plugin W3TC.

TLDR; people check if your REST API isn’t disabled by a plugin or a snippet in your child theme or elsewhere. You can safely disable it again after changing the logo – or at least I think so, as I haven’t found any other unwanted or buggy behavior.

To the Yoast SEO team – Why?
W3TC has an extension for Yoast SEO that does whatever it does, but it doesn’t account nor notify for the unwanted inability to change your organization or site’s SEO logo. Please collaborate with them or further develop your plugin to check if REST is disabled, and provide real and useful information on how that affects your plugin. Scary warnings and factless messages that discourage the user from disabling their REST API are bad (please pass to your dev team).

So, what else that Yoast does, relies on the REST API and might be broken?

Hey, thanks for suggesting a solution! I didn’t get to test it, as I realized that the approach I’ve had taken was wrong.

I will be on the task of conflict testing, will get back to you shortly…