I believe this is relevent to the TODO on line 283 of panels_node.module but maybe not. The problem arose for myself when using a combination of filters, the way panels renders the content, the node was getting processed twice, thus breaking presentation of the node since certain filters specifically had to be in a certain order. this patch to panels/plugins/content_types/node_context/node_content.inc prevents panels from re-rendering a node if it has already been processed by the panels_node module.
| Comment | File | Size | Author |
|---|---|---|---|
| node_content_fix_render.patch | 444 bytes | cangeceiro |
Comments
Comment #1
merlinofchaos commentedIs there a better way to see if the node is already prepared? I don't like checking that flag, unless we're pretty sure this is something that is going to be pretty exclusive to Panel nodes. Also, does this break if you view panel node A inside panel node B? I guess that's an unlikely case since you'd be adding that node via context, but there are ways.
Comment #2
cangeceiro commentedTo the best of my knowledge I could not find a better way to tell if the node was prepared. Haven't tried in the scenario of adding panel nodes inside of each other. I tested a scenario of adding a panel node inside of another panel, and it does still render the panel contents of the node being included.
Comment #3
merlinofchaos commentedThis appears to actually be a patch against CTools. This confused me quite a bit until I realized why that is why it didn't apply.
Comment #4
merlinofchaos commentedI am still highly dubious about this. Can you provide me a scenario that demonstrates the problem (tell me how ot set up...) so that I can work with it and see what is actually wrong?
Comment #5
japerryClosing this issue as outdated as Drupal 6 ctools is not supported. If this issue is relevant for Drupal 7, feel free to re-open and mark for Drupal 7 (or 8)