Term access pages for roles display blank

Hi, using v1.77

will overwrite with 1.88 and see if that fixes it.

Hi,

1.88 has fixed that issue. However, now many of our authenticated users can only see certain posts (from months ago, or only the posts since we upgraded the module. There wasn't a version upgrade in update.php - should there have been?

I had a similar issue with tac-lite - part of the reason I moved to taxonomy access control since it didn't have the same issue. Is there a way to refresh the permissions? uninstalling and reinstalling didn't work.

Thanks.

Managed to fix this by going into each role, taking view permissions for "uncategorised nodes" away from them. saving settings, then going back and putting them back in. Seems to be fine now. We've been doing other work on the site and server the past couple of days so likely due to that I think.

Thanks very much for your help with this, all seems to be working fine now and the module is great!

Hi I'm back and just got this working again.

I did a complete uninstall of taxonomy access, and removed the row in the system table as well. Then reinstalled with the 1.88 version. I also increased php memory limit to 32mb - I think that might be the issue since we have a fairly large number of taxonomy terms (several hundred in 6 different vocabularies).

If that page calls every setting for every taxonomy term that might well be the issue since it'd be quite a big query all at once. Maybe it'd help to be able to call a page by vocabulary instead of (or as well as) by role to set permissions? i.e. we only use tac on forums and have large and increasing free-tagging vocabularies so memory could become an issue again later on assuming that was the problem.

that sounds like a good idea to me.

We've got two possible uses for taxonomy access so far:

1. private forums (and hopefully the ability for individuals to moderate specific forums although I've not tried to set that up yet)

2. editing rights for CCK nodes as described here http://drupal.org/node/77475 - although that seems like a workaround to me, and I saw a patch for CCK which adds "edit all" to the default access control page which seems a lot easier to maintain.

Even if we use both options there are still vocabularies we won't need to use TAC on - i.e. our free tagging vocabulary. since we'd probably do the CCK edit access via a "sections" vocabulary meaning we'd only require it on two out of about 5 or 6, and two of the smaller ones.

Also in general, if sites are using free tagging the ui will require more and more memory as vocabularies increase into the thousands, so in terms of resource usage it'd help a lot.

Just to confirm this - when I tried to reset view permissions (see the reset permissions bug which I just added to) on uncategorised nodes today, I also got the blank page as described before.

Changing memory limit from 32 to 36M in php.ini fixed it. We're currently transferring a lot of old content and free-tagging it from our old CMSes, since that job's just started though I think we could see our memory limit increasing to 50 or 60M within weeks.

How about: For all user roles:
view,update,delete: Ignored.
Create, List: Allowed?
Any ideas?

Those are the settings we use for non-restricted vocabularies - it's not overriding node creation permissions (i.e. create book page) with "allowed" so that seems completely fine.

2. I have a totally different approach in mind to make permission page smaller:
(a) Defining some vocabularies, where you can use different settings for each terms in that vocab.
(b) For terms in other vocabs: use 'default' permissions of the given vocabulary.

That seems more flexible. You'd have vocabulary based permissions, then an option for term permissions for selected vocabularies right?

If I had a choice I'd go for the second idea - then say you had a web/intranet combined in one installation, you could by default hide everything in the intranet vocabulary from certain roles without the extra load on the page of each term - that wouldn't be possible with a default setting of "ignore", and it saves trying to make a catch all solution for default permissions.