System Pages and URL Map

Forum:
- General discussion

Author	Message
DimDragon	25 Oct 2010 09:08 no-new-comments
Joined: 08 Mar 2010 Location:	Current url node types basically represent system pages and some default page selection. I believe some of those definitely do not belong to URL map since their logic is different and others simply have quite weird logic. Will split them in two main types : 1. System pages - page not found - system error - access denied Basically those are site properties/pages. They do not need specific URL, they do not need menu attributes since you never use those in menu, they can't bind to existing URL node ( simply no point in that ). So I believe those should definitelly be set outside URL map by simply creating a page and then assigning/marking it as system page. 2. Default ( as I understand their usage ) pages - logout - register - mail verification - forgotten password - user profile All those are not real 'types' but more like choosing defaults for the entire site. All those have corresponing web frames which actually bring logic to pages of this 'type' so I would consider a page which holds register web frame more or less 'an register' page rather then URL map marked as type 'regsiter'. This brings to question the whole logic behind those URL maps since lets consider the following small example : I have site with 2 blog applications only, first is Auto blog where people register with their car type, etc and second one is Literature blog where users register stating their favourite author, etc... So I have 2 pages where register web wrame is used with different settings and resulting in users going into 2 different security groups. Now I have to choose the 'default' register page for the whole site !? I have 2 options : select one of those 2 I have or create 3rd one which is more general and simply asks for user name/mail/password. In all cases however the selection of 'default' one suggests those pages already exist and you select one of them as default one. Here those pages definitelly need to have URL map entires in order to be accessible but giving map nodes a 'type' is akward at least when you have structure as I give in example. I really can't understand the logic behind those defaults since from one side they can be non present, so those defaults are not really needed, then combine this with the fact I have multiple pages of those types, if I as user have to set it up I would probably leave those as not set ( however I'm currently not sure if site will operate properly if I don't set them ? )

Author

Message

25 Oct 2010 09:08 no-new-comments

Joined:
08 Mar 2010
Location:

Current url node types basically represent system pages and some default page selection. I believe some of those definitely do not belong to URL map since their logic is different and others simply have quite weird logic. Will split them in two main types :

1. System pages

- page not found

- system error

- access denied

Basically those are site properties/pages. They do not need specific URL, they do not need menu attributes since you never use those in menu, they can't bind to existing URL node ( simply no point in that ). So I believe those should definitelly be set outside URL map by simply creating a page and then assigning/marking it as system page.

2. Default ( as I understand their usage ) pages

- logout

- register

- mail verification

- forgotten password

- user profile

All those are not real 'types' but more like choosing defaults for the entire site. All those have corresponing web frames which actually bring logic to pages of this 'type' so I would consider a page which holds register web frame more or less 'an register' page rather then URL map marked as type 'regsiter'. This brings to question the whole logic behind those URL maps since lets consider the following small example : I have site with 2 blog applications only, first is Auto blog where people register with their car type, etc and second one is Literature blog where users register stating their favourite author, etc... So I have 2 pages where register web wrame is used with different settings and resulting in users going into 2 different security groups. Now I have to choose the 'default' register page for the whole site !? I have 2 options : select one of those 2 I have or create 3rd one which is more general and simply asks for user name/mail/password. In all cases however the selection of 'default' one suggests those pages already exist and you select one of them as default one. Here those pages definitelly need to have URL map entires in order to be accessible but giving map nodes a 'type' is akward at least when you have structure as I give in example. I really can't understand the logic behind those defaults since from one side they can be non present, so those defaults are not really needed, then combine this with the fact I have multiple pages of those types, if I as user have to set it up I would probably leave those as not set ( however I'm currently not sure if site will operate properly if I don't set them ? )

DimDragon

25 Oct 2010 09:09 {{new_comments_class}}

Joined:
08 Mar 2010
Location:

Further under this discussion the usage of Login / Logout web frames and respective url node types. From one side we have the login web frame which can be placed where you desire and has good interface to enter credentials, then press a button and then shows the logged in status ( all very good and exactly as expected ). Now in a simple/common scenario this login web frame is placed in main master page in order to be able to provide login from all places and see logged status. This basically means that ANY page that uses this master page can be designated as 'login' page since they all will have it. Now lets look at Logout web frame, I would expect something similar as login frame to provide me will simple interface as link/button to logout and the optional url-redirect ( as present ). Instead every page on which logout frame is placed basically logs you out, so you need a completely fake page to hold this web frame ( no content here since it will not even be seen in case of redirect used ), so in order to have simple logout link I need to add this fake page, place logout frame in it and then in my master page add the link to this page. Now look at logout url node type, with the use of menu item you can add logout link without going through all trouble of 'fake' page as discribed, as result you have fully operational site with no logout page designated.

I would propose as idea to extend the login web frame with option to also provide logout link, this way with simple setting this can be included in interface. The whole idea behind logout web frame currently escapes me...since note that there is always generated logout in form '/wf/logout-page/' which can also be used as simple page redirect anywhere if needed...