when one attempt to access to node without proper term access, drupal says "not found" instead of "access denied".
Moreover, in dinstinct from "recent comments", "most popular content" block shows nodes from restricted terms to the users which are shouldn't see these nodes.

CommentFileSizeAuthor
#1 taxonomy_1.module46.21 KBnurlan.bayaman@bayaman.com
taxonomy_access_2.module32.71 KBnurlan.bayaman@bayaman.com

Comments

nurlan.bayaman@bayaman.com’s picture

nurlan.bayaman@bayaman.com commented
StatusFileSize
new taxonomy_1.module46.21 KB
nurlan.bayaman@bayaman.com’s picture

nurlan.bayaman@bayaman.com commented

I've attached taxonomy_access.module, and patched for taxonomy access and i18n modules taxonomy.module.

pyromanfo’s picture

pyromanfo commented

Moreover, in dinstinct from "recent comments", "most popular content" block shows nodes from restricted terms to the users which are shouldn't see these nodes.

These are issues with the tracker not obeying node_access permissions.

I'll commit the other change.

pyromanfo’s picture

pyromanfo commented

Wait a minute, what did you update? Or did you just attach the modules?

Nonetheless, the problem you describe is Drupal's core access system, you'll have to take it up with the core guys. When you do a term page that you don't have access to, it'll tell you access denied, and that's the only part I have control over.

nurlan.bayaman@bayaman.com’s picture

nurlan.bayaman@bayaman.com commented

Thanx for your reply.
Attached files are just the taxonomy access and taxonomy modules, patched by the patch, provided by miope taxonomy.module.patch
since i need i18n module too. I've attached them just to be sure, that did everething in correct way.

But i've got your message.
And it's pretty pity :). It's not so good, if i have link to the node, which should be in restricted part of the site. Moreover, it says "not found" instead of "access denied"...

pyromanfo’s picture

pyromanfo commented

I agree, it's probably not the right message. You should go talk to the Drupal core team however. Post an issue with the Drupal core team.

Gabriel R.’s picture

Gabriel R. commented

I've applied the patches as described in node/32778, but the 404-instead-403 issue is still not corrected.

Is it just me or this is a know and uncorrectable issue with TAC?

keve’s picture

keve commented
Status: Active » Closed (fixed)

This was solved in latest releases.