Someone reported this 3 years ago, and the post then concluded that the issue is resolved, but no solution is provided in that post; and I can;t find anything on this topic.
This is still a test site. I played around with HTML for an accordion type layout, and it worked perfectly fine.
I then added some Container and Grid blocks to test additional info, but then got hat error message.
I deleted the blocks added since the session when everything worked fine.
But the error message still comes up.
I cleaned the cache with Litespeed - still same problem.
So the deleted block does not show in edit (see screenshot), it still shows on front-end - the first Disaster Management block.
It of course shows as with that message it does not really save.
Sorry, but it's not clear from what you shared what exactly the problem is.
Your screenshot and message refer to blocks and custom JS.
But the title of your posts leads me to think you are editing a post that has custom fields and where you are trying to publish the post with invalid field values, though I can't be sure.
Does the post you are editing have a custom field group assigned? Does it include fields with validation requirements? Possibly with conditional display such that you could be trying to submit a post with hidden fields that have unmet validation requirements?
Hi Nigel - I appreciate your quick reply.
The message did not appear in round one, and the page could save, and public view was fine. The only blocks were the heading and HTML Blocks.
In round two, two Container and Grid blocks were added for additional content, but the message appeared - which usually means the page cannot be saved.
Strangely, one of the new blocks of round 2 was indeed saved with its content - the 1st Disaster container block that shows up on front-end. The second block or Police did not save.
The new blocks were identical. The Disaster block of round 2 was merely duplicated, for the Police content, which was added.
But due to the error message, I reverted manually back - by deleting these new blocks deleted, but the message continued to be displayed.
Now I can't get rid of that disaster block as it does not allow saving.
Could I take a look at your site? As I can't say what is happening based just on your description.
Let me mark your next reply as private so that I can get log-in credentials from you—you may want to create a temporary admin user for me to use that you can later delete. And be sure to have a current backup of your site.
Can you also confirm the url of where we can see the problem. What are you editing?
Thanks
Our system is setup to add users by email invitation only - the email I received from you is a no-reply address. If there is a usable email address, I can send.
I received the email invitation and have logged in.
As I suspected, you have a custom field group which applies to Pages and the field group includes required fields (screenshot). So you cannot save a page until you provide values for the required fields (they are required).
I suggest you go to Toolset > Custom Fields and edit the field group and specify which post types it applies to (currently, because it is not assigned to specific post types, it applies to all).
Then you should no longer be prevented from saving pages (or any other post type).
As an aside, I noticed you had Layouts active, which is a legacy plugin. You don't appear to be using it on either of the sites in the network, so I deactivated it, and recommend you avoid using it.