I'm not sure what's going on here because I'm not getting anything in my logs, with error_reporting set to all. On some pages, I get this error in the page footer; on other pages, I ONLY get this error:
The website encountered an unexpected error. Please try again later.
If I disable the Extras module, it's fine.
Don't have more info for you yet but I'll add more here as I learn more.
| Comment | File | Size | Author |
|---|---|---|---|
| #27 | list_of_modules.txt | 24.31 KB | ardnet |
Comments
Comment #1
swentel commentedhrm, that doesn't sound good :/ Could you give me a list of the modules you're using, maybe I can reproduce this.
Comment #2
BrockBoland commentedHere's the full list. I tried it on my more basic D7 local testing site and couldn't replicate it, so I'm going to create a dev copy of this site and start disabling modules to see if it goes away at some point.
block
addthis
color
comment
contact
content_migrate
contextual
ctools
dashboard
date
date_api
date_popup
date_views
ds_extras
field
field_sql_storage
field_ui
file
filter
googleanalytics
help
image
link
list
markdown
menu
mollom
node
nodequeue
number
options
path
rdf
search
semanticviews
shortcut
smartqueue
system
taxonomy
text
toolbar
trigger
update
user
views_ui
xmlsitemap_menu
xmlsitemap_node
xmlsitemap_taxonomy
ds
pathauto
xmlsitemap
xmlsitemap_engines
token
views
standard
dblog
overlay
redirect
Comment #3
BrockBoland commentedI just realized something I should have led with: this is a site that I'm in the process of upgrading from D6. The site crapped out completely after running the update script, because the ds update function didn't update the schema so one of the tables was missing (ds_view_modes, I think). Since it's a pretty simple personal site, I just uninstalled DS so it would remove my old data, then re-installed it to re-create the DB tables.
Did some more digging and found the schema version in the system table is -1. I ran update.php, but it didn't list any updates for ds_extras - not sure about that part.
Then, I found where the "The website encountered an unexpected error" message was coming from and added some more debugging output and found this:
SQLSTATE[42S22]: Column not found: 1054 Unknown column revision.ds_switch in field listSo the ds_switch field was missing from node_revision. As it turns out, the ds_vd table already existed. The install process for ds_extras was failing when it tried to create that table (since it was already there), so it never got to creating this missing column - and that's why the schema number was -1 in the system table.
I nuked the table manually and re-enabled the ds_extras module, and that fixed it. I'm not sure how that table got there without finishing the install process - so maybe this was a one-time problem?
Comment #4
swentel commentedHrm yeah, must have been a one time problem here - updates from D6 to D7 are complicated anyways (especially with a more complex site). So closing this for now.
Comment #5
yareckon commentedAnother common case for this is when you make a backup with backup and migrate, enable extras, do some stupid stuff, and try to roll back to the backup. Backup and migrate doesn't drop tables, so you get in the situation above.
Here is an issue to try to get backup and migrate to allow dropping tables on restore #1104012: On restore, provide option to drop all tables
Comment #6
MrsWho commentedI have a site that was built from the start in 7.10 and I've run into this same problem. I had tried extras at one point in developing this site, but ran into a problem and reverted back to before (or so I thought). Today I tried to enable Extras, and ran into this message:
DatabaseSchemaObjectExistsException: Table <em class="placeholder">ds_vd</em> already exists. in DatabaseSchema->createTable() (line 652 of C:\wamp\www\fwbpress\includes\database\schema.inc).Also, when I navigated to any node on the site, I only saw this message:
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'revision.ds_switch' in 'field list': SELECT revision.vid AS vid, base.uid AS uid, revision.title AS title, revision.log AS log, revision.status AS status, revision.comment AS comment, revision.promote AS promote, revision.sticky AS sticky, revision.ds_switch AS ds_switch, base.nid AS nid, base.type AS type, base.language AS language, base.created AS created, base.changed AS changed, base.tnid AS tnid, base.translate AS translate, base.premium AS premium, revision.timestamp AS revision_timestamp, revision.uid AS revision_uid FROM {node} base INNER JOIN {node_revision} revision ON revision.vid = base.vid WHERE (base.nid IN (:db_condition_placeholder_0)) ; Array ( [:db_condition_placeholder_0] => 290 ) in DrupalDefaultEntityController->load() (line 196 of C:\wamp\www\fwbpress\includes\entity.inc).I disabled the module, which got rid of the PDOexception. I tried going into the databases and deleting the table "ds_vd" table, then enabling Extras. The same thing happened.
I reverted to a backup (by which I cleared my sites folder, put in my backup of the sites folder, and used backup/restore to restore the database). I went into MYSQL and deleted the "ds_vd" table. I enabled Extras and got this error message:
And the PDOException is back on all nodes.
So, it seems there's some other Extras artifact floating in the database causing problems when I enabled it. Any help hunting them down would be appreciated. I have the following modules installed on version 7.10:
Address Field: 7.x-1.0-beta2
Backup and Migrate: 7.x-2.2
Block: 7.1
Book: 7.1
CAPTCHA: 7.x-1.0-beta2
Chaos tools: 7.x-1.0-rc1
Chaos Tools (CTools) Plugin Example: 7.x-1.0-rc1
CKEditor: 7.x-1.6
CKEditor Link: 7.x-2.1
Color: 7.1
Colorbox: 7.x-1.2
Comment: 7.1
Content locking (edit lock): 7.x-1.1
Contextual links: 7.1
Dashboard: 7.1
Database logging: 7.1
Date: 7.x-2.0-rc1
Date All Day: 7.x-2.0-rc1
Date API: 7.x-2.0-rc1
Date Context: 7.x-2.0-rc1
Date Migration: 7.x-2.0-rc1
Date Migration Example: 7.x-2.0-rc1
Date Popup: 7.x-2.0-rc1
Display suite: 7.x-1.4
Dynamic display block: 7.x-1.0
Email: 7.x-1.0
Entity API: 7.x-1.0-rc1
Entity tokens: 7.x-1.0-rc1
Extras: 7.x-1.4
Facebook Likebox: 7.x-1.2
Field: 7.1
Field SQL storage: 7.1
Field UI: 7.1
Fieldgroup: 7.x-1.1
File: 7.1
File Field Sources: 7.x-1.4
Filter: 7.1
Footnotes: 7.x-2.5
Footnotes Wysiwyg: 7.x-2.5
Gallery Formatter: 7.x-1.0
Geocoder API: 7.x-1.x-dev
Geofield: 7.x-1.0-beta2
Geofield Map: 7.x-1.0-beta2
Help: 7.1
Image: 7.8
Image caption: 7.x-1.0-beta3
Image caption filter: 7.x-1.0-beta3
IMCE: 7.x-1.5
IMCE Mkdir: 7.x-1.0
Insert: 7.x-1.1
Libraries: 7.x-1.0
Link: 7.x-1.0
List: 7.1
Masquerade: 7.x-1.0-rc4
Menu: 7.1
Module filter: 7.x-1.6
Name Field: 7.x-1.4
Node: 7.1
Node Option Premium: 7.x-1.1
Number: 7.1
On The Web: 7.x-1.2
Options: 7.1
Overlay: 7.1
Path: 7.1
Pathauto: 7.x-1.0
Pathologic: 7.x-1.4
RDF: 7.1
Real name: 7.x-1.0-rc2
reCAPTCHA: 7.x-1.7
Scheduler: 7.x-1.0
Search: 7.1
Search 404: 7.x-1.1
Shortcut: 7.1
Smart Paging: 7.x-1.3
System: 7.1
Taxonomy: 7.1
Taxonomy display: 7.x-1.0
Text: 7.1
Text Resize: 7.x-1.7
Token: 7.x-1.0-beta7
Toolbar: 7.1
Update manager: 7.1
User: 7.1
User protect: 7.x-1.0
User role field: 7.x-1.0-beta1
Views: 7.x-3.0
Views Accordion: 7.x-1.0-rc1
Views UI: 7.x-3.0
Webform: 7.x-3.15
Comment #7
Louis Bob commentedsame issue here, with the 7.x-1.5 version of the Extras module.
When the Extras module is activated, /admin/structure/types/manage/annonce/display/teaser page causes a HTTP 500 Error (Internal Server Error).
For all other displays no problem, except for /admin/structure/types/manage/annonce/display/full where I have this error:
I had the same error message just before but indicating the Panels module, instead of cTools now. So I uninstalled Panels, and get this error now with cTools. I don't want to uninstall cTools module now, and get the same error message with another module again.
When Extras is not activated, there is no error.
What do you reckon?
Comment #8
broncomania commentedHere is my error when i install extras.
The field ds_switch is not created when i enable the extras module.
Comment #9
Jan van Diepen commentedI'm running 7-x-1.4 of the whole display suite and get the following error:
(Note the "//" at the start of the path. It's because the required module can not be found.)
I checked for the required module and it's panels.
Seems there is some kind of dependency on the panels module introduced by ds_extras.
Comment #10
swentel commentedLooks like #1459910: Drupal 7 crashing after ds_extras had been disabled and uninstalled has some answer - could you check the solution in #1 in that issue to see if that fixes the errors ? If so, I can easily create a patch for that.
Comment #11
Louis Bob commentedTried deleting 'entity_form' from the cache table as mentioned in #10,
but I still have the same error as in #7.and it's working!Comment #12
Louis Bob commentedSorry, it's actually working fine for me now (I was mistaking with another similar issue I have with the Search API module).
Comment #13
dgtlmoon commentedsame problem here
Comment #14
muranod commentedI get this message when enabling extras:
Warning: array_flip() [function.array-flip]: Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->load() (line 178 of C:\wamp\www\drupal-7.10\includes\entity.inc).
Warning: array_flip() [function.array-flip]: Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->cacheGet() (line 354 of C:\wamp\www\drupal-7.10\includes\entity.inc).
Notice: Undefined index: in ds_extras_entity_view_alter() (line 895 of C:\wamp\www\drupal-7.10\sites\all\modules\ds\modules\ds_extras\ds_extras.module).
Hoping for some direction here before I try disabling, uninstalling and reinstalling DS, since that looks problematic.
Thanks
Comment #15
muranod commentedI displayed the Extras, Forms and Search display components of Display Suite, then uninstalled them, leaving Display Suite itself intact, since that by itself was not causing any issues. Everything worked without errors. Then I reinstalled / enabled those three components and everything seems to be functioning normally.
Comment #16
dgtlmoon commentedso its not really solved, perhaps it's looking for a function that doesnt exist?
Comment #17
puddyglumI have a possibly related issue when Extras is enabled. I get an error related to Entity load. I updated the Date module on my site, and when I go to /update.php I get an error: Undefined index base table
Date module (date_views.module:100)
entity_get_info() returns an array of entity arrays, which has a 'base table' index. But ds_views does not, and it gives me an error. I disabled DS Extras and the error went away.
Comment #18
puddyglumI disabled Extras and then enabled it and it works now...
Comment #19
swentel commentedOk, closing this for now. As for the data_views thing, checking if a base table exists is probably the best idea in that module.
Comment #20
tdurocher commentedI'm still getting the exact same errors as #6 on 7.x-1.5 when enabling Extras. Disabling Extras removes the errors but re-enabling Extras brings them back again. Thanks.
Comment #21
tdurocher commentedOk, now with Extras turned off I get the following error when attempting a two-column layout on a node teaser. Note that I attempted to uninstall Display Suite entirely in response to these errors and it did not appear in the uninstall list after disabling all related modules. To my knowledge I have no other DS stuff in use, although I have played with it on this test site in the past.
Here is the (long) error message:
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'revision.ds_switch' in 'field list': SELECT revision.vid AS vid, base.uid AS uid, revision.title AS title, revision.log AS log, revision.status AS status, revision.comment AS comment, revision.promote AS promote, revision.sticky AS sticky, revision.ds_switch AS ds_switch, base.nid AS nid, base.type AS type, base.language AS language, base.created AS created, base.changed AS changed, base.tnid AS tnid, base.translate AS translate, base.premium AS premium, revision.timestamp AS revision_timestamp, revision.uid AS revision_uid FROM {node} base INNER JOIN {node_revision} revision ON revision.vid = base.vid WHERE (base.nid IN (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2, :db_condition_placeholder_3, :db_condition_placeholder_4, :db_condition_placeholder_5, :db_condition_placeholder_6, :db_condition_placeholder_7, :db_condition_placeholder_8, :db_condition_placeholder_9, :db_condition_placeholder_10, :db_condition_placeholder_11, :db_condition_placeholder_12, :db_condition_placeholder_13, :db_condition_placeholder_14, :db_condition_placeholder_15, :db_condition_placeholder_16, :db_condition_placeholder_17, :db_condition_placeholder_18, :db_condition_placeholder_19, :db_condition_placeholder_20, :db_condition_placeholder_21, :db_condition_placeholder_22, :db_condition_placeholder_23, :db_condition_placeholder_24, :db_condition_placeholder_25, :db_condition_placeholder_26, :db_condition_placeholder_27, :db_condition_placeholder_28, :db_condition_placeholder_29, :db_condition_placeholder_30, :db_condition_placeholder_31, :db_condition_placeholder_32, :db_condition_placeholder_33, :db_condition_placeholder_34, :db_condition_placeholder_35, :db_condition_placeholder_36, :db_condition_placeholder_37, :db_condition_placeholder_38, :db_condition_placeholder_39, :db_condition_placeholder_40, :db_condition_placeholder_41, :db_condition_placeholder_42, :db_condition_placeholder_43, :db_condition_placeholder_44, :db_condition_placeholder_45, :db_condition_placeholder_46, :db_condition_placeholder_47, :db_condition_placeholder_48, :db_condition_placeholder_49)) ; Array ( [:db_condition_placeholder_0] => 1373 [:db_condition_placeholder_1] => 1374 [:db_condition_placeholder_2] => 1212 [:db_condition_placeholder_3] => 1240 [:db_condition_placeholder_4] => 1236 [:db_condition_placeholder_5] => 1371 [:db_condition_placeholder_6] => 1248 [:db_condition_placeholder_7] => 1365 [:db_condition_placeholder_8] => 1166 [:db_condition_placeholder_9] => 1262 [:db_condition_placeholder_10] => 1263 [:db_condition_placeholder_11] => 1239 [:db_condition_placeholder_12] => 1186 [:db_condition_placeholder_13] => 1363 [:db_condition_placeholder_14] => 1190 [:db_condition_placeholder_15] => 1188 [:db_condition_placeholder_16] => 1187 [:db_condition_placeholder_17] => 1361 [:db_condition_placeholder_18] => 1360 [:db_condition_placeholder_19] => 1230 [:db_condition_placeholder_20] => 1232 [:db_condition_placeholder_21] => 1220 [:db_condition_placeholder_22] => 1201 [:db_condition_placeholder_23] => 1200 [:db_condition_placeholder_24] => 1208 [:db_condition_placeholder_25] => 1228 [:db_condition_placeholder_26] => 1223 [:db_condition_placeholder_27] => 1233 [:db_condition_placeholder_28] => 1218 [:db_condition_placeholder_29] => 1214 [:db_condition_placeholder_30] => 1300 [:db_condition_placeholder_31] => 1210 [:db_condition_placeholder_32] => 1215 [:db_condition_placeholder_33] => 1330 [:db_condition_placeholder_34] => 1272 [:db_condition_placeholder_35] => 1270 [:db_condition_placeholder_36] => 1269 [:db_condition_placeholder_37] => 1249 [:db_condition_placeholder_38] => 1237 [:db_condition_placeholder_39] => 1271 [:db_condition_placeholder_40] => 1238 [:db_condition_placeholder_41] => 1337 [:db_condition_placeholder_42] => 1336 [:db_condition_placeholder_43] => 1335 [:db_condition_placeholder_44] => 1334 [:db_condition_placeholder_45] => 1333 [:db_condition_placeholder_46] => 1332 [:db_condition_placeholder_47] => 1331 [:db_condition_placeholder_48] => 1297 [:db_condition_placeholder_49] => 1209 ) in DrupalDefaultEntityController->load() (line 196 of /home/cmalamed/public_html/ccghe_main/includes/entity.inc).
Comment #22
tdurocher commentedOops, and every other page non-admin page gives the other PDO error. All this without Extras enabled. Clearing the cache did solve the problem, and the layout appears to be working, but this is no way to work. :-)
Comment #23
tdurocher commentedSorry - do I need to change the status to get a response? If there is documentation telling me how to prevent my site from crashing every time I enable Extras, I don't see it. Clearing cache does not enable Extras to work - it only prevents the layout crash with Extras disabled. I would try uninstalling the whole thing, but DS does not appear in the Uninstall list when it was all disabled. I can manipulate the database directly if need be but don't figure that's the documentation error, so I don't see what fix or workaround I could be applying.
Comment #24
lcatlett commentedI am getting all the same "PDOException: SQLSTATE[42S22]" errors after installing the module with extras, disabling and uninstalling all components, clearing the cache, and even manually removing the recommended entries in the database...
Comment #25
ardnet commentedThis thread and the other one (https://drupal.org/node/1459910) seems related each other after I encountered the same issue.
Every time I install DS Extra, I got this message below in admin/backend page:
DatabaseSchemaObjectExistsException: Table ds_vd already exists. in DatabaseSchema->createTable() (line 657 of /Library/WebServer/Documents/clubvivre/includes/database/schema.inc). and when I refresh the admin/backend page, the message gone.
But on the other hand, all my frontend can not display at all, and instead got this message below:
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'revision.ds_switch' in 'field list': SELECT revision.vid AS vid, base.uid AS uid, revision.title AS title, revision.log AS log, revision.status AS status, revision.comment AS comment, revision.promote AS promote, revision.sticky AS sticky, revision.ds_switch AS ds_switch, revision.vuuid AS vuuid, base.nid AS nid, base.type AS type, base.language AS language, base.created AS created, base.changed AS changed, base.tnid AS tnid, base.translate AS translate, base.uuid AS uuid, base.cv_menu_pick AS cv_menu_pick, revision.timestamp AS revision_timestamp, revision.uid AS revision_uid, base.cv_menu_pick AS base_cv_menu_pick FROM {node} base INNER JOIN {node_revision} revision ON revision.vid = base.vid WHERE (base.nid IN (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2)) ; Array ( [:db_condition_placeholder_0] => 67 [:db_condition_placeholder_1] => 74 [:db_condition_placeholder_2] => 72 ) in DrupalDefaultEntityController->load() (line 191 of /Library/WebServer/Documents/clubvivre/includes/entity.inc).
All kind of way suggested as mentioned in this thread are not working for me, still find a way how to solve this.
The only way to solve this is by disabling the DS Extra module, but I can't as I need it.
Please advise.
Thanks
Comment #26
ardnet commentedSorry, I had to change the title and the status for this thread.
Thanks
Comment #27
ardnet commentedBtw, I attached txt files that list out all the modules that I used for reference.
Thanks
Comment #28
aspilicious commentedDo not reopen 2 issues when you have a problem.
Well, did you try to:
1) Disable ds_extras ==> clear caches
2) Uninstall ds_extras ==> clear caches
3) Install ds_extras ==> clear caches
Comment #29
ardnet commentedHi aspilicious, yes I did, and I still dunno what's the problem, but I will update this ticket once I find the solutions, as at this moment I'm quite tight up with other things.
I reverted back the status and title of this issues then, sorry for the trouble.
Thanks
Comment #30
ardnet commentedComment #31
tanvirahmad commentedGot database, may be in you phpmyadmin
Empty all cache tables
This will fix it.
Comment #32
m.zerres commentedTo clear the cache didn't worked for me. But this helped me:
1. Complete uninstall DS
2. Check if there are any ds_* tables in your DB. If yes, delete them
3. Clear cache
4. Install DS
This worked for me and all errors have gone
Comment #33
brandonc503 commentedi used dynamic field to make entity > render node and got wsod with
Fatal error: Unsupported operand types in /drupal/modules/node/node.module on line 1415
if im going to try a dev module, would i try ds, ds extra, node, ctools?
Comment #34
sobi3ch commented@BrockBoland mention in comment #3 that
but I found that if you disable
Views UI(and author had it enabled) then the problem disappearing. Maybe it help someone.