[horde] haspermission() error?

[Rich West]

Hrmm.. I sent this to the list (it is in my Sent folder), but it never showed
up.   Weird.. eh.. no biggie.

Anyhow, here's a dump of the DB schema from phpMyAdmin:
CREATE TABLE horde_categories (
  category_id int(11) NOT NULL default '0',
  group_uid varchar(255) NOT NULL default '',
  user_uid varchar(255) NOT NULL default '',
  category_name varchar(255) NOT NULL default '',
  category_parents varchar(255) NOT NULL default '',
  category_order int(11) NOT NULL default '0',
  category_data text,
  category_serialized smallint(6) NOT NULL default '0',
  category_updated timestamp(14) NOT NULL,
  PRIMARY KEY  (category_id),
  KEY category_category_name_idx (category_name),
  KEY category_group_idx (group_uid),
  KEY category_user_idx (user_uid),
  KEY category_order_idx (category_order),
  KEY category_serialized_idx (category_serialized)
) TYPE=MyISAM;


I checked all of the tables against the CVS tree, and everything is in sync...

-Rich



> Quoting Tim Glen <tim at nonfiction.ca>:
> 
>  | On 12/12/02 3:18 PM, "Chris Albertson" <alb at chrisalbertson.com> wrote:
>  | 
>  | > I had the same problem.
>  | > One thing to check is the dates on the prefs.php.dist files in the
> config
>  | > directory of horde.
>  | > However, I believe the change that fixed this problem was adding another
>  | field
>  | > to the category table of horde.
>  | > Table horde_categories now has a field called category_parents. Check
> the
>  | > /scripts/db/category_mysql.sql file for details on the field.
>  | >
>  | > I believe this will fix your problem. It's been a little bit since I had
>  | that
>  | > problem.
>  | 
>  | I've also been having this problem. My horde_categories has a field called
>  | category_parents which is a varchar(255) but I still get exactly the
>  | symptoms Rich described. I have been unable to find any help with this
>  | problem as of yet.
>  
> Tim,
> 
> There have been quite a few changes to horde_categories in the last week or
> so.  I suggest that you do a cvs update to the latest head version.  Then
> check the horde_categories table definition in horde/schemas/db with the
> definition that you are currently using.  They are probably different.
> The last issue was with 
>        category_order INT,
> IIRC
>