🆕 [NEW PLUGIN] iFrame & Embed Detector


iFrame iFrame & Embed Detector


Hi there!
We just release this new plugin to the Bubble marketplace :santa: !

The plugin offers these functionalities:

:arrow_right: Trigger an event if the page is embedded or not
:arrow_right: Expose a state that indicates if the page is embedded
:arrow_right: Expose a state that indicates the URL of the parent page that displays your page

This plugin offers nice use cases such as blocking pages from unauthorized sources!


:heavy_dollar_sign:The plugin is available for $2/month or $7 for a lifetime license.

:blue_book: We offer full documentation with the plugin and forum support.

LINKS


:link: Plugin page: https://bubble.io/plugin/embed–iframe-dete…
:link: Our shop page: https://app.ottho.tools/nos-plugin…

:link: Demo app: https://plugin-demo-iframe.bubbleapps…
:link: Demo editor: https://bubble.io/page?name=index&id…

:link: Documentation: https://www.notion.so/Embed-iFrame-Detector-…

:gift: WIN IT

The first 3 people to suggest an improvement track will have a free lifetime license!


This plugin is made by the French platform Ottho.

ottho

2 Likes

Is there a way to block individuals from iFrameing? If not, maybe that’s a suggestion?

Hi @johnny No really a feature to block iFraming but the plugin can be used for that. You can, for instance, put on condition on your groups to not show or redirect the user if the page is rendered in an iFrame :slightly_smiling_face:

1 Like

Hi

Nice plugin.

It does not seem to be working with the new responsive engine engine.

Any plans on updating it?

Thanks
ZubairLK

Hey @ZubairLK

What’s the issue?

The parent url is the app’s own domain/url and not the actual parent that is iframing url

Curious bug, I’ll look into it before next week :+1:t3:

Hi @vnihoul77 , plugin doesn’t seem to be picking right parent url in Shopify. It is not picking the path

Hey @alan.thomas111997
As stated in the documentation, in most cases the plugin can only retrieve the parent host URL, and not the full URL.

This is because of browser-based restrictions: Referrer-Policy - HTTP | MDN

:frowning:

My bad, I missed this. Thanks for sharing @vnihoul77 .