Forum OpenACS Q&A: Re: Problem with newest xowiki

Collapse
31: Re: Problem with newest xowiki (response to 16)
Posted by Avni Khatri on 07/29/07 02:29 AM
Gustaf -

Has anyone made progress with porting xowiki to oracle?
If not, I would like to do it because I want to use xowiki at UCLA.

I've installed xotcl-core and have a working openacs5.3.1 on oracle9i
and have checked out xowiki from HEAD

My first question is:
Where is: xowiki/xotcl-core??
There is no xotcl-core directory under the xowiki package and I don't see any xql files in the xowiki package. Can you point me to where the queries are?

Thanks much,
Avni 😊

Collapse
32: Re: Problem with newest xowiki (response to 31)
Posted by Malte Sussdorff on 07/29/07 10:59 AM
Hi Avni, just make a checkout of the xotcl-core package. If I remember correctly Gustaf mentioned it "should" work. Once xotcl-core is working in Oracle, XoWIKI should not be much of an issue, though you might have to wade through the /tcl directory and search for the SQL commands, but instantiate_sql_query (in XoTCL Core) should be smart enough to "only" return a working query string, unless it is overridden with the "-where_clause" parameter.

This all being said, I got it installed on Oracle after I cut down the description tag of xowiki.info as Oracle was complaining about "long" parameters.

Collapse
33: Re: Problem with newest xowiki (response to 31)
Posted by Gustaf Neumann on 07/29/07 12:12 PM
Avni,

you need to checkout two packages from cvs head,
xowiki and xotcl-core. If you have a recent dotlrn installation, move away the version of xotcl-core that you have already before getting the head versions

For you other questions, please wait a couple of days for the new release. We discussed with roc to update xotcl-core in the oacs-5-3 branch and put xowiki there as well to have a place for a "stable release", while the eager development continues in cvs head. More and more sites rely on xowiki. Depending on when they grab a version of xowiki the get a current snapshot of xowiki. While i am trying to keep thinks working, with about 15 commits per week, people get sometimes features and new behaviors, they don't expect, which makes as well communication and support harder than necessary.