.../admin/settings/
* Caches borrados.
* Skipping broken view 

* warning: Invalid argument supplied for foreach() in .../sites/all/modules/views/includes/view.inc on line 1674.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY vid, position' at line 1 query: SELECT * FROM micrviews_display WHERE vid IN () ORDER BY vid, position in .../sites/all/modules/views/includes/view.inc on line 1305.

This error happened for the first time (& continues on reloading page or clearing cache again) after I activated Javascript Aggregator to minimize javascript, even with JSMin+ instead of JSMin. Before I had activated this module too, but didn't get this error (instead I then got a CSS error on IE only, but not now). No idea if this has anything to do with the views error, not why this error hasn't shown up before.

1296    // Stop if we didn't get any views.
1297    if (!$views) {
1298      return array();
1299    }
1300
1301    $vids = implode(', ', array_keys($names));
1302    // Now load all the subtables:
1303    foreach (view::db_objects() as $key) {
1304      $object_name = "views_$key";
1305      $result = db_query("SELECT * FROM {{$object_name}} WHERE vid IN ($vids) ORDER BY vid, position");
...
...
1660   * Load the object with a row from the database.
1661   *
1662   * This method is separate from the constructor in order to give us
1663   * more flexibility in terms of how the view object is built in different
1664   * contexts.
1665   *
1666   * @param $data
1667   *   An object from db_fetch_object. It should contain all of the fields
1668   *   that are in the schema.
1669   */
1670  function load_row($data) {
1671    $schema = drupal_get_schema($this->db_table);
1672
1673    // Go through our schema and build correlations.
1674    foreach ($schema['fields'] as $field => $info) {
1675      $this->$field = empty($info['serialize']) ? $data->$field : unserialize(db_decode_blob($data->$field));
1676    }
1677  }

Schema module reporting: Nothing with Views, however some other modules with inconsistent databases, mostly minor or slightly different MySQL version adaptions.

Comments

merlinofchaos’s picture

merlinofchaos commented

This message usually indicates the schema is corrupt because something has done strange things to it or not implemented hook_schema() correctly. Try a cache clear.

ClearXS’s picture

ClearXS commented

Ticked-off: "Use JSMin+ instead of JSMin" & "Guardar la configuración" = safe configuration.
=> error messages disappear!

clear cache => exactly same views errors are back.
reload page => message disappears again
clear cache => same error shows up again
reload page => message disappears again

Now I see I hadn't ticked "Optimize and Minify JavaScript files:", so I did:
safe configuration => no errors
clear cache => same errors return

OK, just get rid of all caching ticking off and de-activating everything:
safe configuration => no errors
clear cache => same errors return
reload page => errors disappear
clear cache => errors return

=> Errors seem to be independent of caching variables.

ClearXS’s picture

ClearXS commented

This message usually indicates the schema is corrupt because something has done strange things to it or not implemented hook_schema() correctly. Try a cache clear.

Could be; so many modules trying to let them work together; result: almost always something will go wrong... But see other reply, clearing cache didn't help (I don't have booster or other caching modules activated, only the regular caching page shows up)

Luckely I have no data yet (lost my site over a month ago and now first rebuilding without data). So I will de-install and remove views and install again and see if the error disappears. Problem: views is used by many other modules, so I have to tick them off first and keep record to be able to bring them back in the same state as before.

