Account created on 10 March 2006, almost 19 years ago
#

Recent comments

🇵🇭Philippines jaesperanza

Still an issue on Drupal 10 when File Entity is enabled and used. #2 💬 Plugin does not exist when uploading custom font Closed: duplicate works. Thanks!

🇵🇭Philippines jaesperanza

For Drupal: ^9 | ^10 - https://www.drupal.org/project/scanner

I am updating this thread as this comes up easily on search and should be useful.

🇵🇭Philippines jaesperanza

"change the 'type' of the field in the search API field settings from 'string' to 'fulltext'. "
This worked, thanks! 

🇵🇭Philippines jaesperanza

After 2 years, there's seem to be no response, or any pointing to the right documentation.

🇵🇭Philippines jaesperanza

(Not intending to open this issue) as per Dave, just to illustrate the steps especially for the uninitiated, on Drush, you can:

first, run composer require drupal/config_update:^2.0@alpha
then, composer require 'drupal/features:^3.14' (this version to date)

🇵🇭Philippines jaesperanza

I just found this googling - how to backup drupal 10 using drush. We should update to at least put a note to direct people to an updated set of instructions, no? Or, at least provide a reference here of relevant information.

🇵🇭Philippines jaesperanza

Are there any documentation for Drupal 9, I can't seem to find one. Thanks!

🇵🇭Philippines jaesperanza

Seems this is still an outstanding issue for some versions from D8, D9 all the way to D10. See  https://www.drupal.org/project/drupal/issues/3163123

Workaround is indeed to use the tar.gz version, not the zip version in installing modules via backend UI. Or use FTP to upload manually the downloaded module.

🇵🇭Philippines jaesperanza

Sorry for reopening, obviously people still find this thread. For those having issues with the above, read the official documentation here: https://www.drupal.org/node/44164

🇵🇭Philippines jaesperanza

In our experience, on Siteground's NGINX hosting, a common issue for Drupal 8/9. For one particular project we inherited, also on SG, we noticed the following is enabled and set to true:

$config['image.settings']['suppress_itok_output'] = TRUE;
$config['image.settings']['allow_insecure_derivatives'] = TRUE;

Disabling both, seems to fix the issue.

🇵🇭Philippines jaesperanza

An old issue, but persistent error for some on latest D7.x core and module versions. In case this helps anyone still running on D7, see below. Encountered the same both for commerce and panels modules, same error:

commerce_order module
Update #7113
Failed: PDOException: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes: ALTER TABLE {commerce_order} ADD INDEX `order_id_status_type` (`order_id`, `status`, `type`); Array ( ) in db_add_index() (line 3077 of /home/ibuildp1/public_html/plaridel.ibuildph.com/includes/database/database.inc).

panels module
Update #7309
Failed: PDOException: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes: ALTER TABLE {panels_allowed_types} ADD PRIMARY KEY (`module`, `type`); Array ( ) in db_add_primary_key() (line 3027 of /home/ibuildp1/public_html/plaridel.ibuildph.com/includes/database/database.inc).

What helped:

For commerce_order module, skip the errors temporarily by placing the following in settings.php until you get to run update.php again successfully:

$conf['skip_order_update_7113'] = TRUE;
$conf['skip_order_update_7114'] = TRUE;

For panels error:
executing SQL (for instance in your PHPMyAdmin) ALTER TABLE `panels_allowed_types` ENGINE=InnoDB;

on both, run update.php again

🇵🇭Philippines jaesperanza

This fixed the problem for me for the same error on an old D7 website. Thanks, @nessunluogo

🇵🇭Philippines jaesperanza

Haven't tried the patch yet. Just reporting same issue is still happening for:

Drupal version : 9.5.7
PHP Version 8.1.17
Module version: 8.x-2.19

Allow parents to override children is usable intermittently, I think as long as you run drush cache:rebuild

Enabling both options crashes the website with the same error

Production build 0.71.5 2024