Migrations

From Complete Cyclos documentation wiki
Jump to: navigation, search

Migration 3.0 > 3.5

Upgrade

The migration of Cyclos 3.0 to 3.5 works as a normal upgrade (see Installation & maintenance#Upgrade)
There are a few issues to consider. These are explained in the following sections.

Translation

Like any upgrade new translation keys will be added and old (unused) keys will be removed. The upgrade won't modify existing keys. If you use another language than the default (English) you might want to do a search for empty keys and translate them. The migration will fail if there are empty keys in the file CyclosSetup.properties (can be found in the directory: /cyclos_3.5/src/nl/strohalm/cyclos/setup/)

Apply new themes

The upgrade process does not add new layout items incrementally like the transaction keys (this will be possible with the future Cyclos4 version). The upgrade process leaves the layout (style sheets and images) as they are.

If you are upgrading and are using one of the default themes in Cyclos you will have to apply them again in order for the new layout to appear correctly. You can do this by going to (Content management - Themes - select the Theme - Submit). You should also apply the new login page them (by selecting "login page" from the theme combo select) Now the new layout should appear (you might have to clear your browser cache).

If you have customized a theme or created your own one you will have to add the new style elements manually. You will need to make the following changes to the style.css file (Content management - CSS files - select the style.css - Change)

Add the following declarations:

    body.main {
        background-color: #f1f1f1;
        text-align: center;
    }

    .topContainer {
        margin: 16px auto;
    }

    .topContainer>tr>td, .topContainer>tbody>tr>td {
        border: 1px solid #dedede;
        border-radius: 6px;
        -moz-border-radius: 6px;
        -webkit-border-radius: 6px;
    }
    .topContainerBorder {
        border: 1px solid #c4c4c4;
        border-radius: 6px;
        -moz-border-radius: 6px;
        -webkit-border-radius: 6px;
        padding: 9px 9px 12px 9px;
        background: white;
        min-height: 600px;
    }
    .topBanner {
        background: white url(top_background.jpg) no-repeat;
        height: 129px;
        margin-bottom: 7px;
        position: relative;
    }
    .topBannerText {
        font-family: Verdana, sans-serif;
        font-size:   12px;
        font-weight: bold;
        color: white;
        font-weight: bold;
        position: absolute;
        bottom: 8px;
        left: 10px;
    }
    .minHeight {
        height: 500px;
    }
    
    .standaloneContents {
        width: 577px;
        margin-left: auto;
        margin-right: auto;
    }

    .tdContentsStandalone {
        text-align: center;
    }

    .tdPrintDataBold {
        color:           black;
        font-weight:     bold;
        text-align:      left;
        vertical-align:  middle;
        border:          1px solid #808080;
        border-spacing:  0px;
        border-collapse: collapse;
    }
    
    div.fakeField, div.fakeFieldDisabled {
        background-color: #FFFFFF;
        border:         #658dcf 1px solid;
        color:          navy;
        font-family:    Verdana, sans-serif;
        font-size:      11px;
        font-weight:    normal;
        padding-left:   2px;
        padding-right:  2px;
        vertical-align: top;
    }
    
    div.fakeFieldDisabled {
        background-color: #FFEED7 !important;
    }

    ul.categoryLevel0 {
        list-style-type: none;
        margin-bottom: 10px;
        padding-left: 20px;
        margin-left: 0px;
    }
    
    ul.categoryLevel1 {
        list-style-type: square;
        padding-left: 15px;
        margin-bottom: 5px;
        margin-left: 0px;
    }
    
    ul.categoryLevel2 {
        list-style-type: disc;
        padding-left: 15px;
        margin-left: 0px;
    }
    
    li.categoryLevel1 {
        font-weight: bold;
        padding-left: 0px;
        color: #658dcf;
    }
    
    li.categoryLevel2 {
        font-weight: normal;
        padding-left: 0px;
        color: #658dcf;
    }
    
    li.categoryLevel3 {
        font-weight: normal;
        padding-left: 0px;
        color: #658dcf;
    }
    
    span.categoryLevel1Text, span.categoryLevel2Text, span.categoryLevel3Text {
        color: navy;
    }

    span.categoryLevel1TextHover, span.categoryLevel2TextHover, span.categoryLevel3TextHover {
        color: blue;
        text-decoration: underline;
    }
    
    span.categoryCountText{
        color: #658dcf;
    }
        
    div.manualPage h1 {
        font-size: 14pt;
    }

    div.manualPage h2 {
        font-size: 12pt;
    }

    div.manualPage h3 {
        font-size: 10pt;
        margin: 0px;
        padding: 0px;
        margin-top: 20px;
    }

    div.manualPage a {
        text-decoration: underline;
        color: blue;
    }
    
    a.manualLink {
        color: navy;
    }

    a.manualLink:hover {
        color: blue;
        text-decoration: underline;
    }

Note: Some of the colors are depending on the theme. Make sure you adjust them according to your custom theme.

Finally you have modify the following items:

* Removed the height and padding definitions on ".headerBar"
* Changed the background color to transparent and removed the width definition on ".tdContents"
* Added the "a.operatorProfileLink" declaration in the same block as "a.linkList, a.profileLink, a.adminProfileLink"
* Added the "a.operatorProfileLink:hover" declaration in the same block as "a.linkList:hover, a.profileLink:hover, a.adminProfileLink:hover"
* Added repeat-x to the background declaration in "button, .button, .linkButton"

Inlcude Cyclos in website

It is now possible to inlcude Cyclos in a website. You can find the documentation here: Installation & maintenance#How to inlcude cyclos in website

Migration 3.5 > 3.6

Upgrade

The migration of Cyclos 3.5 to 3.6 works as a normal upgrade (see Installation & maintenance#Upgrade)
There are a few issues to consider. These are explained in the following sections.

Application pages

There have been various change to the application (jsp) pages. If you have made any modification to an application page (in Administration section, menu: Content management - Application page) you will need to save the page (code) locally and remove them as customization in Cyclos before doing the upgrade. (remove an customized application page will restore the original page). When performing an upgrade without removing these pages from the database the layout might display wrongly and possibly block you to login (and fix the problem).

Translation

Like any upgrade new translation keys will be added and old (unused) keys will be removed. The upgrade won't modify existing keys. If you use another language than the default (English) you might want to do a search for empty keys and translate them. From the 3.6 version missing translation keys in other languages than English will display the English (default) translation. (previous versions did not show the translation when a key was missing).

Apply new themes

The upgrade process does not add new layout items incrementally like the transaction keys (this will be possible with the future Cyclos4 version). The upgrade process leaves the layout (style sheets and images) as they are.

If you are upgrading and are using one of the default themes in Cyclos you will have to apply them again in order for the new layout to appear correctly. You can do this by going to (Content management - Themes - select the Theme - Submit). You should also apply the new login page them (by selecting "login page" from the theme combo select) Now the new layout should appear (you might have to clear your browser cache).

If you have customized a theme or created your own one you will have to add the new style elements manually. You will need to make the following changes to the style.css file (Content management - CSS files - select the style.css - Change)