Confirmed, no where is it checked that the component exists and is enabled.

Also, the description of the plugins does not help much

The Gallery Fields plugin. means nothing to me.

No way to know what happens when these plugins are disabled.

There is an option (the one JM identified the other day as confusing) in the Options to hide or not the component from the content menu

The Gallery Fields plugin. means nothing to me.
That is an extra field that is available in custom fields

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12633.}

There is an option (the one JM identified the other day as confusing) in the Options to hide or not the component from the content menu

Yes, we know that. As @andrepereiradasilva righfully states, when you disable the component in Extensions Manager=> Manage, it still displays the specific menus

As for the Gallery plugin, as it is a new proposed field, there should be an explanation of what it is and how to param it.

Such a shame that in the almost year that this PR existed you didnt help to
test it - Instead it was just left to just a few people.!!!

On 30 October 2016 at 10:31, infograf768 notifications@github.com wrote:

There is an option (the one JM identified the other day as confusing) in
the Options to hide or not the component from the content menu

Yes, we know that. As @andrepereiradasilva
https://github.com/andrepereiradasilva righfully states, when you
disable the component in Extensions Manager, it still displays the specific
menus

As for the Gallery plugin, as it is a new proposed field, there should be
an explanation of what it is and how to param it.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12633 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8dJFB_IgNbZX6LFi9Rlbi8UJnik-ks5q5HHmgaJpZM4KkVZE
.

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

IMO we still have time to 3.7.0 to solve this issues and others that exist.

Thats exactly why it was merged!!!!
No one was looking at it so nothing was ever going to happen

On 30 October 2016 at 10:44, andrepereiradasilva notifications@github.com
wrote:

IMO we still have time to 3.7.0 to solve this issues and others that exist.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#12633 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8WmMBVDiI_N4O2qERe6xGmaPIVyeks5q5HUJgaJpZM4KkVZE
.

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

yes, i understand that.

that PR was hard to test before that it has been merged, if IRC i was not able to test using com_patchtester (for example) ...

I guess we need something similar to JLanguageMultilang::isEnabled() to propose the new field in the components Options (for the moment com_users, com_contacts, com_content) as well as the menus for com_content and com_users. (To get submenus in com_contact needs even more tweaking, if even possible with present core).

Will make a PR for that

Closing as we have PR

#12646

Set to "closed" on behalf of @infograf768 by The JTracker Application at issues.joomla.org/joomla-cms/12633