I set up a new test site to test and debug Panels Everywhere, starting with a fresh install of Drupal 8, Page Manager, Panels and the latest dev build of Panels Everywhere. With all these modules (and dependencies) enabled, I was able to go to Pages > Site Template > Enable OK, but when leaving the admin pages, all I would see in the browser viewport would be:

The website encountered an unexpected error. Please try again later.

Checking the status logs in Drupal, this error was indicated:

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "onecol" plugin does not exist. in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 52 of /Users/[User Name]/Sites/[Site Name]/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

karolus created an issue. See original summary.

karolus’s picture

Status: Needs review » Active
mattlt’s picture

Hi @karolus,

Are you using the versions of page_manager and panels that support the experimental layout_discovery module introduced into core in 8.3 ? If so panels_everywhere has yet to be updated to support layout_discovery.

I've got panels_everywhere working with the 8.3 versions of page_manager, panels, and panelizer using layout_plugin.

If you are able to help here's the issue to support the new module…

https://www.drupal.org/node/2869185

Hope this helps.

Thanks,

•• matt

karolus’s picture

@mattlt, Thanks--I'll take a look. Just getting back from DrupalCamp Nordics. Also had spoken briefly with Damien McKenna about this back at DrupalCon Baltimore. Yes, I've upgraded the 8.3.x, so will take a look at this issue.

Just spun up another instance, using the Layout Plugin module, and 8.x-3.x version of Panels, and still having the same issues. Will try some other tests.

Alumei’s picture

I just tried to run the current alpha version with:
- drupal: 8.3.2
- layout_plugin: 1.0-alpha 23
- page_manager: 1.0-alpha 24
- panels: 3.0-beta 6

on simplytestme.
Using a stacked layout seems to work although only the position .. got the black background of the Batik footer everywhere. ..

I also noticed that simply enabling the site-template probably does not work since nothing is beeing placed there at the beginning. Not even the main content block ...

Alumei’s picture

Just tried it again but this time I simply enabled the site_template without any modifications ... still work .. although the site only remains usable because there is the toolbar on top ;-)

I hope this helps ...

markus_petrux’s picture

It looks like the reported error can be fixed by pacthing the file config/install/page_manager.page_variant.panels_everywhere.yml as follows:

-  layout: onecol
+  layout: layout_onecol

Then reinstall PE as follows:
1) Uninstall Panels Everywhere.
2) Manually delete the site_template page in Panels.
3) Install Panels Everywhere.

huzooka’s picture

karolus’s picture

@markus_petrux: Thanks, your code update worked for me on a test build.

@Alumei: Yes, the black is part of using Bartik. I'd suggest a theme that works well with Panels out of the box, like Cog. I got the black on an experimental build with Bartik as the default theme, but switching to my Cog custom theme fixed things.

DamienMcKenna’s picture

Version: 8.x-1.0-alpha1 » 8.x-4.x-dev
Status: Active » Needs review
Issue tags: -error, -not found
FileSize
512 bytes

This is marcus_petrux's suggested change in code.

DamienMcKenna’s picture

Status: Needs review » Needs work
Parent issue: » #2845415: Plan for Panels Everywhere 8.x-4.0 release

Ok, that's in, but we need an update script like what Page Manager, Panels and Panelizer have.

DamienMcKenna’s picture

Status: Needs work » Needs review
FileSize
1.21 KB

Does this cover it? I based it off the Page Manager update script and just changed a bit to match the variant name.

karolus’s picture

@DamienMcKenna I just applied this patch. No errors found, but this was run on a test instance.

I'm looking for a scenario to test--would starting an install with Panels Everywhere 1.x, building a layout, then upgrading to PE 4.x and applying the patch be the most straightforward method?

DamienMcKenna’s picture

Yes, the correct test would be to build a display on a D8.2 site and then upgrade to 8.3 with the full Panels 8.x-4.x suite, see if the site works after the script updates run.

NWOM’s picture

#13 and performing the following via drush fixed the issue for me:

drush updatedb -y && drush cr

Thank you!

  • DamienMcKenna committed 9769cde on 8.x-4.x
    Issue #2874012 by DamienMcKenna, karolus, NWOM: Update script to fix...
DamienMcKenna’s picture

Status: Needs review » Fixed

Committed. Thanks @karolus and @NWOM for the review.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.