when the taxonomy_access module is enabled, it becomes impossible to create published pages that are publicly accessible. i'm not yet sure if this is also the case with other node types. the short experiment i did:

1. with taxonomy access disabled, as admin user, create a new page node, and publish it with read/write on the comments
2. logout and check to see if the page is viewable by anonymous and authenticated users. it is.
3. log in as admin and properly enable the taxonomy access module.
4. log out and repeat step 2 above. - the page is still viewable.
5. log back in as admin and make a minor change to the test page body text, and resubmit the page.
6. log out and repeat step 2 above. the page is NOT viewable.
7. log back in as admin, and properly disable taxonmy access module.
8. log out and repeat step 2 above. - the page IS viewable

the same thing happens with new pages that are created while the taxonomy access module is enabled. i've gone throught the settings and everything appears to be checked or unchecked as appropriate, but maybe i'm missing something. is this a bug, or by design?

any help wpuld be appreciated.

thanks,

stephen

Comments

pyromanfo’s picture

pyromanfo commented

So you have given anonymous users the permission to view that taxonomy that the post resides in, right?

Anonymous’s picture

(not verified) commented

the page is not a part of the taxonomy, and is not associated with any terms, as i understand it. i have looked the settings and haven't found a place that would allow me to ope this page up to any user (anonymous or authenticated). am i missing something?

Anonymous’s picture

(not verified) commented

also, anonymous and authenticated users are set to be able to view "uncategorized nodes", but this does not seem to be working.

Anonymous’s picture

(not verified) commented

a little more information: it seems that if you go to administer->users->configure->category permissions, and edit the anonymous user (or authenticated user) category permissions, and simply click "save category permissions" without making any changes, uncategorized page nodes become available for those users. so it looks like when permissions are saved from this part of the application, they are applied correctly, but when content is going in initially (or on edit) they are not.

this looks like a bug, should i be reporting it someplace else?

thanks,

srs

pyromanfo’s picture

pyromanfo commented

It's adding the permissions when you add content, you did enable the module from both the module menu and from administer >> settings >> taxonomy_access as per the installation instructions right?

It sounds like the module wasn't enabled properly because saving the permissions fixed it.

Anonymous’s picture

(not verified) commented

yes it has been enabled in both places, and the message on the taxonomy_access settings page indicates that it has been enabled properly. i've tried disabling and re-enabling a few times just to make sure, but i still get the same result.

any other suggestions. have you seen anything like this before? and i don't think i mentioned before, i'm using drupal v4.5.1 and several other modules from the drupal site. do you know of any potential conflicts?

thanks,

srs

pyromanfo’s picture

pyromanfo commented

Try this.

Go to mysql, and put in "select * from term_access;"

Then add a term from administer >> categories.

Then put in "select * from term_access;" again. Tell me what changes, or just paste both outputs in here.

Anonymous’s picture

(not verified) commented

i did the test, and after adding a term, the term_access table had 4 new rows (i'm guessing one for each of the user roles, plus the admin) - the rows looked like this:

tid,rid,grant_view,,grant_update,grant_delete
6,1,1,0,0
6,2,1,0,0
6,3,1,0,0
6,0,1,0,0

i had already spent some time familiarizing myself with the tables involved, so i think this is the desired result. yes?

the problem i'm having is with nodes that are not associated with any particular term or vocabulary, such as static pages that i have attached to menus items.

my setup is this: so far i have a single vocabulary with a few terms that i wish to use to describe blog entries and and stories (so the page node type is not associated with the vocabulary on the edit vocabulary page). i wish to be able to create pages freely without having to associate them with a particular term, but if i create a page (or edit an existing page) it is not viewable until i re-save the category permissions.

i think i see the problem: afetr i edit an existing page (say node 17), the node_access table contains one row for node 17 that looks like this:

nid,gid,realm,grant_view,grant_update,grant_delete
17,0,term_access,0,0,0

and only the admin user can access the page.

immediately after going to the administer->users->configure->category permissions->anonymous user->edit page, and saving the category permissions, the node_access table has 3 new rows, and a change to the previously existing node 17 row. they look like this:

nid,gid,realm,grant_view,grant_update,grant_delete
17,0,term_access,1,0,0
17,1,term_access,1,0,0
17,2,term_access,1,0,0
17,3,term_access,1,0,0

have i configured something wrong, or is this a problem in the code?

thanks,

srs

pyromanfo’s picture

pyromanfo commented

This looks like a problem with the code, I'll take a look at it when I get home and get my computer back up and running again.

Thanks for debugging it.

stephenrs’s picture

stephenrs commented

no problem, thanks for being so responsive - and thanks for the module in the first place. aside from this small problem, it works great and allows me to set my site up the way i want.

also, i've got a drupal login now (stephenrs)...

srs

pyromanfo’s picture

pyromanfo commented

Fixed in CVS, I found the problem. In the uncategorized part, it was using db_fetch_array instead of db_fetch_object, so none of the right info was making it back into the DB.

stephenrs’s picture

stephenrs commented

ok, i pulled from cvs and installed the updated module, and the problem has been fixed. i didn't apply the patch though, and i can't remember if i applied it the first time i installed the module. is the patch necessary for full functionality?

thanks,

srs

pyromanfo’s picture

pyromanfo commented

The patch makes sure taxonomies that you can't view don't show up, and that users can't post to taxonomies they don't have create access to.

If you can't remember, just search taxonomy.module for 'taxonomy_access'. If it's there, you applied the patch, if not you didn't.

Anonymous’s picture

(not verified) commented