Upgraded to 1.3 beta of panels - when i create a panels node (carete content / panels) and then add content to it, when i try to view it i get a white screen.

This is happening on two sites on two different servers, so i'm wondering if i have something configured incorrectly?

On one of the servers I upgraded to the dev version, and am still having the same problem.
http://sandbox.stonekeep.com/node/24

Comments

sdboyer’s picture

sdboyer commented
Status: Active » Postponed (maintainer needs more info)

1.3beta? I'll assume you're referring to 5.2-beta3. Also, please don't use -dev. There's really no guarantee that it won't make things worse.

I don't quite know what to tell you, as the link you posted works perfectly fine for me.

catya’s picture

catya commented

Yes, sorry - 5.x-2.0-beta3

I figured that trying dev was in order before i tried to write for support at least :) The sandbox link is the dev variant.

Apparently the problem only happens when one is logged in - I can also hit that link if i'm not logged into the site.

Any clues for me?

sdboyer’s picture

sdboyer commented

Ahh, fair enough.

Unfortunately, I really don't know what could be causing this. Best place to start that I can think of is to ask what's in the panel nodes that result in white screens (or is it all of em?), and from there, what other modules you have installed.

catya’s picture

catya commented

It's everything I have tried, which is to say basic nodes, forums, and blogs. These are both drupal/civicrm sites - any modules in particular that might be in conflict?

mike booth’s picture

mike booth commented
Title: Cannot view panel nodes - white screen » Panel nodes can be recursive -> white screen
Category: support » bug

This has been resolved, in the course of which we uncovered a problem:

If, while experimenting with a Panel Node, you create a pane on that node and choose node context/node content for that pane, it will attempt to display the Panel Node inside of itself. You get a nifty picture-in-picture-in-picture effect -- but only if you hack into the Panels code and adjust panels_admin_node_content() to terminate the infinite recursion. The default case is that the page just blows up and cannot be fixed without direct SQL queries. :)

If your pane is set to only be visible for admins then it only blows up when you're logged in as an admin!

Presumably, in the absence of a way to explicitly choose a "node context" for a Panel Node, it has a context already... the Panel Node itself. I'm told that this is not how earlier versions of Panels worked.

Probably it would be a good idea to patch Panels so that it refuses to recursively render the same Panel Node over and over inside itself. Though this "feature" might have amusing applications in the hands of elite hackers, it's mostly just a big trap waiting to catch people and cause an eruption of trouble tickets. :)

It might make sense to merge this ticket with, e.g., http://drupal.org/node/206317 -- which talks about selecting the node context of a Panel Node, an upcoming feature. If so, please combine and close this ticket.

mike booth’s picture

mike booth commented
Status: Postponed (maintainer needs more info) » Active
sdboyer’s picture

sdboyer commented

Heh, funny...I didn't see your followups until just now, mechfish, but I've just been working on a hefty rewrite of some of panels' core API and I found some similar infinite recursion problems that stem from a similar but separate problem. In any case, this isn't going to be fixed for the long term right away, but it is something I have my eye on and will get to as I can.

esmerel’s picture

esmerel commented
Status: Active » Closed (won't fix)

No fixes are going to get committed to the 2.x line