ldwd

Thanks @hellokhoyer, that would be awesome!

Thank you @hellokhoyer, I will try!

@kevinb
Thank you for the quick update.

I can confirm that the issue with ACF is resolved. But when a required custom field from HivePress is left blank there IS a button now, but it is disabled (and reads Publish instead of Update in case of a published post).

Can you fix this as well please?

Edit: while the issue with ACF is resolved, that button also reads Publish instead of Update for published posts. Just fyi ??

@rizaardiyanto, my apologies, I meant regular posts and pages, and custom post types.

Yes this should be the default behavior. But this is not the case with my websites. When I click Notify Me the link changes to Stop Notifying Me and my name is added to the Notifications metabox. When I click on the Stop Notifying Me link nothing happens.

This issue occurs on regular pages and custom post types.

Hi @kevinb and @rizaardiyanto,

It happens on regular pages with classic editor as well.

I used custom fields from ACF and/or HivePress:
– custom post type with HivePress and ACF
– regular page with ACF only

Edit: when no custom status is assigned to the post type the button does not disappear on that post type.

Hello @hellokhoyer ?? or colleague,

Do you have any update on this?

Thank you!

Hi @rizaardiyanto,

I followed the thread on GitHub and see you marked it as completed. This is not resolved though. As I said the Notify Me link works fine. Once set, it is the Stop Notifying Me link that does not work. Even though it is set as the the only option:

So while the link is there, it simply doesn’t respond to a click. The only way to stop notifications is to open the post, remove my name from the Notify Me metabox and hit Update, but that’s not very efficient.

This is happening on three different websites on different servers. You confirmed the bug earlier, what did you experience?

Thank you @rizaardiyanto!

@kevinb, just fyi: after updating to 1.0.5 I can safely set the Gutenberg / Classic Editor option back to Automatic. The Save As button now shows the correct status name ??

Ah yes, the statuses now stay where they are ??

Thank you so much for all your effort @kevinb!

Hi @brikou,

Thanks for your reply. As far as I know there are no issues, but WordPress is warning that this plugin hasn’t been tested with the latest 3 major releases of WordPress. So checking and updating the WordPress compatibility version sounds like a good idea ??

Thank you!

@kevinb Sure!

Site 1
WP: 6.4.2
PHP: 8.1.27

Site 2
WP: 6.2.2
PHP: 8.1.24

@kevinb, I followed your steps and this is indeed repeatable. There are no JavaScript errors shown in the console.

I do have to rephrase myself: in my opening post I said ALL the statuses were back, but this is only the case for the ones shown in the screenshot in my first post. This includes the plugins alternate workflow example statuses as well as my custom statuses.

These are left in the disabled box:

@kevinb, thank you for your hard work.

Yes the Label tab is now displayed correctly!

The update to 1.0.4.1 didn’t change anything about the Save As button, BUT I discovered that changing the Gutenberg/Classic Editor option from Automatic to Classic Editor did the trick!

I didn’t think of this before because the statuses themselves were loaded in the dropdown, so I left it as it was. Now I just tried everything and this solves the problem (again, I use a custom post type which uses the classic editor).

Testing on two sites I can confirm changing this setting also works in the previous version (1.0.4).

Thank you for all your help!