Forum OpenACS Development: Re: Extending User Properties

I resusciated this thread wondering if there would be a similar and neat solution as cr_item's.

function content_type__create_attribute

After a quick search in the api-doc, I found
api-doc/plsql-subprogram-one?name=acs_attribute__create_attribute&type=FUNCTION

That got me wonder if there would be any acs_object_type__create_attribute ... :)

Thanks Gustaf, for the references of the packages. im_dynfields is indeed a nice and potential solution to my case. It needs a bit testing to get only intranet-core and intranet-dynfields only. I don't want to fork too much of OACS core.

Best wishes,
I

If it does the expected, the new column in the table user_preferences should be created, shouldn't it?

I explicity added the argument in the plsql function,

Example:
select acs_attribute__create_attribute(
'user',
'purchased_plan',
'text',
'Purchased Plan',
'Purchased Plans',
'user_preferences',
'purchased_plan',
null,
1,
1,
null,
null,
'f'
);

The pl/sql functions accept a table_name parameter, but it clearly throws an error if table_name is not null. That does not make sense.

I have a set of changes that allow passing in table name to the function to allow passing in the table name. I can find those and make them available somewhere, if anyone in interested in trying to add that back into OpenACS core.