By jwilson3 on
Change record status: 
Published (View all published change records)
Project: 
Filename Transliteration
Introduced in branch: 
1.2.x
Introduced in version: 
1.2.0
Issue links: 
https://www.drupal.org/node/3238461
Description: 

Drupal core now provides opt-in support for filename sanitation and transliteration. (See Change Record #2972665).

As of Drupal core version 10.2, all features provided by the Filename Transliteration contrib module are covered by out-of-the-box functionality.

Users on previous versions of Drupal may safely continue to use this module.

Users who have updated to the final release of this module (version 1.2.0) will see a deprecation notice in the module name listed on the "Extend" page. Additionally, a warning message on the "Status Report" page will be shown if Drupal core version is greater than or equal to version 10.2.

Existing users of Filename Transliteration may follow these steps to transition away from the module.

  1. Ensure you're running Drupal version 10.2+ and Filename Transliteration version 1.2.0
  2. Opt-in into filename sanitization in File system settings at URL /admin/config/media/file-system.
  3. To maintain feature parity with the Filename Transliteration module, enable all filename sanitization options provided by Drupal core including:
    • ✅ Transliterate
    • ✅ Replace whitespace with replacement character
    • ✅ Replace non-alphanumeric characters with the replacement character
    • ✅ Replace sequences of dots, underscores and/or dashes with the replacement character
    • ✅ Convert to lowercase
  4. At the point in time when the "Transliterate" option has been enabled, all features of the Filename Transliteration module are immediately disabled in favor of core filename sanitization tooling.
  5. Once all core filename sanitization options are enabled, the Filename Transliteration module may be safely uninstalled without interruption to functionality of your site.

Note: If you're using Drupal configuration management to enable/disable modules and deploy config changes between environments, you do not need to upgrade to the latest version of Filename Transliteration. Just be sure to uninstall the module AND configure core filename sanitization settings, then sync both of the resulting configuration changes as part of a single deployment step.

Please direct questions or concerns to the issue queue: https://www.drupal.org/project/issues/filename_transliteration

Impacts: 
Site builders, administrators, editors