Skip to content

Set exclude_from_nav=True on Members folder#738

Open
jensens wants to merge 1 commit intomasterfrom
fix-members-exclude-from-nav
Open

Set exclude_from_nav=True on Members folder#738
jensens wants to merge 1 commit intomasterfrom
fix-members-exclude-from-nav

Conversation

@jensens
Copy link
Copy Markdown
Member

@jensens jensens commented Mar 24, 2026

Summary

  • The Members folder was never explicitly excluded from navigation
  • Previously hidden by accident: the exclude_from_nav indexer silently failed during deferred catalog queue processing (site manager not set at before_commit time), leaving the index empty (None), which didn't match exclude_from_nav=False queries
  • With Products.CMFCore 3.9+ and the _ensure_site fix (Running the tests takes like ages (migration tests & robot tests). #160), the indexer now works correctly, revealing the missing attribute
  • Fix: set exclude_from_nav=True explicitly in configure_members_folder()

Refs: plone/buildout.coredev#1080, zopefoundation/Products.CMFCore#160

Test plan

  • TestCatalogPortalTabs::testCreateTopLevelTabs passes (7 tabs, Members excluded)
  • All Catalog navigation tests pass

🤖 Generated with Claude Code

The Members folder was never explicitly excluded from navigation.
Previously this went unnoticed because the exclude_from_nav indexer
silently failed during deferred catalog queue processing (site
manager not set).  With Products.CMFCore 3.9+ the indexer now works
correctly during deferred processing, revealing that the default
value (False) was being indexed.

Explicitly set exclude_from_nav=True in configure_members_folder().

Refs: plone/buildout.coredev#1080
@mister-roboto
Copy link
Copy Markdown

@jensens thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

@jensens
Copy link
Copy Markdown
Member Author

jensens commented Mar 24, 2026

@jenkins-plone-org please run jobs

@jensens
Copy link
Copy Markdown
Member Author

jensens commented Mar 24, 2026

Note: Jenkins runs against full coredev which still uses CMFCore 3.8 (@mauritsvanrees reverted the pin).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants