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.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kayograco created an issue. See original summary.

RunePhilosof’s picture

Status: Active » Postponed (maintainer needs more info)

This sounds critical.
However, it works for me.

So you need to provide steps from a newly installed Drupal site to reproduce this error.

vladadj31’s picture

@kayograco, did you fixed this issue? I have the same problem on my site.

MarcoPBazz’s picture

I 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).

hgoto’s picture

Status: Postponed (maintainer needs more info) » Active

I met the same error while testing this module.

I investigated a little and confirmed the following steps can reproduce the error.

  1. Set up a Drupal 7.57 site
  2. Install file_entity module with Drush
  3. Disable and uninstall file_entity module with Drush
  4. Try to enter the Drush shell

The 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.

cd /your/drupal/root/directory
drush si
drush en file_entity
drush dis file_entity
drush pm-uninstall file_entity
drush php

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. )

hgoto’s picture

Status: Active » Needs review
FileSize
431 bytes

This error seems to be caused because the file entity property type remains though the corresponding column type 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.

hgoto’s picture

  • joseph.olstad committed 872785a on 7.x-2.x authored by hgoto
    Issue #2643672 by hgoto: Any version of this module breaks my whole site
    

  • joseph.olstad committed 872785a on 7.x-3.x authored by hgoto
    Issue #2643672 by hgoto: Any version of this module breaks my whole site
    
joseph.olstad’s picture

Status: Needs review » Fixed

committed patch to 7.x-2.x and 3.x
thx

hgoto’s picture

@joseph.olstad how quick! thanks!

Status: Fixed » Closed (fixed)

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