1

I wondered if I can get some advice regarding working with Drupal 8. I've tried installation after installation and sooner rather than later I'm effectively bricking the installs by just installing third party modules.

Can someone please advise how I can debug effectively? I'm not a dev but can do some basic dev tasks.

I used to use for Drupal 7 in settings.php:

error_reporting(E_ALL); 
ini_set('display_errors', TRUE); 
ini_set('display_startup_errors', TRUE); 

However, I have no luck with this in Drupal 8.

It's getting incredibly frustrating when trying out new modules for this constantly to be happening.

Log file reads (which I've Googled) prior to asking.

[proxy_fcgi:error] [pid 15594:tid 139919129229056] [client 79.70.230.243:47902] AH01071: Got error 'PHP message: Uncaught PHP Exception Drupal\Component\Plugin\Exception\PluginNotFoundException: "The "file_type" entity type does not exist." at core/lib/Drupal/Core/Entity/EntityTypeManager.php line 125\n'

A second site outputs:

[pid 15594:tid 139919154407168] [client 79.70.230.243:49570] AH01071: Got error 'PHP message: Uncaught PHP Exception Drupal\Component\Plugin\Exception\PluginNotFoundException: "The "file_type" entity type does not exist." at core/lib/Drupal/Core/Entity/EntityTypeManager.php line 125\n', referer: http://domainname/user/login

Despite me having the above information, I really don't know what is causing this. Furthermore, I never do as reading the log files and following those error messages (like the above ones) doesn't clearly illustrate which module is causing the problem.

2

That exception is thrown by EntityTypeManager::getDefinition() when it doesn't find any definition for the entity with the ID passed as argument.

  if (($entity_type = parent::getDefinition($entity_type_id, FALSE)) && class_exists($entity_type->getClass())) {
    return $entity_type;
  }
  elseif (!$exception_on_invalid) {
    return NULL;
  }

  throw new PluginNotFoundException($entity_type_id, sprintf('The "%s" entity type does not exist.', $entity_type_id));

The ID of that entity could confuse: It's not the File entity Drupal core implements because its ID would be file, not file_type. That is the entity defined from the File Entity (fieldable files) project, in its FileType.php file.

I take you installed the module, and uninstalled it, but your site still have some instances of that configuration entity. I would try cleaning Drupal cache, and if that doesn't work, I would re-install the module, go to /admin/structure/file-types, delete any entity listed there, and uninstall the module again.

  • Thank you but I can't get into the back end to do anything. It's just outputting that error. – phil_c64 Jun 28 '16 at 15:44
  • 1
    There are other ways to clear the cache, if you can't get in the back end: drupal.org/documentation/clearing-rebuilding-cache – 4k4 Jun 29 '16 at 6:20
  • Drush installed, cleared all caches and uninstalled apparently corrupted modules, however it's still outputting that error. According to drush backup_migrate and simple_sitemap were causing issues, they are both uninstalled along with file entity. What else can I do? Many thanks for your help and time it is appreciated. – phil_c64 Jun 30 '16 at 13:36
1

What module is this? I checked there is no file_type entity in core. This is caused by a contrib module.

You probably have the source files still in your installation. Look for the missing plugin. This should look like this:

modules/modulename/src/Entity/FileType.php

When you found the module which is causing this, try to reproduce the error with a clean install and go to the issue queue of the module.

To set up debugging in D8 look at:

/sites/example.settings.local.php

/**
 * @file
 * Local development override configuration feature.
 *
 * To activate this feature, copy and rename it such that its path plus
 * filename is 'sites/default/settings.local.php'. Then, go to the bottom of
 * 'sites/default/settings.php' and uncomment the commented lines that mention
 * 'settings.local.php'.
 *
 * If you are using a site name in the path, such as 'sites/example.com', copy
 * this file to 'sites/example.com/settings.local.php', and uncomment the lines
 * at the bottom of 'sites/example.com/settings.php'.
 */

Most important is the backtrace information you get with that, this could give you some clues what is causing your error.

Most times you get errors after removing a module it helps to clear the cache.

  • modules/file_entity/src/Entity/FileType.php exists in the install. I've updated to the latest stable file entity as kiamlaluno suggested it's that module via ftp, however still broken. I'm just locked out. Can't get in to flush caches. My major concern in this is that it's incredibly difficult to find out what on earth is causing these issues in the first place. – phil_c64 Jun 28 '16 at 19:14
  • I will do as you suggested above though, thanks for your time – phil_c64 Jun 28 '16 at 19:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.