Forms + Actions — Elgg master documentation Example: User registration Simple sticky forms require little logic to determine the input values for the form This logic is placed at the top of the form body view itself The registration form view first sets default values for inputs, then checks if there are sticky values If so, it loads the sticky values before clearing the sticky form:
Registration page : Elgg. org 5 Create a file in "forms" called "register php" 6 Copy the contents of the core register php to your new register php 7 Make your customizations to your new register php 8 Install your plugin as you would any other - you now have a customized register php
php - How to call an elgg module action via url - Stack Overflow First thing: you're using deprecated action registration parameters - update your call I assume you're writing to Elgg 1 8 or later You're additng action tokens in completely wrong way! They're necessary to prevent XSRF attacks, so need to pe added at URL generation To elgg_register_action, you need to pass action file PATH, not URL
Page handler — Elgg master documentation - Read the Docs The plugin’s page handler is passed two parameters: an array containing the sections of the URL exploded by ‘ ’ With this information the handler will be able to apply any logic necessary, for example loading the appropriate view and returning its contents