-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improper validation message is displayed while adding existing name in User manage Viewing access Level. #4727
Comments
Changed status to Medium since this is not critical. However I do agree the message should be more userfriendly. |
I have also tested this issue in joomla 3.7-dev. |
Same issue exist in Edit case too. |
I have tested with Joomla! 3.3.7-dev version |
Yes. Replicated issue on my side as well & added patch. Please find the patch for this issue here. #4838 |
Set to "closed" on behalf of @zero-24 by The JTracker Application at issues.joomla.org/joomla-cms/4727 |
Closing as we have a PR by @atpatil11 for this #4838 |
Steps to reproduce the issue
1.Go to User Manager: Add New Viewing Access Level
2. Enter public in name field(existing name)
3. Click save button verify the result
4. Following error is displayed.
Error
Save failed with the following error: Duplicate entry
'Public' for key 'idx_assetgroup_title_lookup' SQL=INSERT INTO
b12lm_viewlevels
(
id
,title
,rules
) VALUES('0','Public','[]')
Expected result
Proper validation message should display.
Actual result
Validation message with sql query is displayed.
System information (as much as possible)
PHP Built On Windows NT 6.2 build 9200
Database Version 5.6.12-log
Database Collation utf8_general_ci
PHP Version 5.4.12
Web Server Apache/2.4.4 (Win64) PHP/5.4.12
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.3.7-dev Development [ Ember ] 01-October-2014 02:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 6.1; rv:32.0) Gecko/20100101 Firefox/32.0
Additional comments
The text was updated successfully, but these errors were encountered: