Label Blanc

I just pushed an update. Only the readme file was updated (not the code), so the version number didn’t change.

The plugin isn’t “abandoned”, but no new features will be developed. Also, it doesn’t work with the Gutenberg editor and a new WordPress 5 installation will use the Gutenberg editor by default, so I’m reluctant to mark the plugin as “compatible with WordPress 5”. So it may show a warning “This plugin hasn’t been tested with the latest WordPress versions…”

After analyzing, it unfortunately won’t be possible for now to have it work with Gutenberg in a way that is useful. The Gutenberg editor is completely different and doesn’t allow the same level of customization around the “Publish” button as the old editor.

Unfortunately, the plugin only works in the admin. The functionalities the plugin adds are specific to actions that you can do in the admin. The same functionalities for the front end would require a different plugin.

Hi, thank you for your suggestion. It would be difficult to implement, because, for security reasons, the browser doesn’t allow a script (like a click on the “Save” button) to close a window that you opened yourself. It is a good idea, but, to work, it would probably need to restrict the user to perform a certain flow, which is not ideal.

Hello,

The new version (1.2.1) fixes this issue.

Thank you

Hello,

Do you mean that you want a “Save and duplicate” action which does not create a draft, but a published post?

Or do mean that you want a “Save and next/previous” action that skips drafts?

Thank you

Do you still have this issue ? What version of the plugin are you using ? Did you try disabling all other plugins to see if the problem still arises ?

Hello,

The German translation pack has been approved by a GTE and released. Your WordPress installation should install it soon.

Hello,

Thank you for notifying me of this bug, because it looks effectively like a bug. I will analyse your solution and provide a bug fix (in the next few days/weeks!).

Hello,

Thank you for taking the time to comment. However, the plugin does not replace the original “publish/update” button, it adds a new one under it, so what you are seeing is the normal behavior. I am, though, currently thinking if the plugin should have an option to replace the original button or not.

Thank you again!

Hi Nevil,

Sorry for the (outrageously long!) delay. Originally, the idea of the plugin was to add a button with additional options, but not to replace the main “publish” button. I will, though, think if the plugin should have an option to replace the button.

Hello,

Thank you for taking the time to make a suggestion. Do you have an example of what you would like to be able to do (example of a custom text label) ?

Thank you

Hi,

Thank you for your comment. Unfortunately, it is not me who can approve a translation. In the new WordPress translation system (the one used in the plugin), translations must be approved by Project Translation Editors (PTE) of the said language, not by the plugin developer (unless he is a PTE in the language).

I will check if I can ask for a quicker review.

Hi nathanwright. Thank you for taking the time to give feedback. I’m not 100% sure I understand the steps you describe, but I will give you a use case that I think is what you describe. I also give you the expected result of that use case when you click “Save and Return”. If this use case is what you are saying but the end result is not the same, then it is a bug. If the use case is not what you describe, tell me.

Use case :
– The user is on page “A” which is not a post edit page, but contains a link to edit a post (ex: a post list page, a frontend page with the admin bar, etc.).
– The user clicks on a link to edit a post ( -> the user goes to the post edit page).
– The user clicks the regular “Publish/Update” button (once or more) ( -> the post is saved and the same post edit page is shown again).
– The user clicks on the “<Save> and Return” button action.

Expected result: after that last step, it brings the user back to page “A”, even if the regular “Publish/Update” button was clicked before.

If the use case is what you describe, but you don’t get the expected result, could you give me more details (the exact page “A” you have, where you click, etc.).

Thank you again.

Hi tomasbarao, I did some research but could not find a way to import a .po file to the WordPress Translation Service. I’m afraid the only solution is to copy-paste. Note, though, that some strings were changed and others added in the latest release of the plugin (from a few days ago), so those strings will have to be re-translated (or added).

Thank you again for taking the time to translate the plugin, it is greatly appreciated and I’m sure it will be really useful for all Portuguese users.

Your next steps (if you still want to submit your translation): go to the plugin translation project (https://translate.www.ads-software.com/projects/wp-plugins/improved-save-button) and click on the language you want to translate. Click on “Stable (latest release)” and start submitting the strings (please note that some strings may have changed since the last update, so be careful when copy-pasting from your .po file if it was made before the latest release). The translations would then have to be approved by a PTE (Project Translation Editor) of the language.