(in between I got a message that a javascript was running and asked to break off, what normally is a message from my hoster, but this time it said something that JSMin+ still was running. anyway, error didn't go away after turning that javascript of and think its unrelated)

ClearXS’s picture

ClearXS commented

Here my views list of dependencies from .../admin/build/modules (in Spanish):
Requerido por: Audio (activado), Calendar (activado), Calendar iCal (activado), Chart API Views Integration (desactivado), Content Distributor (desactivado), Domain Views (desactivado), Drupal for Facebook Views (desactivado), Features Tests (desactivado), FileField Podcast (activado), Flag abuse (activado), FlashVideo Views (activado), GMaps Views (desactivado), Google Visualization Style (desactivado), Views translation (activado), Image Browser (activado), Image assist (activado), iTunes (activado), Calendar Popup (activado), Linkit Views (desactivado), Migrate (activado), Media Mover Views (desactivado), Notifications Views (desactivado), Organic groups Views integration (activado), Pollfield (activado), Project (desactivado), Project package (desactivado), Project releases (desactivado), Select translation (activado), Spaces Blog (desactivado), Station Archive (activado), Station Catalog (activado), Station Playlist (activado), Station Program (activado), Station Schedule (activado), Statistics Pro (desactivado), Table Wizard (activado), UR-Views (desactivado), Views attach (activado), Bonus: Views Export (desactivado), Bonus: Paged Feed (desactivado), Bonus: Panels (desactivado), Bonus: Views Spy (desactivado), Views Bulk Operations (activado), Views Calc (desactivado), ViewsCharts (activado), Views content panes (activado), Views exporter (desactivado), Views Gallery (desactivado), Views GroupBy (desactivado), Views Popup (desactivado), Views Service (desactivado), Views Slideshow (desactivado), Views Test (desactivado), Views UI (activado), XSPF Playlist Views (activado), Icecast YP (desactivado), Audio Attach (activado), Audio Feeds (activado), Audio getID3 (activado), Audio Images (activado), Audio Import (activado), Audio Playlist (activado), Calendar tooltips (desactivado), Organic Groups Comment (activado), GMaps Content marker options (desactivado), GMaps Views Geo (desactivado), GMaps Views Geo Taxonomy (desactivado), GMaps Views Location (desactivado), Image Browser Plugin - FCKeditor (desactivado), Image Browser Plugin - WYSIWYG API (activado), MediaFront Audio (desactivado), OG Hide Membership (activado), OG Project (desactivado), Organic groups statistics (activado), Organic groups user roles (activado), Project Legacy Paths (desactivado), Project Solr (desactivado), Project usage (desactivado), Simplenews Content Selection Views Integration (desactivado), SoundManager 2 audio player (activado), Spaces OG (desactivado), Total Control (activado), Total Workflow Control (activado), Table Wizard Import Delimited Files (activado), Views Gallery for Organic Groups (desactivado), Views Slideshow: SingleFrame (desactivado), Views Slideshow: ThumbnailHover (desactivado), XSPF Playlist Audio (activado), Icecast YP log (desactivado), Localization groups (desactivado)
Only the activated modules from above list:
Audio (activado), Calendar (activado), Calendar iCal (activado), FileField Podcast (activado), Flag abuse (activado), FlashVideo Views (activado), Views translation (activado), Image Browser (activado), Image assist (activado), iTunes (activado), Calendar Popup (activado), Migrate (activado), Organic groups Views integration (activado), Pollfield (activado), Select translation (activado), Station Archive (activado), Station Catalog (activado), Station Playlist (activado), Station Program (activado), Station Schedule (activado), Table Wizard (activado), Views attach (activado), Views Bulk Operations (activado), ViewsCharts (activado), Views content panes (activado), Views UI (activado), XSPF Playlist Views (activado), Audio Attach (activado), Audio Feeds (activado), Audio getID3 (activado), Audio Images (activado), Audio Import (activado), Audio Playlist (activado), Organic Groups Comment (activado), Image Browser Plugin - WYSIWYG API (activado), OG Hide Membership (activado), Organic groups statistics (activado), Organic groups user roles (activado), SoundManager 2 audio player (activado), Total Control (activado), Total Workflow Control (activado), Table Wizard Import Delimited Files (activado), XSPF Playlist Audio (activado)

=> OK, don't think it's a good idea to tick off (&de-install) all these modules together with views and then install again; quite a lot of work. And suppose I had brought my site back with all data, then I had lost my site again! Anyway, first will try to install other views version and try to do a database update?

merlinofchaos’s picture

merlinofchaos commented

Your best bet is to try an install with just Views and core active and none of the extra contrib modules. If the message appears with just Views, then there's some other strange problem.

If the message doesn't appear then, activate modules one at a time until you can figure out which module causes it.

ClearXS’s picture

ClearXS commented

update.php, cron.php & /admin/content/node-settings/rebuild => no effect (of course not, I had done them before)

Now I get that message again, how is that possible:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: .../sites/all/modules/jquery_update/replace/jquery.min.js?d:12

?? stopped it again, nut how-come, it was de-activated several times on the caching page... The name looks a bit the same as JSMin from the other Javascript Aggregator module ?

ClearXS’s picture

ClearXS commented

recently I installed some additional calendar, so will de-install Calendar iCal & Calendar Popup =>
ticked-off, safe configuration, .../admin/build/modules/uninstall:
de-install: menu-block (was there from something before) & Calendar iCal ; rebuild permissions, cron
=> error remains

I ONLY SEEM TO GET THIS ERROR ON: .../admin/settings/performance AFTER "rebuild cache" button.

So maybe this error just means that there just is no data from views to cache, as I have an empty site? Could that be?

Anyway, I like a clean site before I make it a life site again. But it's a lot of work ripping all those depending modules of and restoring again, for an error that till now hasn't proofed to be more than an error message only. So probably will follow up with making a view page with a few articles, in a few days from now (& maybe the error disappears when there is view content to cache).

ClearXS’s picture

ClearXS commented
Project: Views (for Drupal 7) » Javascript Aggregator
Version: 6.x-3.0-alpha3 » 6.x-1.x-dev

I keep getting this error message on loading the very long modules list in /admin/build/modules :

"A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: .../sites/all/modules/jquery_update/replace/jquery.min.js?C:12" (that C:12 is sometimes differnet)

This error doesn't show up anymore after I click continue (the long list then might be able to finish?). Anyway, I have removed the Javascript Aggregator module.

As the name of jquery.min.js resembles that of JSMin, could it be that the JSMin and JSMin+ option from the Javascript Aggregator module is the cause of this?

=> go shopping around: First change this to Javascript Aggregator and if that's not the place, then to jquery_update module...

jmunning’s picture

jmunning commented

I get this error also on the modules page

subscribing

palanee83’s picture

palanee83 commented

I'm also facing this error and I'm not able to see some of the view that i created.. Any help would be appreciated

ClearXS’s picture

ClearXS commented
Project: Javascript Aggregator » Views (for Drupal 7)
Version: 6.x-1.x-dev » 6.x-3.0-alpha3

After months I ticked some modules on and got this error back; nothing changed yet (except for newly installed module releases),

# warning: Invalid argument supplied for foreach() in .../sites/all/modules/views/includes/view.inc on line 1674.
# user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY vid, position' at line 1 query: SELECT * FROM ....views_display WHERE vid IN () ORDER BY vid, position in .../sites/all/modules/views/includes/view.inc on line 1305.

Well, yes; this time I haven't activated Javascript Aggregator, so most likely this module is not the cause, or at least not in this new case. Though some javascript stopped working.

For the moment I transfer this issue to views, but will research if I get more clues within the next hour or hours.

ClearXS’s picture

ClearXS commented
Project: Views (for Drupal 7) » Calendar
Version: 6.x-3.0-alpha3 » 6.x-2.x-dev

That's quick; I ticked of Calendar 6.x-2.x-dev and the error disappears.

I have no idea or the cause of the error here is the same as a few months ago.

I assume that this error could be generated with any module that clicks into views, causing views to respond with a general error?

I get another error now from another module:
warning: in_array() [function.in-array]: Wrong datatype for second argument in .../sites/all/modules/activism/activism.module on line 612.
This appears unrelated, but one never knows, reason I have to mention it here.

ClearXS’s picture

ClearXS commented
Project: Calendar » Views (for Drupal 7)
Version: 6.x-2.x-dev » 6.x-3.0-alpha3

Back to views again.

After I ticked Calendar on again, the view error didn't return.

So this error might not be Calendar or Javascript Aggregator -or whatever module- related, but:

Views not being able to make the connection on ticking on a module that works with views?

Maybe the error happens more when ticking many modules on, causing an overload somewhere, resulting in not processing the request properly?

ClearXS’s picture

ClearXS commented

I'm not sure about the earlier situations, but now I have a lot of modules that are ticked of against my will, because Drupal could not process the new added modules & started flipping and throwing many (like 50-60) modules out (I have seen this before!)

So I have to put the extensive modules list from .../admin/build/modules/uninstall in one window and tick those on again in another window.

Maybe the error is both caused by views and drupals core?

For the core part, what modules causes this and where can I file the issue?

Letharion’s picture

Letharion commented
Status: Active » Postponed (maintainer needs more info)

Someone with this problem, please provide an export the reproduces this problem.

esmerel’s picture

esmerel commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

No updates for 30 days,

kenorb’s picture

kenorb commented

See: #1330834: Error upgrading Views 6.x-2.12 to 6.x-2.14