|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
|
|
migrating from 6.03.08 to 6.05.07Everyone,
I followed all the upgrade paths in details (or maybe not enough ;-) and now I have a working CMS instance, but when I click on a document, I get an infinite spinning wheel on the top right of the screen and no document actions (bottom-right box) are shown; my first guess is that something is wrong with the workflow (stored in a MS SQL database). My configuration is maven.cocoon.servermanager.configuration=example_project maven.cocoon.servermanager.configuration.dir=${basedir}/templates/example_project_sqlserver_J2EE cms.datasource.workflow.jndi=java:comp/env/jdbc/projectDataSource cms.datasource.workflow.reference=jdbc/projectDataSource and <Resource name="jdbc/repositoryDataSource" auth="Container" type="javax.sql.DataSource" username="fake_uid" password="fake_pwd" validationQuery="SELECT 1" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" maxActive="100" maxIdle="30" maxWait="100" url="jdbc:sqlserver://fake.host;DatabaseName=fakedb_slide;SelectMethod=cursor;" /> <Resource name="jdbc/projectDataSource" auth="Container" type="javax.sql.DataSource" username="fake_uid" password="fake_pwd" validationQuery="SELECT 1" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" maxActive="100" maxIdle="30" maxWait="100" url="jdbc:sqlserver://fake.host;DatabaseName=fakedb_projectdata;SelectMethod=cursor;" /> Looking at the log files I see the following exception, which is related with the workflow, but I cannot really understand what is wrong... any clue? TIA mau ---------- Exception in thread "QuartzScheduler_sampleProjectSchedulerStore-Testwebserver_ClusterManager" java.lang.NullPointerException at org.apache.commons.logging.LogFactory.getCachedFactory(LogFactory.java:489) at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:227) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.quartz.impl.jdbcjobstore.JobStoreSupport.getLog(JobStoreSupport.java:458) at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:2384) at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:2409) Exception in thread "example_projectProjectScheduler_QuartzSchedulerThread" java.lang.NullPointerException at org.apache.commons.logging.LogFactory.getCachedFactory(LogFactory.java:489) at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:227) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.quartz.core.QuartzSchedulerThread.getLog(QuartzSchedulerThread.java:475) at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:404) Exception in thread "QuartzScheduler_sampleProjectSchedulerStore-Testwebserver_ClusterManager" java.lang.NullPointerException at org.apache.commons.logging.LogFactory.getCachedFactory(LogFactory.java:489) at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:227) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.quartz.impl.jdbcjobstore.JobStoreSupport.getLog(JobStoreSupport.java:458) at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:2384) at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:2409) Met vriendelijke groet, -- Maurizio Pillitu - 0031 (0)615655668 Opensource Software Engineer Scrum Certified Master - http://www.scrumalliance.org Sourcesense - making sense of Open Source: http://www.sourcesense.com ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Maurizio Pillitu wrote:
> Everyone, > > I followed all the upgrade paths in details (or maybe not enough ;-) and now > I have a working CMS instance, but when I click on a document, I get an > infinite spinning wheel on the top right of the screen and no document > actions (bottom-right box) are shown; my first guess is that something is > wrong with the workflow (stored in a MS SQL database). Sounds like a problem with the workflow, have you converted the absolute URI in your database to relative ones? See: http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.03+to+v6.04+upgrade+path Note that you'll probably need to edit the path in that query to match your setup. Regards, -- Bartosz Oudekerk .---------------------------------.-----------------------------------. | Hippo B.V. | Hippo USA Inc. | | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | | 1017 WT Amsterdam | 94952-5100 San Francisco | | The Netherlands | United States | | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | +---------------------------------+-----------------------------------+ | b.oudekerk@... | http://www.onehippo.com | `---------------------------------^-----------------------------------' ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Thx Bartosz for the quick reply... my comments interleaved ....
On Mon, Nov 9, 2009 at 6:44 PM, Bartosz Oudekerk <b.oudekerk@...>wrote: > Maurizio Pillitu wrote: > >> Everyone, >> >> I followed all the upgrade paths in details (or maybe not enough ;-) and >> now >> I have a working CMS instance, but when I click on a document, I get an >> infinite spinning wheel on the top right of the screen and no document >> actions (bottom-right box) are shown; my first guess is that something is >> wrong with the workflow (stored in a MS SQL database). >> > > Sounds like a problem with the workflow, have you converted the absolute > URI in your database to relative ones? > Good point! I did it and I got another error, which is perfectly explained by an unanswered question to this mailing-list http://hippo15.castaserver.com/pipermail/hippocms-dev/2009-March/005960.html Any clue? Maybe Daniel managed to figure it out? TIA mau > > See: > http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.03+to+v6.04+upgrade+path > > Note that you'll probably need to edit the path in that query to match > your setup. > > Regards, > -- > Bartosz Oudekerk > .---------------------------------.-----------------------------------. > | Hippo B.V. | Hippo USA Inc. | > | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | > | 1017 WT Amsterdam | 94952-5100 San Francisco | > | The Netherlands | United States | > | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | > +---------------------------------+-----------------------------------+ > | b.oudekerk@... | http://www.onehippo.com | > `---------------------------------^-----------------------------------' > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > -- Met vriendelijke groet, -- Maurizio Pillitu - 0031 (0)615655668 Opensource Software Engineer Scrum Certified Master - http://www.scrumalliance.org Sourcesense - making sense of Open Source: http://www.sourcesense.com ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Maurizio Pillitu wrote:
> Good point! I did it and I got another error, which is perfectly explained > by an unanswered question to this mailing-list > > http://hippo15.castaserver.com/pipermail/hippocms-dev/2009-March/005960.html Sorry, I have no idea from the top of my head, and currently have little time available to investigate. Maybe you could compare the template from the new version with the configuration from the original? And then see if apart from datasource configuration they have any other differences? Regards, -- Bartosz Oudekerk .---------------------------------.-----------------------------------. | Hippo B.V. | Hippo USA Inc. | | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | | 1017 WT Amsterdam | 94952-5100 San Francisco | | The Netherlands | United States | | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | +---------------------------------+-----------------------------------+ | b.oudekerk@... | http://www.onehippo.com | `---------------------------------^-----------------------------------' ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Just checking. Did you follow these steps?
http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.03+to+v6.04+upgrade+path then http://wiki.onehippo.com/display/CMS/Hippo+CMS+6.04.00+to+6.04.01+upgrade+path then http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.04+to+v6.05+upgrade+path Kind regards, Mathijs Brand Hippo m.brand@... Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100 +1 (707) 773-4646 www.onehippo.com info@... On Tue, Nov 10, 2009 at 5:08 PM, Bartosz Oudekerk <b.oudekerk@...> wrote: > Maurizio Pillitu wrote: >> >> Good point! I did it and I got another error, which is perfectly explained >> by an unanswered question to this mailing-list >> >> >> http://hippo15.castaserver.com/pipermail/hippocms-dev/2009-March/005960.html > > Sorry, I have no idea from the top of my head, and currently have little > time available to investigate. > > Maybe you could compare the template from the new version with the > configuration from the original? And then see if apart from datasource > configuration they have any other differences? > > Regards, > -- > Bartosz Oudekerk > .---------------------------------.-----------------------------------. > | Hippo B.V. | Hippo USA Inc. | > | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | > | 1017 WT Amsterdam | 94952-5100 San Francisco | > | The Netherlands | United States | > | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | > +---------------------------------+-----------------------------------+ > | b.oudekerk@... | http://www.onehippo.com | > `---------------------------------^-----------------------------------' > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Yes, all of them.
BTW, you forgot these :P Hippo CMS 6.04.01 to 6.04.02 upgrade path<http://wiki.onehippo.com/display/CMS/Hippo+CMS+6.04.01+to+6.04.02+upgrade+path> Hippo CMS v6.05.00 to v6.05.01 upgrade path<http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.05.00+to+v6.05.01+upgrade+path> Hippo CMS v6.05.01 to v6.05.02 upgrade path<http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.05.01+to+v6.05.02+upgrade+path> Hippo CMS v6.05.02 to v6.05.03 upgrade path<http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.05.02+to+v6.05.03+upgrade+path> Hippo CMS v6.05.03 to v6.05.04 upgrade path<http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.05.03+to+v6.05.04+upgrade+path> Hippo CMS v6.05.04 to v6.05.05 upgrade path<http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.05.04+to+v6.05.05+upgrade+path> Hippo CMS v6.05.05 to v6.05.06 upgrade path<http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.05.05+to+v6.05.06+upgrade+path> Hippo CMS v6.05.06 to v6.05.07 upgrade path<http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.05.06+to+v6.05.07+upgrade+path> On Tue, Nov 10, 2009 at 5:21 PM, Mathijs Brand <m.brand@...> wrote: > Just checking. Did you follow these steps? > > http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.03+to+v6.04+upgrade+path > then > > http://wiki.onehippo.com/display/CMS/Hippo+CMS+6.04.00+to+6.04.01+upgrade+path > then > http://wiki.onehippo.com/display/CMS/Hippo+CMS+v6.04+to+v6.05+upgrade+path > > Kind regards, > Mathijs Brand > Hippo > > m.brand@... > > Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 > San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA > 94952-5100 +1 (707) 773-4646 > > www.onehippo.com info@... > > > > > On Tue, Nov 10, 2009 at 5:08 PM, Bartosz Oudekerk > <b.oudekerk@...> wrote: > > Maurizio Pillitu wrote: > >> > >> Good point! I did it and I got another error, which is perfectly > explained > >> by an unanswered question to this mailing-list > >> > >> > >> > http://hippo15.castaserver.com/pipermail/hippocms-dev/2009-March/005960.html > > > > Sorry, I have no idea from the top of my head, and currently have little > > time available to investigate. > > > > Maybe you could compare the template from the new version with the > > configuration from the original? And then see if apart from datasource > > configuration they have any other differences? > > > > Regards, > > -- > > Bartosz Oudekerk > > .---------------------------------.-----------------------------------. > > | Hippo B.V. | Hippo USA Inc. | > > | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | > > | 1017 WT Amsterdam | 94952-5100 San Francisco | > > | The Netherlands | United States | > > | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | > > +---------------------------------+-----------------------------------+ > > | b.oudekerk@... | http://www.onehippo.com | > > `---------------------------------^-----------------------------------' > > ******************************************** > > Hippocms-dev: Hippo CMS development public mailinglist > > > > Searchable archives can be found at: > > MarkMail: http://hippocms-dev.markmail.org > > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > > > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > -- Met vriendelijke groet, -- Maurizio Pillitu - 0031 (0)615655668 Opensource Software Engineer Scrum Certified Master - http://www.scrumalliance.org Sourcesense - making sense of Open Source: http://www.sourcesense.com ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07> Good point! I did it and I got another error, which is perfectly explained
stacktrace:
> by an unanswered question to this mailing-list > > > http://hippo15.castaserver.com/pipermail/hippocms-dev/2009-March/005960.html > > Any clue? Maybe Daniel managed to figure it out? > > TIA > mau > > I did some further investigation, and managed to get a meaningful Root cause: com.microsoft.sqlserver.jdbc.SQLServerException: 'nextVal' is not a recognized built-in function name. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source) at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.sendExecute(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteQuery(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(Unknown Source) at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93) at com.opensymphony.workflow.spi.jdbc.JDBCWorkflowStore.getNextEntrySequence(JDBCWorkflowStore.java:597) at com.opensymphony.workflow.spi.jdbc.JDBCWorkflowStore.createEntry(JDBCWorkflowStore.java:159) at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:582) So, sqlserver throws an error on the nextVal function. This function is in the osworkflow code as the default value for entry.sequence and step.sequence properties. We're using the example_project_sqlserver_J2EE template, and in the WorkflowStore.xml entry.sequence is not defined causing osworkflow to fall back on the default value, which causes the error. I assume putting a correct value for entry.sequence in the WorkflowStore.xml would solve this, but I have no idea what the value should be. Could you please help me with this? Thanks, Rogier ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Rogier Peters wrote:
> I assume putting a correct value for entry.sequence in the WorkflowStore.xml > would solve this, but I have no idea what the value should be. Could you > please help me with this? Could you please check if/how it was defined in 6.03.08? (I'm assuming you still have a functioning copy somewhere) I'm curious as to why it stopped working. AFAICS the version of osworkflow used did not change between 6.03.08 & 6.05.07. Regards, -- Bartosz Oudekerk .---------------------------------.-----------------------------------. | Hippo B.V. | Hippo USA Inc. | | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | | 1017 WT Amsterdam | 94952-5100 San Francisco | | The Netherlands | United States | | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | +---------------------------------+-----------------------------------+ | b.oudekerk@... | http://www.onehippo.com | `---------------------------------^-----------------------------------' ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Bartosz Oudekerk wrote:
> Rogier Peters wrote: >> I assume putting a correct value for entry.sequence in the WorkflowStore.xml >> would solve this, but I have no idea what the value should be. Could you >> please help me with this? > > Could you please check if/how it was defined in 6.03.08? (I'm assuming > you still have a functioning copy somewhere) > > I'm curious as to why it stopped working. AFAICS the version of > osworkflow used did not change between 6.03.08 & 6.05.07. Looking at the differences between older versions and the current one the only significant difference I spot is that the older versions use the 'nl.hippo.servermanager.util.SpringMySqlWorkflowStore' class where the newer one uses 'nl.hippo.servermanager.util.SpringJdbcWorkflowStore' Could you test if that change is indeed what broke things for you between versions? Regards, -- Bartosz Oudekerk .---------------------------------.-----------------------------------. | Hippo B.V. | Hippo USA Inc. | | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | | 1017 WT Amsterdam | 94952-5100 San Francisco | | The Netherlands | United States | | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | +---------------------------------+-----------------------------------+ | b.oudekerk@... | http://www.onehippo.com | `---------------------------------^-----------------------------------' ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Rogier Peters wrote:
> I assume putting a correct value for entry.sequence in the WorkflowStore.xml > would solve this, but I have no idea what the value should be. Could you > please help me with this? If anyone is feeling adventurous, they could try to define entry.sequence as: <entry key="entry.sequence"> <value>select count(*) + 1 from OS_WFENTRY</value> </entry> Note that this is *untested* !! Regards, -- Bartosz Oudekerk .---------------------------------.-----------------------------------. | Hippo B.V. | Hippo USA Inc. | | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | | 1017 WT Amsterdam | 94952-5100 San Francisco | | The Netherlands | United States | | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | +---------------------------------+-----------------------------------+ | b.oudekerk@... | http://www.onehippo.com | `---------------------------------^-----------------------------------' ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07So, how would I determine if this is right or wrong? Anything in the
database I can look at? On Fri, Nov 13, 2009 at 1:41 PM, Bartosz Oudekerk <b.oudekerk@...>wrote: > Rogier Peters wrote: > >> I assume putting a correct value for entry.sequence in the >> WorkflowStore.xml >> would solve this, but I have no idea what the value should be. Could you >> please help me with this? >> > > If anyone is feeling adventurous, they could try to define > entry.sequence as: > > > <entry key="entry.sequence"> > <value>select count(*) + 1 from OS_WFENTRY</value> > </entry> > > Note that this is *untested* !! > > > Regards, > -- > Bartosz Oudekerk > .---------------------------------.-----------------------------------. > | Hippo B.V. | Hippo USA Inc. | > | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | > | 1017 WT Amsterdam | 94952-5100 San Francisco | > | The Netherlands | United States | > | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | > +---------------------------------+-----------------------------------+ > | b.oudekerk@... | http://www.onehippo.com | > `---------------------------------^-----------------------------------' > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > -- Rogier Peters rogier@twitter, flickr, delicious ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
|
|
Re: migrating from 6.03.08 to 6.05.07Rogier Peters wrote:
> So, how would I determine if this is right or wrong? Anything in the > database I can look at? According to the api docs[0], it's defined as: 'SQL query that returns the next ID for a workflow entry.' So you should check if new workflow entries indeed get an ID, one higher than the previous one. There might very well be a better way to do this in MSSQL, but this should work AFAICT without actually having tested it. [0]http://www.opensymphony.com/osworkflow/api/com/opensymphony/workflow/spi/jdbc/JDBCWorkflowStore.html > > On Fri, Nov 13, 2009 at 1:41 PM, Bartosz Oudekerk > <b.oudekerk@...>wrote: > >> Rogier Peters wrote: >> >>> I assume putting a correct value for entry.sequence in the >>> WorkflowStore.xml >>> would solve this, but I have no idea what the value should be. Could you >>> please help me with this? >>> >> >> If anyone is feeling adventurous, they could try to define >> entry.sequence as: >> >> >> <entry key="entry.sequence"> >> <value>select count(*) + 1 from OS_WFENTRY</value> >> </entry> >> >> Note that this is *untested* !! >> >> >> Regards, >> -- >> Bartosz Oudekerk >> .---------------------------------.-----------------------------------. >> | Hippo B.V. | Hippo USA Inc. | >> | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | >> | 1017 WT Amsterdam | 94952-5100 San Francisco | >> | The Netherlands | United States | >> | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | >> +---------------------------------+-----------------------------------+ >> | b.oudekerk@... | http://www.onehippo.com | >> `---------------------------------^-----------------------------------' >> ******************************************** >> Hippocms-dev: Hippo CMS development public mailinglist >> >> Searchable archives can be found at: >> MarkMail: http://hippocms-dev.markmail.org >> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >> >> > > -- Bartosz Oudekerk .---------------------------------.-----------------------------------. | Hippo B.V. | Hippo USA Inc. | | Oosteinde 11 | 101 H Street, suite Q Petaluma CA | | 1017 WT Amsterdam | 94952-5100 San Francisco | | The Netherlands | United States | | Tel +31 (0)20 5224466 | +1 (707) 773-4646 | +---------------------------------+-----------------------------------+ | b.oudekerk@... | http://www.onehippo.com | `---------------------------------^-----------------------------------' ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html |
| Free embeddable forum powered by Nabble | Forum Help |