Active
Project:
Domain Access Advanced
Version:
6.x-1.0-rc1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Jun 2009 at 10:31 UTC
Updated:
8 Jul 2011 at 17:23 UTC
Jump to comment: Most recent file
Comments
Comment #1
threeps commentedI came across the same problem described above. I wanted a tracker view that compiled nodes from multiple domains, even though the nodes were published on a different domain. My temporary solution was to change the hook_db_rewrite_sql code of Domain Access Advanced to first check if the SQL query already references the domain_access table. If it does, then the query is left as is. This way, if there are no domain_access filters in a View, then everything works as usual with Domain Access Advanced (ie, the view only shows nodes for the current domain). However, if you add a domain_access filter, then my change will prevent any other restrictions from being added, so you can use the view interface to control the domain access conditions.
This approach is working for me, but it is probably not the best solution and may have some unintended consequences that I have not found yet. Attached is a patch against 6.x-1.0-rc1 that implements these changes. Feedback on a better way would be appreciated.
Comment #2
theoracleprodigy commentedThe patch seems to work but only for authenticated users. If you are not logged in the views are not present. I really wish this was resolved.