Finally after a couple of days searching the issue queue of Page Manager and other projects, I stumbled over a comment in #3031778-8: Change panels store where it says that Panels 4.3 and CTools 3.1 currently won't work together.
I had the same symptoms in Page Manager when trying to add a user role selection criteria with CTools 3.1. After the downgrade to CTools 3.0 it seems to work.
For one thing, I wanted to share this, because it took me such a long time to find some workaround in the issue queue of a different (though related) module. Second, though I can't really judge because I'm not into the code, from reading the comment in #3031778-15: Change panels store, I seems to me, that the same actions to fix the problem in Panels must be applied to Page Manager as well, so I would not really consider this a duplicate of this issue.
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | interdiff-15.txt | 1.94 KB | jian he |
| #15 | 3033057-ctools31-15.patch | 21.78 KB | jian he |
| #5 | interdiff-3033057-3-4.txt | 9.14 KB | manuel.adan |
| #4 | page_manager-user_tempstore_fix-3033057-4.patch | 17.72 KB | manuel.adan |
| #3 | page_manager-user_tempstore_fix-3033057-3.patch | 11.91 KB | m.lebedev |
Comments
Comment #2
manuel.adanYes, page manager UI is also affected by #2936263: User's temp stores has been moved to core for 8.5.x, introduced in ctools 3.1
Comment #3
m.lebedev commentedYeah!! I get this problem too.
I attach quick fix.
Comment #4
manuel.adanI did the same work. I fix some CS in affected files and added dependency on core system >= 8.5. However, it wont work until #3033634: Replace user temp store service name by the core temp store in forms is solved in ctools.
Comment #5
manuel.adan#3 - #4 interdiff.
Comment #6
m.lebedev commentedI have some problems on the Page access. After submission the plugin form nothing happens. But I found a cause.
https://www.drupal.org/node/2854819
$content['submit']['#attached']['drupalSettings']['ajax'][$content['submit']['#id']]['url'] = $url;
'url' was getting a string value but it gets a object now.
If set it as a string value then settings are submitted. BUT! redirect url will be is wrong
Comment #7
manuel.adanYes, that is another issue, I open a new issue in ctools issue queue for it: #3033651: AJAX forms broken after URL refactoring, string expected instead of object
Comment #8
m.lebedev commentedYes! It's work now..
wow!! My weekend time was spent to solve these problems. I am disappointed
Comment #9
skybow commentedYes, it works now, thanks!
However, it took me a moment to realize that the patch has to be applied onto the
4.x-devcode and not against4.0-beta3. I tried to apply the patch viacomposer.jsonagainst the beta and it failed. After switching to the dev-branch it worked.Comment #10
rajab natshahComment #12
rajab natshahComment #13
rajab natshahComment #15
jian he commentedFix failed testing.
Comment #17
rajab natshahThanks Jian for helping, you are first
still one test .. not sure
Do we have messing fixes in the patch?
or should be a change in the test.
Comment #18
xem8vfdh commentedSo I guess this patch isn't production ready if it's still failing a test, right?
Comment #19
manuel.adanDrupal\page_manager_ui\Tests\PageManagerAdminTest->doTestAddVariant() test fails anyway without the patch and ctools 3.0, It seems to be related to the Drupal core version. Trying with Drupal 8.6 it pass.
Comment #20
xem8vfdh commentedGood to know @manuel.adan, thanks. Is it safe to patch production? Will the future updated release, whenever that comes out, simply overwrite the patch and install seamlessly?
Also, is what @skybow said in #9 true, that this patch must be applied to the
8.x-4.x-devbranch instead of the official8.x-4.0-beta3release branch? If so, and one already has8.x-4.0-beta3installed, are there any instructions anywhere for how to "update" to the dev branch?Also, if it must be applied to the
8.x-4.x-devbranch, I'm wondering why a new beta branch isn't released to handle this. It looks like the beta branch hasn't been touched since April 13 2018, and the dev branch hasn't been touched since April 14th 2018, so I'm guessing they haven't diverged that much in that 1 day, and that the dev branch with this patch can be released as a new8.x-4.0-beta4branch. Is there any hope of that happening?Comment #21
manuel.adanSome other modules, like panels, are also affected by the latest ctools updates. From my point of view, for production environment it is better not to update the ctools module nor any other module that depends on it, keeping it in the 3.0 whenever possible.
I just found #2960937: Replace usage of deprtecated SharedTempStore, dated on April'18 as well. It seems that current maintainers are busy. According to the projects page, it is in seeking co-maintainer(s) status, so I think there will be no new release soon.
Comment #22
xem8vfdh commentedthanks for the info @manuel.adan. The lack of commits for going on 1 year is slightly concerning. Hopefully some co-maintainers can be identified soon. Its such a popular module, I'd think many people would be invested in keep it up.
Also, the problem with your suggestions is that I and others have already updated Ctools.
Comment #23
binnythomas commentedI am facing the same issues. Trying to get Varbase Total Dashboard working and ran into an issue when changing the layout in Page Manager.
Comment #24
ifrikPatch #15 works for me with core 8.6 and Page Manager 4.0-beta3.
Comment #25
xem8vfdh commentedFailing test not related to this patch (see #19)
Verified in #24
Thankfully Panels has released their related patch.
@japerry (or another maintainer), would you mind releasing patch #15 above to finish this up? Would greatly appreciate it :)
Comment #26
OnkelTem commentedAll this is too complicated.
I have Ctools 3.2 and Page Manager seems to work properly in most cases. Does it mean that Page Manager is compatible with Ctools 3.2 or not? Can anybody please elaborate on this? Do I need to apply this patch if I use Ctools 3.2?
Comment #27
OnkelTem commentedI update the title of the issue as it seems applicable to Ctools 3.2 either.
I applied the patch from #15 and things are looking up. I can now reorder variants (see #3044231: Variant weights are not saved) and delete them as well (see #3037225: Call to a member function getVariant() on null )
Comment #28
knyshuk.vova commentedComment #30
japerryThanks for the patches! this is fixed :-D
Comment #31
xem8vfdh commentedThanks for the commit japerry! Any change for a new release to include this commit?