I installed and enabled the "7.x-2.0-beta2" version of this module in order to install the Media 2.x. module and the whole site crashed with "The website encountered an unexpected error. Please try again later.", so I gave up upon 2.x, uninstalled* and reinstalled the 1.x version with same error.
Looking at admin reports there is:
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.type' in 'field list': SELECT base.fid AS fid, base.uid AS uid, base.filename AS filename, base.uri AS uri, base.filemime AS filemime, base.filesize AS filesize, base.status AS status, base.timestamp AS timestamp, base.type AS type FROM {file_managed} base WHERE (base.fid IN (:db_condition_placeholder_0)) ; Array ( [:db_condition_placeholder_0] => 156 ) en DrupalDefaultEntityController->load() (línea 198 de /home/content/59/13505459/html/includes/entity.inc).
* I'm not a developer, so I don't know how to hack the DB, so what I do in order to disable the module after the crash is to have two tabs with "Modules" page on my web browser before enabling it. When I enable the "File Entity" module and get the crash, I go to the other tab, verify that the module is unchecked and press the save button. Don't know it that's a bad practice, but at least get my site running again.
All of my modules are updated as well as the Core.
Comment | File | Size | Author |
---|---|---|---|
#6 | file_entity-fix_column_not_found_error-2643672-6.patch | 431 bytes | hgoto |
|
Comments
Comment #2
RunePhilosof CreditAttribution: RunePhilosof commentedThis sounds critical.
However, it works for me.
So you need to provide steps from a newly installed Drupal site to reproduce this error.
Comment #3
vladadj31 CreditAttribution: vladadj31 commented@kayograco, did you fixed this issue? I have the same problem on my site.
Comment #4
MarcoPBazz CreditAttribution: MarcoPBazz commentedI have this problem too.
I'm using latest core version. My installation previously had installed media module, but last year has been uninstalled and removed.
Also I'm using File (Field) Paths and filefield sources (both last version).
Comment #5
hgoto CreditAttribution: hgoto as a volunteer commentedI met the same error while testing this module.
I investigated a little and confirmed the following steps can reproduce the error.
file_entity
module with Drushfile_entity
module with DrushThe fourth step cannot be done since the error is raised. Even when I try to get the site status with
drush st
, the error occurs. That is, we don't get this error until we uninstall the module. Once you uninstall the module, you cannot run the site.I believe anyone can follow the above steps with the following series of commands.
I'm not sure the priority is Critical but I don't change it for now. I would like to have maintainers decide it :)
(Edited: I confirmed this error occurs with the dev 2.x version and 7.x-2.16. )
Comment #6
hgoto CreditAttribution: hgoto as a volunteer commentedThis error seems to be caused because the file entity property
type
remains though the corresponding columntype
is dropped when the module gets uninstalled.So I believe the implementation of
hook_uninstall()
of this module needs to clear the related cache. The attached patch (for the dev 2.x HEAD) solves this issue in my environment.Comment #7
hgoto CreditAttribution: hgoto as a volunteer commentedComment #10
joseph.olstadcommitted patch to 7.x-2.x and 3.x
thx
Comment #11
hgoto CreditAttribution: hgoto as a volunteer commented@joseph.olstad how quick! thanks!