Jason,
 
The DefaultTopNavigation is inserting itself directly into the page contained in the RunData parameter and returning null. This seems rather limiting (and confusing) because it doesn't give the DefaultLayout any say in where the navigation goes even though the DefaultLayout thinks it does have a say because it's inserting the return value (null) into the body as well. Here's my tiny little fix:
 
The DefaultLayout calls(delegates) to the navigation to decide where it goes in the page. This way you can define/ customize your navigation.   So for example you could do something like this in the top navigation:

data.getPage().getBody()

.addElement( new Center()

.addElement( new H2("Turbine User Management") )

.addElement("[ ")

.addElement( new A(new DynamicURI(data,"admin.Main",true).toString(),"Admin Main") )

.addElement(" ]")

.addElement("  [ ")

.addElement( new A(new DynamicURI(data,"DefaultScreen","LogoutUser",true).toString(),"Logout") )

.addElement(" ]") )

.addElement("<BR>");

 
What's the status of the AddUser and related screens? I'm getting an unknown table 'VISITOR_SEQUENCE' error whenever I try to add a new user. Is this supposed to work? Some of the related screens also seem like work-in-progresses.
 
I'm currently working on all the Admistrative screens now.  And have fixed the AddUser error your talking about.  Should be coming soon.
 
The DefaultScreen has got something that looks like a test on it but I appear to be failing:
 
Role: This value should be True: False
Role: This value should be False: False
Perm: This value should be True: False
Perm: This value should be False: False
Not having dug at all into the Role and Permission code yet, I'm not entirely certain what the code is testing that my install isn't passing. Any ideas or is this expected?
 
This is because there are no role and permissions inserted into the database when you first install.  There are some fixes for this
on the way as well.
 
Dave
 
 

Reply via email to