merefield introduces the Tag Intersection Navigator, a Discourse plugin designed to enhance the native tag intersection interface by allowing empty or single-tag combinations, supporting various filters beyond “Latest,” and enabling a desktop homepage default. A critical warning advises against using “everything” as a tag. The plugin integrates with Bars for sidebar support and offers settings to customize the “all” string and add community links.
During the discussion, Jagster inquired about accessing the interface without replacing the homepage; merefield confirmed a new “Community Section Link” setting was added and the homepage default is now off. Jagster noted a mobile display glitch and a missing localization issue, which merefieldfixed. gormus reported a bug when customizing the “everything” string, leading to a merged fix. merefield later implemented Category filter integration.
Regarding limitations, Dimava asked about negative tags, which merefield confirmed are unsupported, noting the plugin requires funding or PRs for expansion. cmdntd reported 404 errors with sub-categories, which merefield acknowledged as unsupported. mhawash suggested native implementation, to which merefield offered to develop a PR if hired. Finally, Jagster encountered a 500 error after an upgrade, prompting merefield to release updates addressing core changes and adding a feature for banner notifications within the intersection view merefield.
Please consider becoming an ongoing sponsor of my open source work at a level that suits your or your organisation’s resources and needs to ensure this plugin gets the maintenance it deserves and continues to work for your site in the future.
you must not use the word “everything” as a tag on your instance.
Settings
There are just four settings:
to enable the plugin
determine which string is used to describe “everything” in the routing - I advise you don’t change this, but you can experiment with alternative options. You must avoid using the same string as a tag
to make the interface the Homepage for desktop (default OFF)
include a community link in sidebar/header dropdown (default ON)
Limitations/A Roadmap?
Hire me or submit a PR to add the following:
Like core intersections, does not yet work with a combo of Category - but this continues to fall back to the Category/Tag interface
Sub-categories are not yet supported
There are no Topic counts on the navigation tabs and their
visibility/availability is presently not determined by availability of the corresponding topic list population count.
Respect availability/ordering of filter settings.
The interface is not offered on mobile due to lack of real-estate.
BTW, I know mobiles aren’t supported, but it works just fine in mobiles. Only that is different is they can see Latest etc. menu, and most of mobile-users can show such four point menu. If there would be hot, top etc. then it would be crowded.
תודה על התגובה
אני אשאיר בקשת תכונה בבעיות
ובקשת תכונה לשדה חיפוש
(אני לא באמת צריך אותם, הם רק המסקנה ההגיונית של החלפה מוחלטת של חיפוש לשימוש כללי)
(תגיות שליליות הן התכונה הכי פחות מתועדת שאני מכיר. בטוח שיש כאלה גרועות יותר שאין לי מושג לגביהן)
כמו כן, הייתי אומר שעלינו להיזהר שלא להוסיף יותר מדי תוספות, כדי לא לסרבל או לסבך יתר על המידה את הממשק, אשר כרגע הוא די אינטואיטיבי וממלא את השטח הפנוי בשולחן העבודה בצורה נאה למדי. תכונות כמו אלה שציינת בהחלט יצטרכו להיות מאחורי אפשרויות.
it on GitHub ! 
you must not use the word “everything” as a tag on your instance. 
