Am Mittwoch, 2. Mai 2007 schrieb Will Scheidegger:
> Well, that was rather easy. Next problem:
>
> The patched code requires workspace definitions like this:
>
> <workspaces>
>       <workspace>
>               <name>workspacename</workspacename>
>       </workspace>
> </workspaces>
>
> whereas the original code expects something like this:
>
> <workspaces>
>       <workspace>workspacename</workspace>
> </workspaces>
>
> Unfortunately not all of the original code gets patched! So if you
> change the workspace definition to the new syntax namespace
> registration works, but the workspaces are not set up. If you leave
> them in the original syntax... well you can guess what's happening.

Hello Will,

have you applied all patches from MAGNOLIA-1346 and MAGNOLIA-1348? 
MAGNOLIA-1346 contains the patches for existing workspaces.
Can you tell me what is not getting patched? Maybe the source changed too much 
and the patches (3 month old) are rejected?

> @ Oliver: May I make a suggestion? Your extension to Magnolia is
> great and very important to many of us I would guess. Would you mind
> setting up a (wiki?) page with _all_ patches necessary? That would be
> awesome.

I hope that custom node types and namespaces will be part of 3.1. So I think 
it will be more useful to port/refactor my working products module which 
relies on MAGNOLIA-1346, MAGNOLIA-1348 and multi value properties from 
client's namespace to info.magnolia and from java5 to 1.4.

You could also try my complete diff (I'm on trunk) instead of many small as a 
quick solution. But I'm sure we can solve this.

O.



----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to