You have to register a pagehandler for your intermediates pages first. Then you can follow any of the method below.
These links will be helpful for you
The 2nd method looks easier.
Do you mean that I can create a regular plugin (in <Elgg root dir>/mod/<my plugin>) and then hook it to the Elgg core to change the work flow of user registration?
After looking into the start.php of Plugin "uservalidationbyemail", I am clearer about the procedure for hooking a plugin to the core.
My plugin only has 2 files, "manifest.xml" and "start.php".
The start.php of my plugin should contain
=====
elgg_register_event_handler('init', 'system', '<my plugin name>_init');
function <my plugin name>_init() {
elgg_register_page_handler('<page type to handle>', '<my plugin name>_page_handler');
elgg_register_plugin_hook_handler('register', 'user', '<my plugin name>_hook_handler');
}
function <my plugin name>_page_handler() {
/* empty function. this is a blank page which just displays all queued Elgg messages. */
}
function <my plugin name>_hook_handler() {
forward('<the url for another site>');
}
=====
Is my design correct?
What should the <page type to handle> be?
When does the engine calls the hook handler? The "List of plugin hooks in core" does not explain when the hook handler is called relative to the registration operation.
Thanks!
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.