Dirk S

Hi Chris,
with secured I actually meant restricted access to blog. Only a defined group of users has access (probably via s2member plugin or similar). So if the wordpress plugin pushes information to the Pushover servers, it should still work. Contrary to pulling the RSS Feed, which should be restricted as well – I hope.

Its now more of a general question, which data will be pushed. Probably everybody could sign up for this channel at Pushover? If users are then routed back to the server for more information related to the message, at least access control is in place….

I used:

[video mp4="https://www.webzunder.com/de/files/videos/Online-Marketing-Assistent-fuer-KMU.mp4"]

Should I set a size if its set to responsive anyway?

OK. I did a workaround by adding a class to the responsive video div wrapper mentioned. But I needed to make the change directly in video-js.php … maybe you can add a class to it in a next release? So everyone can style positioning when using responsive settings.

Hi Dustin,
tried that, however – before the div video wrapper is another div:
<div style="max-width:640px;>"

I think I need to be able to add centering here. With adding aligncenter to my shortcode, I only center the video in the left aligned wrapper.

Its something else: the 30 px seems to be related to class=”vjs-poster”
Out of an original preview picture of 640×360 it streches it to 640×390…

That will probably stay the size for the video wrapper, adding a black bar of 15px above and below.

It might also be the style="padding-bottom:56.25%;" in the video Wrapper. If I lower it, the black bars get smaller…

please have a look at https://www.webZunder.com/

Thanks a lot!

can confirm the bug with 1.8.3 as well. have a new user as editor who can’t see the frontend

yes, sent it to your facebook account.

my own installation…

Found out it was activated (but still not used) for all blogs. Network deactivation and single blog activation solved it.

Ups, yes you are right! Thanks for fixing so quickly.

Release 2.3.6 seems to have fixed this issue.

I opened a new thread related to the plugin itself.