Skip to content. | Skip to navigation

Four Digits | Willemsplein 44, 6811 KD Arnhem, The Netherlands | info@fourdigits.nl
 
Roel Bruggink works for Four Digits and is a Plone developer since 2008. Roel's day-to-day work consists of a wide range of activities linked to Plone; from system administration and backend/frontend development, to project management. Roel currently maintains the collective.anonymousview product.
 

collective.anonymousview released

collective.anonymousview allows authenticated users to view a page as if they are not logged in.

What is collective.anonymousview and why does it exist?

During the interviews done by Laurens some of the clients said that they use a second browser to see what the website looks to normal visitors. We also use multiple browser to see how the website behaves.

We released collective.anonymousview (SVN, pypi, plone.org) to allow content editors (and our developers) to view the current page as an anonymous user more easily. The product adds an extra tab to the object actions bar, which links to a browserview that under water uses urllib2 to open that page for you. That way you effectively have an extra browser, and it saves time for our clients and developers, because they no longer have to navigate through the website (or copy the url) in a seperate browser.

What does it look like?

The extra tab is located to the right side:

Extra 'anonymous view' tab

The normal 'logged in' screen looks like this:

Front-page for an authenticated user

And the 'anonymous' screen, with just another browserview looks like this:

Front-page for an 'anonymous' user

Installation

Installation is the same as other products:

Add the following to buildout.cfg:

eggs +=
    collective.anonymousview
zcml +=
    collective.anonymousview

Next up is to install it via the quickinstaller, or (if you use that) include it in your policy product (page 14) and reinstall that.

 
Made by Four Digits based on Plone.
Made by Four Digits based on Plone.