Sovica

@jobiwon9178 We have released a new plugin version which fixes the PHP notice you mentioned. Please update to 3.5.4 and let us know if you still see them.

Hi,

This usually happens if your site is already registered with a different user account or an invalid user account is being used to login into the system and used for verification services.

If you need any further help please reach out to use via a ticket here – https://brid.zendesk.com/hc/en-us/articles/200302562

Hi,

Thanks for reporting this.
I have forwarded this to our dev so they can take a look into this warning and fix it on our next WP plugin release.

@sneader Just wanted to inform your that we have pushed a new release live which returns support for PHP 5.6. Apologies for any inconvenience caused.

Hi,

I’ll confirm with my team about this and get back to you. It was not intentional to require a PHP upgrade.

Hi,

We are aware of this notice.
This is already fixed in our dev environment and is in Q&A before it is pushed to the WP repository. The next release will have this issue fixed.

Hi,

First please try to re-install the plugin and do a new authorization. This may fix the issue at hand.
If this doesn’t work, then please tell us what site you have registered with us in Brid.

Hi,

Apologies for the late reply here!

The planned usage of this specific input field in our system is to be used with our newly planned player bidding system which would take into account the CPM of your ad tag and many other variables to create an optimum rotation of your current waterfall.

This is currently a placeholder value only and will be used in our bidding process in the future. This value has no influence on the CPM of your ad tag.

Davide,

It looks like that the ampforwp plugin added inherit support for our player in the AMP ecosystem so it references the required JS file and so do we so there is a double-reference currently.

We’ll be pushing a change to our plugin so that we remove our reference and let the ampforwp plugin do this instead of us as it seems to be the fastest way to fix this inconsistency.

You can expect a new plugin version of our plugin today regarding this.

Thanks for bringing this to our attention.

Hi Davide,

What Brid plugin version are you using and also what AMP plugin are you using?
Do you also perhaps have an example page where we can see this problem?

No, this is not possible.

Hi,

This specific video file has CORS permissions to playback on only specific domains. Footballorgin.com is one of these domains.
Most likely the reason why this video does not work on your or any other domain is due to these CORS restrictions.

Hi,

First, thanks for leaving a review.

Regarding adult content. We clearly state in our help desk located here – https://brid.zendesk.com/hc/en-us/articles/201492741 and the Brid video platforms TOS located here https://cms.brid.tv/pages/view/terms-conditions that adult content is strictly prohibited and will be removed without any notice. This applies to our WordPress plugin as well as it uses our Brid video CMS backend API.

Before a user registers a new account in Brid through the plugin, the user must accept our TOS which is clearly stated on the register page when a user creates an account. By creating an account with Brid, you have accepted our TOS and this TOS is clearly visible and fully accessible on the register page – https://cms.brid.tv/pages/view/terms-conditions

Our blog site @ https://brid.tv (which your screenshot shows) is, in fact, a separate entity from our Brid Video CMS platform and may not have the same TOS so you were looking in the wrong place for our Brid video platform TOS. But thank you for bringing the blank page for our blog TOS to our attention as we will setup a proper TOS for our blog site as well.

You are still free to use our system for non-adult content but adult content will be removed promptly without any prior notice.

Sorry for the late reply.

Have you tried the widget shortcode as described in our FAQ here – https://www.ads-software.com/plugins/brid-video-easy-publish/faq/

The jQuery mobile code is used for the Brid playlist widget for scrolling on mobile devices.
Without it the mobile scroll functionality probably won’t work.

We’ll definitely though address this issue in a future release and try to migrate away from the jQuery plugin.
Thank you for bringing this to our attention.