It seems normal that in large installation only one or two persons (web admins) will be responsible for managing sites, and much more business ones (directors, CEO, and so on) would only ever need to see the statuses. However, current implementation shows only one's own nodes:

 //file (sentry_server_mysites.inc)
function sentry_server_mysites() {
...
/*32*/ $sql = 'SELECT nid FROM {node} WHERE type = "sentry_site" AND uid = %d';
...

There should be some kind of permission, like "view any sentry site", that we would give to a role we'll put our business users.

Comments

snufkin’s picture

snufkin commented

This would become obsolete once you use the views handlers to build the mysites page though. Could you do me a favour and test the views branch from git? I have no time to do a thorough testing, but that branch contains a default view to replace the mysites page plus all the field handlers required.

rmolotkiewicz’s picture

rmolotkiewicz commented

I'll try to test that branch.
However, I can't see this becoming obsolete. I mean now one either sees all sites or only own ones. No view will ever be triggered when one opens directly a node (like http://czs.[cut].pl/node/3). Ability to define if one is only operator and should see only own sites' statuses, or overseer seeing all sites in system, is needed and does not depend on views. Said place was only an example.

On the other hand, you could just make sure your module works properly with http://drupal.org/project/taxonomy_access - that would allow us to do all the things we need and more.