RoxenCMS 5.4FAQMain

     

Database
Developer
Editor
Maintenance
Java
Performance
Managing multiple sites in one SiteBuilder
Security
Upgrading

Upgrading

Questions:


How do I get the Insite Editor to work under 3.3 after a upgrade from a 2.* SiteBuilder site?

  1. In the SiteBuilder repository there is a configuration file for sitebuilder called "<site name>.sb/sbconfig". Open it and add the following to the end of the file:
    "mount_points": ({ /* 1 element */ ([ /* 4 elements */ "read_only":1, "real_path":"$SBROOT/insite-files", "type":"no_vc_fs", "virtual_path":"roxen-files" ]) }),

  2. If not the module "Insite Editor Filesystem", which should be present under CMS: in the module listing under the site, is present that should be added together with the Insite Editor components you want. You find the modules under CMS Modules when choosing "Add module".

  3. Reload "CMS Main Module". It might be necessary that "CMS Content Editor" and "CMS Insite Editor" is reloaded. As a last step if things aren't working it might be necessary to reload the server. Keep an eye on the debug log to see if anything else goes wrong. One error that might (but mustn't) come up is that the file sbconfig contains errors after editing it earlier.

  4. There should now be a folder called "roxen-files" in the SiteBuilder interface if you log on to the site http://siteurl/edit/

  5. Now you need a few files to get the Insite Editor to work and that the default layout for these filer are transformed.

    • /cms-news-stationery.xml
      metadata:
      Type : CMS News Editor
      XSL Template : /cms-common.xsl
      Use as stationery : Yes
      content: (see tip below)

    • /cms-page-stationery.xml
      metadata:
      Type : CMS Page Editor
      XSL Template : /cms-common.xsl
      Use as stationery : Yes
      content: (see tip below)

    • /cms-menu-stationery.xml
      metadata:
      Type : CMS Menu Editor
      Externally Visible : Never
      Use as stationery : Yes
      content: (see tip below)

    • /cms-common.xsl
      metadata:
      Selectable : Yes
      Externally Visible : Never
      content: (see tip below)

    • /cms-components.xsl
      metadata:
      Selectable : No
      Externally Visible : Never
      content: (see tip below)

    • /cms-news-archive.xsl
      metadata:
      Selectable : No
      Externally Visible : Never
      content: (see tip below)

    • /cms-print.xsl
      metadata:
      Selectable : No
      Externally Visible : Never
      content: (see tip below)

Tip
To get the right file content for the above files the simplest way to it is to create a new Basics site, (use the license file "personal.lic"). Copy the content by doing a "Download" on the above files and save it on your hard drive and then, in the "old" site, do a "Upload contents..." for each file. The metadata for each file must be set manually.

After upgrading I can not run Roxen as root any more.

The internal MySQL can now run as a user other then the one Roxen is started as.

You need to either add a line 'user = root' to the file roxen/configurations/_mysql/my.cfg, or remove the same file before starting Roxen.