Our Getting Started tutorial will get you up to speed with Hippo development.Follow the Hippo Trail
The relations between repository, CMS and delivery tier.How it all fits together
Source code, forge, license, roadmap and system requirements.Developer Info
Interested? We're always on the lookout for new talent.Have a look
Did you see this?
Meet Hippo CMS 10 for Developers
May 27, 2015
Last week, we announced the release of Hippo CMS 10. Now we want to take the time to truly introduce this new release.
I'm setting up the configuration for the Styles drop-down in my CKEditor, and am wondering if it is possible to apply multiple classes to a single element with a single style. The section of my stylesSet definition looks like this (note: this is a snippet and not the complete stylesSet definitio
Hi all, I've been starting upgrading Hippo from 7.8 to 7.9 and face a problem that property "/hippo:configuration/hippo:frontend/cms/cms-services/htmlCleanerService/cleaner.config" doesn't exist. What should I do in Hippo 7.9 to set that parameters? Kind regards, Andrew.
Hi William, Thanks for your answer. I just copied the entire hippo:domains node from production to staging. So now I'm sure they are both identical. But I have still the same behavior. Thomas. Le jeudi 27 août 2015 14:07:31 UTC+2, w.borgbarthet a écrit : > > Hi Thomas, > > are you sure the
Hi Thomas, are you sure the hippo:configuration/hippo:domains are identical? Can you confirm this by replacing the entire hippo:domains on staging (make a backup) with the domains on production? That should exclude any differences due to security domains. William On 27 August 2015 at 05:01,
Hi there, you can probably safely truncate the REPOSITORY_JOURNAL table. Otherwise it's pretty hard to remove parts of the repository from the database level AFAIK. If you are doing local development, you might be better off using the default H2 file database and manually exporting and importing
Hi, Jeroen solved this problem for us. :) The Freemarker servlet parses the .ftl using the platform's default Java encoding which for me (and most Windows users) is Cp1282. What worked was changing the file encoding system property in the root pom by adding it to the cargo-maven2-plugin