Updated to use the latest Views dev release for 7.x and the latest dev release of Ctools, i now get WSOD when trying to get to the Views admin panel, and any page on the site with a view on it shows this notice
Notice: Undefined index: export in ctools_export_crud_load() (line 75 of /Users/.../.../.../sites/all/modules/ctools/includes/export.inc).
And no views are shown.
I couldn't find another issue so not sure if it has been reported yet
Comments
Comment #1
acoustika commentedSame, after opdating views and Ctools to latest dev versions.....
Comment #2
bojanz commentedPlease clear your cache.
Reopen if needed.
Comment #3
renenee commentedI have the exact same situation. My cache is cleared. Problem persists.
Comment #4
pbz1912 commentedI had this problem.
I fixed it by running updates. /update.php
Comment #5
gmopinillosv commentedHi there
The issue continues. I clear cache from my browser and nothing happened. Also I ran " updates. /update.php" and nothing happened.
I don't know what to do. The recomendation is update the last version of View and Ctool and now all is crash.
Could somebody give me a light for all this issue?
I appreciate it so much. Thank you
Comment #6
stephensont commentedYou need to clear Drupal's caches, not your browsers - visit http://yoursite/admin/config/development/performance and click "clear all caches".
You may need to do this a couple of times to clear the problem.
Comment #7
rodolfo.flavio commentedOnly need clear cache, update database and run cron.
Comment #8
Lonelywolf-1 commentedDid clear cache and run cron multple times , still the same.
Comment #9
unknown interloper commentedI cleared all caches, updated database and runed cron and it solved the problem. Thanks!
Comment #11
hass commentedAlso cleared views and core caches several times. This is not the issue of the notice. The issue still exists. I've digged it down to a View that is shown as Block in a sidebar.
These block is from http://drupal.org/project/calendar module and shows the upcoming events. This 'export' array in the
$schemaarray is not set in ctools_export_crud_load() and the reason is that there no $table value provided for this calendar block view.$tableis NULL and thanif (empty($cache[$table])) {is always FALSE and nothing get's cached plus the export array don't get added with "some defaults" insidectools_export_get_schema(). Additionaldrupal_get_schema($table);cannot gives anything back if the $table is NULL...As I'm not sooo 100% familiar with the views code and I cannot say if this is a calendar module issue or views itself. So - what's wrong here?
Comment #12
dawehnerAre you really sure we talk about the same bug as the initial one?
I think this one is definitive different as it's in another function. I underlying issue is about the internal change in the calendar module.
Comment #13
hass commentedThis is 100% the same notice AND I have debugged it down to a bug! So don't close these bug case as it contains a lot of important debug information that took hard time to dig out, please.
Comment #14
swentel commentedSame report in ctools queue, see #1508062: Empty schema array - Undefined index: export in ctools_export_crud_load() (line 75, so this more or less a dupe (or the other). Can't reproduce this also with latest ctools, views AND/OR calendar. It also doesn't make sense that a block is causing that notice. So either some module is calling ctools_export_crud_load() with an empty $table parameter (which would be weird), or someone is calling ctools_export_crud_load() on a table which effectively has no 'export' key. Try adding a debug_backtrace() (or ddebug_backtrace() from devel) in that function to find out.
Note, these are the places where views calls ctools_export_crud_load and table parameter is never empty, so it has to be another module causing that notice.
Comment #15
hass commentedI'm currently only able to repro it if the block in inside the sidebar and I'm using a post form (e.g. search/node). After you hit the submit button the message is shown.
If you look into the code this is all logic. It must happen as the $table is NULL.
Comment #16
hass commentedTried to disable the upcoming block and issue is still there after I posted a search.
Comment #17
hass commentedAfter I disabled the calendar view completely it goes away.
Comment #18
swentel commentedYes, if $table is null, you'll get a notice, we need to know *why* it's throwing a notice as we can't reproduce. So again, can you change to code temporarily in export.inc to this:
That will give us a clue to which schema doesn't have the export key, but also gives the completely call stack.
Comment #19
hass commentedI do not like to post this internals to public... what are you looking for?
Comment #20
swentel commentedWell, the backtrace won't list any confidential information, but you can temporarily paste this in a pastebin somewhere if you want to and add the link here. I'm at least online the next 3 hours, so I can have a very quick look at it and then you can delete that pastebin code again. What I'm looking for ? Well, the backtrace will tell which function where is reponsible for making $table NULL.
Comment #21
hass commentedHeck... maybe related to http://drupal.org/project/custom_formatters, too. If a content type is shown in search results and the a field value exists and is therefore formatted I see this, plain text nodes don't show the message. Just wonder why this change if calender get's disabled.
Comment #22
hass commentedOh, I already opened a ticket for this in #1494150: Notice: Undefined index: export in ctools_export_crud_load(). Too many bugs to remember...
Comment #23
esmerel commentedtag abuse
Comment #24
esmerel commentedI'm doing to dup this to the CTools bug: #1508062: Empty schema array - Undefined index: export in ctools_export_crud_load() (line 75
Comment #25
tasetta commentedstephensont -- thank you so much for that tip! I'd been struggling with this issue for days. I was hesitant to try updating views and ctools because he said it crashed on him. But I had no clue how to clear cache from within drupal. I must remember this one! The first time I cleared, I had an error message that had me thinking oh, I guess I do have to update those modules. But then I happened to click clear again and the error resolved and FINALLY, i have my site!!!!!!!! ahhh. Thank you.