Blocking Facebook Feed?
-
If I only allow Functional Cookies, my Facebook feed plugin shows “Click to Accept All Cookies”. That makes sense.
When I do accept all cookies, the Feed shows up blank and just says, “View on Facebook.” Is Complianz blocking this plugin?The page I need help with: [log in to see the link]
-
The activation of the Facebook feed is not working properly. I think the placeholder is not working correctly. Can you check what happens if you disable the placeholders in Complianz/settings?
If that helps, I think the solution might be to make the placeholder matching stricter.
Thanks for the quick reply. Yes, disabling the placeholders solves the problem.
I’m not much good at this technical stuff. Do you have an article or any suggestions on how to make the placeholder match better? I’m not sure if this is something I can do within Complianz, within the Facebook feed, or if I need to try to mess with the css.
Thanks again!@2lovehim I will look at the code that does the matching, and make it stricter, I’ll get back to you on that tomorrow!
Meanwhile, if you want your other placeholders to keep on working, you can use this code to specifically remove the facebook placeholder:
add_filter('cmplz_placeholder_markers', 'my_unset_facebook_placeholders', 100); function my_unset_facebook_placeholders($tags){ unset($tags['facebook']); return $tags; }Can you try this branch?
https://github.com/rlankhorst/complianz-gdpr/tree/mappress
I’ve made the matching stricter, this should resolve the issue with incorrect matches on placeholder elements.
Great.
Never used github like this, but I think I figured it out. You are teaching me new stuff. π
I installed 4.1.2 from github, deactivated 4.1.1, and activated 4.1.2.
It seems to be working perfectly now.
Should I “delete” 4.1.1 now and will 4.1.2 receive updates like normal?
Really, thank you so very much for your help!Great!
Thanks for confirming!
One thing I would recommend, is indeed to delete the 4.1.1 plugin, and then rename the 4.1.2 plugin (which is probably named something like “complianz-gdpr-mappress” back to “complianz-gdpr”, using FTP. Then you have the default plugin folder name back, which is best practice. You’ll have to activate the plugin afterward, as a folder name change deactivates the plugin.
Rogier
This problem is again occurring on my two websites that use both Complianz and this Facebook feed. I think when I accept the Complianz update that it must have reset the problem. Is there a permanent solution to this?
Hi @2lovehim,
I think that this could be caused by some changes we have made in the integrations. Could you check if disabling the Facebook placeholder through Complianz -> Integrations -> Facebook works? So the integration itself kan stay active (left column), but the placeholder disabled (right column).
Please let us know if this solves the problem.
Regards,
LeonWow, Leon, that was fast! Yes, disabling the second toggle (Facebook Placeholder) works fine. Am I still in EU compliance if I do so?
Hi @2lovehim,
Good to hear that solved the problem. While we won’t change the integrations section anytime soon, this should be a permanent solution π
While Facebook is still blocked before consent is provided, this has no influence on your GDPR compliance. Only the embedded content is not replaced with the Complianz placeholder.
p.s. You could also delete the filter as provided by @rogierlankhorst. It is no longer necessary.
Regards,
Leon
The topic ‘Blocking Facebook Feed?’ is closed to new replies.