tenacityio

They had added the checkbox back in on the link preview in 6.4, so at least it reduced the total number of clicks and unhid the option. But once again, they removed it in 6.5, which is very frustrating.

• This reply was modified 7 months, 3 weeks ago by tenacityio.

@jtsternberg That seems to have eliminated the error and restored the editor. Thank you! That would have taken forever to figure out.

Sure here is all of the related PHP code that use CMB2 in the theme.

https://gist.github.com/tenacityio/a6d3afb28a8192677431b53d610567d1

Registration Code? Like an activation code for the plugin?

Or do you mean the theme code that uses CMB2?

It’s not just Gamipress.

When activated, it reports the following error. (Gamipress not active.) I look at it, and basically, it’s using call_user_func but not limiting parameters.
https://help.tenacity.io/rRu5r0nl

When activated, it also breaks the Standard Editor and WP Bakery (but only on Pages), which makes sense because it’s only being used for Pages in our theme.
https://help.tenacity.io/Jruy0qwR

I think this is likely two separate issues. Gamipress activation generates the same errors since they use CMB2 as a library.

I found the following
https://stackoverflow.com/questions/34116787/cmb2-tinymce-menu-bar-not-showing
But I’ve been through our theme code, and we don’t use wysiwyg fields, so it didn’t apply. Perhaps there is something else?

Ok, thanks. I can probably generate something, based on a baseline wordpress install. Or perhaps from the plugin code, but if it existed already it would be helpful.

Follow up do you have all the rules that AOIS writes to htaccess as a reference or in documentation?

@onesignal To be clear, it’s the CSS files that the Service Worker is caching that matter to us and causing issues.

Is there no way to clear those or prevent them from being cached?

Why does a push notification script need to cache CSS?

@karinapremio Found it.

@karinapremio… yes, is there a way to stop the bar from hiding?

Sorry for the delay.

We just want to “show the bar when the user refreshes the page or visits another page.” Or really just the option to not hide the bar at all.

How is this resolved?

Follow up, as Imagify paid support responded to me there. Imagify has known about this issue since at least October 9, 2020.
https://github.com/wp-media/imagify-plugin/issues/521

The Plugin code and API docs have height and width parameters. JPG compression already uses the scaled image, there is no reason WebP does not. Someone familiar with the plugin code should be able to fix this in less than an hour.

So in the last 22 months, Imagify has potentially made tens of thousands of websites load slower.

@thekendog This seems like such an easy fix just send the “-scaled” version rather than the original version, which seems to be what they do with JPG. Or set the width, which is literally part of their API.

Checking ShortPixel out now; I’ve always stuck with Imagify because of its relationship to WP Rocket. The Smart optimization was annoying, this is unacceptable.

Just discovered this bug today, it literally means that Imagify is making pages heavier if we use WebP… 600,000+ installs