ldwd
Forum Replies Created
-
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 onlyEdit: when no custom status is assigned to the post type the button does not disappear on that post type.
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!
Forum: Plugins
In reply to: [Simple Revisions Delete] Is this plugin obsolete now ?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, 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!
@kevinb, Iβm not sure what you mean with your comment.
My confusion is that when the option is set to For all plugin statusses I expect the label tab to be displayed on ALL statuses. But itβs not: itβs displayed at Pending Review, but not on the custom one.
–
Switching to For user-created plugin statuses only will make it the other way around:
Pending Review -> no label tab
Custom status -> label tab
(which IS expected behaviour).And do you have any update on the buttons still showing Save as Draft in the classic editor?
Thank you!
Hi @kevinb, thank you for your quick response!
The translations are working now!
Unfortunately, the button text still reads Save as draft.With the new setting for Status Label Customization set on For all plugin statusses, the Label tab on my custom status is not visible, is that correct behaviour? Only when set to For user-created plugin statuses only the label tab appears. I find that confusing.
Btw, even when the label tab is not there, the value is still shown in the editor.
Forum: Plugins
In reply to: [Simple Revisions Delete] Is this plugin obsolete now ?I came looking here too if this plugin will be updated. In another thread from a year ago someone reported the same, after which the plugin author replied he updated.
@brikou Can you help us determine if this plugin is getting revived? We miss it! π
Thank you!
Awesome, thanks!