- last update
over 1 year ago Patch Failed to Apply - Open on Drupal.org →Core: 10.1.x + Environment: PHP 8.2 & MySQL 8last update
over 1 year ago Waiting for branch to pass - last update
over 1 year ago Patch Failed to Apply
When using the IPE to edit an existing landing page with multiple blocks, periodically we are getting a 500 error in the JS console :
VM106:1 PUT /admin/panels_ipe/variant/panelizer_field/node:1:full:1626/layouts/layout_onecol 500 (Internal Server Error) which links to a page with json output of:
{"message":"A fatal error occurred: Plugin ID \u0027a76465f8-a8e9-4596-bb77-99f78714e3ea\u0027 was not found."}
This is the same error as reported in https://www.drupal.org/node/2744145 → and I have confirmed that the patch for Panelizer in https://www.drupal.org/node/2700597 → is applied. There is another comment on the original issue of this cropping up for another user, so I'm thinking this may not be fully solved.
The blocks in question are largely custom blocks / block types that have been created for this project.
(Description of the proposed solution, the rationale behind it, and workarounds for people who cannot use the patch.)
(reviews needed, tests to be written or run, documentation to be written, etc.)
(New or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text.)
(API changes/additions that would affect module, install profile, and theme developers, including examples of before/after code if appropriate.)
(Database or configuration data changes that would make stored data on an existing site incompatible with the site's updated codebase, including changes to hook_schema(), configuration schema or keys, or the expected format of stored data, etc.)
(Text of the original report, for legacy issues whose initial post was not the issue summary. Use rarely.)
Needs work
4.0
In-Place Editor (IPE)
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.