Mickaël Tricot | 12 Oct 2010 10:47

CMS doesn't run

Hi Hippos,

The CMS which used to work fine, doesn't run anymore. I switched from 
Windows to Linux since last time.
Cocoon deployment is successful. Then fortress startup appears to be 
successful. But the cms is not reachable from my browser. See the logs 
below.
No problem to run the site though.

- Is there a missing "excalibur" dependency? (Maven files didn't change)
- Are there missing properties? (configuration files didn't change)
- Is there a network issue? (I disabled the firewall)

Any clue? Thanks,

Mickaël

----------

*logs/fortress.log*

WARN  fortress.system.roles.defaults Unable to load class 
org.apache.avalon.excalibur.datasource.JdbcDataSource. Skipping.
WARN  fortress.system.roles.defaults Unable to load class 
org.apache.avalon.excalibur.datasource.J2eeDataSource. Skipping.
WARN  fortress.system.roles.defaults Unable to load class 
org.apache.avalon.excalibur.datasource.InformixDataSource. Skipping.
WARN  fortress.system.roles.defaults Unable to load class 
org.apache.excalibur.xml.xpath.XPathProcessorImpl. Skipping.
WARN  fortress.system.roles.defaults Unable to load class 
(Continue reading)

Jasha Joachimsthal | 12 Oct 2010 11:16
Gravatar

Re: CMS doesn't run

On 12 October 2010 10:47, Mickaël Tricot <m.tricot <at> onehippo.com> wrote:

> Hi Hippos,
>
> The CMS which used to work fine, doesn't run anymore. I switched from
> Windows to Linux since last time.
> Cocoon deployment is successful. Then fortress startup appears to be
> successful. But the cms is not reachable from my browser. See the logs
> below.
> No problem to run the site though.
>
> - Is there a missing "excalibur" dependency? (Maven files didn't change)
> - Are there missing properties? (configuration files didn't change)
> - Is there a network issue? (I disabled the firewall)
>
> Any clue? Thanks,
>
> Mickaël
>
> ----------
>
> *logs/fortress.log*
>
> WARN  fortress.system.roles.defaults Unable to load class
> org.apache.avalon.excalibur.datasource.JdbcDataSource. Skipping.
> WARN  fortress.system.roles.defaults Unable to load class
> org.apache.avalon.excalibur.datasource.J2eeDataSource. Skipping.
> WARN  fortress.system.roles.defaults Unable to load class
> org.apache.avalon.excalibur.datasource.InformixDataSource. Skipping.
> WARN  fortress.system.roles.defaults Unable to load class
(Continue reading)

Mickaël Tricot | 12 Oct 2010 11:33

Re: CMS doesn't run

Oh OK, I found my stupid mistake.
The build.properties file was under cms-customized instead of 
cms-customized/editor.
Thanks Jasha.

On 10/12/2010 11:16 AM, Jasha Joachimsthal wrote:
> On 12 October 2010 10:47, Mickaël Tricot<m.tricot <at> onehippo.com>  wrote:
>    
>> Hi Hippos,
>>
>> The CMS which used to work fine, doesn't run anymore. I switched from
>> Windows to Linux since last time.
>> Cocoon deployment is successful. Then fortress startup appears to be
>> successful. But the cms is not reachable from my browser. See the logs
>> below.
>> No problem to run the site though.
>>
>> - Is there a missing "excalibur" dependency? (Maven files didn't change)
>> - Are there missing properties? (configuration files didn't change)
>> - Is there a network issue? (I disabled the firewall)
>>
>> Any clue? Thanks,
>>
>> Mickaël
>>
>> ----------
>>
>> *logs/fortress.log*
>>
>> WARN  fortress.system.roles.defaults Unable to load class
(Continue reading)

Mickaël Tricot | 13 Oct 2010 10:42

DASL query: order by and null values

Hi all,

With such DASL expression, I get first documents with empty street, then 
documents with a street sorted in alphabetic order.

<d:orderby>
<d:order>
<d:prop><hc:street/></d:prop>
</d:order>
</d:orderby>

I was wondering if there is a way to handle null values differently, in 
order to get first documents with a street filled.

Thanks,

Mickaël
********************************************
Hippocms-dev: Hippo CMS 6 development public mailinglist

Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html

Maurizio Pillitu | 29 Oct 2010 16:58
Gravatar

prevent deletion if documents are published

Hi everyone,

I'm working on Hippo CMS 6.05.10 and I'd like to know if it somehow possible
to prevent users to remove documents that are currently published; I
remember this feature was implemented somehow, but I cannot find any
reference or documentation.

Any hints?
Thanks,
  mau

-- 

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 6 development public mailinglist

Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html

Jasha Joachimsthal | 30 Oct 2010 10:19
Gravatar

Re: prevent deletion if documents are published

Hi Maurizio,

On 29 October 2010 16:58, Maurizio Pillitu <m.pillitu <at> sourcesense.com>wrote:

> Hi everyone,
>
> I'm working on Hippo CMS 6.05.10 and I'd like to know if it somehow
> possible
> to prevent users to remove documents that are currently published; I
> remember this feature was implemented somehow, but I cannot find any
> reference or documentation.
>

The default reviewed actions workflow in CMS 6 allows you to delete or move
a document that is currently published. In CMS 7 the only action you can do
on a published document is to unpublish. Other actions are available if a
document is unpublished.
If you want this same behaviour in CMS6 you'll have to modify the reviewed
actions workflow [1]. For the renameDocument function this check already
exists and you can see its condition in [2]. Renaming a document is only
possible if a document is unpublished.

[1] https://wiki.onehippo.com/display/CMS/10.+Workflow
[2]
http://svn.hippocms.org/repos/hippo/hippo-workflows/tags/Release-WFREVACT-v1_04_14/src/workflow/ReviewedActionsWorkflow.xml

Ciao,

Jasha Joachimsthal

(Continue reading)


Gmane