doffine

Hi Kenneth,
thanks for answering all our questions. Great support!

We’re using your free plugin as well as your pro plugin version (on different websites of course) and we have the Explicit Consent Mode active in the pro version but the “wgact” is still being loaded before consent is given. We followed your guide on how to use your plugin with the Borlabs Consent Tool and it seems to be working except for the “wgact” source.

Our question now is: How can we block the “wgact” even though we already have the Explicit Consent Mode active?

Thank you in advance!

Hello @shehabulislam,

no problem.

The exact name of the plugin I install is “Html5 Video Player – mp4 player, Video Player for WordPress”. I guess the slug is “html5-video-player” – at least that’s the plugin’s folder name.

It is really not difficult to reproduce the bugs I stated above. It costs only a few clicks.

1. Surf to wpsandbox.net
2. Click on “Create test site”.
3. Wait some seconds and log in there.
4. Then you install and activate nothing but your plugin.
5. Activate your browser’s JS console.
6. Get back to admin dashboard and, to be safe, reload it one time.
7. You’ll see the JS errors related to paypal.com addresses.

If you want to see more…
Also on the dashboard: Take then a look with Firefox and Chrome in the external sources where connections are made to. There are a lot. As soon as you deactivate your plugin they are all gone.

And if you want to see even a clear bug…
Go to “Appearance” > “Add new” and you will see that the “Upload Theme” button doesn’t work as long as your plugin is activated.

Greetings,
-doffine

Hello @shehabulislam,

two times sorry: 1) I didn’t get an email to your first response, so I couldn’t react in time. 2) It was my fault to write about a “YouTube WordPress plugin”. I’m just the technician here, not the one using this plugin. But, indeed, I meant your plugin – no other.

So I have to substantiate that your plugin causes some problems. That is completely reproducible.

If you don’t believe, please just go to wpsandbox.net, get you a fresh WP installation and just install + activate your plugin – nothing else.

(At least) in the admin dashboard…

1) …you will find several JavaScript console errors having something to do with paypal.com – I think it has got something to do with your dashboard widget.

2) …you will find many external connections. Also take a look with Firefox in the external connections (F12 > Debugger > Sources), not only with Chrome.

3) As long as your plugin is active installing a theme manually from a ZIP file doesn’t work, since in “Appearance” > “Add new” the “Upload Theme” button on the top doesn’t work / is no more clickable. As soon as we deactivate your plugin this button works again.

So I revoked the mark as “resolved” of this thread for now.

Please try the above on your own.

Greetings,
-doffine

Hello @themefic,

done. We sent the message to you.

-doffine

Hello @inputwp,

we found the reason for this bug: Its your file…

/wp-content/plugins/date-time-picker-field/assets/css/custom-admin-styles.css?ver=1.0.0

In line 417 of your file you’ll find the following CSS:

.metabox-holder {
  border: 1px solid #ccc !important;
  border-radius: 8px !important;
}

As soon as this CSS is disabled, the annoying empty box is gone.

The question is: Why do you use this CSS and why is it set up in a way that causes this irritating empty box on the dashboard?

Will you make a fix making this disappear?

Greetings,
-doffine

Hey @macmanx,

thank you very much for your answer. Most interesting for us is the question if wordpress.org themselves closed this plugin and the other ones of the author.

For these plugins there were updates yesterday, and a few hours later all of them were closed. Additionally the plugins no longer are listed as the author’s ones in his profile. In our eyes this somehow looks like not the author himself did the closure and those things. And if wordpress.org did the closure they must have had a reason. And if there was a reason it seems quite not unlikely that the reason has a security background.

Isn’t there a possibility that wordpress.org just makes a statement “We didn’t do the closure.” or “We did the closure, and the reason was …”? This would do something against the current uncertainty of situation. And it would be good for transparency.

Can you do something about this – can we get such a simple statement of wordpress.org to this plugin closure?

Or – if wordpress.org makes a closure on their own – is it usual, that in such cases a shroud of silence is put over it?

Greetings,
-doffine

Hi @strategio,

ah, thank you for this information.

Greetings,
-doffine