Konstantin

I just wasted a couple of hours fighting the same issue and still not 100% sure if everything works as it should. I have to admit your warning messages are somewhat confusing. Not sure how the following message can be considered as optional:
For online services to work correctly, you must allowlist all QUIC.cloud server IPs.

It sounds like a strick requirement to me. So, it would be nice if those warnings had clearer messages.

• This reply was modified 12 months ago by Konstantin.

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,
Kon

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, 6 months ago by Konstantin.

Hi @yithemes

I faced with the same issue and your code doesn’t work for me either.
I’ve tested it on multiple themes, with and without other plugins enabled.

What is more, I found that activating your plugin also breaks default blog comments. They also stop displaying comments on moderation.

I wonder if you plan to fix this in future updates?
Letting users know that their comment or review was submitted is crucially important. Especially, that it’s working fine in default wordpress comments.

Regards,
Kon

Hi @cartflows

Thank you so much for your help. Your code works for me perfectly fine. Very much appreciate your help on this one.

Cheers,
Kon

Hi Hannah,

Thanks for your help on this one.
I’ve managed to import this template. Initially I was trying to import .zip file instead of .dat

Quick readme file inside of the archive would definitely be helpful.

Many thanks,
Kon

Hi @cartflows

Thanks your reply and the article on this topic. I’ve adjusted my code accordingly:

function override_cartflows_template($template, $template_name, $template_path) {
    if ($template_name == 'checkout/form-login.php') {
        $template = 'wp-content/themes/hello-theme-child-master/woocommerce/checkout/form-login.php';
    }
    return $template;
}
add_filter('woocommerce_locate_template', 'override_cartflows_template', 20, 3);

In the article you mentioned, they use absolute path to the template, but in my case it doesn’t work.
Unfortunately, I don’t have a lot of experience with WP functions and would really appreciate your help on this one.

Many thanks,
Kon

Hi @cartflows

Thanks for your reply.
I was trying to use the following code to point to my template, but looks like I’m doing something wrong

add_filter( 'woocommerce_locate_template', 'override_cartflows_template', 10, 3 );
function override_cartflows_template( $template, $template_name, $template_path ) {
	if ( 'form-login.php' === basename( $template ) ) {
		$template = 'wp-content/themes/my-child-theme/woocommerce/checkout/form-login.php';
	}
	return $template;
}

I wonder if you could help me to figure out why it’s not working?

Many thanks,
Kon

• This reply was modified 4 years, 9 months ago by Konstantin.
• This reply was modified 4 years, 9 months ago by Konstantin.

Hi OceanWP Team,

I’ve recently faced with the same issue. I had tried all of the above suggestions, but nothing works.
During my troubleshooting I was disabling different plugins to find the conflicting one and I’ve finally found it. That’s Elementor Pro.
When I turn it off, Cart Menu displays properly. I assume, that’s because Elementor Pro also has Woo Cart widget and somehow they conflict.
Obviously, I can’t stop using Elementor Pro, so I would really appreciate to have some fix.

Many thanks,
Kon

In the last way, I restored Nextgen Gallery 2.0.30. I was wondering because the error was removed. In order to restore Lightbox Effects functionality, I opened section “Other Options” – “Lightbox Effects” – “Show Advanced Settings” and changed domain name at “Stylesheet URL” and “Javascript URL”. After that I updated Nextgen Gallery to the latest version. In my case the error hasn’t appeared.

I have the same problem. I tried to solve the problem in different ways.
I replaced domain name in DB-backup many times. All times my site worked perfectly, before I began to use Nextgen Gallery.

How replacing domain name in DB-backup can break Nextgen Gallery?
I can’t find any string pertinent to Nextgen Gallery options and include domain name.

Thanks…

Hi Everyone,

I use:
Wordpress 3.8
WordPress SEO 1.4.20
NextGEN Gallery 2.0.30

I have a little trouble with my sitemap.
https://yana-butenko.com/blog-type-sitemap.xml

It doesn’t include all images from NextGEN Gallery which added to post. For adding images in my posts I use “NextGEN Basic SinglePic” and “NextGEN Basic Thumbnails”. As a result my sitemap includes all singlepic and all preview singlepic, also it includes my post’s miniature.
But the sitemap not includes all images added through NextGEN Basic Thumbnails.

If you’ll see my sitemap, you can see that the first string of the sitemap shows that post has 3 images. There are 6 images in this post really. Here is code:

<url>
<loc>https://yana-butenko.com/ru/blogs/37-moskovskaya-mezhdunarodnaya-vyistavka-obrazovanie-i-karera-21-vek</loc>
<lastmod>2013-10-06T19:10:39+00:00</lastmod>
<changefreq>weekly</changefreq>
<priority>0.6</priority>
<image:image>
<image:loc>https://yana-butenko.com/images/ngg_featured/20130228_00.jpg</image:loc>
</image:image>
<image:image>
<image:loc>https://yana-butenko.com/nextgen-attach_to_post/preview/id--1548</image:loc>
</image:image>
<image:image>
<image:loc>https://yana-butenko.com/images/gallery/blog20130228/20130228_01.jpg</image:loc>
<image:title>blog20130228</image:title>
<image:caption>20130228_01</image:caption>
</image:image>
</url>

Mark,
I tried to use your code for sitemap.php but then the sitemap includes preview singlepic and post’s miniature, but not includes fullscreen singlepic. Here is code:

<url>
<loc>https://yana-butenko.com/ru/blogs/37-moskovskaya-mezhdunarodnaya-vyistavka-obrazovanie-i-karera-21-vek</loc>
<lastmod>2013-10-06T19:10:39+00:00</lastmod>
<changefreq>weekly</changefreq>
<priority>0.6</priority>
<image:image>
<image:loc>https://yana-butenko.com/images/ngg_featured/20130228_00.jpg</image:loc>
</image:image>
<image:image>
<image:loc>https://yana-butenko.com/nextgen-attach_to_post/preview/id--1548</image:loc>
</image:image>
</url>

Help me, please. How can I add images which added through NextGEN Basic Thumbnails to my sitemap?

Thanks…

Peter,

You’re right. My hoster demand memory limit (64Mb for one process). I checked my web-server’s log file and found this string:
[Sat Dec 14 18:38:05 2013] [error] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 536 bytes) in /public_html/wp-includes/pomo/streams.php on line 66

After long Googling this trouble I found solution:
Add “define(‘WP_MEMORY_LIMIT’, ‘128M’);” in “wp-config.php”

After this I could deactivate AIOSP without problem.
But I don’t understand how this solution allows overcome my hoster’s demand.

Peter, what do you mean when you wrote about “open a new thread”. Can you tell me more details about this?

Thanks…

Hi, everyone.

I also use AIOSP together with WPML.
I’m having other issue:
When I try to deactivate AIOSP I lose access to my site’s admin panel, ‘wp-admin’ just doesn’t open. The only way to restore access to admin panel – rename folders ‘sitepress-multilingual-cms’ and ‘all-in-one-seo-pack’.
Both plugins deactivate, but I can activate WPML only after activating AIOSP, otherwise ‘wp-admin’ again doesn’t open.

Help me, please. How can I deactivate AIOSP?

Thanks…