Cannot add "Content" to Panels Page since page_manager 8.x-1.0-alpha24

Glad I'm not crazy. I downgraded to alpha23 as well, which was kind of a pain, as I had to uninstall page_manage and page_manager_ui, which wiped out all of my page_manager pages, then manually remove page_manager from my modules directory, then reinstall using the alpha23 tar, then rebuild my pages. Oh well. If someone know a better way to have done that (downgrade module), I'm all ears!

Nice, great resources. Thanks for passing along!

Just my opinion, but using an alpha snapshot that we know works with current page_manager is better than using the changing dev branch. Its also a moot point when the dev branch doesn't work with current_page manager.

Thanks for the feedback @dobrzyns

UPDATE: Panels' recent beta release 8.x-3.0-beta5 claimed to have implemented the Wizard API, which would lead me to believe that this issue was resolved. Well, I updated Page Manager to 8.x-1.0-alpha24 and Panels to 8.x-3.0-beta5 at the same time and, things appears all good immediately following the updates. I went to edit one of my page's that used a panel variant, and the UI had changed, reflecting the new Wizard API layout, and I was actually able to view the panel variant properly and see all of my content blocks, which was not the case under the circumstances which caused me to originally open this issue.

However, once I tried to add a block to my panels variant and click "Update and save", all hell broke loose. It brought me to the dreaded Nginx 502 Bad Gateway error screen. I hit the back button and tried to just click "save" instead of "Update and save" (what the hell is the difference between update and save anyways, in this new UI??), and that brought me back to the nginx 502 error page. And now I get the nginx 502 error page whenever I try to hit any url on my site. Trying to make sense of the error logs now, but they are kind of cryptic.

So far, I'd suggest people who have production sites (not me, yet), to not pursue these updates quite yet. Something is off. If a dev wants to chime in to guide me as to what I should be looking for in the nginx/php logs, I'm happy to provide more info.

EDIT1: clearing cache through stale tab using admin toolbar's "Flush all caches" resulted in 502 error page. Clearing site caches through Pantheon site manager also did not work. The only way I could get the site to opperate was by "drush cr" (using Terminus, since its a Pantheon site). However, once I tried to naviagate to my page with the Panel variant, the 502-on-every-page issue came back. This time I couldn't even view the variant edit page.

EDIT2: see https://www.drupal.org/node/2818123

Thanks @andypost for the tip on keyvalue_expirable table! Can you please comment on my new ticket https://www.drupal.org/node/2818123 to corroborate the bad behavior?

@andypost when I ran delete from key_value_expire;, my 502 issue unfortunately persisted. Just a heads up to others out there. My site seems to be irrecoverable. Thanksfully I have a backup. I'd advise anyone pursuing these Panels/Page Manager updates to do so with extreme caution, and definite create a backup before doing to.

@DamienMcKenna, thanks for checking in! I tested the updates with pre-existing panel variants somewhat recently and still had issues. In December, I actually even tested the following:

• backups system
• Deleted all panel page varitants
• Updated Panels (8.x-3.0-beta5)
• Updated Page Manager (8.x-1.0-alpha24)
• Recreated Panels Page variants

while I did not run into the 502 errors right away, as described in my initial issue, I did eventually hit them. See: https://www.drupal.org/node/2818123#comment-11832737

So, I am at a loss for how to move forward. I have has warning about critical security updates for Panels, but I simply can't seem to run a working combination of current Panels + Page Manager. If you have ANY suggestions for what to try, or what info I could provide to be more helpful, PLEASE LET ME KNOW. Due to the security aspect, this is a major issue for us.

EDIT: Sorry @DamienMcKenna... I might be confusing issues. This specific issue doesn't appear to be a problem anymore after updating both modules, but the combination of the two current betas just doesn't seem to work still. Maybe this issue should be closed and https://www.drupal.org/node/2818123 should be pursued? I am not sure if the issue described there is something that needs to be addressed in Panels or Page Manager. Open to any and all suggestions.

sure... I don't know. If the developers think its covered, feel free to close. I think you are correct that this specific issue is no longer a problem, and that I'm experiencing #2818123, which is a specific instance of #2831521

Will do, thanks @DamienMcKenna for chiming in here with the helpful info. I'll test #2831521 patch now and will report back on the related issues if it fixes the problem. Fingers crossed.

UPDATE: For anyone else experiencing the weirdness with updating to the newest Panels and Page Manager, my problems with these updates were solved by this ctools patch mentioned here. More here

@DamienMcKenna, this is a super noob question, but how do I know when that patch goes into production? Do I wait to see it committed in #2831521, then wait for new release/version on ctools (8.3.0-alpha28 or 8.3.0-beta), then wait for the subsiquent core release/update?

An even noobier question... are you physically typing/C&Ping your references to issues above in your comments, or is there an official tag/tool to reference issues in drupal.org comments? I wish there was a way to reference users as well, but by looking around the place, it appears that there is no such thing.

Thanks again.

awesome, thanks @DamienMcKenna and @andypost for the helpful resources/info