In-Portal Issue Tracker - In-Portal CMS
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Type: | Reproducibility: | Date Submitted: | Last Update: |
1445 | [In-Portal CMS] Install / Upgrages | feature request | always | 2013-01-05 12:32 | 2013-01-05 12:33 |
|
|||||
Reporter: | alex | Platform: | |||
Assigned To: | alex | OS: | |||
Priority: | normal | OS Version: | |||
Status: | resolved | Product Version: | 5.2.1-B1 | ||
Product Build: | Resolution: | fixed | |||
ETA: | none | Fixed in Version: | 5.2.1-B2 | ||
Reference: | https://groups.google.com/d/topic/in-portal-dev/Sl03Ta5Zv70/discussion | ||||
Change Log Message: | Automates language pack export for deployment script | ||||
Estimate Points: | 1 | ||||
|
|||||
Summary: | 0001445: Automate language pack export for deployment script | ||||
Description: |
Deployment script is a real time saver when it comes to deploying an update to dev/live servers. However it still requires user actions in terms of exporting latest language pack and comparing it to one we have right now. Right now I'm doing this (see below) to export language pack for each task: click on "Regional" section in Admin Console select English language click on Export toolbar button enter language pack filename click on "Select None" to uncheck all modules click on "Custom" to select module which I want to export click on Export button on toolbar These are horrible 7 clicks I need to make just to have "Custom" module's language pack being exported. I'm proposing to perform an export of all language packs from modules, that have "project_upgrades.sql" file when "Synchronize" button is pressed in "System Tools" section. As a result we'll have a separate language pack for every module, that is used by deployment script. |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: |
![]() http://tracker.in-portal.org/file_download.php?file_id=1898&type=bug |
||||
|
|||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2013-01-05 12:33 | alex | Note Added: 0005345 | |||
2013-01-05 12:33 | alex | Status | reviewed and tested => resolved | ||
2013-01-05 12:33 | alex | Fixed in Version | => 5.2.1-B2 | ||
2013-01-05 12:33 | alex | Resolution | open => fixed | ||
2013-01-05 12:33 | alex | Assigned To | !COMMUNITY => alex | ||
2013-01-05 12:33 | alex | Changeset attached | 5.2.x r15660 | ||
2013-01-05 12:33 | alex | Status | needs testing => reviewed and tested | ||
2013-01-05 12:32 | alex | Assigned To | => !COMMUNITY | ||
2013-01-05 12:32 | alex | Developer | => alex | ||
2013-01-05 12:32 | alex | Status | active => needs testing | ||
2013-01-05 12:32 | alex | New Issue | |||
2013-01-05 12:32 | alex | File Added: langpack_deployment_automation.patch | |||
2013-01-05 12:32 | alex | Reference | => https://groups.google.com/d/topic/in-portal-dev/Sl03Ta5Zv70/discussion | ||
2013-01-05 12:32 | alex | Change Log Message | => Automates language pack export for deployment script | ||
2013-01-05 12:32 | alex | Estimate Points | => 1 |
Notes | |||||
|
|||||
|
|