Re: Installation problems

Michael Wechner <[email protected]>
Newsgroups gmane.comp.cms.wyona.user
Message-ID <[email protected]>

Jann Forrer wrote:

> Dear Michi
> 
> 
>>Dear Jann
>>
>>Jann Forrer wrote:
>>
>>
>>>Dear Group
>>>
>>>Yesterday, I made a new installation of wyona using cvs. When I try to
>>>open the unipublic sample publication I get the introduction page but
>>>I get the error message posted below if I try to access "editor's view". 
>>>As far as tested the other publications are ok. 
>>>
>>>I run wyona on linux 2.4 (SuSE 7.3), using tomcat 4.1 as my servlet engine
>>>and java version 1.3.1. 
>>>
>>
>>Do you really mean Tomcat 4.1, or do you mean Tomcat 4.0.1?
>>Tomcat 4.0.1 and 4.0.4 should be working.
>>The Link for Tomact 4.0.4 is at
>>http://www.wyona.org/download/download_wyona_developer_linux.html
>>
>>Hope that helps
>>
>>
> Thanks, that helps very much. I installed version 4.0.4 and all worked
> well again. 
> 
> Two comments (questions) to the installation docu: 
> 1. Within the INSTALL-SRC File you propose to get a copy of tomcat from
> the nightly directory. Should you not refer to the release builds as on
> http://www.wyona.org/download/download_wyona_developer_linux.html? 



I agree.
At the moment the "Download Pages" are just XHTML. Marc is currently 
structuring the "Download Pages" into some more structured XML, which 
means in the near future we should be able to generate the INSTALL-SRC 
and INSTALL-BIN from this XML by some XSLT (text based).


> 
> 2. If I create an new publication according to your docu on
> http://www.wyona.org/docs/tutorial/index.html and run an ant reset (after
> a cvs update or checkout) the new publication will be lost :-( (of
> course that happen only once ...). Is it a solution to define a new target
> in the ant build file which did not delete the installation directory?



Yes, I know. The whole "change management/release update" has not been 
defined yet. It would certainly be better to have a target within 
build.xml, which is backuping at least the users data (docs/publication, 
etc.) into some directory, because else as you are saying everything 
will be gone! (Maybe we could set a parameter in the build.properties, 
which activates a target "backup". We also have to take care of multiple
resets, which means somebody has to count, bak1 bak2 bak2 etc.)

Any help (coding) or suggestions on the above topics is very welcome

Thanks

Michael


> 
> All the best 
> 
> Jann 
> 
> 
> 
> 
> _______________________________________________
> WyonaCMS-users mailing list
> [email protected]
> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-users
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.