Forum OpenACS Q&A: Intranet Module Giving me Headaches!

Collapse
1: Intranet Module Giving me Headaches!
Posted by Jamie Ross on 02/22/01 07:51 AM
I am running the current/latest OpenACS (3.4.2?) , AOLServer3.2 and PostgreSQL 7.1. Most stuff is running fine but intranet is a basket full of errors. Several are due to constraint where ORDER by has to apply to one section of a UNION.. and so fails in the current code. I added parens around the second SELECT and that fixed that.  Projects error off with another related error in the UNION statement and I cannot find where to add new projects. I added a subgroup to the group Projects in Intranet but that didnt seem  to help.  Has everyone had these problems (ie does it just need more debugging) or is this related to changes in the way 7.1 handles UNIONS etc

thanks, Jamie

Collapse
2: Response to Intranet Module Giving me Headaches! (response to 1)
Posted by Ben Adida on 02/22/01 04:21 PM
This sounds like issues with 7.1.... Any way you can try running your same codebase on 7.0? Intranet is by no means perfect, but that's in part due to ACS Classic 3.x Intranet being less than perfect. The number of errors you're describing seems significantly higher than I've encountered.
Collapse
3: Response to Intranet Module Giving me Headaches! (response to 1)
Posted by Roberto Mello on 02/22/01 04:28 PM
Download the new documentation or fetch the latest CVS sources. It includes good tips for Intranet that are in the Getting Started Guide.
Collapse
4: Response to Intranet Module Giving me Headaches! (response to 1)
Posted by Jamie Ross on 02/22/01 04:36 PM
It could well be 7.1 changes.. but I think I may see if I can get the outer joins to work now which would make life easier when porting  from Classic, besides.. I haven't contributed in a LONG while and now that my system is current, time I did something useful:)

I admit I didn't look at the Quick Start Guide ...  (RTFM).. will check that and see if that clears up some of my initialization problems.  The bright side is my current company is considering letting my set this up for the company website. (and no.. not Vignette who I parted ways ;)

Collapse
5: Response to Intranet Module Giving me Headaches! (response to 1)
Posted by Dan Wickstrom on 02/22/01 06:00 PM
Outer joins will work, but I think that we would like to keep openacs 3.2.x compatible with postgresql 7.0.x. See this recent thread about fixing problems with order by in unions due to using pg 7.1. There have been several contributions to the cvs sources to help make openacs compatible with pg 7.1.
Collapse
6: Response to Intranet Module Giving me Headaches! (response to 1)
Posted by Ben Adida on 02/22/01 06:02 PM
Dan is right: let's make sure OpenACS 3.x remains PG 7.0 compatible.
Collapse
7: Response to Intranet Module Giving me Headaches! (response to 1)
Posted by Don Baccus on 02/23/01 07:05 AM
Ditto...and the necessary changes aren't simply gratuitous, they fix
cases where PG 7.O "pretended" to do the right thing, but in actuality
didn't.  So the existing ported queries only worked in a limited sense
anyway.  The changes necessary to make them work correctly are
minimal, and we're better off having PG tell us to do them right
rather than have the queries not work quite as expected (as was true
in 7.0)