On date 08/06/2005 11:16:31  Jann Forrer wrote:

>On Tue, 7 Jun 2005, Gregor J. Rothfuss wrote:
>
>> Sergi Tur/SGA/UPC wrote:
>> > Hi all,
>> >
>> > When I try to edit a page with bxe lenya responses with a blank page
and a
>> > "bxe_start is not defined" error in javascript console.
>>
>> please try to change the lenya.step=open to lenya.step=config and
>> lenya.step=xml and see if those pages (which are loaded by bxe in the
>> background) have a problem.
>>
>
>We had the same problem due to the use of an "old" (or more exact an old
>usecase-bxeng.xmap) publication. You should  check wether the followong
>transformation appears in your usecase-bxeng.xmap.
>
><map:transform src="../../xslt/util/strip_namespaces.xsl"/>
>

You are right!

My custom publication was an old one 1.2.2 version. Then I upgrade lenya to
version 1.2.3 but i forget to check my own publication!
Now in default publication BXE works but not in my own publication!

It's a pity but I not found any HOWTO or Tutorial talking about upgrading a
publication from 1.2.2 to 1.2.3......

I investigate a little bit more and I found in local.build.properties file
this:

#------------------------------------------------------------------------------------
# Files and directories which should be excluded during 'install', 'clean'
and 'reset'
# Comma- or space-separated list of patterns
# All files are included when commented
# This is useful for preserving content while you are developing a
publication

#target.install.excludes=**/pubs/default/content/**,**/pubs/default/resources/authoring/**,**/pubs/default/resources/live/**,**/pubs/default/config/ac/passwd/*.iml
#target.reset.excludes=${target.install.excludes}

Then trying to summarize..... Could I say that to upgrade a publication
from 1.2.2 to 1.2.3 we have to overwrite all the files except the
target.install.excludes ones?

>HTH
>
>Jann
>
>---------------------------------------------------------------------
>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]

Reply via email to