Crisoforo Gaspar

Thanks for your comments @feverinlove and I agree with this behavior in fact we do have an open issue with a suggested approach that you can find it here:

– https://github.com/WordPress/performance/issues/155

Link to the open document can be found here:

– https://github.com/WordPress/performance/issues/155#issuecomment-1059273330

In case you want to take a look and provide some feedback.

Thanks for confirming this is not working on your site I have been working on trying to replicate your setup however I faced some issues while trying to locate some of your plugins and theme in the plugins repository.

Would you mind testing the plugin by deactivating the following plugins and testing with the theme: https://pcm.www.ads-software.com/themes/twentytwentytwo/

Plugins to deactivate:

– pixfort Core: version: 2.1.7, author: pixfort, Mises à jour auto désactivées
– PixFort Likes: version: 1.0.2, author: PixFort, Mises à jour auto désactivées

Another approach is just by using Twenty Twenty-two and only activate the Performance plugin, this is to verify the Performance plugin might be facing a conflict with any of your plugins or theme.

Thanks for your help troubleshooting this one @arashtoo

Hey @arashtoo

We identified another problem that was preventing in some installations the generation of WebP images. This would be released in the upcoming version on April 4th, in the meantime, we have a workaround that you can test and include in your functions.php

– https://github.com/WordPress/performance/issues/258#issuecomment-1077055885

This is the link of the report as well https://github.com/WordPress/performance/issues/258 in case you have any additional findings, please let us know in case the workaround didn’t work for you or in case it did, once the new version is released the workaround won’t be required anymore so feel free to remove it once we publish the new version.

Let us know as well in case you face any additional problems or issues with this workaround or any additional problem with the plugin.

Thanks again for your report and taking the time to test the plugin.

Hey @fabioassenzio thank you for your report we were able to identify this problem and we are looking to release this as part of the upcoming release 1.0.0.beta-4 the next week however there’s a workaround you can use described on this ticket: https://github.com/WordPress/performance/issues/258

Code with the workaround that you can include on your functions.php file can be found here: https://github.com/WordPress/performance/issues/258#issuecomment-1077055885

Let us know if that works for you after the workaround is applied try to upload a new image after the release is completed the workaround won’t be required any more

Thank you for creating this page for us to verify this problem in your setup. I’m going to try to replicate an environment closer to yours in order to see if I can replicate the error based on the configuration presented above.

If I might ask a couple of questions to verify this is behavior is not introduced or modified by another plugin/theme:

• Would you mind disabling all plugins besides the *Performance* plugin and retrying uploading an image and observing if the webp images were created.
• If the above didn’t work on top of that would you mind switching to a default theme like Twenty Twenty-Two

In addition to those tests would you mind describing the process you are using to upload your images?

Thank you @fabioassenzio so much for your effort in getting this resolved and for your patience. Let me know in case you have any additional questions, on my end would work on trying to recreate an environment with your hosting settings to see if I’m able to replicate the bug.

Thanks for sharing this with us, it sounds like the WebP is supported and working based on your settings above, can you replicate the following steps with us and share the results:

1. Create a new post
2. Upload a new JPEG image into your media library
3. Insert the image into the content of your post.
4. Publish your post
5. Share the markup generated by your post content here with us.

Additionally that if you have access to your server, can you review that *.webp files were not stored on your server?

When I upload a jpeg image from the media library nothing happens, the image remains in jpeg and I think it’s the normal behaviour.

Just to clarify images would remain loading as JPEG in the admin and media library, the plugin creates a new version without replacing the original image. When an image is inserted into the content an a WebP image size is available it would be loaded if not original JPEG would be served instead.

Let us know how that goes and in case you have additional questions. Thank you for taking a look at this and for giving us your feedback on the Performance Plugin, is really helpful for us to keep improving it, so looking forward to hear back from you.

Hey!

Thanks a lot for your report, would you mind helping us to debug this issue by sharing with us the following results:

Checking the support of WebP on your server, by going into Tools > Site Health and checking in the Passed tests dropdown to see if you can find the Your site supports Webp.

Lastly, would you mind going into the Info tab on the Site Health module as well and clicking in Copy site info to clipboard, then sharing the copied data here so we can take a closer look at your current setup?

Thanks again for your report and for sharing with us the output of those steps described above.

Thank you for your report.

Usually this cron is used to process EA imports, (EA is the service used to pull events from external sources such as Google Calendar and such) if you are not an active or a user of EA you should be good to remove this cron work, on the other hand if you are expecting to have schedule events coming in from EA source you might need to change your type of import from Cron to Async, on the Import settings tag of TEC plugin.

I’m going to take a look at this into our internal bug track system in order for us to run a bit more of investigation around this cron as only should be executed if you have active EA license running to process schedule events.

Please let us know in case you have additional questions and thanks for reaching out.

Thank you for your report, based on the error we can identify that you are using Promoter (and you are experiencing some connection errors), the error itself is used to identify any time your site has problems to notify promoter of any changes on your WordPress installation.

Additionally to this it looks like your site is reporting all warning errors, usually warnings does not prevent any functionality from working as expected, so you might want to change the level of verbosity of your logs in case you are looking to remove this specific notice from your logs with the following snippet.

function change_tribe_log_level() {
   return 'ERROR';
}
add_filter( 'tribe_log_level', 'change_tribe_log_level');

However I think we can change the level of verbosity on upcoming releases for this logged value so on upcoming releases this notice is only registered at debug level.

Please let us know in case you have additional questions about this report, thank you for reaching out.

Muchas gracias por tus comentarios que para nosotros son muy importantes saber que estamos haciendo un gran trabajo.

Seguiremos trabajando para seguir entregando mejoras al plugin y seguir teniendo a nuestros usuarios felices.