Error when not logged-in as admin
Dear Beng
I had talked to you previously via email about a problem with our new site where errors ocur when users were not logged in as an administrator. Our computer guys are now happy to use Prosepoint, so I will bring our Discussion back to the forum. Your initial supsicion was that the problem was due to our installation using the multi-site feature of Drupal, but this was the reply from our department:
"The Prosepoint installation is a single installation for the news. We have not used the multi-site feature for the same. It seems that the errors that are being generated are due to prosepoint not taking parameters on the page. We need check this again."And a further reply, more specifically on the errors:
"Except users having admin role ,others are not able to view the `views, which requires arguments`. If we remove the arguments passing to views then there is no error, but this displays stories from all the channels."
In more direct terms: we get the non-logged-in errors when we configure (in Zones) a composite-layout edition to use one or more subchannels that are configured to deliver their stories in reverse chronological order. I would like to use this option because in allows us to get close to my desired layout (http://www.prosepoint.org/node/507).
When not logged-in as admin, we get the "No suitable Stories" message where the stories should appear, and one oft he following error msgs per missing story at the top of the page:
- user warning: Unknown column 'node.nid' in 'on clause' query: SELECT COUNT(*) FROM (SELECT node.nid AS nid FROM node node LEFT JOIN workflow_node workflow_node ON node.nid = workflow_node.nid LEFT JOIN content_type_story node_data_field_date ON node.vid = node_data_field_date.vid WHERE (node.type in ('story')) AND (workflow_node.sid = 4) AND (node.status <> 0) AND (node.vid IN ( SELECT tn.vid FROM term_node tn INNER JOIN node_access na ON na.nid = node.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 1 AND na.realm = 'workflow_access') OR (na.gid = 0 AND na.realm = 'workflow_access_owner'))) AND ( tn.tid = 15 )) )) count_alias in /home/www/html/news/profiles/prosepoint/modules/views/includes/view.inc on line 729.
The Content Permissions module is not enabled.
Ive added you in as an admin user, and you should have site, username and pw info sent to you by email.
Many thanks for your excellent previous assistance, and for any insights with this.
Cheers
geoff
Dear Beng
Many thanks for your reply in the middle of the holiday season!
I have no connection with royrana who had the squid issue- I posted one post on that thread by mistake, and immeditely removed the post's content (not seeing any way to delete the post itself).
I have forwarded your question re the missing node.nid column, and will get back to you as soon as info comes to hand.
cheers
geoff
Dear Beng,
The reply from computing guy:
"This is not a database issue, since the error is not appearing for admin. If the column (node.nid) is not present in database how admin user is able to see those pages without any error. Moreover, as I have already informed in previous mail, the error is appearing only in `views which requires arguments` (only for non-admin user)."
cheers
geoff
Dear Beng
The problem has now been resolved, when I know how they did it, I will post it here,
geoff
Strange. I still suspect there were altering the system in some way ... but no matter, as long as your issue is resolved.
Dear Beng:
Explanation as per email from tech support:
"While going through forums it was suggested somewhere to upgrade php and
prosepoint."

Hi,
(Yes, I got your email with the site credentials)
Firstly, following on from Validation Error Please contact Site Administrator ...
Is the squid issue resolved or bypassed? For all I know, that could affect this.
Secondly, what have your guys done?
The database column node.nid is absolutely critical to the functioning of ProsePoint. If this column is really non-existent on your site, I'm surprised your site isn't more broken. There is no code in ProsePoint which allows this column to be dropped, so my questions are ...
Can you check your database to see the the column nid in the table node exists?
If not, then it seems like your database is severely wrong, so please as your people what they have done.