rgasch,
As I reported earlier in the thread, that merely filters the category, but doesn't restrict any content with the assigned category.
The News module is a prime example. If you set the news article to a certain category (say MEMBERSONLY with catid of 999), then put a permission of NONE on that category, the news article still shows to everyone.
ALL GROUPS Categories::Category 999:: NONE - placed above all generic permissions.
Admins see the news WITH a category:
News
[ Front Page | Archive | Submit Article ]
MEMBERONLY: News Title
Blah Blah Blah...
------------------------------
NON-logged in or non-MEMBERS group user(hence no permission) user sees:
News
[ Front Page | Archive | Submit Article ]
News Title
So, the generic permission for categories blocks the use of the category, but not the content itself that is assigned to that category.
Again, this is a step backwards from using topics/old style categories in that at least there you could block (or enable) an entire section of the site by setting permissions for certain topics. The content AND the topic were blocked.
I am using
SVN and cannot filter any module content by category, just the categories themselves are filtered, but not the content with those assigned categories.
Following the code in several catagory-enabled modules, I don't see where the content ever has a category filter applied at any level - News, crpCalendar, etc.
Again, originally, I though this was a features of the new categories - where all modules that use them could have global categories and filter the modules content by using a Categories permission.
The issue is now, the original Stories Category permission no longer works (as story categories are just a part of the new categorization system) and you can't use the Categories permissions to filter content, either.
So, to clarify -
What is the intended functionality with .8? Should it, or should it not filter content by category.
If so, who else sees the same behavior I do - that the category is filtered, but the content is not.
Mateo seemed to see the problem, but as he, and I stated, there seem to be some technical problems implementing at the DBUtil level.
1. Categories are not attached to the returning data until late in the DBUtil process, so a filter does not work - would need to be done in the marshall / postProcess phase when other iterations occur and a permission check can be done on categories.
2. With multiple categories possible, how to check against multiple categories at once and determine the "highest" permission. (only applies where multi-categorization is allowed by the module).
3. If the category permission check is late in the DBUtil postprocess, then record counts are off if some returned records are dropped - affecting total record counts, paging, etc.
If this is NOT intended functionality, lets just state the limitation and make sure
documentation says that categories cannot be used to filter content, merely to classify it.