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.
Hi Mahesh This works if i'm referencing an image which is part of the document bean, but for an image I've added as a component parameter I can't seem to access any of the variants. Thanks! Ashil On Friday, July 31, 2015 at 11:59:50 AM UTC+1, m.acharya wrote: > > Hi Ashil > > In the rendering
Hi Jay, are you just trying to expose the repository over RMI? In that case that's a setting usually placed in the context.xml file in tomcat. Jeroen On Fri, Jul 31, 2015 at 3:31 PM, Jay F <pcba...@gmail.com> wrote: > We're using hippo enterprise edition 7.9.1 with tomcat 6.0.24 on centos 6.6 >
I've currently got the attached repository.xml to try and run it with just jackrabbit, but this is giving me a few errors, starting with ERROR main [RepositoryImpl.<init>:366] failed to start Repository: Cannot instantiate persistence manager org.apache.jackrabbit.core.persistence.pool.DerbyPer
We're using hippo enterprise edition 7.9.1 with tomcat 6.0.24 on centos 6.6 Our current instance is using oracle as an external repository, that's working fine but we're trying to replace this instance with another that does not use oracle because of reasons. The first thing I did was to change
Hi Eric, how were these documents created? I can see the problem: the "validationlabels" document's handle's name doesn't match the variant name (see  for info on what a handle is). I'm guessing this was created by moving nodes around in the console or by using the JCR API directly, or maybe
Hi, I would like to display multiple content on the same page. Let's say I have the following content structure: Root - Translated folder1 - Simple Document1 - Translated folder2 - Simple Document2 - Simple Document3 AFAIK under one sitemapitem I can reference one relative