The error did disappear as soon as I created a community so it seems to be an initialisation problem that goes away once the fez instance is being used (as you sort of indicated).
Also the svn diff (fixed below) in the earlier email seemed to be garbled but I assume you could work out that there were 2 hardcoded "fez_"s at the end of the upgrade2007090601.sql file where there should be 2 "%TABLE_PREFIX%"s instead.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Matthew Smith
Sent: Wednesday, 19 September 2007 1:19 PM
Subject: Re: [Fez-developers] Missing fez_auth_roles table and sql syntaxproblem
Christiaan is away until next week. If there are no rows in the testfez_auth_rule_group_rules then the problem is to do with indexing the authorisation rules. There should be at least one row which is a mapping to the testfez_auth_rules rule for public_list. This all happens in function setIndexMatchingFields in class.record.php (which calls AuthIndex::setIndexAuth($pid);) which runs whenever a record is edited or reindexed.
On 9/18/07, Peter Newman <Peter.Newman@cdu.edu.au> wrote:
> Hi Christiaan
> A minor problem with the upgrade script (svn diff upgrade/sql_scripts/upgrade2007090601.sql):
> Index: upgrade/sql_scripts/upgrade2007090601.sql
> --- upgrade/sql_scripts/upgrade2007090601.sql (revision 1005)
> +++ upgrade/sql_scripts/upgrade2007090601.sql (working copy)
> @@ -351,8 +351,8 @@
> REPLACE INTO %TABLE_PREFIX%workflow_state_roles
> select wfs_id, aro_id from %TABLE_PREFIX%workflow_state
> -inner join fez_auth_roles on instr(wfs_roles, aro_role) > 0 and aro_id != 0;
> +inner join %TABLE_PREFIX%auth_roles on instr(wfs_roles, aro_role) > 0 and aro_id != 0;
> REPLACE INTO %TABLE_PREFIX%workflow_roles select wfL_id, aro_id from %TABLE_PREFIX%workflow
> -inner join fez_auth_roles on instr(wfL_roles, aro_role) > 0 and aro_id != 0;
> +inner join %TABLE_PREFIX%auth_roles on instr(wfL_roles, aro_role) > 0 and aro_id != 0;