Make a tree of categories. Move and copy these categories. It is possible to make wrong moves, then a warning appears like this one.
The warning should be informative for the user.
For non-developers, the warning looks harsh.
Status | New | ⇒ | Confirmed |
Maybe I'm too much a developer, because to me the message is very clear.
It might be related in that it may fix the issue to not get the error message.
Well, it might be that I got this issue wrong.
I think the error message itself is necessary, but the message could be less "development". Something like "Moving the category to this place is not possble".
This is why it's a bad idea for errors to go uncaught throughout the system and them eventually get shown to all end users. This is the type of error message that is appropriate for debugging at a development level, but this is also the same type of error that should be getting caught in the component MVC and being transformed into something more appropriate for end user display. The right fix is not to "dumb down" Exception messages because they might get shown to an end user who isn't the intended audience.
Agree.
Status | Confirmed | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-11-02 15:18:32 |
Closed_By | ⇒ | chmst | |
Labels |
Added:
No Code Attached Yet
Removed: ? |
In J4 no longer valid.
Please test PR #20943 for J3