michelgreenwood

Ok, thank you

When I check for compatibility with php 7 I get this error…

In master-slider/includes/init/define.php

—————————————————————————————————————————————
FOUND 2 ERRORS AFFECTING 1 LINE
—————————————————————————————————————————————
32 | ERROR | Function name, class name, namespace name or constant name can not be reserved keyword ‘__dir__’ (since PHP version 5.3)
32 | ERROR | Function name, class name, namespace name or constant name can not be reserved keyword ‘__dir__’ (since PHP version 5.3)
—————————————————————————————————————————————

Hello,

I’m wondering the same thing about php 7. Can we expect Master Slider to be updated, or is it no longer supported.

Hi Tom,

Thanks for the quick answer as always.

That’s a good point. I guess without the extra font styles your bold and italic will fall back to the browser default. I suppose for the general user it’s best to have it the way you do.

Thanks ??

Thanks for taking a look. Maybe I’m looking at google’s response and not the request.

Yes, thanks

https://www.christianpedophile.com

Ok, the problem was with using Rocketloader for javascript/jquery. I am using Cloudeflare, and had that option turned on.

It had been working fine, but suddenly stopped. Maybe something on cloudeflare’s end. Rocketloader works with ajax. Masterslider has an option in settings to load assets on every page (which is supposed to make things work with ajax), but that doesn’t fix the problem for me.

I turned off Rocketloader and it works again.

Ok, I have a few sliders set up. It seems that Masterslider uses that method of loading a blank gif for src, and then the actual file is under data-src…

At the moment, the same slider is working on phones, but not desktops. Idk

I’m having this exact same problem. It seemed to just pop up. The only thing I can think is that I added the ShortPixel image optimizer plugin recently. But now Masterslider is making the img src some blank gif file, and putting the correct url in data-src.

Thanks for the explanation.

I was just going to suggest this. The Customizer makes a separate call for each font option selected. Come on now…

That’s a good article thanks.

It seems the custom css option in 4.7 adds the css to the head. Does that mean Autoptimize will strip that if you choose to aggregate inline css, and include it in the general output file?

Yes, I would do that, but Jetpack inserts a feature that allows you to bypass the theme’s original css, and only use the custom.

Is there another way to do that? I know that’s a bit off topic.

Thanks for clarifying.

https://www.christianpedophile.com

Oops…

Removing the basic WordPress js exclusion is what broke the slider and made aggregating necessary.

That seems obvious now ::headsmack::

Thanks again for the help!