Closed (won't fix)
Project:
Activity
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
17 Oct 2009 at 21:10 UTC
Updated:
18 Oct 2009 at 19:35 UTC
I use the Domain node access control module, where some nodes are published on sub1.foo.com, other nodes on sub2.foo.com, etc.... I do not want to publish any node on the "main" site main.foo.com, yet I used the activity view to list all nodes on it. That is not working anymore, possibly due to recent changes? Please confirm. If so, is there any way I can keep the old "feature"? Maybe a configuration option to honor (or not) node access restrictions? Thank you.
Comments
Comment #1
Scott Reynolds commentedWhats not working anymore? What did you expect the view todo and what did the View do?
What is the behavior that changed from the old code to the new code?
From what I understand, you wanted an Activity View on the main.domain.com to have Activity from all the other subdomains.
Not a fan of this idea. Activity is not a node access module. Perhaps domain access shouldn't apply its access restrictions on certain queries? Maybe you write a custom Views Filter Handler to allow access to those.
Or maybe on the main.subdomain.com turn off domain access?
Their of tons of different ways to achieve what you want. Activity2 does like Drupal core does, it assumes that node access control must be applied on all queries. In Drupal 7, their will be an opportunity to turn off the node access per query but this is Drupal 6.
Comment #2
Scott Reynolds commentedYou can of course work on implementing number 2 or 3 (they are generally the exact same) in the previous issue and we can then debate if that solution is better then current
#605670: Node Access filter using a Node -> Activity relationship breaks
Comment #3
skizzo commentedSorry, I am not a software expert, so I can't really implement or change anything, I am just using off-the-shelf capabilities. To answer your question: what the view did was to consolidate and list (on main domain) activity that was viewable on a dozen remaining subdomains, in my use case that was very handy. Following recent upgrades, the activity view now turns up empty when entered from main domain... Maybe that's the way it's supposed to be. As Sirktree says: "we need to assume that a user should have access to the node in order to view activity about it", but in my use case the same user does have access to the node (as long as she enter it from the subdomain where it was published). Indeed, I could still use the activity view to list activity on a per-domain basis, what I am missing is the global cross-domains list linking to all different subsites. Without coding I might find a workaround (publish to subsites AND main site), but it won't be as simple.
Comment #4
Scott Reynolds commentedYep, see the point is you have to setup up your access control policy properly.