Fatal error: Class ‘MaxButtons\maxButton’ on attempted ‘Clear button cache’

Hi Ian,

This is a bug, thanks for letting us know. We’ll fix this in the next version.

Is there any urgent reason for attempting to reset the cache? Usually you wouldn’t need the button unless you have some issues with the plugin.

Hi,

I’d noticed some issues with a button rendering – it initially draws in the wrong colour before finally correcting itself. When the webpage containing the button loads more slowly the effect is noticeable. I was hoping that clearing the cache would resolve, but have been unable to try this due to the error described.

My subsequent test was going to be to create the button from new, which I still might try.

Urgency,… not massively so, but resolving my render issue would be great.

Thanks for your help

Ian…

Hi,

Find the button and hitting the save button will also clear the cache (of that button).

You can post a link to the page you are having problems with, it sounds like something is overwriting the style of the button. I can have a look and tell you what I think.

Thanks

I hadn’t appreciated that saving the button would clear the cache – makes sense.
Sounds like an issue unrelated to the button cache.

You’ll find the button here on a development site; https://web01-dvl.mmuk.net/.

The ‘SUBSCRIBE’ button on the slider seems to display in a purple font and briefly italicises before finally being rendered correctly.

Ian…

I checked. What I see is a flash second of a different color ( the same color actually as the background of the ‘what we do’ title in a different font.

The reason is that some styling loads on top and the plugin loads the style by default in the bottom footer of the page ( this is considered better for SEO and load times ).

The term for it is ‘flash of unstyled content’ ( https://en.wikipedia.org/wiki/Flash_of_unstyled_content )

To solve it in general you can try to make the site render / load faster by implementing something like caching, optimizing images and such.

You can try to change the shortcode as well by adding [maxbutton id=’x’ style=’inline’] ( change the button id of course ).

This will cause the style to load just before the button is loaded so the effect should be much less ( or hopefully none ) .

• This reply was modified 7 years, 10 months ago by Bas Schuiling.

Thanks. I learn something new every day.

Adding style=’inline’ to the MaxButtons shortcode seems to have resolved this.

Thanks massively for your help.

Ian…

Hooray! This one is resolved then.