Tips and Tricks: Troubleshooting

Clean URLs not working? Check your .htaccess file!

Here are some of the most common reasons why your clean URLs may not be working (assuming you're using a normal Linux/Apache hosting environment).

1. Your site is in a subdirectory, or you're using an Alias, but you didn't set RewriteBase

2. Your .htaccess file didn't get uploaded at all

3. Your .htaccess file is corrupt

4. Pager and other query strings don't work

https://drupal.org/node/256410

Drupal 8: Mismatched entity and/or field definitions

If you get the warning "Entity/field definitions Mismatch detected Mismatched entity and/or field definitions." after upgrading (for example from 8.37 to 8.45 i.e. required security update) you have to fix this issue first before running database updates. If you don't you might get into unresolvable problems. The solution is easy.

1. Adapt index.php

Add the following script before $response->send(); in index.php file(located in Drupal root folder)

Drupal 8: Mismatched entity and/or field definitions

Drupal "Fatal error: Allowed memory size of 134217728 bytes exhausted when clearing the cache"

Frequently after the change of a server or hoster or during the build-up of a Drupal site you might run into the "Fatal error: Allowed memory size of 134217728 bytes exhausted when clearing the cache". This usually isn't as dramatic as it looks like. The most common cause for this problem is a php memory limit that is too low. Thus the solution is to increase the php memory limit. If you increase the limit to 256M or even 512M you will certainly be without any php memory limit troubles with a standard Drupal installation.

Drupal module XML Sitemap generates wrong URL

If you move your Drupal site from one server to another it might happen that the URLs generated by the module XML Sitemap are wrong. This is also the case after clearing cache, running cron or regenerating the sitemap. Although it is not a bug, it is certainly a not well "thought trough" issue, because one would expect, that at least the running of cron or the regeneration of the XML sitemap should update the XML sitemap to the new URL.

Drupal XML Sitemap

How to troubleshoot white screen of death (WSOD) after admin login – move of Drupal website

In our experience it happens from time to time that one gets a "white screen of death" - short WSOD - after the login with the admin account. Most frequently this happens after the move of a Drupal website to a new host or an upgrade to a new release. This is of course very odd and can lead to a very time consuming troubleshooting. Unfortunately we did not find out the precise causes and we couldn't find clear answers either. But processing the following set of measures always helps us to resolve the problem.

URL Redirects: "Fix 404 pages" tab is missing

After the installation of the Drupal module Redirect there is usually the tab "Fix 404 pages" under "URL Redirects". As the designation indicates this function allows you to redirect 404 pages. If this tab does not appear it usually has a very simple reason: The Drupal core module "Database Logging" is not enabled. Being able to reconnect 404 pages, the 404 pages obviously need to be recorded and that's done by the core module "Database Logging". Enable this module and the tab will appear.

Shadowbox gallery displays only the first image on a multi-image field (option "compact")

In 7.x-3.0-beta5 version a new compact parameter has been added to the shadowbox formatter. So if you have an image field (multimage, accepts more than 1 image) and you set its formatter as shadowbox with gallery type and compact checked, you will get a gallery in which only the first image thumbnail is displayed and when you click on it shadowbox is opened and you can view all the images there.

https://drupal.org/node/1107162

File entity module: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'DATABASENAME.image_dimensions' doesn't exist: SELECT * FROM {image_dimensions} id WHERE id.fid IN (:fids_0); Array ( [:fids_0] => 444 ) in file_entity_file_load() (Zeile 225 von /DRUPALROOT/sites/all/modules/media/file_entity/file_entity.module).

Same for me, after the update to Media 7.1.4, that I did following PSA-2014-001.

How to solve the problem with the mobile dropdown menu of the Surreal Drupal Theme?

If you purchased the Surreal One Page Parallax Drupal Theme (inspiromedia) in the past or recently (status October 28, 2014) you will encounter a problem with the mobile drop-down menu. All menu entries on the same page as the homepage starting with # work, all the others don't work. The cause is wrong coding.

To resolve the problem you have to edit and change the following section of the inspiromedia.js (sites/all/themes/surreal/js):

Change from:

Troubleshooting: Impossible to save settings for a new Multimedia asset field

Using 7.x-2.0-alpha4 or media 7.x-2.0-alpha3 of the Drupal media module, you might get the following error while saving the settings for a new multimedia asset field.

"Notice: Undefined index: settings in media_field_instance_validate() (line 382 of [...]\sites\all\modules\media\media.module). The upload destination must be one of the allowed schemes."

Whether you check upload or any other option has no influence. To solve the problem you have to options.

Pages

Drupal themes to be compared