Process Revize Login Updated: 03-03-2011 03:46:10

Following information is for Revize Developer Troubleshooting:
(Detailed explanations are at the end of this page)

Click here to continue with login or click here to cancel
(screen paused because trace enabled).

Revize webSpace:	plugins (defined when this page was published)
This Page URL:	(location.href)
referrer:	(document.referrer)
opener:	(window.opener.location.href)
All Channels:
Current Server:	(location.protocal / hostname / port )
Calling Page URL: (fully qualified url)	( source: )
Calling Page Path: (appended to channel)	(RZ.callerPath needs "/" as suffix but not prefix)
Calling Page Filename:	(RZ.callerFilename)
Current Server Channel:
Revize Server:	(defined in .../resin/conf/revize.xml)
Editing Channel:
Revize Server Path/Filename:	(revizeChannelPath+callerPath+callerFilename)

Calling Frame URL:	(window.opener.location.href)
Calling Frame Name:	(window.opener.name)
Calling Page Frame Tree:

Explanations:

This published page is the entry point for login and logout processing on the live server. Both login and logout attempt to switch servers staying on the corresponding page and frame urls.

Login is usually started from live server. Login always transfers to the Revize Server as configured in the revize.xml (if revize.xml is changed, this page must be republished).

If a Revize enabled page was displayed prior to login and and login is successful, control will transfer to the corresponding page on the Revize server (assuming the page belongs to the login webspace). If the page does not belong to the login webspace, control transfers to the home page of the webspace on the Revize server.

Logout is usually started from the Revize Server. Logout transfers to the Live Server to the corresponding page currently displayed on the Revize server. This page (revizelogin template) is used to complete the transfer to the corresponding page on the Live Server. If logout is requested from the Live server, the request is passed to the Revize server for processing and results are indeterminable.

If a login request is made from the Revize Server, the following scenarios are considered:

A prior login completed from a live server: the live server is retained as the server of choice to get control upon logout. We currently don't get confirmation from user.
There are no live servers defined (only Revize channels defined): This usually means the Revize server is the same as the live server OR we are in the development stage of the project and live servers are not yet configured. If either case, we complete the login. The subsequent logout request will remain on the Revize server.
There are channels defined for other servers but none yet used for login: We proceed with the login and a subsequent logout will remain on the Revize Server. We could prompt the user to select a Live Server at logout time but this is not yet implemented.

This is the only file posted and required on the live server for the entire login or logout process. All necessary information is retrieved from the Revize server and published on this page.

On login requests, this page initially tries to captures the calling or prior page frame tree so the corresponding page on the either the Revize or Live server is displayed upon successful login or logout respectively.

In keeping with Revize design philosophy, most logic is implemented by includes files and library functions. However, since this page is usually deployed to non-Revize servers, all include files are embedded in the published page. What this means is that when updated include files are received, they will not take effect until the this page is republished.

The layers are prompts and stored in this template so they can be modified if necessary by customers. The "Create/Setup webspace" item on the Revize menu will by default create a new version of this template using all currently defined channels and appropriate Revize properties.

Usage Notes:

This template provides a means of conveniently transferring to Revize Server from a non-Revize server where production pages as often published for site visitor viewing.

This page should ultimately be published to all servers (revize and live). It can be published anywhere in the web directory hierarchy. By default this template is published into a revizelogin directory at the top level directory of the channel. The page can then be easily referenced using "/revizelogin/" at a link target or a browser url such as: www.mywebsite.com/revizelogin/
An more reliable method for linking to the revizelogin page is to use: <rz:link template="revizelogin" target="revizelogin">Revize Login</rz:link>

The "webspaces" layer let's you display a list of webspaces for selection prior to login. This is useful when visitors are managing multiple webSpaces. This feature is disabled if the webspaceList variable is set to OFF at the top of this page.

User notes can be added to the login screen by replacing the following file with html:

<revize install dir>/www/revize/security/revizelogin/revizelogin_usernotes.jsp

window.name:
window.opener:
opener access:
location.href:
RZ.loginserverpath:
RZ.frameurls: