I just updated one of my play around installs and received those warnings:

    * warning: array_merge() [function.array-merge]: Argument #2 is not an array in C:\Users\David\Sites\acquia-drupal-site\acquia-drupal\update.php on line 174.
    * The plugin definition of stylizer cannot locate schema stylizer.
    * warning: Invalid argument supplied for foreach() in C:\Users\David\Sites\acquia-drupal-site\acquia-drupal\sites\all\modules\ctools\plugins\export_ui\ctools_export_ui.class.php on line 54.
    * warning: Invalid argument supplied for foreach() in C:\Users\David\Sites\acquia-drupal-site\acquia-drupal\update.php on line 338.

But luckily:

The following queries were executed
panels module
Update #6310

    * No queries

ctools module
Update #6007

    * No queries

Is this something to worry or investigate?

Comments

merlinofchaos’s picture

Priority:Normal» Minor

Probably not, though I need to find a way to get rid of those warnings.

merlinofchaos’s picture

Status:Active» Fixed

I'm pretty sure I've fixed the update warnings now.

videomusik’s picture

I thought I'd just mention that I had a similar error after updating. I actually found this post by googling the error.

Type          php
Date          Tuesday, July 27, 2010 - 11:32
User          ****
Location	http://nomono.dk/update.php?id=14&op=finished
Referrer	http://nomono.dk/update.php?op=start&id=14
Message	Invalid argument supplied for foreach() in /home/nomono/public_html/sites/all/modules/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.
Severity	error
Hostname	***.***.***.***
Operations	

Doesn't seem to have any effect on the sites functioning though.

Jakob

cheeop’s picture

I got the same error just now while updating it.

warning: Invalid argument supplied for foreach() in .../public_html/modules/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.

The following queries were executed
ctools module
Update #6005
No queries
Update #6007
No queries
panels module
Update #6310
No queries

merlinofchaos’s picture

Fixed the newest round of update warnings.

kt226’s picture

Got the following when I updated ctools AND panels together:

warning: Invalid argument supplied for foreach() in .../httpdocs/modules/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.

The following queries were executed
ctools module
Update #6005
No queries
Update #6007
No queries
panels module
Update #6307
No queries
Update #6308
CREATE TABLE {panels_layout} ( `lid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `category` VARCHAR(255) DEFAULT NULL, `plugin` VARCHAR(255) DEFAULT NULL, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (lid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6309
CREATE TABLE {panels_renderer_pipeline} ( `rpid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `weight` SMALLINT DEFAULT 0, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (rpid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6310
No queries
panels_mini module
Update #6302
ALTER TABLE {panels_mini} ADD `admin_description` LONGTEXT DEFAULT NULL
panels_node module
Update #6001
ALTER TABLE {panels_node} ADD `pipeline` VARCHAR(255) DEFAULT NULL

zap-admin’s picture

Got the same warning myself on two sites I'm working on. First one this afternoon on site 1..... got the line 54 error.....but everything seemed to be running okay. Then I come home this evening to work on site number two. I replaced the ctools and panels modules as I had done before..... went to run update.php and CRASHOLA...... like an idiot....I had a rather emotional outburst at this point... luckily nobody is in the house but me right now...LOL Anyway, I wasn't even able to run the update.php. The error it gave me was something about "line 124" if that means anything to someone more knowledgable of the code here. Should have copied it but I was busy yelling at the computer.

Since I couldn't access anything on the site I went onto my server and deleted the panels module entirely. At this point I was able to access the site again although the mini-panel that made up the home page was no longer showing. This was followed by another emotional outburst and some yelling at God. I don't know if this really helped my case but we all have our moments right? I ran out for a coffee and on the way back home I pulled my head out of my rear and realized that the update had never run/finished. So... I run the update.php again and this time things are okay... but I did get the same "line 54"error you got and another had mentioned. But as one of the good authors of this module stated.... it's probably nothing to worry about since everything so far, is running honkey dory again.

Just thought I'd add my 2 cents here in case someone else runs across the crash with running update.php

c0ley’s picture

I'm getting the same error as #6 when I update to the latest versions of CTools and Panels:

warning: Invalid argument supplied for foreach() in ..etc../sites/all/modules/ctools-6.x-1.3/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.

CTools seems to update OK, but the above error appears when you run update.php after installing the new version of Panels - as a result, none of my node templates display correctly.

I've managed to roll back to an earlier backup (thankfully without losing data).

merlinofchaos’s picture

CTools seems to update OK, but the above error appears when you run update.php after installing the new version of Panels - as a result, none of my node templates display correctly.

I don't follow. How does this warning which does nothing affect your node templates?

c0ley’s picture

I don't follow. How does this warning which does nothing affect your node templates?

I'm a relative newcomer when it comes to Drupal, but I edited the node template for a couple of nodes and used the flexible layout to make the nodes look a bit more presentable (i.e. through admin/build/pages/nojs/operation/node_view/handlers/node_view_panel_context_2/content). However, when I update to the latest version of Panels, the node layout has been affected - panels are no longer displaying where they should be, etc. I also get the following error on the homepage:

    * The plugin definition of panels_layouts cannot locate schema panels_layout.
    * user warning: Table 'db_socref.panels_layout' doesn't exist query: SELECT * FROM panels_layout t__0 WHERE plugin = 'flexible' in /Applications/MAMP/htdocs/socref/sites/all/modules/ctools-6.x-1.3/ctools/includes/export.inc on line 379.
    * user warning: Table 'db_socref.panels_renderer_pipeline' doesn't exist query: SELECT * FROM panels_renderer_pipeline t__0 WHERE name IN ('standard') in /Applications/MAMP/htdocs/socref/sites/all/modules/ctools-6.x-1.3/ctools/includes/export.inc on line 379.

And the following error on update:

warning: Invalid argument supplied for foreach() in /Applications/MAMP/htdocs/MYSITE/sites/all/modules/ctools-6.x-1.3/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.

CTools seems fine, but if I update Panels, this is what happens. Hope that makes sense!

merlinofchaos’s picture

The line 54 error is cosmetic. It's odd that the panels_layout table would not exist, that is created by Panels update #6308.

Go back to update.php, open up the specific updates fieldset and select Panels 6008 and run that. That should ensure the panels_layout table is created.

c0ley’s picture

Hmmm.

While the homepage error didn't appear this time (indicating that the table has been created), the layout for node templates I've edited are still messed up. What appears to have happened is that everything is being "shoved" to the left, so that what was originally in the left hand panel of the main content section is now showing up in the left sidebar, and there is a massive area of white space to the right of the screen, resulting in some horizontal scrolling. If this doesn't explain things, I can post up a couple of screenshots to show you what I mean.

I used the Zen theme to create my own layout - could there be some conflict here?

The previous versions of Panels have no effect - just this one update.

Thanks for your help!

merlinofchaos’s picture

A screenshot might be useful.

I might possibly want to look at the HTML output as well, though actually seeing the page as a whole might be better.

So this is using a custom layout and not flexible?

c0ley’s picture

StatusFileSize
new33.98 KB
new159.94 KB
new388.24 KB

Hi again, thanks for helping out.

I am using a customised theme based on the Zen theme, but I don't think think this is the problem.

The problem seems to be where I have selected a flexible layout. Those using *fixed* column layouts *seem* to be OK, but I'd need to do further investigation.

I've attached some examples. The first screenshot (PanelsProblem1-OK) shows the page before the update, and how it *should* look, and is taken before the most recent Panels update. The second screenshot (PanelsProblem1-NOTOK) shows the result of the update - the column on the left is now pushed to the far left (underneath the menus). PanelsProblem3-NOTOK also shows an example where the column on the far right has been pushed "outside" the main content, and thus horizontal scrolling is required (you can see this by the fact that the menu bar at the top changes from black to white).

The easiest solution would be to use the various column layouts, rather than select the flexible option, but I'm concerned that there is a greater underlying problem.

Hope this is enough info for you!

eatsleepdev’s picture

Hi.

Just installed panels for the first time and this is the warning I get at the top of the modules page:

The plugin definition of panels_layouts cannot locate schema panels_layout.

php5.3.2

appears to be working though

edit - sorry, I posted this in the wrong place. I'm using 6.x-3.7

merlinofchaos’s picture

Can you do an export of one of the failing panels?

#15: eatsleepdev, I don't know why the panels_layout table wouldn't be installed; it's right there, properly, in the schema in panels.install. Try doing an uninstall and a reinstall.

czil’s picture

Hi.
Last update I got a wsod. After I deleted the panels-module, the page was back, but with bad errors. Was not able to update my database.
most of all is this Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 913 bytes) in ....
whats this?
can you help me?

dddave’s picture

@#17

Please don't hijack issues. Your problem is unrelated to the issue discussed here. About your problem: You need more memory. See: http://drupal.org/node/207036

glennnz’s picture

#15 / #16

Same error for me, but it has installed the panels_layout table fine...

c0ley’s picture

#16 here is an export of a failing panel. Thanks so much for your help!

$handler = new stdClass;
$handler->disabled = FALSE; /* Edit this to true to make a default handler disabled initially */
$handler->api_version = 1;
$handler->name = 'node_view_panel_context_2';
$handler->task = 'node_view';
$handler->subtask = '';
$handler->handler = 'panel_context';
$handler->weight = 1;
$handler->conf = array(
  'title' => 'Project',
  'no_blocks' => FALSE,
  'css_id' => '',
  'css' => '',
  'contexts' => array(),
  'relationships' => array(),
  'access' => array(
    'plugins' => array(
      0 => array(
        'name' => 'node_type',
        'settings' => array(
          'type' => array(
            'project' => 'project',
          ),
        ),
        'context' => 'argument_nid_1',
      ),
    ),
    'logic' => 'and',
  ),
);
$display = new panels_display;
$display->api_version = 1;
$display->layout = 'flexible';
$display->layout_settings = array(
  'items' => array(
    'canvas' => array(
      'type' => 'row',
      'contains' => 'column',
      'children' => array(
        0 => 'main',
      ),
      'parent' => NULL,
    ),
    'main' => array(
      'type' => 'column',
      'width' => 100,
      'width_type' => '%',
      'children' => array(
        0 => 'main-row',
      ),
      'parent' => 'canvas',
    ),
    'main-row' => array(
      'type' => 'row',
      'contains' => 'region',
      'children' => array(
        0 => 'project_left',
        1 => 'center',
      ),
      'parent' => 'main',
    ),
    'center' => array(
      'type' => 'region',
      'title' => 'Center',
      'width' => '100',
      'width_type' => '%',
      'parent' => 'main-row',
    ),
    'project_left' => array(
      'type' => 'region',
      'title' => 'Project Left',
      'width' => '240',
      'width_type' => 'px',
      'parent' => 'main-row',
    ),
  ),
);
$display->panel_settings = array();
$display->cache = array();
$display->title = '%node:title';
$display->content = array();
$display->panels = array();
  $pane = new stdClass;
  $pane->api_version = 1;
  $pane->pid = 'new-1';
  $pane->panel = 'center';
  $pane->type = 'block';
  $pane->subtype = 'quicktabs-2';
  $pane->shown = TRUE;
  $pane->access = array();
  $pane->configuration = array(
    'override_title' => 0,
    'override_title_text' => '',
  );
  $pane->cache = array();
  $pane->style = array();
  $pane->css = array();
  $pane->extras = array();
  $pane->position = 0;
  $display->content['new-1'] = $pane;
  $display->panels['center'][0] = 'new-1';
  $pane = new stdClass;
  $pane->api_version = 1;
  $pane->pid = 'new-2';
  $pane->panel = 'project_left';
  $pane->type = 'views';
  $pane->subtype = 'project_staff_avatar';
  $pane->shown = TRUE;
  $pane->access = array();
  $pane->configuration = array(
    'override_pager_settings' => 0,
    'use_pager' => 1,
    'nodes_per_page' => '0',
    'pager_id' => '',
    'offset' => '0',
    'more_link' => 0,
    'feed_icons' => 0,
    'panel_args' => 1,
    'link_to_view' => 0,
    'args' => '%0',
    'url' => '',
    'display' => 'panel_pane_1',
    'context' => array(
      0 => 'argument_nid_1.nid',
    ),
    'override_title' => 0,
    'override_title_text' => '',
  );
  $pane->cache = array();
  $pane->style = array();
  $pane->css = array();
  $pane->extras = array();
  $pane->position = 0;
  $display->content['new-2'] = $pane;
  $display->panels['project_left'][0] = 'new-2';
  $pane = new stdClass;
  $pane->api_version = 1;
  $pane->pid = 'new-3';
  $pane->panel = 'project_left';
  $pane->type = 'views';
  $pane->subtype = 'project_status';
  $pane->shown = TRUE;
  $pane->access = array();
  $pane->configuration = array(
    'override_pager_settings' => 0,
    'use_pager' => 0,
    'nodes_per_page' => '1',
    'pager_id' => '',
    'offset' => '0',
    'more_link' => 0,
    'feed_icons' => 0,
    'panel_args' => 1,
    'link_to_view' => 0,
    'args' => '%1',
    'url' => '',
    'display' => 'panel_pane_1',
    'override_title' => 0,
    'override_title_text' => '',
  );
  $pane->cache = array();
  $pane->style = array();
  $pane->css = array();
  $pane->extras = array();
  $pane->position = 1;
  $display->content['new-3'] = $pane;
  $display->panels['project_left'][1] = 'new-3';
  $pane = new stdClass;
  $pane->api_version = 1;
  $pane->pid = 'new-4';
  $pane->panel = 'project_left';
  $pane->type = 'views';
  $pane->subtype = 'project_fundingbody';
  $pane->shown = TRUE;
  $pane->access = array();
  $pane->configuration = array(
    'override_pager_settings' => 0,
    'use_pager' => 1,
    'nodes_per_page' => '0',
    'pager_id' => '',
    'offset' => '0',
    'more_link' => 0,
    'feed_icons' => 0,
    'panel_args' => 1,
    'link_to_view' => 0,
    'args' => '%1',
    'url' => '',
    'display' => 'panel_pane_1',
    'context' => array(
      0 => 'argument_nid_1.nid',
    ),
    'override_title' => 0,
    'override_title_text' => '',
  );
  $pane->cache = array();
  $pane->style = array();
  $pane->css = array();
  $pane->extras = array();
  $pane->position = 2;
  $display->content['new-4'] = $pane;
  $display->panels['project_left'][2] = 'new-4';
  $pane = new stdClass;
  $pane->api_version = 1;
  $pane->pid = 'new-5';
  $pane->panel = 'project_left';
  $pane->type = 'views';
  $pane->subtype = 'project_fundingbody';
  $pane->shown = TRUE;
  $pane->access = array();
  $pane->configuration = array(
    'override_pager_settings' => 0,
    'use_pager' => 1,
    'nodes_per_page' => '0',
    'pager_id' => '',
    'offset' => '0',
    'more_link' => 0,
    'feed_icons' => 0,
    'panel_args' => 1,
    'link_to_view' => 0,
    'args' => '%1',
    'url' => '',
    'display' => 'panel_pane_3',
    'context' => array(
      0 => 'argument_nid_1.nid',
    ),
    'override_title' => 0,
    'override_title_text' => '',
  );
  $pane->cache = array();
  $pane->style = array();
  $pane->css = array();
  $pane->extras = array();
  $pane->position = 3;
  $display->content['new-5'] = $pane;
  $display->panels['project_left'][3] = 'new-5';
$display->hide_title = PANELS_TITLE_FIXED;
$display->title_pane = '0';
$handler->conf['display'] = $display;

Seems to be affecting anything edited through the Manage Pages section (/admin/build/panels/dashboard) - anything edited through pages (/admin/build/pages) seems to be fine (note that, despite what I said earlier, user pages seem to be OK).

Thanks again!

EDIT - note that the above export was taken before the update.

bkosborne’s picture

Version:6.x-3.x-dev» 6.x-3.7

Also got this error while upgrading from 3.5 to 3.7

warning: Invalid argument supplied for foreach() in /var/www/vhosts/wearerugby.com/httpdocs/sites/all/modules/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.
jamesskywalker’s picture

Received similar warning message when updating Chaos tool suite 6.x-1.6 to 6.x-1.7 and Panels 6.x-3.5 to 6.x-3.7.

warning: Invalid argument supplied for foreach() in /Applications/MAMP/htdocs/ktwr/sites/all/modules/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.

The following queries were executed
ctools module
Update #6005
No queries
Update #6007
No queries
panels module
Update #6307
No queries
Update #6308
CREATE TABLE {panels_layout} ( `lid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `category` VARCHAR(255) DEFAULT NULL, `plugin` VARCHAR(255) DEFAULT NULL, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (lid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6309
CREATE TABLE {panels_renderer_pipeline} ( `rpid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `weight` SMALLINT DEFAULT 0, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (rpid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6310
No queries
panels_mini module
Update #6302
ALTER TABLE {panels_mini} ADD `admin_description` LONGTEXT DEFAULT NULL
panels_node module
Update #6001
ALTER TABLE {panels_node} ADD `pipeline` VARCHAR(255) DEFAULT NULL

gozigzag’s picture

On updating Ctools to 1.7 and Panels to 6.x-3.7 together, I got the error message that Panels could not update without updating Ctools to 1.7. Ctools seemed to update ok. Anyway, why Panels could not update seemed puzzling to me, as I was updating Ctools as the error said I needed to.

So, I tried rolling back to previous version of Panels- ran update and I got this message:

Failed: The Panels module cannot be updated while disabled. If you wish to update Panels, please enable it. If you do not wish to update Panels, please uninstall it.

Question - Do you need to enable Panels before updating?

dddave’s picture

??
Quote from the error message you just posted: "If you wish to update Panels, please enable it."

gozigzag’s picture

The correct procedure is not clear. For updating modules, I thought it was best practice to backup files and db, disable modules, delete old module files, upload new modules files, and then run update.

So, once I got the message to enable Panels before updating, I went and enabled Panels module. I ran update and got:

user warning: Table 'panels_renderer_pipeline' already exists query: CREATE TABLE panels_renderer_pipeline ( `rpid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `weight` SMALLINT DEFAULT 0, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (rpid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /home/content/44/4787244/html/includes/database.inc on line 550.
warning: Invalid argument supplied for foreach() in /home/content/44/4787244/html/sites/all/modules/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.
The delegator module has been replaced by the Page Manager module. You should enable the page manager module to ensure that any panel pages you have will not be lost.
Updates were attempted. If you see no failures below, you may proceed happily to the administration pages. Otherwise, you may need to update your database manually. All errors have been logged.

Main page
Administration pages
The following queries were executed
panels module
Update #6290
ALTER TABLE {panels_pane} CHANGE `access` `access` LONGTEXT DEFAULT NULL
DELETE FROM {system} WHERE name IN ('panels_page', 'panels_views')
Update #6291
Failed: ALTER TABLE {panels_pane} ADD `style` LONGTEXT DEFAULT NULL
Failed: ALTER TABLE {panels_pane} ADD `css` LONGTEXT DEFAULT NULL
Failed: ALTER TABLE {panels_pane} ADD `extras` LONGTEXT DEFAULT NULL
Update #6292
Panel panes were updated
Update #6293
Panel displays were updated
Update #6300
No queries
Update #6302
No queries
Update #6303
No queries
Update #6304
No queries
Update #6305
Failed: ALTER TABLE {panels_display} ADD `title_pane` INT DEFAULT 0
Update #6306
No queries
Update #6307
No queries
Update #6308
Failed: CREATE TABLE {panels_layout} ( `lid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `category` VARCHAR(255) DEFAULT NULL, `plugin` VARCHAR(255) DEFAULT NULL, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (lid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6309
Failed: CREATE TABLE {panels_renderer_pipeline} ( `rpid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `weight` SMALLINT DEFAULT 0, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (rpid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6310
No queries

I feel like I am wasting a lot of time trying to update (initially the supposed correct way). I tried enabling other modules and updating, but could not get it to work. For now, I have rolled back to previous versions.

I would appreciate some instructions ahead of time of the correct update procedure.

codewatson’s picture

I think this is related to #15 but on a brand new install of drupal and installing panels i get the following:

Drupal 6.17
Panels 6.x-3.7
ctools 6.x-1.7

Ctools:
Enable ctools: Fine
Enable Bulk Export: Fine
Enable custom content panes: fine
Enable Stylizer:
"The plugin definition of stylizer cannot locate schema stylizer.
warning: Invalid argument supplied for foreach() in C:\Servers\wamp\www\drupal6\sites\all\modules\ctools\plugins\export_ui\ctools_export_ui.class.php on line 54."

Enable Custom Rulesets:
"The plugin definition of ctools_access_ruleset cannot locate schema ctools_access_ruleset.
warning: Invalid argument supplied for foreach() in C:\Servers\wamp\www\drupal6\sites\all\modules\ctools\plugins\export_ui\ctools_export_ui.class.php on line 54."

Enable Page manager: Fine
Enable Views content Panes: Fine

Panels:
Enable panels: Fine
Enable panel_nodes: Fine

Enable mini_panels:
"The plugin definition of panels_mini cannot locate schema panels_mini.
warning: Invalid argument supplied for foreach() in C:\Servers\wamp\www\drupal6\sites\all\modules\ctools\plugins\export_ui\ctools_export_ui.class.php on line 54."

On each of the errors i checked the db to see if the table existed which it in fact did, so it seems like on install/update there is something within panels/ctools that is looking for those tables before they are actually created?

There doesn't seem to be any problems outside of the error message with this on a new install and on the existing site that i updated from panels 3.5 to 3.7 (ctools 1.5 to 1.7) i got these errors but saw no problems otherwise.

dddave’s picture

re#25

Just noticed that the docs about upgrading modules is ... not that good. First I could not find anything and when I found the docs they were very misleading.

When you only want to upgrade a module without changing the drupal version (e.g. from D6 to D7), i.e. just want go from Panels 3.6 to 3.7 you should do it this way:

1) Put site in maintenance
2)Delete the old module folder and replace it with the new one (without disabling it). Do NOT use the delete function on the module page because this will wipe the database. Delete the folder at sites/all/modules.
3) Run update.php

Note that for Panels and CTools you should do the upgrade for both simultaneously.

gozigzag’s picture

Sorry, before I did not show the full info of my update. I tried to update again. This time, I first updated CTools by itself 6.1.6 -> 6.1.7. I then updated Panels 6.3.5 ->6.3.6, I got the following:

The following queries were executed
panels module
Update #6307
No queries
Update #6308
CREATE TABLE {panels_layout} ( `lid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `category` VARCHAR(255) DEFAULT NULL, `plugin` VARCHAR(255) DEFAULT NULL, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (lid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6309
CREATE TABLE {panels_renderer_pipeline} ( `rpid` INT NOT NULL auto_increment, `name` VARCHAR(255) DEFAULT NULL, `admin_title` VARCHAR(255) DEFAULT NULL, `admin_description` LONGTEXT DEFAULT NULL, `weight` SMALLINT DEFAULT 0, `settings` LONGTEXT DEFAULT NULL, PRIMARY KEY (rpid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6310
Failed: Panels cannot be updated because CTools 1.7 (API v1.7.2) is required. Please update CTools and then try update.php again.
panels_mini module
Update #6302
ALTER TABLE {panels_mini} ADD `admin_description` LONGTEXT DEFAULT NULL
panels_node module
Update #6001
ALTER TABLE {panels_node} ADD `pipeline` VARCHAR(255) DEFAULT NULL

I am confused about what I do if anything from this point. It appeared to create and alter tables. But message suggests it failed to update. This is the only error message I receive. No modules have been enabled yet. On modules page, it lists Panels version as 6.3.7 as if it updated successfully. Should I just ignore failed update message?

Thanks in advance

yosisays’s picture

I'm getting this message upon my upgrade attempt

Failed: Panels cannot be updated because CTools 1.7 (API v1.7.2) is required. Please update CTools and then try update.php again.

the problem with this is that the latest version of CTools 1.7 is updated! so why am i getting this error?

gozigzag’s picture

Re: #27

This should be more clearly spelled out somewhere. I've read a couple of different pages about how to update modules. I have not seen where it says you should do it this way. I couldn't find anything regarding procedure in the Panels files (such as in INSTALL.txt) nor on the Panels Project page. Granted, there is a lot of work to be done, only so many people doing it. I would really like to see this better spelled out somewhere.

merlinofchaos’s picture

In general my module upgrade procedure is this:

Log in as UID 1. Put the site in maintenance mode. Delete the directories of the modules to be upgraded and unpack the tarballs. (Alternatively use cvs up -dP or use drush). Then visit update.php and proceed normally.

I'm not sure why there are instructions out there telling people to turn modules off to run update.php. Panels, unfortunately, cannot update while it's not enabled, as the updater needs to access code within the module which is not available if the module is disabled. I can't address those instructions. All I can do is to put the instructions in.

People: PLEASE stop reporting this error:

    * warning: Invalid argument supplied for foreach() in C:\Users\David\Sites\acquia-drupal-site\acquia-drupal\sites\all\modules\ctools\plugins\export_ui\ctools_export_ui.class.php on line 54.

As I said in #11, the error is cosmetic. It's fixed in -dev, and you can ignore it in the current release.

Finally, to the people receiving the complaint about Panels saying it can't be updated because you don't have CTools 1.7, I suggest you double and triplecheck that you have the right version of CTools. I just checked the released version of the file, and that version of CTools correctly reports its API version as 1.7.2. It is also possible that you can get this error if you do not have Panels enabled when updating. As said above, Panels must be enabled for the updates. The error will simply cause Panels to pause the update. Enabling it and reprocessing update.php should cause it to pick up where it left off.

You can upgrade CTools first or you can upgrade Panels and CTools simultaneously. You can't upgrade Panels prior to CTools. The dependencies make that not possible. That's why the system prevents it.

c0ley’s picture

Just to say...I managed to "fix" the problem I had with wonky panels (see e.g. #14). Basically, as I only had a few panels, I deleted them and recreated them - so they seem to work fine now (plus I've made them look nicer too :-) )

For info, the problem related to panels based on a flexible layout - not sure why, as I'm a Drupal newbie, plus it doesn't seem to be a "known" error as no-one else (as far as I can tell) has reported it.

So you can close my issue!

mrgoltra’s picture

subscribing..

beyond67’s picture

Subscribe

megic’s picture

subscribing as well ...

Observer123’s picture

sub....

HGrf’s picture

sub

buttonwillowsix’s picture

subscribe

lilott8’s picture

subscribe

jeffreyvddb’s picture

I've updated Panels and CTools today and I've got the warning "The plugin definition of panels_layouts cannot locate schema panels_layout.". Furthermore, a Panel isn't showing any information due to another error. I can't say which error it was, because I deleted the panel. When I try to import it, I get the error "Unable to get a page from the import. Errors reported: No handler found."

Here is the export of the page:

Removed the code.
merlinofchaos’s picture

That export is only the variant, not a full page, so all you can do is add that to an already existing page by using the 'import variant' function.

jeffreyvddb’s picture

Thanks! It worked :)

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

texas-bronius’s picture

For anyone else just coming across this, see merlinofchaos' comment above to run update.php. I came across this persistent warning after doing a drush up, allowing all modules to update, then aborting before Drupal Core would get updated. Apparently the db updates never took. Running update.php from the browser took care of it.

Junro’s picture

subscribe

Louis Swanepoel’s picture

On #31:

I upgraded Ctools and Panels at the same time. I still got the error message and after this some new installation of modules would install, but not operate correctly. (mobify & backup&migrate)

bryancasler’s picture

subscribe

Summit’s picture

Version:6.x-3.7» 6.x-3.x-dev

subscribe having on latest dev (april 20th 2011).
It is the first time I install panels on this instance!

* The plugin definition of panels_layouts cannot locate schema panels_layout.
# The plugin definition of panels_mini cannot locate schema panels_mini.
vegantriathlete’s picture

I also had received the error:
The plugin definition of panels_mini cannot locate schema panels_mini.

I'm on 6.x-3.9. When I looked in panels_mini.install everything seemed to be okay. There is clearly a schema defined. So, I thought that maybe the problem lay elsewhere.

I was using drush (4.4) to enable modules and had enabled Menu Minipanels, which triggered the dependencies. Maybe something is not running properly through drush.

I think I have "resolved" the issue by:

Uninstalling Menu Minipanels
Uninstalling Mini Panels
Install Mini Panels (through the modules UI)
Install Menu Minipanels (through the modules UI)

vegantriathlete’s picture

Update: I have had to do some other things on the site and I am still getting the error message. My situation is a little messy, so it's hard to isolate all the variables. But, I can tell you that the latest status is that uninstalling and reinstalling is not removing the error message.

However, I do see the table in the database. So, it seems that something is falsely triggering the error message.

VM’s picture

6.x-3.x-dev should be tested in a test environment to try and reproduce the issue.

Dave Kopecek’s picture

Getting same error as #48 above:

The plugin definition of panels_mini cannot locate schema panels_mini.

I'm running the same code, checked out with SVN on a dev server and local environment. Mini panels installs without an error on the local environment, but has the error on the dev server.

Dev Server - gets schema error:
MySQL database 5.1.41
PHP 5.2.13

Local Machine - no schema error:
MySQL database 5.1.52
PHP 5.3.3

Tried uninstalling / reinstalling panels_mini both with ui and with drush. Install creates panels_mini table in database, uninstall removes the table. No errors Apache logs or watchdog. Unable to resolve issue.

Dave Kopecek’s picture

Ok, this issue has been bouncing around for quite a while.

CLEAR YOUR CACHE !!

#3 here: http://drupal.org/node/1057542 was the clue I needed. This error is dispalyed from ctools\includes\export-ui.inc.

Here's a comment from export-ui.inc:

// If we're on the modules page and building a menu, there is a design flaw
  // in Drupal core that causes modules to be installed but the schema does
  // not become available until AFTER menu rebuild. This helps smooth that
  // out. This is a HACK but it should work:

Here's all I needed to do:
1. Install panels_mini
2. Clear the cache.
Voila, "Panels Mini" shows up under "Site Building" in admin_menu.

As noted elsewhere this may be a repeat of:
#1099838:Cannot locate schema errors, #856636: Update warnings, #1057542: Error message when initially enabling the module, #875916: Installation error for mini panels,#902750 The plugin definition of panels_mini cannot locate schema panels_mini, and possibly a couple more.