Whenever I enable this module (I am using Domain Access, Domain Configuration, and Domain Settings) on a 7.14 site, I am no longer able to see unpublished content from the admin/content page, regardless of the filter settings, and despite being logged into the uid=1 account with all permissions enabled. When I disable the modules, I am immediately able to see unpublished content from the same account (same session even.) When I re-enable the modules, the symptom reappears.
I do not believe this to be a duplicate of http://drupal.org/node/1420876, but I suspect that they might be related(?)
I've seen reports of similar symptoms, but I do not know if they are related to this module: http://drupal.org/node/1559866
Comments
Comment #1
Bill Bostick commentedTo clarify, the unpublished nodes are still accessible to the uid=1 account via the node/x URLs. They just don't show up on the admin/content page.
Furthermore, views created with a filter criteria of published=NO will fail to work when this module is enabled. As soon as I disable the module, the view works as expected. When I re-enable the module (which forces me to rebuild my permission table), the view displays empty results.
Comment #2
agentrickardDo you have the "enforce access rules on administrators" setting for the module enabled?
Comment #3
Bill Bostick commentedTurns out this option is enabled. I do not recall enabling this option as I've only discovered it's existence as a result of your response. Regardless, disabling this option has resolved the problem I was experiencing. Thank you very much for the response... sorry for the erroneous report.
Comment #4
4kant commentedTook me a while to find this issue - thanks for the hint about the settings in domain module.
But I must have the "enforce access rules on administrators" setting enabled because of lots of menu items of different domains in one menu, leading to "current domain content". After reenabling the settings I got all menu items at once on each domain.
So my solution is:
I created a bulk operation views page and set it´s URL as an exception under admin/structure/domain/settings --> "Special page requests".
(Of course you could also put in "admin/content")
That does it for me.