Problem with Borlabs Cookie Plugin Compatibility

Lord_Chrisi · February 26

Hello,

I am having a problem with compatibility with the plugin: Borlabs Cookie.

I have already been in contact with Borlabs Cookie support about this, and they have referred me to the theme developer.

The issue is that content such as Google Maps or YouTube is not/cannot be blocked by the plugin on "post pages / news pages". On "normal pages", these can be blocked by the plugin.

They said: "There are no hooks available for us to work with."

However, it works on normal pages. Could it be that you still need to adjust something on the post pages / news pages for this to work?

You can see here that the content is blocked (normal page):

https://metal-check.group/schulung-ausbildung/

Here, however, the content is not blocked (news page):

https://metal-check.group/erste-kurse/

In both pages, the videos are inserted the same way, with the video module from BeBuilder.

Could you please take a look at this?

Best regards,

Christoph

Phil · February 26

Hi,

We do not support this plugin. However, please ask the plugin support what hooks are needed, and we will check if we can add them.

Thanks

Lord_Chrisi · February 26

thanks, I will ask the plugin developer about what exactly is needed.

Any GDPR that you recommend with your theme?

Phil · February 27

We have a built-in GDPR feature in Theme options.

https://support.muffingroup.com/video-tutorials/gdpr-2-0/

Best regards

Lord_Chrisi · February 27

This is the reaction of the plugin support

It’s best to filter the content of a page (HTML) through the_content or a custom filter.

"Am besten sie filtern den Inhalt einer Seite (HTML) durch the_content oder einen eigenen Filter."

Phil · February 27

Putting BeBuilder content in the the_content filter is impossible because it is a JS object.

Best regards

Lord_Chrisi · February 27

ok, can you implement it the way it's done on "normal pages"?

Because the plugin woks on normal pages but only woorks not on news pages

Phil · February 27

Regular pages are built the same way as posts. We do not know how this plugin works, and from our point of view, we do not see any difference, so we have no idea why it works for pages and not for posts.

With such lack of details, we are not able to help, unfortunately.

Best regards

Lord_Chrisi · March 5

i just got Info from plugin, developer:

For a seamless integration to detect iframes, we suggest you provide a filter function for your rendered content.

It seems that all your template files render the actual content via the Mfn_Builder_Front class in method show(). It would be beneficial if you could provide a filter before outputting the html.This could be done by using an output buffer, e.g. start the buffer at the beginning of the function show() and stop it at the end of said function the output buffer, provide a filter and echo it. Other than that there would not be any required changes. It could look something like this:

public function show($items = false, $vbtoolsoff = false) {
  ob_start();
  // all existing code
  $content = ob_get_contents();
  ob_end_clean();
  echo apply_filters('your/plugin/filter/name', $content);
}

To clarify why it works for pages but not for posts: For pages you offer two actions in your page template, mfn_before_content and mfn_after_content, on which we start and end an output buffer, to search for iframes. For other content types, there is no such hook available. A filter on your side would lead to much cleaner code than when an start/end action. After you have provided the new filter, we would also adapt our existing integration for pages.

Phil · March 5

I have passed it on to the dev team.

As soon as I hear back from them, I will let you know.

Best regards

Lord_Chrisi · March 5

Thank you!

Phil · March 7

Turning on the buffer for the whole content might have a negative impact on other plugins' functionality, but we will add the action same action mfn_before_content / after as for the pages.

We will add this action in the upcoming updates.

Best regards

Problem with Borlabs Cookie Plugin Compatibility

Comments