| [ Index ] |
PHP Cross Reference of Drupal 6 (yi-drupal) |
[Source view] [Print] [Project Stats]
(no description)
| File Size: | 150 lines (6 kb) |
| Included or required: | 0 times |
| Referenced: | 0 times |
| Includes or requires: | 0 files |
| default_profile_modules() X-Ref |
| Return an array of the modules to be enabled when this profile is installed. return: |
| default_profile_details() X-Ref |
| Return a description of the profile for the initial installation screen. return: |
| default_profile_task_list() X-Ref |
| Return a list of tasks that this profile supports. return: |
| default_profile_tasks(&$task, $url) X-Ref |
| Perform any final installation tasks for this profile. The installer goes through the profile-select -> locale-select -> requirements -> database -> profile-install-batch -> locale-initial-batch -> configure -> locale-remaining-batch -> finished -> done tasks, in this order, if you don't implement this function in your profile. If this function is implemented, you can have any number of custom tasks to perform after 'configure', implementing a state machine here to walk the user through those tasks. First time, this function gets called with $task set to 'profile', and you can advance to further tasks by setting $task to your tasks' identifiers, used as array keys in the hook_profile_task_list() above. You must avoid the reserved tasks listed in install_reserved_tasks(). If you implement your custom tasks, this function will get called in every HTTP request (for form processing, printing your information screens and so on) until you advance to the 'profile-finished' task, with which you hand control back to the installer. Each custom page you return needs to provide a way to continue, such as a form submission or a link. You should also set custom page titles. You should define the list of custom tasks you implement by returning an array of them in hook_profile_task_list(), as these show up in the list of tasks on the installer user interface. Remember that the user will be able to reload the pages multiple times, so you might want to use variable_set() and variable_get() to remember your data and control further processing, if $task is insufficient. Should a profile want to display a form here, it can; the form should set '#redirect' to FALSE, and rely on an action in the submit handler, such as variable_set(), to detect submission and proceed to further tasks. See the configuration form handling code in install_tasks() for an example. Important: Any temporary variables should be removed using variable_del() before advancing to the 'profile-finished' phase. param: $task param: $url return: |
| default_form_alter(&$form, $form_state, $form_id) X-Ref |
| Implementation of hook_form_alter(). Allows the profile to alter the site-configuration form. This is called through custom invocation, so $form_state is not populated. |
| Generated: Mon Jul 9 18:01:44 2012 | Cross-referenced by PHPXref 0.7 |