Upgrade the Site

Channel object package moved

The package (and project) of the Channel object moved from

org.hippoecm.hst.configuration.channel.Channel

to 

org.onehippo.cms7.services.hst.Channel

If you are using the Channel object in your code, you have to move the package to avoid compilation errors. The Channel object moved from the hst-api module to hippo-services module (on which your project most likely already has a transitive dependency, if not, add hippo-services explicitly).

Remove some HST Spring imports

If the Channel Manager is enabled for your project, the site webapp contains the imports

<import resource="classpath:/org/hippoecm/hst/cmsrest/SpringComponentManager-cmsrest.xml" />
<import resource="classpath:/org/hippoecm/hst/pagecomposer/SpringComponentManager-pagecomposer.xml" />

By default, they are found in the hst-cms-rest.xml and template-composer-rest.xml files. These imports need to be removed. If they are the only content of the Spring configuration files they're in, these files can be deleted entirely.

See CMS rest and Template Composer rest configurations are loaded as HST Addon Modules at HST Changes Background for more details and background.

Channel Filtering Spring wiring file location must be moved

If you use custom Channel Filtering, you need to move the file that contains customChannelFilters.

Note that if the file also contains non-channel-manager Spring wiring, only the customChannelFilters part needs to be moved, not the entire file.

See CMS rest and Template Composer rest configurations are loaded as HST Addon Modules at HST Changes Background for more details and background.

Account for hst:nochannelinfo

Depending on your configuration, you might need to set manually 

hst:nochannelinfo = true

on certain mounts. See explicitly hide a mount in the channel manager for more info and if you need to take action.

Channel Editor container type hst.table no longer supported

The Channel Editor container type hst.table is no longer supported. If your project contains containers of the hst.table type, we recommend to refactor them to use the hst.vbox or hst.nomarkup type.

Path to check Admin privileges in Channel Manager has changed

Before CMS 12, the default method for checking whether a CMS user was an Admin in the Channel Manager was by checking whether the user had the privilege hippo:admin on the node /hst:hst/hst:channels. This node no longer exists in CMS 12. Therefore, Admin privileges are now checked against /hst:hst. In general, projects that upgrade don't need to do anything for this, since the corresponding new configuration will be set up automatically during the upgrade. However, if your end project did modify the Admin check, you might need to account for this change. The new configuration is as follows:

+ hippo:configuration
  + hippo:frontend
    + cms
      + hippo-channel-manager
        + channel-manager-perspective
          + templatecomposer
            - manage.changes.privileges = hippo:admin
            - manage.changes.privileges.path = /hst:hst

The only change is that manage.changes.privileges.path = /hst:hst/hst:channels changed into manage.changes.privileges.path = /hst:hst. In general, if a user was a hippo:admin on /hst:hst/hst:channels, (s)he also is on /hst:hst.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?

    We rely on cookies

    to optimize our communication and to enhance your customer experience. By clicking on the Accept and Close button, you agree to the collection of cookies. You can also adjust your preferences by clicking on Manage Preferences. For more information please see our Privacy policy.

    Manage cookies
    Accept & close

    Cookies preferences

    Accept & close
    Back