|
Thursday 21 June 2007 1:48:21 am
As pointed out above, eZ Publish has it's own set of functionality to redirect pages.
This is something you control from your extension module/view php code.
More on modules and views:
http://ez.no/doc/ez_publish/technical_manual/3_9/concepts_and_basics/modules_and_views
Urls in eZ Publish:
http://ez.no/doc/ez_publish/technical_manual/3_9/concepts_and_basics/url_translation
Relevant if this is a content/view page:
One other thing is that since eZ Publish supports nice urls, it has it own set of GET parameters support.
So instead of:
http://somepage.com/me/sparetime?day=friday&type=social
You have:
http://somepage.com/me/sparetime/(day)/friday/(type)/social
There are several advantages to this:
* Google will index the various urls as separate pages (as long as the content differs, Google sense this)
* eZ Publish's view cache handling will handle the cache correctly for you
* template variables for the params will automatically be created for you
for the above two params: {$view_parameters.day} and {$view_parameters.type}
Relevant if this is custom php code:
In ez publish own content modul, action view, there is a lot of examples on redirects and redirect codes:
http://pubsvn.ez.no/nextgen/trunk/kernel/content/action.php
For a extension example:
http://zev.ez.no/svn/extensions/ezdhtml/trunk/modules/ezdhtml/
module.php is the file defining the modul, and the rest is the vews.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
