dr:api_sequences
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dr:api_sequences [2005/10/23 11:36] – corrected and extended fgm | dr:api_sequences [2020/11/23 17:23] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ... during the building of the various pages creating and editing a custom node..., as noted on a 4.6.3 installation during the development of the [[http:// | ... during the building of the various pages creating and editing a custom node..., as noted on a 4.6.3 installation during the development of the [[http:// | ||
| + | |||
| + | |||
| + | ===== Table of hook calls seen by a module ===== | ||
| < | < | ||
| + | |||
| <style type=" | <style type=" | ||
| body { font-size: | body { font-size: | ||
| + | th, td { vertical-align: | ||
| th[scope=" | th[scope=" | ||
| td { vertical-align: | td { vertical-align: | ||
| Line 13: | Line 18: | ||
| <table cellspacing=" | <table cellspacing=" | ||
| <tr> | <tr> | ||
| - | < | + | <th>< |
| < | < | ||
| <th width=" | <th width=" | ||
| Line 22: | Line 27: | ||
| < | < | ||
| after create</ | after create</ | ||
| - | <th>6 View node</ | + | <th>6: View node</ |
| < | < | ||
| < | < | ||
| Line 115: | Line 120: | ||
| < | < | ||
| < | < | ||
| - | name</ | + | name of node owner</td> |
| < | < | ||
| </tr> | </tr> | ||
| Line 285: | Line 290: | ||
| </tr> | </tr> | ||
| <tr> | <tr> | ||
| - | <th scope=" | + | <th scope=" |
| < | < | ||
| < | < | ||
| Line 318: | Line 323: | ||
| </tr> | </tr> | ||
| <tr> | <tr> | ||
| - | <th scope=" | + | <th scope=" |
| - | <td>node/add/& | + | < |
| - | <td>node/add/& | + | < |
| - | <td>node/add/& | + | < |
| - | <td>node/add/& | + | < |
| - | <td>node/& | + | < |
| - | <td>node/& | + | < |
| - | <td>node/& | + | < |
| - | <td>node/& | + | < |
| </tr> | </tr> | ||
| </ | </ | ||
| - | < | + | |
| - | module defines the additional fields it handles as fields as wrapped in an | + | |
| - | object (as I describe <a href=" | + | |
| - | < | + | |
| - | < | + | |
| - | with the builtin array entries</ | + | |
| - | < | + | |
| - | wrapper object. </ | + | |
| - | </ | + | |
| - | < | + | |
| - | object comes from the DB. </ | + | |
| - | <p>Of course, any additional calls done by the module will appear somewhere in | + | |
| - | between these. For instance, helpdesk loads the information about a contract' | + | |
| - | customer, which is a drupal USER, so hook_user(' | + | |
| - | Similarly, any call to <a href=" | + | |
| - | <a href=" | + | |
| </ | </ | ||
| + | |||
| + | ===== Notes ===== | ||
| + | |||
| + | The difference between ' | ||
| + | |||
| + | * " | ||
| + | * " | ||
| + | |||
| + | Basically, modules fields are returned from a HTML form, whereas a loaded object comes from the DB. | ||
| + | |||
| + | Of course, any additional calls done by the module will appear somewhere in between these. For instance, helpdesk loads the information about a contract' | ||
| + | |||
| + | Similarly, any call to [[http:// | ||
dr/api_sequences.1130067405.txt.gz · Last modified: (external edit)
