I have a department content type where I use Panelizer enabled for "Full page override." When I click "customize this page" using the IPE everything seem to be fine until I hit "save as default." I am then shown a js dialog that tells me "this will save this configuration as the new default....". I hit ok and then I get another js dialog with this error:
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /panels/ajax/ipe/save_form/panelizer%3Anode%3A208%3Apage_manager
StatusText: OK
ResponseText: Strict warning: Creating default object from empty value in panelizer_panels_cache_save() (line 1211 of /Users/glenn/websites/7c9d097f-0bc1-457d-8314-1d9e37f102bf/profiles/cmf/modules/contrib/panelizer/panelizer.module). =>
*/Let me know if I can provide any more information. I'm running this locally on a Mac using Acquia Dev Desktop along with Google Chrome. I'm running the latest devs of Panels-3.x, Panelizer-3.X, and ctools.
In my logs I see the following:
Notice: Undefined property: stdClass::$export_type in panelizer_export_save_callback() (line 939 of /Users/glenn/websites/7c9d097f-0bc1-457d-8314-1d9e37f102bf/profiles/cmf/modules/contrib/panelizer/panelizer.module).
Hope that helps
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 1931422-save-as-default-getting-wrong-name.patch | 858 bytes | merlinofchaos |
| #6 | Screenshot_3_1_13_2_26_PM.jpg | 74.54 KB | gmclelland |
Comments
Comment #1
merlinofchaos commentedHm. That's really weird. That suggests that, for some reason, this line is failing for you:
Unless your line numbering is significantly different from what's in -dev right now, that's failing on a piece of code that shouldn't actually be running. Can you check panelizer.module and give me 3 or 4 lines around the line that is failing there?
Comment #2
gmclelland commentedStarting at 929
939 is the line if ($object->export_type & EXPORT_IN_DATABASE)
I will replace the module again with a fresh download of the dev release and set if that helps.
Comment #3
gmclelland commentedJust replaced with a fresh copy of panelizer module 3.x-dev
starting at 1209
line 1211 is the line $panelizer->display = $cache->display;
This is included in the function panelizer_panels_cache_save($argument, $cache) {
Comment #4
merlinofchaos commentedSorry, I was referring to the one in the ResponseText at line 1211. I hadn't progressed to the next one yet, though I'll look at that too.
Comment #5
merlinofchaos commentedAh. Yes, that error is just an extension of the first error. It does suggest that our line numbering IS the same, but that just leaves me confused as that shouldn't be an issue.
Question: What the panelizer configuration for the node type? Is 'has default' checked?
Comment #6
gmclelland commentedYes, provide default panel is checked. See attachment.
Comment #7
merlinofchaos commentedAt line 1210, can you use error_log() to find out what the values of $bundle and $name it has acquired and using are?
Comment #8
gmclelland commentedI'm not sure if I'm doing this way you are wanting, but I added the following after line 1210
error_log($bundle, 3, "/users/glenn/Desktop/temp/deleteme.txt");and it printed "department.page_manager" inside of deleteme.txt
Then I changed it to:
error_log($name, 3, "/users/glenn/Desktop/temp/deleteme.txt");but nothing printed inside of deleteme.txt
Comment #9
merlinofchaos commentedTry this patch.
Comment #10
merlinofchaos commentedI'm pretty confident this fixes the issue, though the OP appears to be having other issues discussed on IRC. I think these are unrelated and need to be handled separately.
Committed this patch.
Comment #12
leahtard commentedI was getting the same AJAX error as @gmclelland and my panel layout changes were not saving. I just wanted to confirm that the patch in #9 fixed my issue.
Cheers, Leah