Jay

Hi t-p, thanks for the follow up.

Just to verify. I would expect that if I edit the reusable block within the “Manage all reusable blocks”, then those changes would affect every instance of that reusable block.

However, if that reusable block is on a blog post and I edit it there, I would not expect those changes to be applied globally. That is not the case though, Editing the block in that context also changes it globally with basically no indication that I changed a “Global block”.

I would expect some sort of indication that this block is a reusable block and in order to edit it, I would need to convert it to a regular block. Or at a minimum a notification that I am changing a global block.

What version of WordPress did this change in if you know? Is there a way to disable this capability?

As you can imagine the scenario, where Admin-A creates a reusable block which is used all over. Editor-B edits a post which has the reusable block and wants to edit the content of the reusable block. Editor-B does not realize its a reusable block or even what a reusable block is and changes or deletes part of it and changes every instance of the reusable block.

This threw me off and I have been using WordPress for 10 years.

• This reply was modified 3 years, 6 months ago by Jay.

Hello,

I have been able to replicate this issue. Whenever a reusable block was created with the plugin and added to a new page, it disappears in the editor. I have replicated this on two different WordPress installs.

WP Version 5.7.1
Plugin Version 1.22.1

Great turn around and thanks for such quick response!

I can confirm this is happening on version 1.5.12.3.

To fix the restriction error

Log in to your Google Cloud Platform API & Services and for the key, edit it and remove the http from the url or just remove the restrictions all together.

So instead of https://yourwebsite.com/*
yourwebsite.com/*

You may still see the error message in the admin, but the calendar will display.

To fix this error. Log in to your Google Cloud Platform API & Services and for the key, edit it and remove the http from the url or just remove the restrictions all together.

So instead of https://yourwebsite.com/*
yourwebsite.com/*

Same problem here and related topic

I am seeing this as well

I was getting this error as well and the below plugin was the culprit.
https://www.ads-software.com/plugins/cimy-swift-smtp/

Just recently had an issue with this as well. The culprit was the below plugin.
https://www.ads-software.com/plugins/cimy-swift-smtp/

It was having the same issue and the culprit was this plugin
https://www.ads-software.com/plugins/cimy-swift-smtp/

Spot on! Thanks for the tip.

I am seeing this issue as well, but I don’t see anywhere that it is even being addressed, so I would not get your hopes up. This is your possible solution and the author claims it has been a WordPress bug for sometime. Maybe a mod can jump in an advise.

Have you looked at this? Also, here is a detailed tutorial on how to accomplish what you are trying to do. Scroll down a bit to view the domain mapping part.

I would also mention though that Google frowns on having two domains with the same information causing duplicate content penalties. You may want investigate further.

@alchymyth you always come to the rescue! Works perfectly Cheers!