Jason LeMahieu (MadtownLems)

Patterns are now renamed?compositions

I just updated to the latest Gutenberg, and do not see any mention of Compositions – only Patterns. I also can’t find any other information about this change. Are you able to provide more information?

There are countless threads about this. The most common reason “open in a new tab” isn’t working for you is because an adblocker extension is blocking the new-tab.js script.

Thank you so much! I would probably leave the functionality in place if it was restricted to Network Admins in multisite, but we don’t want standard Administrators to see it. If there’s a filter for disabling, I should be able to put my own logic in there regarding that.

Cheers!

This is a known issue in 6.4 and is being worked on.

Update: After more testing, this sure looks like a Core bug and is not TT3 specific. I can’t make it work in ANY theme.

From my experiences, that JS file is most typically blocked by Ad Blocker browser extensions.

Just for reference, I got the same error now when logging into a network I haven’t used in a while, running QM 3.10.1. Upgrading to 3.13.1 fixed the issue, as expected.

The error messages have reappeared in the logs after clearing all transients. Any other ideas? Thanks!

Thanks for the quick reply. I’ve deleted all sites’ transients, and will check the logs again in a few days to see if the errors have returned. Cheers!

New posts added that have “page links to” set do not render as the destination link on the frontend anymore, just the short url permalink. This also breaks the “open in new tab” functionality.

On WordPress 6.3.1, I just made a new post, and set the Page Links To value. The link my news archive uses the value from Page Links To, and is working as expected.

When the “open in a new tab” functionality doesn’t work, it’s usually caused by an ad-blocker extension blocking the new-tab.js file from loading.

If Page Links To isn’t working on new posts for you, I encourage you to try it with a core theme and no other plugins installed. We use it on literally hundreds of sites and it works as expected with the most recent (and previous) versions of WordPress, including on brand new posts.

Heya. So while I had installed the latest version, I had simply dropped it on top of a previous one. As such, the old style_tags.php check was still there and trying to run. A complete delete and reinstallation of the current version has resolved it. Thank you so much!

Same experience with suppressed errors and PHP 8 for me, too. Great post, Albert!
Just as another thing to look at, John, I really liked the approach taken in this StackOverflow thread: https://stackoverflow.com/a/74324388

What you’re seeing there is Query Monitor’s output. I’d imagine that “WC Cancel Order” is outputting invalid HTML, such as one or more unclosed tags. As a result, Query Monitor’s output is appearing in the middle of the page instead of at the very end, and the issue would almost assuredly be with WC Cancel Order. I’d start there.

it causes problems

Can you be more specific about the types of problems it’s causing for you?

You can use a filter to control which post types are supported:

add_filter( ‘page-links-to-post-types’, ‘my_filter_page_links_to_post_types’, 10, 1 );

It receives an array of post types. Muck as needed, and return the desired array of post types.