[#17572] - Possibility for the frontend to have the 3 buttons (save, save & close, cancel)
- Closed
- 16 Aug 2017
- Medium
- Build: 3.8-dev
- # 17572
- Diff
- joomla:staging
- Success continuous-integration/drone/push the build was successful Details
- Success continuous-integration/travis-ci/push The Travis CI build passed Details
- Failure continuous-integration/appveyor/branch AppVeyor build failed Details
User tests: Successful: Unsuccessful:
Pull Request for Issue #17572 .
Summary of Changes
Use the trio, Save, Save & Close, and Cancel in the frontend edition to increase publisher productivity.
Testing Instructions
Expected result
As a result, the frontend publisher will have greater productivity in the work of creating and editing articles, preventing it from leaving the edit mode with each update of the content.
Actual result
Currently, the publisher is forced to exit edit mode every time it saves content while editing through the portal frontend.This makes editing by the frontend too time-consuming, unproductive and annoying.
Documentation Changes Required
joomla-cms-bot
- | Category | ⇒ | Unit Tests Repository Administration com_admin SQL Postgresql MS SQL com_categories com_config com_contact com_content |
| Status | New | ⇒ | Pending |
| Category | Unit Tests Repository Administration com_admin SQL Postgresql MS SQL com_categories com_config com_contact com_content | ⇒ | Unit Tests Repository Administration com_admin SQL Postgresql MS SQL com_associations com_categories com_config com_contact |
| Labels |
Added:
?
?
|
||
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-08-16 20:30:53 |
| Closed_By | ⇒ | zero-24 |
How can I make an improvement request for the Joomla developers group?
What I'm asking for is very simple, I'm just trying to request that the new versions have the possibility to have the buttons (save, save & close, close) when editing articles by the frontend. Just to remember the backend already exists this possibility.
What is the best way for me to make this request?
What is the best way for me to make this request?
Do you have code that implement that change or do you just want to suggest that without submitting code?
Suggest without sending code. Sorry for the stress.
Could you guide me?
Suggest without sending code. Sorry for the stress.
No problem just go here: https://github.com/joomla/joomla-cms/issues/new
And put all the input / request data in there in the most detail as possible. Thanks.
Issue Tracker is the better place perhaps? https://issues.joomla.org/
Issue Tracker is the better place perhaps? https://issues.joomla.org/
Isn't the issue Tracker === Github ? So all that is in the issue tracker is also in Github ;)
@zero-24 most of the Time yes. But now there are new issues reported at Github which aren't shown in Tracker (#17581, #17582).
Please report that to this tracker than: https://github.com/joomla/jissues/issues/new So michael can take a look into that. Thanks.
It just takes some time. Both Issues are now displaying on issues.joomla.org
thanks @zero-24 @infograf768 Issue reported an closed.
Items posting on the issue tracker relies on either our cron jobs picking things up or GitHub's webhook delivery (the latter one is the preferred method as it is usually instantaneous). If there are issues with GitHub's webhook system then things posting to the issue tracker will be delayed. That is out of my hands.
Looking at the GitHub log, there appears to have been a 20 minute delay earlier in one of the webhooks opening one of the noted issues.
@belinifm it looks like you have done a mistake as you just try to merge staging into 3.8-dev branch. Please double check that. So we can test your patch.
As this is not going to be merged this way I'm going to close this PR. Please let me know when you need help creating the pull request.