Skip to content

[com_config] Error?/Success? messages on save#10425

Merged
rdeutz merged 3 commits intojoomla:stagingfrom
andrepereiradasilva:com_config-save-messages-ux
May 16, 2016
Merged

[com_config] Error?/Success? messages on save#10425
rdeutz merged 3 commits intojoomla:stagingfrom
andrepereiradasilva:com_config-save-messages-ux

Conversation

@andrepereiradasilva
Copy link
Copy Markdown
Contributor

@andrepereiradasilva andrepereiradasilva commented May 11, 2016

Summary of Changes

In com_config when we get an error on save (ex: bad session token or no permission) we get a green (aka success) message.

This is a bad UX problem:

  • Green messages are for success
  • Blue messages are for information
  • Yellow messages are for warnings
  • Red messages are for errors or very importing stuff

This PR corrects that.

Testing Instructions

Code review, or, for instance:

  1. (browser Tab 1) Go to global config form, don't save
  2. (browser Tab 2) Open a new browser tab, go to backend, logout and login again
  3. (browser Tab 1) Press "Save" or "Save and Close" in the global config to save.
  4. You'll notice you get and invalid token message and the message is green and from a user perspective it's associated with action success.
    image
  5. Apply patch, repeat process 1 to 3. Now the message is red.
    image

@brianteeman
Copy link
Copy Markdown
Contributor

I have tested this item ✅ successfully on d7b3fdb

Good find


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10425.

@BurtNL
Copy link
Copy Markdown

BurtNL commented May 11, 2016

I have tested this item ✅ successfully on d7b3fdb

Works as described.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10425.

@brianteeman
Copy link
Copy Markdown
Contributor

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10425.

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label May 11, 2016
@brianteeman brianteeman added this to the Joomla 3.6.0 milestone May 11, 2016
@andrepereiradasilva
Copy link
Copy Markdown
Contributor Author

@brianteeman @BurtNL thanks for testing!

@richard67
Copy link
Copy Markdown
Member

I have tested this item ✅ successfully on d7b3fdb

Works as described.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10425.

@richard67
Copy link
Copy Markdown
Member

I was a bit late I just see 😄


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10425.

@andrepereiradasilva
Copy link
Copy Markdown
Contributor Author

thanks @richard67 another test in always good 😄

@brianteeman
Copy link
Copy Markdown
Contributor

all tests always welcome

On 11 May 2016 at 17:51, Richard Fath notifications@github.com wrote:

I was a bit late I just see [image: 😄]

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/10425
https://issues.joomla.org/tracker/joomla-cms/10425.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#10425 (comment)

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

@richard67
Copy link
Copy Markdown
Member

I will soon (in a few days) need testers for PR I am preparing, make utf8mb4 conversion use files with version numbers so not on every change all has to run, and make it handle extensions, too, so I am also working on a PR for weblinks to provide an example. Testers will be welcome, I'll let you know when my PR is ready.

@rdeutz rdeutz merged commit 09b624c into joomla:staging May 16, 2016
@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label May 16, 2016
@andrepereiradasilva andrepereiradasilva deleted the com_config-save-messages-ux branch May 16, 2016 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants