-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Upgrade Script to Convert Language Variables to Locale Content Items #27703
Comments
Copy paste issue in the original description. Fixed now. |
…d this as a DataTask once the lang variables portlet is updated
Not to QA: Now the task will look for files present in the folder /assets/messages/ Important: QA is blocked on this task because this task won't be enabled until the work in the front end is completed. This is to prevent customers from applying this script and continuing to use the old portlet which continues to save LanguageVariables as resource bundles and not content. |
Internal QA: this change will be tested when this card is completed. |
* #27703 Langvars migratation script * #27703 save point * #27703 UT should able deal with non-exising ct * #27703 cleaning sample file not used by the test * #27703 reverting changes on TaskLocatorUtil * #27703 fixing comment grammar * #27703 fix in path after testing in dotCMS. Adding todo comment to add this as a DataTask once the lang variables portlet is updated * #27703 doc * #27703 reverting changes in TaskLocatorUtil * #27703 doc
Parent Issue
#25603
Task
Create Upgrade Script to Convert Language Variables to Content Items
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
Acceptance Criteria
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: