Michael Wohlfart wrote:
Hi Jürgen,
same problem here, tried to switch from lenya12x to lenya 14x, I remember
fiddling around with some migration tasks, trying to convert the default
publication to UUIDs (at least that's what i think it does ?-/):
./build.sh --noconfig module.test -Dmodule=org.apache.lenya.modules.migration
[ see: http://www.mail-archive.com/[email protected]/msg06513.html ]
I ended up with 2 default publication:
* the original publication was still there and didn't work at all,
the errors i got were the same as you reported
This one should now contain UUID-based content.
It would be very nice if you could add all problems to bugzilla.
And it would be even better if you could attach a test case
(see http://lenya.apache.org/docs/tests.html for instructions).
* in the other publication (probably converted to UUIDs but with the same
name) all the editors were broken, i couldn't check in a single document
after editing, i also couldn't create a any new documents, this was some
days ago so maybe this is fixed now :-/
This publication is only needed for testing.
So i guess there must be some magic to do with the trunk to get the default
publication working, but i have no clue what it is.
It works quite well for me with UUID-based content.
Maybe someone else can
shed some light on this, why is the default publication in the trunk not
already converted to UUIDs ?
The major reason is that we want to test the current content structure
for some time before forcing users to migrate their content. But at
the moment this is critical, because some things certainly don't work
anymore with the old content structure. I guess we have to abandon the
support for non-UUID content.
-- Andreas
Or what is he magic to get it working ?
TIA
Michael
Jürgen Ragaller wrote:
Am 10.07.2006 um 10:29 schrieb Andreas Hartmann:
Jürgen Ragaller wrote:
Hi all!
I'm trying to switch from lenya12x to lenya 14x.
How can I make a copy of the default publication under a different
publication_id (folder name) and a different Publication Name? Up to
now it was basically trial and error finding occurences of «default»
in the various files and replacing them with my publication id (and
partially also java package names). The result of my attempts is only
partially working. Where do I have to change what to get a new and
fully working Publication?
The «New Publication» mechanism does not seem to help me here because
it delivers a publication based on the default pub.
That depends if you want to use publication templating [1] or if you want
to create a publication from scratch.
Some hints:
- If you use publication templating and base your pub on the default pub,
use the "New Publication" function, copy the results to a source
directory of your choice, and start adding and overriding stuff.
Thank You for the quick answer.
I'm opting for the first version. If I'm trying this with todays 14x svn
I get an error after the login in the new publication:
The requested document '' with document-id '' does not exist.
If I now click on «create this document» the error message says:
The parameter [document] must not be null!
Maybe this has problem has already been posted...
Do I have to convert the default pub to uuid first?
Help is appreciated!
- If you want to start from scratch, put your custom resource types
and other functionality in modules, and put only presentation logic
and styles in your publication.
[1]
http://lenya.apache.org/1_4/reference/publication-templating/index.html
HTH,
-- Andreas
--Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jürgen Ragaller, null-oder-eins ltd.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
