A category is defined on a PORTAL level, NOT on a module instance level. This is basically needed for the possibility for master/child event calendars.

---

Regards,
Ernst Peter



XCESS: DNN/Evoq specialist, zie www.xcess.nl

Events 7.0.1 - Released
Reports 6.1.0 - Released

Maybe I should explain you the scenario a little better. In my user roles, I have next to roles as translator, forum moderator, repository moderator, also roles as sportsevent editor, ceremonyeventeditor, holidayevent editor... These roles get access to a page, hidden and inaccessible for other users. On this page, each role sees only his calendar for a given language.

On the other hand, the home page also has a calendar in list view. It has many of those little calendars, but based on one's user role anyone will only see one of those calendars. Each calendar is a different combination of master calendars. Students and staff would see a calendar that includes holidays for instance, while unregistered users would see a calendar without the holidays (yet with the sports events, always good publicity)

There could be more calendars scattered around the website.

Sportevent editors should not per mistake be allowed to add events under the category "Ph.D. thesis presentation" for instance.

This is a scenario that is more likely to occur when the users are larger organizations with separate people responsible for different types of events.

Think of it: if you want to apply the parent/child logic systematically, inheritance of the categories is the only logical way. You should also consider it in regard to locations (for ML purpose)

---

____________________________________
The one-eyed in the land of the blind.