Import Existing Panel Variants Into Panelizer [#1924800]

My goal is simple:
Create a view of Testimonials (a Content Type) using the existing Panel Node Layout (default View Mode.)
( I used to be able to do this without Panelizer, but there is no way display the Panel Node in Views. DS used to be the way, but now Panelizer seems to be the only way. )

1. I have my Panel Node page all set up with the right layout.
2. Install Panelizer
3. Do I have to re-create everything in Panelizer for it to work with Views?? I tried to check/uncheck "PROVIDE DEFAULT PANEL" and "Panelize" but not successful.

Note: If I "Set to default" in Panelizer, I would expect the default to be the Panel Override, but it is the default for the node template.

If this must be recreated, can I export from Panels into Panelizer?
FYI - I really wish Panels and Panelizer were one, integrated module - would be much more intuitive for the neophyte like me :).

Comments

Comment #1

merlinofchaos commented 22 February 2013 at 17:54

There is an issue in the queue with an update script to migrate a panel node into a panelizer configuration, but it hasn't been updated in awhile, I'm afraid. Right now, Panelizer and Panel Nodes are two different universes.

It is possible to go into the database and move a display from the panel node table into the panelizer entity table, but it's a pretty advanced operation and you need to be pretty comfortable with the system to do it.

Comment #2

sonicthoughts commented 22 February 2013 at 18:40

Ok, that's a shame. I understand that they are different universes, but after setting up the panel content, css, etc. to display properly it's a shame that you have to go and recreate everything just to display it in a view.

BTW - I do see an "export" under panels (default only) but don't see an import anywhere?

Can't find much in the way of docs here so really appreciate your help.

Comment #3

merlinofchaos commented 22 February 2013 at 18:51

The panel node application of Panels is a tiny one that I never liked, and thus has never really received a lot of support. It's very limited in many ways; Panelizer is something that opened up all the limitations, but it's left us in the position that panel nodes still exists. in an ideal world, we'll get the migration script from panel nodes to panelizer actually working, and then you can just use panelizer, remove the panel nodes module entirely, and never have to worry about it again.

Alas, this is a thing that takes time and effort, and wanting to do something isn't the same as having the time and energy to get it done.

Comment #4

merlinofchaos commented 22 February 2013 at 18:52

If you find the issue in the Panels queue about migrating from panel nodes to panelizer, and post on it, it's possible that the author of that patch might update it for today's world, and then you could use it and not have to worry about this problem any more.