WEBP Generating Issue
-
Hi Team,
I tried to enable the “Use WebP Images” option in SG Optimizer, but it could not generate them. After clicking “Confirm”, it displays a spinning wheel with “Converting 1 of 295” message. I left it in this stage for more than an hour, but nothing changed.
I would highly appreciate if you can investigate this issue.
Many thanks,
Kon
-
Hello @k0stell0,
Most probably some of the other plugins installed on your site are blocking the REST API, hence the issue. You can check that by examining the browser console for any errors after starting the WebP conversion process.
Additionally, you can check if the cron event that starts the conversion process is presented:
siteground_optimizer_start_webp_conversion_cron
If not, you can restart it using the following command:
wp cron event run siteground_optimizer_start_webp_conversion_cron >/dev/null 2>&1
In case you are still experiencing the issue, please provide us with the URL in question so we can check the case further.
Thanks for your prompt reply, Delyan!
I just checked the browser console and found that as soon as I open SG Optimizer in WP Admin I get a lot of errors. Please see them below:
backbone.marionette.min.js?ver=2.4.5.e1:24 Uncaught TypeError: Cannot read properties of undefined (reading 'vent') at backbone.marionette.min.js?ver=2.4.5.e1:24:5395 at bt (main.min.js?ver=7.2.1:2:55442) at Function.bi (main.min.js?ver=7.2.1:2:90623) at backbone.marionette.min.js?ver=2.4.5.e1:24:5369 at bt (main.min.js?ver=7.2.1:2:55442) at Function.bi (main.min.js?ver=7.2.1:2:90623) at c._proxyMethods (backbone.marionette.min.js?ver=2.4.5.e1:24:5321) at new c (backbone.marionette.min.js?ver=2.4.5.e1:24:5052) at backbone.marionette.min.js?ver=2.4.5.e1:24:5793 at backbone.marionette.min.js?ver=2.4.5.e1:24:5799 (anonymous) @ backbone.marionette.min.js?ver=2.4.5.e1:24 bt @ main.min.js?ver=7.2.1:2 bi @ main.min.js?ver=7.2.1:2 (anonymous) @ backbone.marionette.min.js?ver=2.4.5.e1:24 bt @ main.min.js?ver=7.2.1:2 bi @ main.min.js?ver=7.2.1:2 _proxyMethods @ backbone.marionette.min.js?ver=2.4.5.e1:24 c @ backbone.marionette.min.js?ver=2.4.5.e1:24 (anonymous) @ backbone.marionette.min.js?ver=2.4.5.e1:24 (anonymous) @ backbone.marionette.min.js?ver=2.4.5.e1:24 (anonymous) @ backbone.marionette.min.js?ver=2.4.5.e1:24 (anonymous) @ backbone.marionette.min.js?ver=2.4.5.e1:24 (anonymous) @ backbone.marionette.min.js?ver=2.4.5.e1:24 common-modules.min.js?ver=3.6.8:3 Uncaught ReferenceError: Marionette is not defined at 99107 (common-modules.min.js?ver=3.6.8:3:59471) at __webpack_require__ (common-modules.min.js?ver=3.6.8:3:103972) at 56525 (common-modules.min.js?ver=3.6.8:3:59695) at __webpack_require__ (common-modules.min.js?ver=3.6.8:3:103972) at common-modules.min.js?ver=3.6.8:3:104515 at common-modules.min.js?ver=3.6.8:3:105228 at common-modules.min.js?ver=3.6.8:3:105232 99107 @ common-modules.min.js?ver=3.6.8:3 __webpack_require__ @ common-modules.min.js?ver=3.6.8:3 56525 @ common-modules.min.js?ver=3.6.8:3 __webpack_require__ @ common-modules.min.js?ver=3.6.8:3 (anonymous) @ common-modules.min.js?ver=3.6.8:3 (anonymous) @ common-modules.min.js?ver=3.6.8:3 (anonymous) @ common-modules.min.js?ver=3.6.8:3 common.min.js?ver=3.6.8:3 Uncaught ReferenceError: Marionette is not defined at 13448 (common.min.js?ver=3.6.8:3:94443) at __webpack_require__ (common.min.js?ver=3.6.8:3:143989) at 71362 (common.min.js?ver=3.6.8:3:87633) at __webpack_require__ (common.min.js?ver=3.6.8:3:143989) at 44027 (common.min.js?ver=3.6.8:3:84982) at __webpack_require__ (common.min.js?ver=3.6.8:3:143989) at 27308 (common.min.js?ver=3.6.8:3:89903) at __webpack_require__ (common.min.js?ver=3.6.8:3:143989) at 2365 (common.min.js?ver=3.6.8:3:94692) at __webpack_require__ (common.min.js?ver=3.6.8:3:143989) 13448 @ common.min.js?ver=3.6.8:3 __webpack_require__ @ common.min.js?ver=3.6.8:3 71362 @ common.min.js?ver=3.6.8:3 __webpack_require__ @ common.min.js?ver=3.6.8:3 44027 @ common.min.js?ver=3.6.8:3 __webpack_require__ @ common.min.js?ver=3.6.8:3 27308 @ common.min.js?ver=3.6.8:3 __webpack_require__ @ common.min.js?ver=3.6.8:3 2365 @ common.min.js?ver=3.6.8:3 __webpack_require__ @ common.min.js?ver=3.6.8:3 47729 @ common.min.js?ver=3.6.8:3 __webpack_require__ @ common.min.js?ver=3.6.8:3 36614 @ common.min.js?ver=3.6.8:3 __webpack_require__ @ common.min.js?ver=3.6.8:3 (anonymous) @ common.min.js?ver=3.6.8:3 (anonymous) @ common.min.js?ver=3.6.8:3 (anonymous) @ common.min.js?ver=3.6.8:3 admin.min.js?ver=3.7.3:2 Uncaught ReferenceError: elementorCommon is not defined at CustomIcons.onInit (admin.min.js?ver=3.7.3:2:9136) at Module.trigger (common-modules.min.js?ver=3.6.8:3:54143) at T.each.q.<computed> [as trigger] (common-modules.min.js?ver=3.6.8:3:52783) at init (common-modules.min.js?ver=3.6.8:3:52944) at CustomIcons.Module (common-modules.min.js?ver=3.6.8:3:54221) at new child (common-modules.min.js?ver=3.6.8:3:54454) at CustomIcons._createSuperInternal (admin.min.js?ver=3.7.3:2:2278) at new CustomAssetsBase (admin.min.js?ver=3.7.3:2:2525) at CustomIcons._createSuperInternal (admin.min.js?ver=3.7.3:2:4416) at new CustomIcons (admin.min.js?ver=3.7.3:2:4643) onInit @ admin.min.js?ver=3.7.3:2 Module.trigger @ common-modules.min.js?ver=3.6.8:3 T.each.q.<computed> @ common-modules.min.js?ver=3.6.8:3 init @ common-modules.min.js?ver=3.6.8:3 Module @ common-modules.min.js?ver=3.6.8:3 child @ common-modules.min.js?ver=3.6.8:3 _createSuperInternal @ admin.min.js?ver=3.7.3:2 CustomAssetsBase @ admin.min.js?ver=3.7.3:2 _createSuperInternal @ admin.min.js?ver=3.7.3:2 CustomIcons @ admin.min.js?ver=3.7.3:2 e.exports @ admin.min.js?ver=3.7.3:2 (anonymous) @ admin.min.js?ver=3.7.3:2 (anonymous) @ admin.min.js?ver=3.7.3:2 (anonymous) @ admin.min.js?ver=3.7.3:2 admin-top-bar.min.js?ver=3.6.8:2 Uncaught ReferenceError: elementorCommon is not defined at admin-top-bar.min.js?ver=3.6.8:2:10230 at admin-top-bar.min.js?ver=3.6.8:2:10594 at admin-top-bar.min.js?ver=3.6.8:2:10598
These error messages appear only in WP Admin and only on SG Optimizer pages.
Do you happen to know what might be causing them? Looks like SG Optimizer is conflicting with Elementor, but I can’t disable it as my website is purely made using Elementor.
-
This reply was modified 2 years, 7 months ago by
Konstantin.
The provided errors are actually not related to the WebP conversion process.
Please try checking the browser console after the process starts.Hi Delyan,
Thanks for your reply.
I don’t get any extra errors after starting WebP conversion prosses. Only those I posted above.Sorry for the dumb question, but could you please clarify where can I check WP Cron Events you mentioned in your first reply?
Many thanks,
KonHello @k0stell0,
You may check all running cron events by using the command below:
wp cron event list
The ones added by our plugin should start with siteground_optimizer.
Best regards,
Daniela Ivanova -
This reply was modified 2 years, 7 months ago by
- The topic ‘WEBP Generating Issue’ is closed to new replies.