ddev start always creates a new hash_salt in settings.ddev.php (Drupal); should be static.

[TonyTheFerg]

Expected Behavior

Consistent hash_salt or none at all, not sure.

Actual Behavior

Whenever ddev builds the containers, they create a new hash_salt every time.

This creates issues with the token values on Drupal contextual links, as the hash_salt value is checked here. which leads to this issue.

You can reproduce this by opening the settings.ddev.php file, doing ddev poweroff, and then ddev start to view it change in real-time.

So a temporary fix is to place your hash_salt value AFTER the $ddev_settings section that gets added by DDEV in settings.php. This will allow that value to persist despite the new hash salt value that's created everytime DDEV starts up.

// Automatically generated include for settings managed by ddev.
$ddev_settings = dirname(__FILE__) . '/settings.ddev.php';
if (getenv('IS_DDEV_PROJECT') == 'true' && is_readable($ddev_settings)) {
  require $ddev_settings;
}

$settings['hash_salt'] = file_get_contents('/home/example/salt.txt');

You could also just move your local settings below the ddev settings, and put the hash_salt value in settings.local.php instead.

[rfay]

@TonyTheFerg could you please test the artifacts in

• fix: provide consistent hash per drupal/backdrop project name, fixes #5255 #5262 (comment)

with your use case?