Don't know how to assign the acces part of the module but this issue is about this component. I tested it and it seems that Panels2 conflicts with the access module. Received this error in the watchdog:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DISTINCT(node.nid), node.created AS node_created, node.title AS node_title' at line 1 query: SELECT DISTINCT(node.nid) AS DISTINCT(node.nid), node.created AS node_created, node.title AS node_title, node_data_field_bb_teaser_text.field_bb_teaser_text_value AS node_data_field_bb_teaser_text_field_bb_teaser_text_value, node.type AS node_type, node.vid AS node_vid, users.name AS users_name, users.uid AS users_uid, node_data_field_bb_teaser_text.field_bb_picture_fid AS node_data_field_bb_teaser_text_field_bb_picture_fid, node_data_field_bb_teaser_text.field_bb_picture_list AS node_data_field_bb_teaser_text_field_bb_picture_list, node_data_field_bb_teaser_text.field_bb_picture_data AS node_data_field_bb_teaser_text_field_bb_picture_data FROM node node LEFT JOIN content_type_bb_eintrag node_data_field_bb_teaser_text ON node.vid = node_data_field_bb_teaser_text.vid INNER JOIN users users ON node.uid = users.uid 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 = 'ng_private') OR (na.gid = 1 AND na.realm = 'ng_private_admin') OR (na.gid = 15 AND na.realm = 'ng_private_author'))) AND ( (node.type in ('bb_eintrag')) AND (node.status <> 0) AND (node.language in ('de')) )ORDER BY node_created DESC LIMIT 0, 15 in C:\xampp\htdocs\D6\sites\all\modules\views\includes\view.inc in Zeile 731.

The panelpage was displayed with failures. Some panes were missing completly.

Just reporting this as I don't plan to work with this feature at the moment. But please keep progressing as I like this module already very much.

Comments

dddave’s picture

dddave CreditAttribution: dddave commented
Title: Acces conflict with Panels 2 » Acces conflict with Panels 2/View Panes and some views
Version: 6.x-1.0-alpha6 » 6.x-1.0-alpha8

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DISTINCT(node.nid), node.created AS node_created, node.title AS node_title' at line 1 query: SELECT DISTINCT(node.nid) AS DISTINCT(node.nid), node.created AS node_created, node.title AS node_title, node_data_field_bb_teaser_text.field_bb_teaser_text_value AS node_data_field_bb_teaser_text_field_bb_teaser_text_value, node.type AS node_type, node.vid AS node_vid, users.name AS users_name, users.uid AS users_uid, node_data_field_bb_teaser_text.field_bb_picture_fid AS node_data_field_bb_teaser_text_field_bb_picture_fid, node_data_field_bb_teaser_text.field_bb_picture_list AS node_data_field_bb_teaser_text_field_bb_picture_list, node_data_field_bb_teaser_text.field_bb_picture_data AS node_data_field_bb_teaser_text_field_bb_picture_data FROM node node LEFT JOIN content_type_bb_eintrag node_data_field_bb_teaser_text ON node.vid = node_data_field_bb_teaser_text.vid INNER JOIN users users ON node.uid = users.uid WHERE (node.type in ('bb_eintrag')) AND (node.status <> 0) AND (node.language in ('en')) ORDER BY node_created DESC LIMIT 0, 15 in C:\xampp\htdocs\D6\sites\all\modules\views\includes\view.inc on line 731.

And a couple of variations of this error (some come on line 705).

It is actually the rebuilding permissions process that breaks Panels. More precisely it affects view panes.

Moreover I put the affected view and displayed it as a page. The effect is the same: The view disappears (but the exposed filters stay).

Some Views (displayed as pages) are not affected.

I will look further into this and perhaps find the time to put a fresh install up.

kmonty’s picture

kmonty
Location San Francisco, CA
CreditAttribution: kmonty commented

I've rebuilt permissions a number of times without incident. Rebuilding permissions is actually not an extremely uncommon thing that Drupal does, but I'll try to replicate the issue.

kmonty’s picture

kmonty
Location San Francisco, CA
CreditAttribution: kmonty commented
Version: 6.x-1.0-alpha8 » 6.x-2.x-dev
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

dddave - Are you still having this issue anymore? Did you notice anything with ng2.0?

I'm tempted to say this isn't critical anymore as ng1.x and panels2.x are no longer recommended modules. Please push to active if you still can replicate this issue or mark as closed.

dddave’s picture

dddave CreditAttribution: dddave commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Sorry, I totally forgot this issue after upgrading to P3. It is a bit startling that I missed it because I did quite a few marches through the issue queue to clean up.
I think due to my focus on ng2.x I totally ignored all the ng1.x issues. This thing can be closed.