Forum OpenACS Development: Re: Problem Using AMS

6: Re: Problem Using AMS (response to 1)

Posted by Michael Steigman on 03/01/13 10:08 PM

The last post on the page you reference indicates that a fix was applied for the issue with Xowiki. In fact many (including us) are using the two together with no problems.

If you're planning to stick with the platform, you should give serious consideration to using the new object management package over AMS - it was designed after considering all of the various solutions (including AMS) to this problem in the toolkit's past.

If there are any specific question you have on the new package, several of us on the forums would be happy to help out.

8: Re: Problem Using AMS (response to 6)

Posted by Jorge Alcaraz on 03/05/13 06:07 PM

Thanks a lot Michael, well, I'd like to know how did you install the Acs Object Management, like I said before, I already have xowiki installed and I got this error when installing:

psql:acs-views-create.sql:20: ERROR: relation "acs_views" already exists
psql:acs-views-create.sql:61: ERROR: relation "acs_view_attributes" already exists
psql:acs-views-create.sql:303: ERROR: column dotlrn_member_rels.portal_id does not exist

And then:

ERROR: current transaction is aborted

Thanks!

9: Re: Problem Using AMS (response to 8)

Posted by Michael Steigman on 03/06/13 10:19 PM

It looks like you've already tried to install the package once before - acs_views and acs_view_attributes are part of AOM. I would run the drop script: packages/acs-object-management/sql/postgresql/acs-object-management-drop.sql first, then run the metadata updates I mention in the other thread. The data model install script creates default attribute views for all objects but it chokes when there is bad metadata. The issues mentioned in the other thread are probably common if you have .LRN installed. Copying those data model updates and running them on your system (on test system first!) would probably do the trick but you could also run the datamodel__acs_object_type_check test case at /test/admin as Jeff indicated to see what's going on in your specific install and clean up your object metadata as necessary. Let us know how you make out.