Hi @shirhix,
If clearing cookies/re-accepting doesn’t help either, I’m wondering whether this behavior is related to the Complianz plugin.
It sounds like you have a caching/optimization tool or CDN enabled which skips the optimizations when you’re logged in as an admin, which would explain why the behavior is different between them.
Could you run some tests without the Complianz plugin enabled as well, to see if this still occurs?
Kind regards, Jarno
I did disable Complianz on a staging size, that’s why I came here. And it does work correctly with it disabled.
I also disabled the Hummingbird caching plugin, but that made no difference.
Hi @shirhix,
It doesn’t look like Complianz is blocking any scripts that I would expect to affect the content in this section. I tried visiting the page while logged in as well, which behaves the same.
Does enabling Safe Mode under Complianz > Settings change the behavior?
Kind regards, Jarno
Yes, enabling safe mode did something. Even after disabling save mode, it seems to have resolved itself. There are some cookies that are no longer there, they used to be set on wp-admin if I remember correctly. I wonder what their purpose was and if they come back.
Thank you.
edit: I may have gotten logged out when trying to save the Complianz settings. Savemode still active, sorry. But at least I can now reliably search for the cookies in the console.
-
This reply was modified 3 years ago by
shirhix.
After meddling with the Complianz Services, we found that disabling YouTube fixes the problem. Is there any reason for this?
Hi @shirhix,
Thank you for sharing your findings. If you’re only experiencing issues with the YouTube integration enabled, there may be YouTube-related content/scripts that are now being blocked; after which the issue with the feed arises.
If the feed’s content is loaded with AJAX, you could additionally try the “Cookie blocker for ajax loaded content” option (Complianz > Settings > General > Enable advanced features > Scroll down to Advanced Features > Enable “Cookie blocker for ajax loaded content”), which could help to block the service correctly.
Kind regards, Jarno