Configuration to Reproduce:

  • MLID filtering: Currently active menu item
  • In the MLID widget is "Front page" selected (not the "real" frontpage menu item, if the option "Enable front page menu items" was enabled)

When the View is executed it will not filter the node correctly, because the field value is "-1", but the query work with the mlid (e.g. 1162). So all nodes with "-1" in the field value will be ignored.

Here is a misunderstanding between the meaning of the "Front page" value and the front page menu item value (when "Enable front page menu items" was activated).

CommentFileSizeAuthor
#2 vms_frontpage_filter-1689588-2.patch1.05 KBAnonymous (not verified)
#1 1689588-allowed-front-page-value-in-current-mlid-filter.diff1.08 KBcbeier

Comments

cbeier’s picture

cbeier commented
StatusFileSize
new 1689588-allowed-front-page-value-in-current-mlid-filter.diff1.08 KB

In my patch the filter will also work, if "Front page" was selected. But then the option "Enable front page menu items" is unnecessary.

The mlid filter considered also the "front page" value as well as the menu item, that was set as the front page.

Anonymous’s picture

Anonymous (not verified) commented
Version: 7.x-1.0-beta1 » 7.x-1.x-dev
Status: Active » Needs review
StatusFileSize
new vms_frontpage_filter-1689588-2.patch1.05 KB

The above patch didn't work for me, as my $frontpage_path = 'node/45' and $menu_item['router_path'] = 'node/%'...

I've attached an updated patch that instead compares $frontpage_path to $menu_item['href'] (which works for me).