|
In-Portal Issue Tracker - In-Portal CMS
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Type: | Reproducibility: | Date Submitted: | Last Update: |
| 487 | [In-Portal CMS] Install / Upgrages | feature request | N/A | 2009-12-23 03:56 | 2010-01-05 03:50 |
|
|
|||||
| Reporter: | alex | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | active | Product Version: | 5.0.2-B1 | ||
| Product Build: | Resolution: | open | |||
| ETA: | none | Fixed in Version: | |||
| Reference: | http://groups.google.com/group/in-portal-dev/browse_thread/thread/15509c5a09972ff5 | ||||
| Change Log Message: | |||||
| Estimate Points: | 0 | ||||
|
|
|||||
| Summary: | 0000487: Add "SkinCRC" column to Skins table for easing skin upgrade process | ||||
| Description: |
I propose to add "SkinCRC" column to Skins table. When user changes skin, then new crc will be calculated based on skin contents. This way, during upgrade process, we could determine fact, that user manually have edited skin. If skin wasn't manually edited, then we will overwrite it's contents based on "style_template.css" file. Without CRC we have to manually upgrade skin after automatic site upgrade is made. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
|
|
|||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2010-01-05 03:50 | alex | Target Version | => Icebox | ||
| 2009-12-23 03:58 | alex | Reference | => http://groups.google.com/group/in-portal-dev/browse_thread/thread/15509c5a09972ff5 | ||
| 2009-12-23 03:56 | alex | New Issue | |||
| There are no notes attached to this issue. |