dutchmanjack

Okay, danke. Aktualisierung des Plugins und der Core von 6.5 auf 6.5.2 haben geholfen. Grü?e, Jack

Liest hier überhaupt noch jemand mit? Das Problem besteht jedenfalls immer noch…

Hey @mateithemeisle

I‘m using WP 5.7.2 and PHP 7.4.23 on an Apache Server.
In case you still need the feed URL, please tell me.

Thanks
Jack

Hey @mateithemeisle

any update on this issue? I’ve got the same behaviour with version 3.7.4 and 3.7.5 on my site when I try to create a new post.

Regards, Jack

Hi @aahulsebos,

thanks for testing. The width is not really a problem for me. It’s the height that matters. Posts are being cut of at the height of the placeholder on mobile/tablet. Using hitmag theme, this only happens if complianz and placeholder is activated . So there must be an issue here somewhere.

But thanks anyway for your time investigating this…

Groetjes,
Jack

Hoi @aahulsebos

Thanks for trying. The div works fine for me too, but in this case I have to change all of the older posts. I create newer post using the Javascript code.

BTW: you can also create the iframe on the tab next to the Javascript/sdk tab where you copy the div-code from. But here is an example:

<iframe src=”https://www.facebook.com/plugins/post.php?href=https%3A%2F%2Fwww.facebook.com%2FFeuerwehrWesterbeck%2Fposts%2F2772798046317295&width=500&show_text=true&height=571&appId&#8221; width=”500″ height=”571″ style=”border:none;overflow:hidden” scrolling=”no” frameborder=”0″ allowfullscreen=”true” allow=”autoplay; clipboard-write; encrypted-media; picture-in-picture; web-share”></iframe>

Groetjes en bedankt
Jack

Hi @aahulsebos,

that’s okay as a workaround. I load the script in the footer and after adding the div instead of an iframe the posts are shown completely.

However the problem is, that I have to edit about 150 posts and I would like to prevent this… I could also deactivate the placeholder in the complianz settings, but that’s not the real solution either, because visitors don’t see the text which is shown on blocked content.

I tried the twenty-twenty theme instead of hitmag. This also works, although I had to increase the height of the iframe to show the full content on mobile displays. You can see the result here: https://s-qtm6dn4k8t2cl.eu1.wpsandbox.org/test/

Switching back to hitmag shows the height problem again. So it seems to be caused by the combination of complianz and hitmag.

Any idea to solve it?

Groetjes en alvast bedankt!
Jack

Hey @aahulsebos,

Since the Problem is not the width, I also tried changing the height. Result: the height of the iframe is always set to the height of the placeholder…

Groetjes,
Jack

Hi @aahulsebos,

I generate the code for the iFrame on the Facebook for Developers site:

https://developers.facebook.com/docs/plugins/embedded-posts/?prefill_href=https%3A%2F%2Fwww.facebook.com%2FFeuerwehrWesterbeck%2Fposts%2F2772798046317295&__cft__%5B0%5D=AZUocQZkf8cHpVL5jbM2yot2Qy2vlklrX3sNHm-KHyG1SyzAvzxR6zjqdI-qmGm9ma5Kq7-6t_IM-FONK5mXRCmc67lYKe0jZEGCgG0-TbhLCuiAOFZb-1T-7cqZV-SsC4iZpNk-0ijkhVJTS0Du-eo0&__tn__=p%2CP-R#

Then I start a new post in WordPress and add this code as an HTML-Code Block (Gutenberg editor)… that‘s it.

It worked fine for a while, but suddenly the height of the iFrame is reduced to the height of the placeholder. Turning the placeholder of also solves the problem, but I need the placeholder for the case our users did not except cookies…

Groetjes
Jack

Hoi Aert,

Thanks for your reply. I meant the height of the iFrame. The Problem occurs on Tablets and Smartphones (in my case: iPad and Samsung S10).
Everything seems fine on windows desktop computer…

Best Regards/groetjes (en blijf gezond)
Jack

BTW: I‘m running Complianz Version 4.9.1 on WordPress 5.5.3

Okay, thanks!

Thanks @rogierlankhorst It seems to work fine now!

Groetjes, Jack

@aahulsebos: ?Enable cookie blocker for ajax loaded content“ was switched off. But turning it on doesn‘t make any difference… Any other ideas?

Goede morgen @rogierlankhorst @aahulsebos

Sorry to say, but after updating to version 4.4.0, I‘m experiencing the same problem as I described in my first post about version 4.3.5.

Could you please fix it again?

Bedankt!