You are here: Home Plone products collective.fourohfour

collective.fourohfour (1.0)

1
by Olha Pelishok last modified 2011-06-29
0.0
0.0
0.0
0.0
Released on 2011-06-20 by Martin Aspeli for Plone 3.0, Plone 4.0 under GPL - GNU General Public License available for All platforms.
Software development stage: alpha
Aliasing of Plone content

This package provides an "error document" that can be used for 404 responses and some middleware to trigger the correct responses.

It is useful if you are deploying a Plone site in a WSGI chain using repoze.zope2. When an error (e.g. a 404 response is triggered) you can forward to a page in Plone, which can display suggestions and a friendly error message.

Furthermore, if an alias can be found in the redirection storage from plone.app.redirector, an automatic redirect will be issued, taking the user to the new page.

Finally, there is a rudimentary UI to bulk load redirects. This is useful if you are migrating from an old site (perhaps not even a Plone site). Go to http://localhost:8080/your-site/@@bulk-load-aliases as a Manager user, and paste in the old and new paths in the form:

/index.php?pageId=123  =>  /some-page/some-where

Note: The portal root path will be automatically prefixed to the paths. Thus, the example above run on the Plone site 'mysite' would result in an underlying redirect of /mysite/index.php?pageId=123 to /mysite/some-page/some-where. The assumption is that you'll deploy with virtual hosting so that the 'mysite' is the VHM root and not shown as part of the URL, but part of rewrite rules.

To remove aliases, install Products.RedirectionTool and use its UI.

Document Actions
Powered by Plone