I've moved the rule:
menu.hierarchy:* (wildcard)
into disabled section, still have inherit items.
Looks like start is ignored.

So move all items:
menu.hierarchy:navigation (Navigation)
menu.hierarchy:primary-links (Primary links)
menu.hierarchy:secondary-links (Secondary links)
menu.hierarchy:admin (Admin)
menu.hierarchy:features (Features)
menu.hierarchy:menu-footer (Footer Menu)
menu.hierarchy:menu-editor (Editor menu)
menu.hierarchy:menu-footer-sitelinks (Footer Sitelinks)
menu.hierarchy:menu-community-links (Community links)

Then it's disabeld. It's normal that star doesn't work in this case?

Comments

kenorb’s picture

kenorb commented
Priority: Normal » Minor
donquixote’s picture

donquixote commented

If the other stuff is in "inherit" section, then it should be sufficient to move only the wildcard into the "disabled" section.
If this does not work, it's a bug.

Of course, if the more specific rules are in "enabled" instead of "inherit", then disabling the wildcard is not supposed to have any effect.

kenorb’s picture

kenorb commented

Pasting this settings:

content_search (Content Search)
* (wildcard)

---- disabled ----
taxinav (Taxinav breadcrumb rules)
breadcrumb_doc (General rule for breadcrumb)
pathauto (the alias that pathauto would assign to this path.)
nodereference.* (wildcard)
taxonomy.* (wildcard)
menu.* (wildcard)
menu.hierarchy:* (wildcard)

Generating additional inherit items:

---- inherit ----
menu.hierarchy:navigation (Navigation)
menu.hierarchy:primary-links (Primary links)
menu.hierarchy:secondary-links (Secondary links)
menu.hierarchy:admin (Admin)
menu.hierarchy:features (Features)
menu.hierarchy:menu-footer (Footer Menu)
menu.hierarchy:menu-editor (Editor menu)
menu.hierarchy:menu-footer-sitelinks (Footer Sitelinks)
menu.hierarchy:menu-community-links (Community links)
...

I don't have anything specific enabled.
Shouldn't menu.hierarchy:* disable all more specified items?
It's a bug or not? I'm not sure.

donquixote’s picture

donquixote commented

This should absolutely disable all the menu.hierarchy:something stuff.
So yes, it must be a bug.

I hope the next release can fix this and a lot of other issues.
I do have some local changes, but I don't want to commit something half-broken. And I don't even know if any of these will fix your issue.

For now I don't have any better advice for you than to put all the stuff into the disabled section explicitly.

kenorb’s picture

kenorb commented
Category: support » bug

Currently this issue is not important for me, doesn't break any functionality.

donquixote’s picture

donquixote commented

is this still the case in 2.x branch?

donquixote’s picture

donquixote commented
Status: Active » Needs review

I use "needs review" for things that are "probably fixed in 2.x".

donquixote’s picture

donquixote commented
Status: Needs review » Closed (fixed)