Grégory Viguier

Hello,

Thank you for reporting this issue. We’re working on this issue and have found a solution.

I believe you are using symlinked MU plugins that are not in open_basedir, am I correct?

Thanks.
Greg

• This reply was modified 1 year, 1 month ago by Grégory Viguier.
• This reply was modified 1 year, 1 month ago by Grégory Viguier.

About the error messages: my colleague says it’s due to php fpm crashing, generally because the RAM is full.

Hello, I’m Grégory, lead developer of Imagify’s plugin.
Sorry to see you have these issues.

1- Imagify also supports this feature since the version 1.7. So if it doesn’t work, we should take a look.

2- That is perfectly normal, this 0 means there is no limit in the height. 0 is what one would use in the media settings to tell any of the 3 available thumbnail sizes there is no limit in width or height.

3- You probably installed a plugin or something that adds a new thumbnail size.
3a- Indeed, we have no bulk for that yet.
3b- I could take a look on the site and tell you.

4- Since Imagify only keeps backup of the main image, like any other image optimization plugin, one can’t simply replace the uploads directory by the backup directory, all thumbnails will be missing, and any other media that are not images or not optimized (and the data would remain in the database anyway, preventing future optimizations). The plugin has no bulk restore feature yet, we know it’s missing and it’s on our road-map. As for the error messages, I have no idea of what it means, this is not my territory.

Regards.

Hello, I’m Grégory, lead developer of Imagify’s plugin.
An issue has been open on our side and some insight from SiteGround would be appreciated.

Hello,

Same cause, different problem: admin notices are displayed behind .wrap, and so they can’t be closed since the button can’t be clicked.

Thanks.

• This reply was modified 6 years, 9 months ago by Grégory Viguier.

Great! I’m a bit surprised it could be solved by emptying Rocket cache. Maybe it’s related to Cloudflare?
Anyway, good thing it could be solved.

OK, I just tested Timeline Express.
I had the same issue with 1.6.14, but 1.6.14.1 fixed it, so it’s obviously the browser cache doing its job.

OK then, can you contact us so I can investigate directly on your site (on Monday ;))? Thanks.

Hello,
If I understand correctly, 1.6.14.1 has an issue but 1.6.14 is fine?

Nice, thanks.

OK, can you contact us so I can investigate directly on your site? Thanks.

OK, can you contact us so I can investigate directly on your site? Thanks.

Hello.
This problem occurred with version 1.6.14, but it should be fixed in 1.6.14.1. Can you try to empty your browser cache? Thanks.
Greg

Hello.
It should be fixed in 1.6.14.1. Can you try to empty your browser cache? Thanks.
Greg

Hello.
It should be fixed indeed. Can you try to empty the browser cache? Thanks.
Greg