igb10

No, it’s ok. I found a different solution, I just went with Stacking (since “No Stacking” didn’t work). So at least it stacks properly now. Not at 33% as you can see from the above video. But FYI – “No Stacking” didn’t work and kept everything at 33% while stacking. You can see my live page here: https://mbzmaster.com/multimedia-video-box/

Hi Sweta,

Sure, check this video. I have Advanced Columns inside another Advanced Columns. As you can see, all 3 columns keep 33% when I select “No Stacking”, but they stack up when I resize the window. By the way, I love your UAG plugin. It’s so much more useful than Gutenberg…

Here is the video:

I actually just noticed that plugin removed website field on 1 page https://mbzmaster.com/2720000-mercedes-amg-one-project-one-hyper-car-the-short-story/ and maybe a few more, but not on all others – it still shows website field in comments. That’s weird! I’m using the standard twenty seventeen theme, which I didn’t modify much – with standard comments.
Can you please provide CSS? Thank you!

Thank you, and I updated my review accordingly!

Sorry, I just realized I put this in the wrong plugin support, but don’t know how to delete it…

I really don’t have time to deal with PHP errors enabling and figuring how to disable external files. Is there any way to roll back AO to the previous version? Because I haven’t had any problems before..
Or maybe I’ll just wait for the new AO version release and then try to enable it again.
But thank you for trying to help anyway.

If I check-mark “Optimize CSS Code?”, but uncheck “Aggregate CSS-files?” then website works. But as soon as I check both – I get blank page.
I also tried to disable AddToAny plugin, but again if I check both – I get blank page even with addToAny disabled completely.

I don’t have my site non-live, it’s wordpress sitting on the server. If any brackets weren’t closed, something wouldn’t work properly. I also successfully validated CSS at W3C without any issues.

I have to say I just moved my website from Windows server with PHP 5.4 to Linux servers with PHP 7.2. Everything worked fine on IIS, but I think if was a coincidence that at the same time this plugin was updated when I moved. However I didn’t move plugin from my old host, I just did a fresh install on the new server. My website is mbzmaster.com

If I checkmark “Optimize CSS code” – it kills my website and screen is completely blank. If I uncheck it, then everything works, but my page-loading time increased…

Hi Pim,

So here how I made it work:
When I created export, I disselected “plugin files” and “media files”. And after that I was able to create successful export .wpress file to download.

But then I couldn’t upload for a new WP site for some reason. So I uploaded it manually to backup folder. Then it wouldn’t open backup file and I tried about 4 times. So when I almost gave up – it opened on the 5th try! But then again failed to install. Then on the 6th try it worked!

After that I manually FTP all my media file from my old site to the new one. And then I just did a fresh install of the same plugins on the new site, that I had on my old site.

So I didn’t have to downgrade PHP and all my database and the rest of files seem to work on the new Linux servers, as they worked on my Windows server.

Since it’s the 2nd largest video-sharing platform in the world, why not include it in the plugin out the box? So we don’t have to mess with installing yet another plugin… This plugin comes with a lot less popular follow services, so why not add more useful functionality?

I have the same question…

As you know Google isn’t a big fan of slow loading pages, especially they test the speed using slow mobile platform. I’m not even mentioning the bad user experience where you have to wait 10-15 sec for the page to load. I have a lot of media on the page, but when I have 5-10 images on the page at 1k or above resolution… not a lot of people have the patience to wait, plus there is a slide in Google positioning as a result.

I set your widget to serve at 371px width, but it serves at 768 on my home and archive pages. I guess I can live with that. But my most important Post pages are served at 1024 and 1280 – that is excessively high. My Post pages are usually landing pages. I really appreciate your help and responses, but if I can’t reduce the resolution of images, I would need to look maybe for another solution.

I wouldn’t want to lose the responsiveness of images either, but I must limit the served size.

One last question: do you have any suggestions how to force this missing CSS line for your widget’s images:

sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px"

I’m not very good with CSS and can’t figure it out.
Thank you,

I’m trying to understand how it is possible myself. Also I don’t think that both browser and Pingdom don’t know what they are doing..

Clearly I can see from 2 HTML results that I provided from above that there is a difference in HTML of the same image serving at different pages. Bot codes look exactly the same… except the ending:

Here is the ending of HTML code image served at Archive page:
sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px"

Here is the ending of HTML code image served at Post page:
sizes="100vw"

Everything else between 2 CSS codes is the same. The only difference are SIZES attribute. The second image is served at 100 Viewport – 100vw. That’s why it serves 1024px wide or even 1280 if it’s the original size as long as it fits in 100 viewport.. Obviously 2000 will not fit in vw and it is resized to nearest 1024.

Can you fix your plugin that it can serve the same CSS for Post pages as it serves for Archive pages?