Side bar menu always goes to article fields, it is bit confusing. You click fields in sidebar menu, change to Categories in dropdown, add your fields, and when you come back, it again shows Article fields. Maybe dropdown selection should be remembered in user state (like in modules manager for admin vs. site modules), or separate sidebar menu items should be present.
I am not sure if sceenshot make it more clear, just follow these steps:
I would expect, that filter for Category will remain, but its lost. Same for Content - Field Groups.
That's because the link in the sidebar is hardcoded to a specific context. Changing the link so it only points to com_content doesn't really work since it's not a valid context, we would have to guess the remaining part if not set already for com_content.
What could be done as well is to have an own UI for com_fields with a dropdown selector where the contexts for each extension could be listed, the we could just point to index.php?option=com_fields&view=fields. But it was decided to not go that route.
Maybe only 'keep in user state' functinality would solve this. Same as in modules manager, language manager etc. If Administrator is seleced in modules manager filter, it is keeped in user state, so after next click to menu it still shows administration modules.
Or add another two links in sidebar and main menu - 'Category fields' and 'Category fields groups'.
That works because in those views, the dropdown has a default value that is used when nothin is set in userstate yet. However in case of fields there is no default value and thus it will fail with the first click.
It could have one (eg com_content.article) if there was a cross-extension "Fields" UI. With a dropdown where you can select from all contexts from all extensions. This would be simple to do actually, but it was decided to not do as it was a bit confusing for the user.
Adding links for each context gets out of hand fast if the extension has multiple contexts. If you have more links for fields in the sidebar than for the extension itself, then something is wrong
Priority | Medium | ⇒ | Low |
Status | New | ⇒ | Expected Behaviour |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-04-05 07:37:56 |
Closed_By | ⇒ | franz-wohlkoenig |
closed as Expected Behaviour.
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/14120
Can you post a screenshot where exactly this happens?