search

VirtusLab-Open-Source / strapi-plugin-navigation

A plugin for Strapi Headless CMS that provides navigation / menu builder feature with their possibility to control the audience and different output structure renderers like (flat, tree and RFR - ready for handling by Redux First Router)
MIT License
318 stars 58 forks source link

[BUG?] Audience collection does exist even when the field is disabled #429

Closed SalahAdDin closed 5 months ago

SalahAdDin commented 6 months ago

Honestly, we have to say, we don't understand what is that collection for so, so maybe it would not be an issue, but: image And: image

Could you update the documentation explaining what and why audience?

Thank you!

Launched In: 1668 ms Environment: development OS: linux-x64 Strapi Version: 4.24.1 Node/Yarn Version: yarn/4.1.1 npm/? node/v20.12.2 linux x64 Edition: Community Database: sqlite

vincentgTroopers commented 5 months ago

same issue here, not sure what this audience collection is about

thanks for the work on this plugin !

cyp3rius commented 5 months ago

The Audience collection is built in Navigation Plugin collection to "filter" the navigations depend on the role / target audience of your client application. Collection is visible in Content Manager as it should. The Enable button is just to show and execute logic in the Nav Item form.

Closing the issue, as not an issue - hope I made it clear above :)

SalahAdDin commented 5 months ago

The Audience collection is built into the Navigation Plugin collection to "filter" the navigations depending on your client application's role/target audience. The collection is visible in Content Manager as it should be. The Enable button just shows and executes logic in the Nav Item form.

Closing the issue, as not an issue - hope I made it clear above :)

So, it is like for signed-in users we show some items, for general users we show other items, etc. Right?

It would be nice to have it on the documentation, with examples.

cyp3rius commented 5 months ago

You could, not should :) it's an option to use. For example we had a project where there were signed users with roles from external source on the client app, and we differ the items based on their roles.

We will add that to doc for v5