Forum OpenACS Development: warning: categories in cvs head broken

Request notifications

Collapse
Posted by Gustaf Neumann on
A short warning: categories in cvs head are currently broken due to the following change:
http://xarg.net/tools/cvs/change-set-details?key=28258

The attribute "widget" is missing in the datamodel

[14/Sep/2007:19:07:02][2164.25676288][-conn:dotlrn-test5::0] Error: dbinit: error(localhost::dotlrn-test5,
ERROR: column "widget" does not exist
LINE 4: require_category_p, widget
^
): '

select
tree_id, subtree_category_id, assign_single_p,
require_category_p, widget
from category_tree_map
where object_id = '849'

Malte, have you forgotten to commit the update script and the changes to the datamodel?

Collapse
Posted by Malte Sussdorff on
Yes indeed. I got confused with SVN client => SVN cognovis-core => CVS openacs HEAD. Somewhere in this chain the SQL files did not get transfered. Sorry, fixed. And I had forgotten Oracle, which I hopefully fixed as well. And last but not least I hope categories is not core and I forgot to TIP this. The change itself was written by MatthewG, so kudos for the code go to him.
Collapse
Posted by Gustaf Neumann on
Sorry, fixed.
Sure? There are no changes CVS. Is your chain still broken?
..forgot to tip...
categories is an infrastructure package with some properties like kernel (other packages might depend on it). Formally, there is no need to tip, and since it is a conservative update, it should not break anything. But it would be nice to inform people about the new functionality and document it somehow (wiki?).

But my post was not about this at all, but only about the fact that it is broken (every package using it will stop working due to the missing sql updates, you won't be able to install it).

Collapse
Posted by Malte Sussdorff on
I think this time I got it right. http://xarg.net/tools/cvs/change-set-details?key=28373

As for documentation, yes, you are right. Here is what you can do now:

When mapping a category tree you can define which widget you are going to use, radio, select, checkbox, multiselect. This in effect will set the parameters for multiple select or not.

Now you are able to control the look and feel of categories easier and better, hopefully making any custom "type" categories easily redundant.