mattce

After some testing, it seems, that the cronjobs were a problem in my case. I’ll close this ticket to not confuse you, no support needed anymore.

Hey, the affected site is currently running php version 8.0.24

Thanks for the quick fix!

I was waiting for further infos, since it was reported to me from another developer, but glad you find it anyway.

Have a nice weekend!

Great, this is what I am looking for, thanks!

Hi Takayuki,
I’ve send you the url via your contact form, since it’s a clients’ site, I’m not allowed to share it in public. Hopefully, it will not get blocked. The subject is referring to this thread no. 15858592

Yes, I can confirm, the preload tags have gone, problem seems to be fixed with the latest beta update. Thanks a lot for your effort!

Thanks for the beta version, unfortunately, it didn’t fix the issue.

I can’t give you access to this project (belongs to a client), but if any logs would help to get behind it, I can surely send them over

Plugins in use:

Advanced Custom Fields PRO
Classic Editor
Classic Widgets
Contextual Related Posts
Custom Post Type UI
Custom Sidebars
Disable Feeds	
Edit Author Slug
Loco Translate
WP-PageNavi
Yoast SEO

Our site is a multisite, the AO settings are all handled inside the network page, individual settings per site are turned “off”. Same for the meta box inside the pages/posts, “Enable configuration per post” is checked off.

Images settings (inside its own tab) are:
Optimize Images [] (off)
Lazy-Load Images [x]
Lazy-Load Exclusions: “loaded” (so one class only)
Lazy-load from nth image: “1” (all)

All further settings can be found here:

View post on imgur.com

One customization, we’ve enabled this filter:

add_filter('autoptimize_separate_blog_caches','__return_false');

via a mu-plugin

The problem only occurs for logged-out users (see second last checkbox, which is checked off)

• This reply was modified 2 years, 7 months ago by mattce.

Hi,
we’re using the lazy load feature from the “images” tab, that’s right. So the filter_lazyload_images filter is adding every image into a preload tag, that is using lazy load? If we’re using “1” (“lazyload all”), it’s adding every image from the whole page inside these tags? In our case, we’re ending up with about 300-400 tags, which is massively blowing up our html code and therefore has negative impact on the performance.

Could you add a filter (or an option) to seperate these functions, so that one can disable it, if not needed/wanted?

Found the problem myself, someone has removed ALL redirect groups. I’ve created a new one named “General” and now it’s possible again to create redirects.

Marking this thread it as solved, thanks anyway ??

Thanks a lot! And I hope you’re feeling well ??

I’m also having this issue, if you could publish the new version soon, it would be great! Thanks a lot!

Is it possible to use this action to add the x-default?

https://msls.co/developer-docs/snippets-examples.html#the-blog-collection

By saying if $blog->get_language() == “<my needed language”) and adding an additional link alternate tag? But how do I get the current url in this action? Wasn’t able to find it in the $blog variable at all, is it possible to access it inside this action?

I’m also needing this at the moment, I will integrate the x-default manually via filter then.

But maybe it’s a good idea for a future update, to add a checkbox in the language settings screen, where you can set a specific language version as x-default and then this tag will automatically getting outputted besides the normal hreflang tag ??

Hi Michael, sorry for the late response. Yes, I’ve added this piece of code, in my case I’m using

add_action( 'init', 'cptui_register_my_taxes' ); for my cptui_register_my_taxes() function

as suggested in the plugin’s export page directly.

“Query monitor” (the plugin) is also showing an error:

Invalid argument supplied for foreach() in wp-includes/class-wp-post-type.php:655

This part is looping the taxonomies that should get registered:

public function register_taxonomies() {
foreach ( $this->taxonomies as $taxonomy ) {
register_taxonomy_for_object_type( $taxonomy, $this->name );
}
}

I don’t know what’s wrong, the taxonomy appears in the backend, creating terms is also working, but some wp functions claim, that it’s invalid. But seems, that I’m the only one with this problem, since no one else is complaining about it. ??

For the moment I’ve disabled the init action and let the plugin doing its magic to register the post type by itself. Via code in the functions.php was useful since I’m needing them on several subsites on my multisite installation, but no drama. We’ll see if someone else is also confronted with the same issue.