* warning: array_unshift() [function.array-unshift]: The first argument should be an array in C:\Users\David\Sites\acquia-drupal-site\acquia-drupal\sites\all\modules\ctools\includes\ajax.inc on line 522.
* warning: array_unshift() [function.array-unshift]: The first argument should be an array in C:\Users\David\Sites\acquia-drupal-site\acquia-drupal\sites\all\modules\ctools\includes\ajax.inc on line 526.
* warning: array_unshift() [function.array-unshift]: The first argument should be an array in C:\Users\David\Sites\acquia-drupal-site\acquia-drupal\sites\all\modules\ctools\includes\ajax.inc on line 530.
I get these warnings when I try to change the Style of a panel pane and try to choose the option "custom layout". This options doesn't work (literally nothing happens after a short spin of the ajax wheel). Selecting any other option works fine, also using predefined styles.
Panels and Ctools latest dev btw.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | ctools ajax problem.JPG | 71.07 KB | dddave |
| #2 | debugging.JPG | 74.77 KB | dddave |
Comments
Comment #1
merlinofchaos commentedHmm. That's odd, this one is working fine for me.
THe error you're seeing indicates that ctools_ajax_render() is being called with $commands not being an array. Can you do me a favor and put a vsm_trace() at that location, trigger the error, and show me where it's being called from? Also dsm($commands) and show me what's in it?
Comment #2
dddave commentedvsm_trace() only:
With dsm($commands) also in the next line:
I have no clue if I am using dsm($commands) the right way as I never used it before. If that was wrong I might need some guidance. See attached pic for "live" message and the krumo bar.
Comment #3
merlinofchaos commentedCan you update to the latest -dev? This looks like something I fixed maybe a week or two ago.
Comment #4
merlinofchaos commentedIn any case, this:
stylizer.inc: ctools_ajax_render line 151That code has changed, so definitely need to try newest to see.
Comment #5
kmv commentedI have this error too, it is very repeatable, although with the latest -dev I see the errors as:
Could this be a PHP v5.3 related problem? My dev system is running v5.3 and I have noted that the stricter type checking in v5.3 seems to be breaking things all over.
Comment #6
dddave commentedTested with latest devs and I still am getting the same errors. I am NOT using php 5.3.
Of course these warnings are a nuisance but I am wondering what the correct behavior would be. As mentioned I trigger these warnings by chosing "Custom style" for a pane. After some ajax wheel turning nothing happens. What SHOULD happen?
Attached is the vsm/dsm output. Let me know what I can do to help.
Comment #7
kmv commentedWhat SHOULD happen is that a model dialog should open in which you can fill in the custom style details.
In my case, the modal dialog does open, but it does not populate the form - it just sits their spinning. However, clicking on the "Close Window" link in the top right corner does close the dialog. The errors show up when the Panel's window refreshes.
Comment #8
kmv commentedI have noticed that this bug seems to be breaking the module 'Tab Panels Style' - which adds new style options to a pane.
Comment #9
dddave commentedre #7
That would make sense.
re #8
Not using Tab Panels Style either. Just for the record.
Comment #10
kmv commentedPlease ignore #8 I just noticed the status report saying that "Panels is operating in Legacy mode" because Tab Panels Style doesn't report compatibility with the 2.0 API. Sorry for any confusion.
I still have the original problem when I disable the Tab Panels Style module.
Comment #11
dddave commentedMarked #863306: Custom Style option not working as dupe.
Comment #12
merlinofchaos commentedOk, I feel kind of dense for missing this. The 'step' was getting set improperly and skipping the step where you choose a style base, which really does not work. At all.
Checked in a fix. Thanks for the reports on this one! Would hate to have shipped with this broken.