Problem/Motivation

I tried to install the latest update and now my path confirgurations give me an invalid token error when I try to use: [file:ffp:onlyname:original].[file:ffp:extension:original] which is what I was using before the update. I also tried to install the latest version of token

Steps to reproduce

  1. Install the module
  2. Configure it
  3. Save
  4. Get an error message
  5. Clear caches
  6. Save, and see that the values are accepted this time

Proposed resolution

Clear the caches, as last step in the installation

Remaining tasks

Update the code, adding a cache clear as the last step of the installation.

User interface changes

API changes

Data model changes

Comments

h0tw1r3’s picture

Those are not valid ffp tokens for 7.x-1.x, and never have been.
The only tokens ffp provides are:
[file:ffp-name-only]
[file:ffp-name-only-original]
[file:ffp-extension-original]

h0tw1r3’s picture

Category: bug » support
Status: Active » Closed (cannot reproduce)
smurfxx’s picture

Issue summary: View changes

I have an error about this tokens, drupal tells me that [file:ffp-name-only-original] and [file:ffp-extension-original] are not valid!

eglaw’s picture

Error message:

The File name is using the following invalid tokens: [file:ffp-name-only-original], [file:ffp-extension-original].

filefield_paths input field is in red.

smurfxx’s picture

Browsing available tokens I found that the best tokens with transliteration module are
[file:ffp-name-only]
[file:extension]

It's better if you update the default token values to workaround these issues!

kris77’s picture

In available token there are "[file:name] and [file:extension]", so this works for me:

[file:name]. [file:extension]

I use last dev version.

ravi kant’s picture

Thanks Kris77, It working for me.

nathan tsai’s picture

Flushing the caches worked for me (on Drupal 8)

chike’s picture

Wao! Thanks @Nathan Tsai

I kept getting this error in Drupal 10 till I saw your post and flushed caches and the error was gone!

ressa’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev
Category: Support request » Task
Status: Closed (cannot reproduce) » Needs work

The module ought to clear caches itself as the last task of the installation, and not require the user to do it.

It's an inferior user experience to install this great module, only to get an error message first time you try to use it.

Because it's a pretty great module :)

ressa’s picture

Issue summary: View changes

Updating Issue Summary.