- Issue created by @dasginganinja
- πΊπΈUnited States dasginganinja Bethlehem, PA
An additional thought I had about this:
Would it be beneficial for this module to have a checkbox for keeping the core folder settings path up to date?
- π³π±Netherlands megachriz
Is this issue about moving what is in
to
I think that it cannot be automatically moved in all cases, because it can be the case that tokens are used that the core file module does not support.
it looks like Drupal core will be handling transliteration at some point
Interesting, do you have a link to a specific core issue about this?
- πΊπΈUnited States dasginganinja Bethlehem, PA
Yes, I was speaking about keeping those two in sync, if it was possible. I'm not sure how feasible it is, but it was something that we completely overlooked after switching over to the filefield functionality for directory pathing.
I was checking out the filename transliteration module [1] and noticed they had linked to core's issue.
It looks like core's issue is #2492171 [2].
[1] - https://www.drupal.org/project/filename_transliteration β -- Filename Transliteration module
[2] - https://www.drupal.org/project/drupal/issues/2492171 β¨ Provide options to sanitize filenames (transliterate, lowercase, replace whitespace, etc) Fixed -- Provide options to sanitize filenames (transliterate, lowercase, replace whitespace, etc)I hope this helps. Thanks for all of your work on this and Feeds, etc.
Yes, I was speaking about keeping those two in sync, if it was possible.
It's not possible. The entire reason I'm considering using this module is to have
[node:some_field:target_id]
in the file path. You can't use the entity's fields as tokens in core.The only possibility would be to notify the admin when the module is (going to be) uninstalled.