I've tried numerous times to update this module. I have completely deleted the old folder and then uploaded the 7.x.1.9 file and extracted it. Continues to say we are using 1.7. I've looked everywhere and cannot find another folder with this module in it. I've even run a search via command line.
Info file:
Update page:
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | Token update.png | 40.43 KB | bebalachandra |
| #3 | token-on-10.1.0.png | 86.58 KB | duckydan |
| #2 | Screenshot from 2023-06-29 13-48-33.png | 7.25 KB | jelle_s |
| token-update.PNG | 9.07 KB | jsimonis | |
| token-info.PNG | 11 KB | jsimonis |
Comments
Comment #2
jelle_sI've got the same thing happening on 8.x-1.12: it keeps saying 8.x-1.11 is the recommended version?
Comment #3
duckydan commentedI am on Drupal 10.1.0 and it is happening as well.
Comment #4
berdirdrupal.org infrastructure did have some composer issues recently, there's probably something weird going on there, check with #drupal-infrastructure or the corresponding issue queue.
this is a Drupal 7 issue you're commenting on and definitely not related.
Comment #5
xem8vfdh commented@Berdir, I am experiencing the same on the 8.x branch as #2 and #3
Since this is a D7 issue, do you want me to open a new issue for this 8.x issue, or are you saying it's not actually an issue with this module but something with upstream Drupal composer?
Comment #6
hestenetI am not sure of the explanation for the OP's Drupal 7 issue, although I would suggest drush disabling and re-enabling that module.
For the Drupal 10 issues, it may have been a CDN caching issue
https://updates.drupal.org/release-history/token/current was not showing 8.x-1.12
I have purged that cache and now the release is showing. Hopefully that resolves the issue for the Drupal 10 users?
Comment #7
leducdubleuet commentedI can confirm the problem is resolved on Drupal 9 now so I guess it should be OK as well on D10.
Thanks!
Comment #8
duckydan commentedAll is good in 10.1.0 too. Thanks so much!
Comment #9
grahamshepherd commentedI am on Drupal 10.1.0 and getting the same result as #3
Comment #10
jsimonis commentedI'll try it again, but I have disabled it and reenabled it that way previously and nothing changed.
Comment #11
bebalachandra commentedAll good on 10.0. Its showing as token is upto date. I have not faced any update errors which is stated in #3. Attached ss for reference.
Thanks.
Comment #12
jsimonis commentedI just finally got a chance to loop around to this. I don't have the ability to connect to the site in a way that allows me to disable via drush. I only have FTP (can't use SSH when I'm logged in that way) and Cpanel. And Terminal isn't turned on by their hosting company.