Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.The modules that make up the "Panels Ecosystem" have not had new releases since February. Those modules are:
- Panels
- Panelizer
- Page Manager
- CTools
We rely on quite a bit of the committed but unreleased functionality in those modules. The purpose of this issue is to create and host mega patches that can be applied to the last release of each of the modules. The patches are essentially diffs between the module's last release and head.
These patches need to be hosted on D.O because the D.O packager will reject patches that live elsewhere when building the legacy tarball. See here for why we can't just reference a specific commit: http://lightning.acquia.com/blog/whats-up-700k-patch-to-panels
| Comment | File | Size | Author |
|---|---|---|---|
| #27 | panelizer--8.x-3.0-alpha2--54f0ac6e.patch | 40.66 KB | phenaproxima |
| #26 | 2747739-26--layout_plugin-alpha22-to-96a5cf90.patch | 17.76 KB | balsama |
| #21 | panels-beta4-75131285.patch | 811.91 KB | balsama |
| #17 | panels--beta4-4c4a3a7--2747739-17--binary.patch | 680.58 KB | balsama |
| #10 | ctools--8.x-3.0-alpha26--1fe3649.patch | 6.04 KB | balsama |
Comments
Comment #2
balsamaPanels patch. Beta4 to 4c4a3a7.
Comment #3
balsamaPage Manager Patch. Alpha23 to 09e79ff.
Comment #4
balsamaComment #5
balsamaPanelizer patch. Alpha2 to 1ddfa61.
Comment #6
balsamaThese three seem to be working.
Comment #7
phenaproximaCTools patch from 8.x-3.0-alpha26 tag to 058c6dfa.
Comment #8
phenaproximaUpdating the CTools patch with additional bugfixes (from 8.x-3.0-alpha26 to 0f3bcebe).
Comment #9
balsamaComment #10
balsamaNew patch for ctools.
Comment #11
balsamaComment #12
mpotter CreditAttribution: mpotter commentedWe ran into a problem with the panels mega-patch. It is trying to delete a bunch of image files. But when using a newer version of patch (2.7.1) there are errors/warnings like this:
for each binary file that was removed.
With an older version of patch (2.5.8) we don't get these errors/warnings.
The side-effect of this is that when doing a "composer update" when it tries to apply the patch with "patch -p1
Once these patches are committed to actual module releases this problem will go away, but would also be interested in knowing if there was a better way to create these patches that didn't cause these errors. Took several hours to track down why our Lightning build on one system was failing compared to another.
Comment #13
balsamaComment #14
balsamaRe: #12 what do you mean by "newer version of the patch" and the version numbers (2.7.1, 2.5.8), @mpotter? Sorry if I'm missing something obvious :) We only provide one patch for panels in this issue - and they aren't "versioned".
Comment #15
mpotter CreditAttribution: mpotter commentedWhat I mean is that if you are using v2.7.1 of the "patch" utility and you do:
patch -p1 <filename.patchyou get the errors like
However, if you are using an older v2.5.8 of the "patch" utility you do not get those errors.
A bit more info...the patch process first tries to use "git apply". Using the panels mega-patch in #2, doing
git apply --check filename.patchgives errors like this:
The failure of "git apply" is what causes it to try the "patch" command. And depending on your version of the patch command it will succeed or fail.
Comment #16
mpotter CreditAttribution: mpotter commentedResearching the git error a bit more, it appears that you need to create the patch file using the --binary option to fix this.
Comment #17
balsamaRecreated the panels patch (which, surprise, contains binary files) with the --binary option.
Comment #18
Dane Powell CreditAttribution: Dane Powell at Acquia commented#17 works for me and also fixes #2752735: Doc mentions removed session component
Comment #19
balsamaBig +1 to mpotter for tracking this down. Tracking this over at #2752375: Cannot apply Panels patch now.
Comment #21
balsamaNew patch for panels.
Comment #22
balsamaComment #24
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commentedI think we need this to work with panels 8.x-3.0-beta5
Playing around with the patch.
Comment #25
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot commentedI had the updated patch in an issue under the panels project
#2810533: Advanced panels 8.x-3.x based on the work of Lightning profile
Comment #26
balsamaThis patch brings layout_plugin from alpha22 to commit 96a5cf90 (which added the getLabel() method to LayoutBase)
Comment #27
phenaproximaThis brings Panelizer from 8.x-3.0-alpha2 to 54f0ac6e4f4ab2c30bf09d143554bb85576edf30.