#members attribute

[David A. Bayly]

This is generally fixed if you delete the members and discuss root 
entries for the offending website and install the site from the 
servers menu once more.


>Yes, the file paths have been changed, but I thought I had fixed all 
>the absolute paths in the databases. That may be the source of the 
>problem, but I can't find anything specific wrong -- each of the 
>addresses being referenced in the admin and members tables seem to 
>be correct.
>
>Thanks for your help!
>
>Pete Harbeson
>
>-----Original Message-----
>From: ext David A. Bayly [mailto:dbayly at udena.ch]
>Sent: Monday, January 06, 2003 01:24 PM
>To: Frontier-Users at userland.com
>Subject: Re: #members attribute
>
>
>>Hi,
>>This is escaping me at the moment. After upgrading to Frontier 9 and
>>moving to new hardware I'm seeing this error when trying to access
>>editorial functions:
>>
>>#members attribute must be either a table or the name of a sub-table
>>or valid address or string in members.root
>>
>>As far as I can tell, this refers to the #members object in the
>>site's admin table -- but it IS a valid address in members.root. I
>>sort of have the feeling I'm overlooking something obvious!
>>
>>Pete Harbeson
>
>Did you change the file paths to the Guest Database fodler? If yes,
>all the websites that point to addresses in the members root have an
>incorrect path. If you did change the file paths, there is likely a
>lot else wrong too, Frontier is very sensitive to that.
>--
>
>- David Bayly.       Programmer and digest reader.     dbayly at udena dot ch
>  		Digest Readers do it once a day.


-- 

- David Bayly.       Programmer and digest reader.     dbayly at udena dot ch
  		Digest Readers do it once a day.