[Resolved] Update button is always disabled

[Author]

Posts

[Alok Sharma]

Hello,

Just like many other users have reported earlier, even dating back to two years or more, the Update button in the Content or Archive template is always disabled. After working so hard on creating the template, there is literally no way to save the changes.

https://toolset.com/forums/topic/update-button-not-working-after-loading/
https://toolset.com/forums/topic/the-update-button-in-the-block-editor-is-disabled-when-editing-a-template/
https://toolset.com/forums/topic/the-update-button-in-the-blocks-editor-is-not-always-available/

Even after so many years, there has been no fix. I simply don't understand why you would disable the Update button, irrespective what your plugin is processing in the background.

N.B.
— URL to WP admin is one-click login. It is valid for 30 days and no username or password is needed.
— I have pasted the Duplicator package URL in Server protection details > Username as the form was not accepting the URL. P.S. I am having MEGA Premium account. Kindly consider adding this service in the Duplicator package section.
— I have pasted the Duplicator package password in Server protection details > Password as there was no provision to specific password. Kindly consider adding the password field in Duplicator package section.

[Nigel]

Hi there

I logged in to your site and edited the reseller archive.

I made trivial changes (which I undid) so that WordPress would recognise something had changed and unlock the Update button (it is disabled when there is nothing to update), and then I clicked Update and the archive saved (note the Post updated notice in the screenshot), and the Update button locked again.

I had the browser dev tools open to see if there were any unresolved requests or errors that might produce a problem, but there were not.

So I couldn't see any problem when editing that archive.

I have experienced a problem in the past where after updating a post (or page or template) and then trying to navigate away I'm asked if I really want to leave the post, even though I just saved the page and nothing has changed, but I haven't experienced a problem whereby I'm not able to update the post at all.

If the Update button is stuck in a disabled state, try making some minor change on the page. If that doesn't unlock the Update button, check the browser tools for any errors.

[Alok Sharma]

Hello,

Across all the similar threads, the common answer has been that it is not happening at your end, and it is very surprising. I cannot comment on what setup you people are using, but whatever it is, it does not justify that not one, but many of your users are facing the similar problem.

Anyway, after a lot of debugging, I traced out the issue. After deactivating the plugins one-by-one, I noticed that after deactivating the Stackable plugin, the Update button gets enabled. But looking at the error log in the console, all the errors are pointing to Toolset, and not even a single trace to Stackable plugin.

And after I re-activate the Stackable plugin, the Update button gets disabled.

You can please refer to the following logs. The password is the same as specified in Server protection details > Password:

Stackable plugin is activated – hidden link

Stackable plugin is deactivated – hidden link

Thanks.

[Nigel]

Is there a particular View or archive you are editing where the problem occurs, because I can't see it when editing the Reseller Products Archive, for example.

The error logs you shared are the browser logs, and they report 500 errors, meaning an error on the server rather than in the browser, so I added a file manager plugin so that I could check the debug.log on your server, where I could see fatal errors from stackable that are likely linked to this issue.

So I re-activated the Stackable plugin and edited the archive, and didn't experience any errors in the console, and the Update button behaved as expected.

So perhaps I need to be editing something else, or doing something specific while editing...

[Alok Sharma]

Hi there,

This morning, I thought to give a different approach to this problem. I completed deleted the Product Category Hosting Archive template and created a new template, and it is working smoothly.

I believe something is causing the templates to become corrupted, and thereafter the whole issue arises.

[Nigel]

I wonder if it is related to caching, which may be why you have seen the problem, and I have not.

In any case, let me know if the problem re-surfaces, and I'll check again.

[Alok Sharma]

As I am continuing to debug this further, I figured out that Stackable (Premium) Blocks are not compatible inside the Archive template.

Adding Stackable blocks inside the Archive template causes any of the following issues:

1. At some certain point, corrupt the Archive template, making it extremely difficult to work on it any further.
2. Disable the Update button.
3. Display the contents of the Archive template itself, instead of the CPT.
4. Prevent the template from being saved.

I am uncertain if the problem is at the server level, or the browser level.

I am using the following setup:

— SpinupWP
— Ubuntu 22.04 LTS
— Linode VPS Nanode 1 GB – 1 CPU Core, 1 GB Ram & 25 GB Storage
— Linode Database Cluster Nanode 1 GB – 1 CPU Core, 1 GB Ram & 15 GB Storage

There are around 5 WP installations and they are all at the development stage.

[Nigel]

I checked again and both custom archives seem to be working without issue.

Let me know if either of them break again and I'll look into it.

[Alok Sharma]

Hi,

Okay, so the thing going on here is like bike owner & mechanic. But when the bike owner goes to the mechanic with a problem, the mechanic is unable to reproduce the problem, and neither the bike owner, LOL.

The archive templates are working perfectly fine, and I am still clueless as to why this issue occurs and then resolves automatically.

As I was editing the template, this message popped up, ‘The editor has encountered an unexpected error’. I had to reload the page and the error went away. But it happened only once.

I will report back if this issue occurs again. If not, then we can close this thread.

[Nigel]

OK, sorry I don't have anything to go on to have some more meaningful feedback.

Let me know if it recurs.

[Alok Sharma]

I'm closing the ticket because the issue is no longer happening, possibly as a result of the server reboot or plugin updates, or maybe any changes I made in Cloudflare, WordPress or elsewhere, can't remember which one.