Problem/Motivation
Pwolanin and I were working on #2338081: Local Tasks, Actions, and Contextual links mark strings from derivatives (or alter hooks) as safe and translated and noticed that title in FielUILocalTask is save to plugin definition before displaying to user so it won't get translated properly at run time.
Proposed resolution
Don't call t() before saving to plugin definition but call it during run time
verify that current language are part of the cache context when plugins are rendered
Comments
Comment #1
kgoel CreditAttribution: kgoel at Forum One commentedComment #2
pwolanin CreditAttribution: pwolanin commentedComment #3
pwolanin CreditAttribution: pwolanin commentedComment #4
pwolanin CreditAttribution: pwolanin commentedComment #5
pwolanin CreditAttribution: pwolanin commentedComment #16
tintoI see that there have not been any updates in the last 7 (!) years. Furthermore, both the referenced issue and the parent issue seem to have been fixed in the meantime.
@kgoel, can you please confirm that this issue has now been resolved? If not, it would be great if you could update the issue summary with some clear steps to test or reproduce this issue in a current local install.
Until then, I am changing the status of this issue to Postponed. If there is no update or additional info posted here in three months, I suggest someone other than me may close this issue to remove it from the Drupal core list of bugs.
Thanks!
Comment #19
Kristen PolThanks for reporting this issue. We rely on issue reports like this one to resolve bugs and improve Drupal core.
As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" almost a year ago and there has been no activity since that time.
Since there hasn't been steps to reproduce added as requested, I'm marking the issue "Closed (cannot reproduce)". If anyone can provide complete steps to reproduce the issue (starting from "Install Drupal core"), document those steps in the issue summary and set the issue status back to "Active" [or "Needs Work" if it has a patch, etc.].
Thanks!