node.api.php 49.8 KB
Newer Older
1 2
<?php

3
use Drupal\Core\Entity\EntityInterface;
4

5 6 7 8 9
/**
 * @file
 * Hooks provided by the Node module.
 */

10 11 12
/**
 * @defgroup node_api_hooks Node API Hooks
 * @{
13
 * Functions to define and modify content types.
14 15
 *
 * Each content type is maintained by a primary module, which is either
16 17
 * node.module (for content types created in the user interface) or the module
 * that implements hook_node_info() to define the content type.
18 19 20 21 22 23
 *
 * During node operations (create, update, view, delete, etc.), there are
 * several sets of hooks that get invoked to allow modules to modify the base
 * node operation:
 * - Node-type-specific hooks: These hooks are only invoked on the primary
 *   module, using the "base" return component of hook_node_info() as the
24 25 26
 *   function prefix.  For example, poll.module defines the base for the Poll
 *   content type as "poll", so during creation of a poll node, hook_insert() is
 *   only invoked by calling poll_insert().
27 28 29 30
 * - All-module hooks: This set of hooks is invoked on all implementing modules,
 *   to allow other modules to modify what the primary node module is doing. For
 *   example, hook_node_insert() is invoked on all modules when creating a poll
 *   node.
31 32 33 34 35 36 37 38 39 40 41
 * - Field hooks: Hooks related to the fields attached to the node. These are
 *   invoked from the field operations functions described below, and can be
 *   either field-type-specific or all-module hooks.
 * - Entity hooks: Generic hooks for "entity" operations. These are always
 *   invoked on all modules.
 *
 * Here is a list of the node and entity hooks that are invoked, field
 * operations, and other steps that take place during node operations:
 * - Creating a new node (calling node_save() on a new node):
 *   - field_attach_presave()
 *   - hook_node_presave() (all)
42
 *   - hook_entity_presave() (all)
43 44 45 46 47 48 49 50 51 52
 *   - Node and revision records are written to the database
 *   - hook_insert() (node-type-specific)
 *   - field_attach_insert()
 *   - hook_node_insert() (all)
 *   - hook_entity_insert() (all)
 *   - hook_node_access_records() (all)
 *   - hook_node_access_records_alter() (all)
 * - Updating an existing node (calling node_save() on an existing node):
 *   - field_attach_presave()
 *   - hook_node_presave() (all)
53
 *   - hook_entity_presave() (all)
54 55 56 57 58 59 60
 *   - Node and revision records are written to the database
 *   - hook_update() (node-type-specific)
 *   - field_attach_update()
 *   - hook_node_update() (all)
 *   - hook_entity_update() (all)
 *   - hook_node_access_records() (all)
 *   - hook_node_access_records_alter() (all)
61
 * - Loading a node (calling node_load(), node_load_multiple(), entity_load(),
62
 *   or entity_load_multiple() with $entity_type of 'node'):
63 64 65 66 67 68
 *   - Node and revision information is read from database.
 *   - hook_load() (node-type-specific)
 *   - field_attach_load_revision() and field_attach_load()
 *   - hook_entity_load() (all)
 *   - hook_node_load() (all)
 * - Viewing a single node (calling node_view() - note that the input to
69
 *   node_view() is a loaded node, so the Loading steps above are already done):
70 71
 *   - hook_view() (node-type-specific)
 *   - field_attach_prepare_view()
72
 *   - hook_entity_prepare_view() (all)
73 74
 *   - field_attach_view()
 *   - hook_node_view() (all)
75 76 77
 *   - hook_entity_view() (all)
 *   - hook_node_view_alter() (all)
 *   - hook_entity_view_alter() (all)
78 79 80 81
 * - Viewing multiple nodes (calling node_view_multiple() - note that the input
 *   to node_view_multiple() is a set of loaded nodes, so the Loading steps
 *   above are already done):
 *   - field_attach_prepare_view()
82
 *   - hook_entity_prepare_view() (all)
83 84 85
 *   - hook_view() (node-type-specific)
 *   - field_attach_view()
 *   - hook_node_view() (all)
86
 *   - hook_entity_view() (all)
87
 *   - hook_node_view_alter() (all)
88
 *   - hook_entity_view_alter() (all)
89 90 91
 * - Deleting a node (calling node_delete() or node_delete_multiple()):
 *   - Node is loaded (see Loading section above)
 *   - hook_delete() (node-type-specific)
92 93
 *   - hook_node_predelete() (all)
 *   - hook_entity_predelete() (all)
94
 *   - field_attach_delete()
95
 *   - Node and revision information are deleted from database
96 97
 *   - hook_node_delete() (all)
 *   - hook_entity_delete() (all)
98 99 100 101 102
 * - Deleting a node revision (calling node_revision_delete()):
 *   - Node is loaded (see Loading section above)
 *   - Revision information is deleted from database
 *   - hook_node_revision_delete() (all)
 *   - field_attach_delete_revision()
103 104
 * - Preparing a node for editing (calling node_form() - note that if it is an
 *   existing node, it will already be loaded; see the Loading section above):
105
 *   - hook_prepare() (node-type-specific)
106
 *   - hook_node_prepare() (all)
107 108 109 110 111 112 113 114 115 116 117 118
 *   - hook_form() (node-type-specific)
 *   - field_attach_form()
 * - Validating a node during editing form submit (calling
 *   node_form_validate()):
 *   - hook_validate() (node-type-specific)
 *   - hook_node_validate() (all)
 *   - field_attach_form_validate()
 * - Searching (calling node_search_execute()):
 *   - hook_ranking() (all)
 *   - Query is executed to find matching nodes
 *   - Resulting node is loaded (see Loading section above)
 *   - Resulting node is prepared for viewing (see Viewing a single node above)
119
 *   - comment_node_update_index() is called.
120 121 122 123 124 125 126 127
 *   - hook_node_search_result() (all)
 * - Search indexing (calling node_update_index()):
 *   - Node is loaded (see Loading section above)
 *   - Node is prepared for viewing (see Viewing a single node above)
 *   - hook_node_update_index() (all)
 * @}
 */

128 129 130 131 132 133 134 135
/**
 * @addtogroup hooks
 * @{
 */

/**
 * Inform the node access system what permissions the user has.
 *
136 137 138 139
 * This hook is for implementation by node access modules. In this hook,
 * the module grants a user different "grant IDs" within one or more
 * "realms". In hook_node_access_records(), the realms and grant IDs are
 * associated with permission to view, edit, and delete individual nodes.
140
 *
141
 * The realms and grant IDs can be arbitrarily defined by your node access
142 143 144 145
 * module; it is common to use role IDs as grant IDs, but that is not required.
 * Your module could instead maintain its own list of users, where each list has
 * an ID. In that case, the return value of this hook would be an array of the
 * list IDs that this user is a member of.
146
 *
147 148 149 150 151
 * A node access module may implement as many realms as necessary to properly
 * define the access privileges for the nodes. Note that the system makes no
 * distinction between published and unpublished nodes. It is the module's
 * responsibility to provide appropriate realms to limit access to unpublished
 * content.
152
 *
153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181
 * Node access records are stored in the {node_access} table and define which
 * grants are required to access a node. There is a special case for the view
 * operation -- a record with node ID 0 corresponds to a "view all" grant for
 * the realm and grant ID of that record. If there are no node access modules
 * enabled, the core node module adds a node ID 0 record for realm 'all'. Node
 * access modules can also grant "view all" permission on their custom realms;
 * for example, a module could create a record in {node_access} with:
 * @code
 * $record = array(
 *   'nid' => 0,
 *   'gid' => 888,
 *   'realm' => 'example_realm',
 *   'grant_view' => 1,
 *   'grant_update' => 0,
 *   'grant_delete' => 0,
 * );
 * drupal_write_record('node_access', $record);
 * @endcode
 * And then in its hook_node_grants() implementation, it would need to return:
 * @code
 * if ($op == 'view') {
 *   $grants['example_realm'] = array(888);
 * }
 * @endcode
 * If you decide to do this, be aware that the node_access_rebuild() function
 * will erase any node ID 0 entry when it is called, so you will need to make
 * sure to restore your {node_access} record after node_access_rebuild() is
 * called.
 *
182
 * @param $account
183 184
 *   The user object whose grants are requested.
 * @param $op
185
 *   The node operation to be performed, such as 'view', 'update', or 'delete'.
186
 *
187
 * @return
188 189
 *   An array whose keys are "realms" of grants, and whose values are arrays of
 *   the grant IDs within this realm that this user is being granted.
190 191 192
 *
 * For a detailed example, see node_access_example.module.
 *
193 194
 * @see node_access_view_all_nodes()
 * @see node_access_rebuild()
195 196 197 198 199 200
 * @ingroup node_access
 */
function hook_node_grants($account, $op) {
  if (user_access('access private content', $account)) {
    $grants['example'] = array(1);
  }
201
  $grants['example_owner'] = array($account->uid);
202 203 204 205 206 207
  return $grants;
}

/**
 * Set permissions for a node to be written to the database.
 *
208 209 210
 * When a node is saved, a module implementing hook_node_access_records() will
 * be asked if it is interested in the access permissions for a node. If it is
 * interested, it must respond with an array of permissions arrays for that
211 212
 * node.
 *
213 214 215 216 217 218
 * Node access grants apply regardless of the published or unpublished status
 * of the node. Implementations must make sure not to grant access to
 * unpublished nodes if they don't want to change the standard access control
 * behavior. Your module may need to create a separate access realm to handle
 * access to unpublished nodes.
 *
219 220 221
 * Note that the grant values in the return value from your hook must be
 * integers and not boolean TRUE and FALSE.
 *
222 223 224 225
 * Each permissions item in the array is an array with the following elements:
 * - 'realm': The name of a realm that the module has defined in
 *   hook_node_grants().
 * - 'gid': A 'grant ID' from hook_node_grants().
226
 * - 'grant_view': If set to 1 a user that has been identified as a member
227 228 229
 *   of this gid within this realm can view this node. This should usually be
 *   set to $node->status. Failure to do so may expose unpublished content
 *   to some users.
230
 * - 'grant_update': If set to 1 a user that has been identified as a member
231
 *   of this gid within this realm can edit this node.
232
 * - 'grant_delete': If set to 1 a user that has been identified as a member
233
 *   of this gid within this realm can delete this node.
234
 *
235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
 *
 * When an implementation is interested in a node but want to deny access to
 * everyone, it may return a "deny all" grant:
 *
 * @code
 * $grants[] = array(
 *   'realm' => 'all',
 *   'gid' => 0,
 *   'grant_view' => 0,
 *   'grant_update' => 0,
 *   'grant_delete' => 0,
 *   'priority' => 1,
 * );
 * @endcode
 *
 * Setting the priority should cancel out other grants. In the case of a
 * conflict between modules, it is safer to use hook_node_access_records_alter()
 * to return only the deny grant.
 *
 * Note: a deny all grant is not written to the database; denies are implicit.
 *
256
 * @param Drupal\node\Node $node
257 258 259 260 261
 *   The node that has just been saved.
 *
 * @return
 *   An array of grants as defined above.
 *
262
 * @see _node_access_write_grants()
263
 * @see hook_node_access_records_alter()
264 265
 * @ingroup node_access
 */
266
function hook_node_access_records(Drupal\node\Node $node) {
267
  // We only care about the node if it has been marked private. If not, it is
268 269 270
  // treated just like any other node and we completely ignore it.
  if ($node->private) {
    $grants = array();
271 272 273 274 275 276 277 278 279 280 281
    // Only published nodes should be viewable to all users. If we allow access
    // blindly here, then all users could view an unpublished node.
    if ($node->status) {
      $grants[] = array(
        'realm' => 'example',
        'gid' => 1,
        'grant_view' => 1,
        'grant_update' => 0,
        'grant_delete' => 0,
      );
    }
282
    // For the example_author array, the GID is equivalent to a UID, which
283 284 285
    // means there are many groups of just 1 user.
    // Note that an author can always view his or her nodes, even if they
    // have status unpublished.
286 287 288
    $grants[] = array(
      'realm' => 'example_author',
      'gid' => $node->uid,
289 290 291
      'grant_view' => 1,
      'grant_update' => 1,
      'grant_delete' => 1,
292
    );
293

294 295 296 297
    return $grants;
  }
}

298 299 300 301 302 303 304 305 306 307 308 309 310 311 312
/**
 * Alter permissions for a node before it is written to the database.
 *
 * Node access modules establish rules for user access to content. Node access
 * records are stored in the {node_access} table and define which permissions
 * are required to access a node. This hook is invoked after node access modules
 * returned their requirements via hook_node_access_records(); doing so allows
 * modules to modify the $grants array by reference before it is stored, so
 * custom or advanced business logic can be applied.
 *
 * Upon viewing, editing or deleting a node, hook_node_grants() builds a
 * permissions array that is compared against the stored access records. The
 * user must have one or more matching permissions in order to complete the
 * requested operation.
 *
313 314
 * A module may deny all access to a node by setting $grants to an empty array.
 *
315
 * @param $grants
316
 *   The $grants array returned by hook_node_access_records().
317
 * @param Drupal\node\Node $node
318 319 320
 *   The node for which the grants were acquired.
 *
 * The preferred use of this hook is in a module that bridges multiple node
321 322
 * access modules with a configurable behavior, as shown in the example with the
 * 'is_preview' field.
323
 *
324 325 326
 * @see hook_node_access_records()
 * @see hook_node_grants()
 * @see hook_node_grants_alter()
327 328
 * @ingroup node_access
 */
329
function hook_node_access_records_alter(&$grants, Drupal\node\Node $node) {
330 331 332 333 334 335 336 337 338
  // Our module allows editors to mark specific articles with the 'is_preview'
  // field. If the node being saved has a TRUE value for that field, then only
  // our grants are retained, and other grants are removed. Doing so ensures
  // that our rules are enforced no matter what priority other grants are given.
  if ($node->is_preview) {
    // Our module grants are set in $grants['example'].
    $temp = $grants['example'];
    // Now remove all module grants but our own.
    $grants = array('example' => $temp);
339 340 341 342 343 344 345
  }
}

/**
 * Alter user access rules when trying to view, edit or delete a node.
 *
 * Node access modules establish rules for user access to content.
346 347 348 349 350
 * hook_node_grants() defines permissions for a user to view, edit or delete
 * nodes by building a $grants array that indicates the permissions assigned to
 * the user by each node access module. This hook is called to allow modules to
 * modify the $grants array by reference, so the interaction of multiple node
 * access modules can be altered or advanced business logic can be applied.
351 352 353 354
 *
 * The resulting grants are then checked against the records stored in the
 * {node_access} table to determine if the operation may be completed.
 *
355 356
 * A module may deny all access to a user by setting $grants to an empty array.
 *
357 358
 * Developers may use this hook to either add additional grants to a user or to
 * remove existing grants. These rules are typically based on either the
359 360
 * permissions assigned to a user role, or specific attributes of a user
 * account.
361
 *
362
 * @param $grants
363 364 365 366 367 368
 *   The $grants array returned by hook_node_grants().
 * @param $account
 *   The user account requesting access to content.
 * @param $op
 *   The operation being performed, 'view', 'update' or 'delete'.
 *
369 370 371
 * @see hook_node_grants()
 * @see hook_node_access_records()
 * @see hook_node_access_records_alter()
372 373 374 375 376 377 378 379 380 381
 * @ingroup node_access
 */
function hook_node_grants_alter(&$grants, $account, $op) {
  // Our sample module never allows certain roles to edit or delete
  // content. Since some other node access modules might allow this
  // permission, we expressly remove it by returning an empty $grants
  // array for roles specified in our variable setting.

  // Get our list of banned roles.
  $restricted = variable_get('example_restricted_roles', array());
382

383 384 385
  if ($op != 'view' && !empty($restricted)) {
    // Now check the roles for this account against the restrictions.
    foreach ($restricted as $role_id) {
386
      if (isset($account->roles[$role_id])) {
387 388 389 390 391 392
        $grants = array();
      }
    }
  }
}

393 394 395
/**
 * Add mass node operations.
 *
396 397 398 399 400
 * This hook enables modules to inject custom operations into the mass
 * operations dropdown found at admin/content, by associating a callback
 * function with the operation, which is called when the form is submitted. The
 * callback function receives one initial argument, which is an array of the
 * checked nodes.
401 402 403 404
 *
 * @return
 *   An array of operations. Each operation is an associative array that may
 *   contain the following key-value pairs:
405
 *   - label: (required) The label for the operation, displayed in the dropdown
406
 *     menu.
407 408
 *   - callback: (required) The function to call for the operation.
 *   - callback arguments: (optional) An array of additional arguments to pass
409
 *     to the callback function.
410 411 412
 */
function hook_node_operations() {
  $operations = array(
413 414 415 416
    'publish' => array(
      'label' => t('Publish selected content'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('status' => NODE_PUBLISHED)),
417
    ),
418 419 420 421
    'unpublish' => array(
      'label' => t('Unpublish selected content'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('status' => NODE_NOT_PUBLISHED)),
422
    ),
423 424 425 426
    'promote' => array(
      'label' => t('Promote selected content to front page'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('status' => NODE_PUBLISHED, 'promote' => NODE_PROMOTED)),
427 428
    ),
    'demote' => array(
429 430 431
      'label' => t('Demote selected content from front page'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('promote' => NODE_NOT_PROMOTED)),
432
    ),
433 434 435 436 437 438 439 440 441
    'sticky' => array(
      'label' => t('Make selected content sticky'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('status' => NODE_PUBLISHED, 'sticky' => NODE_STICKY)),
    ),
    'unsticky' => array(
      'label' => t('Make selected content not sticky'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('sticky' => NODE_NOT_STICKY)),
442 443
    ),
    'delete' => array(
444 445
      'label' => t('Delete selected content'),
      'callback' => NULL,
446 447 448 449 450
    ),
  );
  return $operations;
}

451
/**
452
 * Act before node deletion.
453
 *
454
 * This hook is invoked from node_delete_multiple() after the type-specific
455
 * hook_delete() has been invoked, but before hook_entity_predelete() and
456 457
 * field_attach_delete() are called, and before the node is removed from the
 * node table in the database.
458
 *
459
 * @param Drupal\node\Node $node
460
 *   The node that is about to be deleted.
461
 *
462 463
 * @see hook_node_predelete()
 * @see node_delete_multiple()
464
 * @ingroup node_api_hooks
465
 */
466
function hook_node_predelete(Drupal\node\Node $node) {
467 468 469
  db_delete('mytable')
    ->condition('nid', $node->nid)
    ->execute();
470 471
}

472 473 474 475 476 477
/**
 * Respond to node deletion.
 *
 * This hook is invoked from node_delete_multiple() after field_attach_delete()
 * has been called and after the node has been removed from the database.
 *
478
 * @param Drupal\node\Node $node
479 480 481 482 483 484
 *   The node that has been deleted.
 *
 * @see hook_node_predelete()
 * @see node_delete_multiple()
 * @ingroup node_api_hooks
 */
485
function hook_node_delete(Drupal\node\Node $node) {
486
  drupal_set_message(t('Node: @title has been deleted', array('@title' => $node->label())));
487 488
}

489
/**
490
 * Respond to deletion of a node revision.
491
 *
492 493 494
 * This hook is invoked from node_revision_delete() after the revision has been
 * removed from the node_revision table, and before
 * field_attach_delete_revision() is called.
495
 *
496
 * @param Drupal\node\Node $node
497
 *   The node revision (node object) that is being deleted.
498 499
 *
 * @ingroup node_api_hooks
500
 */
501
function hook_node_revision_delete(Drupal\node\Node $node) {
502 503 504
  db_delete('mytable')
    ->condition('vid', $node->vid)
    ->execute();
505 506 507
}

/**
508
 * Respond to creation of a new node.
509
 *
510 511 512 513 514 515 516 517 518 519 520 521
 * This hook is invoked from node_save() after the database query that will
 * insert the node into the node table is scheduled for execution, after the
 * type-specific hook_insert() is invoked, and after field_attach_insert() is
 * called.
 *
 * Note that when this hook is invoked, the changes have not yet been written to
 * the database, because a database transaction is still in progress. The
 * transaction is not finalized until the save operation is entirely completed
 * and node_save() goes out of scope. You should not rely on data in the
 * database at this time as it is not updated yet. You should also note that any
 * write/update database queries executed from this hook are also not committed
 * immediately. Check node_save() and db_transaction() for more info.
522
 *
523
 * @param Drupal\node\Node $node
524
 *   The node that is being created.
525 526
 *
 * @ingroup node_api_hooks
527
 */
528
function hook_node_insert(Drupal\node\Node $node) {
529 530 531 532 533 534
  db_insert('mytable')
    ->fields(array(
      'nid' => $node->nid,
      'extra' => $node->extra,
    ))
    ->execute();
535 536
}

537
/**
538 539
 * Act on arbitrary nodes being loaded from the database.
 *
540 541 542 543
 * This hook should be used to add information that is not in the node or node
 * revisions table, not to replace information that is in these tables (which
 * could interfere with the entity cache). For performance reasons, information
 * for all available nodes should be loaded in a single query where possible.
544 545
 *
 * This hook is invoked during node loading, which is handled by entity_load(),
546
 * via classes NodeController and Drupal\Core\Entity\DatabaseStorageController.
547 548
 * After the node information is read from the database or the entity cache,
 * hook_load() is invoked on the node's content type module, then
549
 * field_attach_load_revision() or field_attach_load() is called, then
550 551
 * hook_entity_load() is invoked on all implementing modules, and finally
 * hook_node_load() is invoked on all implementing modules.
552
 *
553
 * @param $nodes
554
 *   An array of the nodes being loaded, keyed by nid.
555
 * @param $types
556 557 558 559
 *   An array containing the node types present in $nodes. Allows for an early
 *   return for modules that only support certain node types. However, if your
 *   module defines a content type, you can use hook_load() to respond to
 *   loading of just that content type.
560 561
 *
 * For a detailed usage example, see nodeapi_example.module.
562 563
 *
 * @ingroup node_api_hooks
564
 */
565
function hook_node_load($nodes, $types) {
566 567 568 569 570 571 572 573
  // Decide whether any of $types are relevant to our purposes.
  if (count(array_intersect($types_we_want_to_process, $types))) {
    // Gather our extra data for each of these nodes.
    $result = db_query('SELECT nid, foo FROM {mytable} WHERE nid IN(:nids)', array(':nids' => array_keys($nodes)));
    // Add our extra data to the node objects.
    foreach ($result as $record) {
      $nodes[$record->nid]->foo = $record->foo;
    }
574 575 576
  }
}

577
/**
578
 * Controls access to a node.
579 580 581 582
 *
 * Modules may implement this hook if they want to have a say in whether or not
 * a given user has access to perform a given operation on a node.
 *
583 584
 * The administrative account (user ID #1) always passes any access check, so
 * this hook is not called in that case. Users with the "bypass node access"
585 586 587
 * permission may always view and edit content through the administrative
 * interface.
 *
588 589 590 591
 * Note that not all modules will want to influence access on all node types. If
 * your module does not want to actively grant or block access, return
 * NODE_ACCESS_IGNORE or simply return nothing. Blindly returning FALSE will
 * break other node access modules.
592
 *
593 594 595 596
 * Also note that this function isn't called for node listings (e.g., RSS feeds,
 * the default home page at path 'node', a recent content block, etc.) See
 * @link node_access Node access rights @endlink for a full explanation.
 *
597 598
 * @param Drupal\node\Node|string $node
 *   Either a node entity or the machine name of the content type on which to
599
 *   perform the access check.
600
 * @param string $op
601 602 603 604 605
 *   The operation to be performed. Possible values:
 *   - "create"
 *   - "delete"
 *   - "update"
 *   - "view"
606
 * @param object $account
607
 *   The user object to perform the access check operation on.
608 609
 * @param object $langcode
 *   The language code to perform the access check operation on.
610
 *
611
 * @return string
612 613 614
 *   - NODE_ACCESS_ALLOW: if the operation is to be allowed.
 *   - NODE_ACCESS_DENY: if the operation is to be denied.
 *   - NODE_ACCESS_IGNORE: to not affect this operation at all.
615 616
 *
 * @ingroup node_access
617
 */
618
function hook_node_access($node, $op, $account, $langcode) {
619
  $type = is_string($node) ? $node : $node->type;
620

621 622
  $configured_types = node_permissions_get_configured_types();
  if (isset($configured_types[$type])) {
623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644
    if ($op == 'create' && user_access('create ' . $type . ' content', $account)) {
      return NODE_ACCESS_ALLOW;
    }

    if ($op == 'update') {
      if (user_access('edit any ' . $type . ' content', $account) || (user_access('edit own ' . $type . ' content', $account) && ($account->uid == $node->uid))) {
        return NODE_ACCESS_ALLOW;
      }
    }

    if ($op == 'delete') {
      if (user_access('delete any ' . $type . ' content', $account) || (user_access('delete own ' . $type . ' content', $account) && ($account->uid == $node->uid))) {
        return NODE_ACCESS_ALLOW;
      }
    }
  }

  // Returning nothing from this function would have the same effect.
  return NODE_ACCESS_IGNORE;
}


645
/**
646 647
 * Act on a node object about to be shown on the add/edit form.
 *
648 649
 * This hook is invoked from NodeFormController::prepareEntity() after the
 * type-specific hook_prepare() is invoked.
650
 *
651
 * @param Drupal\node\Node $node
652
 *   The node that is about to be shown on the add/edit form.
653 654
 *
 * @ingroup node_api_hooks
655
 */
656
function hook_node_prepare(Drupal\node\Node $node) {
657
  if (!isset($node->comment)) {
658
    $node->comment = variable_get("comment_$node->type", COMMENT_NODE_OPEN);
659 660 661 662
  }
}

/**
663
 * Act on a node being displayed as a search result.
664
 *
665 666
 * This hook is invoked from node_search_execute(), after node_load() and
 * node_view() have been called.
667
 *
668
 * @param Drupal\node\Node $node
669
 *   The node being displayed in a search result.
670 671
 * @param $langcode
 *   Language code of result being displayed.
672
 *
673 674
 * @return array
 *   Extra information to be displayed with search result. This information
675 676 677
 *   should be presented as an associative array. It will be concatenated with
 *   the post information (last updated, author) in the default search result
 *   theming.
678 679 680
 *
 * @see template_preprocess_search_result()
 * @see search-result.tpl.php
681 682
 *
 * @ingroup node_api_hooks
683
 */
684
function hook_node_search_result(Drupal\node\Node $node, $langcode) {
685
  $comments = db_query('SELECT comment_count FROM {node_comment_statistics} WHERE nid = :nid', array('nid' => $node->nid))->fetchField();
686
  return array('comment' => format_plural($comments, '1 comment', '@count comments'));
687 688 689
}

/**
690
 * Act on a node being inserted or updated.
691
 *
692 693
 * This hook is invoked from node_save() before the node is saved to the
 * database.
694
 *
695
 * @param Drupal\node\Node $node
696
 *   The node that is being inserted or updated.
697 698
 *
 * @ingroup node_api_hooks
699
 */
700
function hook_node_presave(Drupal\node\Node $node) {
701 702 703 704 705 706 707 708 709
  if ($node->nid && $node->moderate) {
    // Reset votes when node is updated:
    $node->score = 0;
    $node->users = '';
    $node->votes = 0;
  }
}

/**
710 711
 * Respond to updates to a node.
 *
712 713 714 715 716 717 718 719 720 721 722 723
 * This hook is invoked from node_save() after the database query that will
 * update node in the node table is scheduled for execution, after the
 * type-specific hook_update() is invoked, and after field_attach_update() is
 * called.
 *
 * Note that when this hook is invoked, the changes have not yet been written to
 * the database, because a database transaction is still in progress. The
 * transaction is not finalized until the save operation is entirely completed
 * and node_save() goes out of scope. You should not rely on data in the
 * database at this time as it is not updated yet. You should also note that any
 * write/update database queries executed from this hook are also not committed
 * immediately. Check node_save() and db_transaction() for more info.
724
 *
725
 * @param Drupal\node\Node $node
726
 *   The node that is being updated.
727 728
 *
 * @ingroup node_api_hooks
729
 */
730
function hook_node_update(Drupal\node\Node $node) {
731 732 733 734
  db_update('mytable')
    ->fields(array('extra' => $node->extra))
    ->condition('nid', $node->nid)
    ->execute();
735 736 737
}

/**
738
 * Act on a node being indexed for searching.
739
 *
740 741
 * This hook is invoked during search indexing, after node_load(), and after the
 * result of node_view() is added as $node->rendered to the node object.
742
 *
743
 * @param Drupal\node\Node $node
744
 *   The node being indexed.
745 746
 * @param $langcode
 *   Language code of the variant of the node being indexed.
747
 *
748 749
 * @return string
 *   Additional node information to be indexed.
750 751
 *
 * @ingroup node_api_hooks
752
 */
753
function hook_node_update_index(Drupal\node\Node $node, $langcode) {
754 755 756
  $text = '';
  $comments = db_query('SELECT subject, comment, format FROM {comment} WHERE nid = :nid AND status = :status', array(':nid' => $node->nid, ':status' => COMMENT_PUBLISHED));
  foreach ($comments as $comment) {
757
    $text .= '<h2>' . check_plain($comment->subject) . '</h2>' . check_markup($comment->comment, $comment->format, '', TRUE);
758 759 760 761 762
  }
  return $text;
}

/**
763 764
 * Perform node validation before a node is created or updated.
 *
765
 * This hook is invoked from NodeFormController::validate(), after a user has
766 767 768
 * finished editing the node and is previewing or submitting it. It is invoked
 * at the end of all the standard validation steps, and after the type-specific
 * hook_validate() is invoked.
769
 *
770 771 772 773
 * To indicate a validation error, use form_set_error().
 *
 * Note: Changes made to the $node object within your hook implementation will
 * have no effect.  The preferred method to change a node's content is to use
774 775
 * hook_node_presave() instead. If it is really necessary to change the node at
 * the validate stage, you can use form_set_value().
776
 *
777
 * @param Drupal\node\Node $node
778
 *   The node being validated.
779
 * @param $form
780
 *   The form being used to edit the node.
781 782
 * @param $form_state
 *   The form state array.
783 784
 *
 * @ingroup node_api_hooks
785
 */
786
function hook_node_validate(Drupal\node\Node $node, $form, &$form_state) {
787 788 789 790 791 792 793
  if (isset($node->end) && isset($node->start)) {
    if ($node->start > $node->end) {
      form_set_error('time', t('An event may not end before it starts.'));
    }
  }
}

794 795 796 797 798 799 800 801 802 803 804
/**
 * Act on a node after validated form values have been copied to it.
 *
 * This hook is invoked when a node form is submitted with either the "Save" or
 * "Preview" button, after form values have been copied to the form state's node
 * object, but before the node is saved or previewed. It is a chance for modules
 * to adjust the node's properties from what they are simply after a copy from
 * $form_state['values']. This hook is intended for adjusting non-field-related
 * properties. See hook_field_attach_submit() for customizing field-related
 * properties.
 *
805 806
 * @param Drupal\node\Node $node
 *   The node entity being updated in response to a form submission.
807 808 809 810 811 812 813
 * @param $form
 *   The form being used to edit the node.
 * @param $form_state
 *   The form state array.
 *
 * @ingroup node_api_hooks
 */
814
function hook_node_submit(Drupal\node\Node $node, $form, &$form_state) {
815 816 817 818 819 820 821
  // Decompose the selected menu parent option into 'menu_name' and 'plid', if
  // the form used the default parent selection widget.
  if (!empty($form_state['values']['menu']['parent'])) {
    list($node->menu['menu_name'], $node->menu['plid']) = explode(':', $form_state['values']['menu']['parent']);
  }
}

822
/**
823
 * Act on a node that is being assembled before rendering.
824
 *
825 826 827 828
 * The module may add elements to $node->content prior to rendering. This hook
 * will be called after hook_view(). The structure of $node->content is a
 * renderable array as expected by drupal_render().
 *
829
 * When $view_mode is 'rss', modules can also add extra RSS elements and
830 831
 * namespaces to $node->rss_elements and $node->rss_namespaces respectively for
 * the RSS item generated for this node.
832
 * For details on how this is used, see node_feed().
833
 *
834
 * @param \Drupal\node\Plugin\Core\Entity\Node $node
835
 *   The node that is being assembled for rendering.
836 837 838 839
 * @param \Drupal\entity\Plugin\Core\Entity\EntityDisplay $display
 *   The entity_display object holding the display options configured for the
 *   node components.
 * @param string $view_mode
840
 *   The $view_mode parameter from node_view().
841
 * @param string $langcode
842
 *   The language code used for rendering.
843
 *
844 845
 * @see forum_node_view()
 * @see comment_node_view()
846 847
 * @see hook_entity_view()
 *
848
 * @ingroup node_api_hooks
849
 */
850 851 852 853 854 855 856 857 858 859
function hook_node_view(\Drupal\node\Plugin\Core\Entity\Node $node, \Drupal\entity\Plugin\Core\Entity\EntityDisplay $display, $view_mode, $langcode) {
  // Only do the extra work if the component is configured to be displayed.
  // This assumes a 'mymodule_addition' extra field has been defined for the
  // node type in hook_field_extra_fields().
  if ($display->getComponent('mymodule_addition')) {
    $node->content['mymodule_addition'] = array(
      '#markup' => mymodule_addition($node),
      '#theme' => 'mymodule_my_additional_field',
    );
  }
860 861
}

862
/**
863
 * Alter the results of node_view().
864
 *
865 866 867
 * This hook is called after the content has been assembled in a structured
 * array and may be used for doing processing which requires that the complete
 * node content structure has been built.
868 869
 *
 * If the module wishes to act on the rendered HTML of the node rather than the
870
 * structured content array, it may use this hook to add a #post_render
871
 * callback.  Alternatively, it could also implement hook_preprocess_HOOK() for
872 873
 * node.tpl.php. See drupal_render() and theme() documentation respectively for
 * details.
874
 *
875 876
 * @param $build
 *   A renderable array representing the node content.
877
 * @param \Drupal\node\Plugin\Core\Entity\Node $node
878
 *   The node being rendered.
879 880 881
 * @param \Drupal\entity\Plugin\Core\Entity\EntityDisplay $display
 *   The entity_display object holding the display options configured for the
 *   node components.
882
 *
883
 * @see node_view()
884
 * @see hook_entity_view_alter()
885 886
 *
 * @ingroup node_api_hooks
887
 */
888
function hook_node_view_alter(&$build, \Drupal\node\Plugin\Core\Entity\Node $node, \Drupal\entity\Plugin\Core\Entity\EntityDisplay $display) {
889
  if ($build['#view_mode'] == 'full' && isset($build['an_additional_field'])) {
890
    // Change its weight.
891
    $build['an_additional_field']['#weight'] = -10;
892
  }
893 894

  // Add a #post_render callback to act on the rendered HTML of the node.
895
  $build['#post_render'][] = 'my_module_node_post_render';
896 897
}

898
/**
899
 * Define module-provided node types.
900
 *
901
 * This hook allows a module to define one or more of its own node types. For
902
 * example, the forum module uses it to define a forum node-type named "Forum
903 904
 * topic." The name and attributes of each desired node type are specified in an
 * array returned by the hook.
905
 *
906 907 908 909 910 911
 * Only module-provided node types should be defined through this hook. User-
 * provided (or 'custom') node types should be defined only in the 'node_type'
 * database table, and should be maintained by using the node_type_save() and
 * node_type_delete() functions.
 *
 * @return
912
 *   An array of information defining the module's node types. The array
913 914 915
 *   contains a sub-array for each node type, with the the machine name of a
 *   content type as the key. Each sub-array has up to 10 attributes.
 *   Possible attributes:
916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931
 *   - name: (required) The human-readable name of the node type.
 *   - base: (required) The base string used to construct callbacks
 *     corresponding to this node type (for example, if base is defined as
 *     example_foo, then example_foo_insert will be called when inserting a node
 *     of that type). This string is usually the name of the module, but not
 *     always.
 *   - description: (required) A brief description of the node type.
 *   - help: (optional) Help information shown to the user when creating a node
 *     of this type.
 *   - has_title: (optional) A Boolean indicating whether or not this node type
 *     has a title field.
 *   - title_label: (optional) The label for the title field of this content
 *     type.
 *   - locked: (optional) A Boolean indicating whether the administrator can
 *     change the machine name of this type. FALSE = changeable (not locked),
 *     TRUE = unchangeable (locked).
932
 *
933 934 935
 * The machine name of a node type should contain only letters, numbers, and
 * underscores. Underscores will be converted into hyphens for the purpose of
 * constructing URLs.
936 937 938 939 940
 *
 * All attributes of a node type that are defined through this hook (except for
 * 'locked') can be edited by a site administrator. This includes the
 * machine-readable name of a node type, if 'locked' is set to FALSE.
 *
941
 * @ingroup node_api_hooks
942 943 944
 */
function hook_node_info() {
  return array(
945 946 947 948 949
    'forum' => array(
      'name' => t('Forum topic'),
      'base' => 'forum',
      'description' => t('A <em>forum topic</em> starts a new discussion thread within a forum.'),
      'title_label' => t('Subject'),
950 951 952 953
    )
  );
}

954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979
/**
 * Provide additional methods of scoring for core search results for nodes.
 *
 * A node's search score is used to rank it among other nodes matched by the
 * search, with the highest-ranked nodes appearing first in the search listing.
 *
 * For example, a module allowing users to vote on content could expose an
 * option to allow search results' rankings to be influenced by the average
 * voting score of a node.
 *
 * All scoring mechanisms are provided as options to site administrators, and
 * may be tweaked based on individual sites or disabled altogether if they do
 * not make sense. Individual scoring mechanisms, if enabled, are assigned a
 * weight from 1 to 10. The weight represents the factor of magnification of
 * the ranking mechanism, with higher-weighted ranking mechanisms having more
 * influence. In order for the weight system to work, each scoring mechanism
 * must return a value between 0 and 1 for every node. That value is then
 * multiplied by the administrator-assigned weight for the ranking mechanism,
 * and then the weighted scores from all ranking mechanisms are added, which
 * brings about the same result as a weighted average.
 *
 * @return
 *   An associative array of ranking data. The keys should be strings,
 *   corresponding to the internal name of the ranking mechanism, such as
 *   'recent', or 'comments'. The values should be arrays themselves, with the
 *   following keys available:
980 981 982 983 984 985 986 987 988 989
 *   - title: (required) The human readable name of the ranking mechanism.
 *   - join: (optional) The part of a query string to join to any additional
 *     necessary table. This is not necessary if the table required is already
 *     joined to by the base query, such as for the {node} table. Other tables
 *     should use the full table name as an alias to avoid naming collisions.
 *   - score: (required) The part of a query string to calculate the score for
 *     the ranking mechanism based on values in the database. This does not need
 *     to be wrapped in parentheses, as it will be done automatically; it also
 *     does not need to take the weighted system into account, as it will be
 *     done automatically. It does, however, need to calculate a decimal between
990
 *     0 and 1; be careful not to cast the entire score to an integer by
991 992 993
 *     inadvertently introducing a variable argument.
 *   - arguments: (optional) If any arguments are required for the score, they
 *     can be specified in an array here.
994 995
 *
 * @ingroup node_api_hooks
996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016
 */
function hook_ranking() {
  // If voting is disabled, we can avoid returning the array, no hard feelings.
  if (variable_get('vote_node_enabled', TRUE)) {
    return array(
      'vote_average' => array(
        'title' => t('Average vote'),
        // Note that we use i.sid, the search index's search item id, rather than
        // n.nid.
        'join' => 'LEFT JOIN {vote_node_data} vote_node_data ON vote_node_data.nid = i.sid',
        // The highest possible score should be 1, and the lowest possible score,
        // always 0, should be 0.
        'score' => 'vote_node_data.average / CAST(%f AS DECIMAL)',
        // Pass in the highest possible voting score as a decimal argument.
        'arguments' => array(variable_get('vote_score_max', 5)),
      ),
    );
  }
}


1017
/**
1018
 * Respond to node type creation.
1019
 *
1020 1021
 * This hook is invoked from node_type_save() after the node type is added to
 * the database.
1022 1023
 *
 * @param $info
1024
 *   The node type object that is being created.
1025 1026
 */
function hook_node_type_insert($info) {
1027
  drupal_set_message(t('You have just created a content type with a machine name %type.', array('%type' => $info->type)));
1028 1029
}

1030
/**
1031
 * Respond to node type updates.
1032
 *
1033 1034
 * This hook is invoked from node_type_save() after the node type is updated in
 * the database.
1035 1036
 *
 * @param $info
1037
 *   The node type object that is being updated.
1038
 */
1039 1040 1041 1042 1043
function hook_node_type_update($info) {
  if (!empty($info->old_type) && $info->old_type != $info->type) {
    $setting = variable_get('comment_' . $info->old_type, COMMENT_NODE_OPEN);
    variable_del('comment_' . $info->old_type);
    variable_set('comment_' . $info->type, $setting);
1044 1045 1046
  }
}

1047
/**
1048
 * Respond to node type deletion.
1049
 *
1050 1051
 * This hook is invoked from node_type_delete() after the node type is removed
 * from the database.
1052 1053
 *
 * @param $info
1054
 *   The node type object that is being deleted.
1055 1056 1057 1058 1059
 */
function hook_node_type_delete($info) {
  variable_del('comment_' . $info->type);
}

1060 1061 1062
/**
 * Respond to node deletion.
 *
1063 1064
 * This hook is invoked only on the module that defines the node's content type
 * (use hook_node_delete() to respond to all node deletions).
1065
 *
1066 1067 1068
 * This hook is invoked from node_delete_multiple() after the node has been
 * removed from the node table in the database, before hook_node_delete() is
 * invoked, and before field_attach_delete() is called.
1069
 *
1070
 * @param Drupal\node\Node $node
1071
 *   The node that is being deleted.
1072 1073
 *
 * @ingroup node_api_hooks
1074
 */
1075
function hook_delete(Drupal\node\Node $node) {
1076
  db_delete('mytable')
1077
    ->condition('nid', $node->nid)
1078
    ->execute();
1079 1080 1081
}

/**
1082
 * Act on a node object about to be shown on the add/edit form.
1083
 *
1084 1085
 * This hook is invoked only on the module that defines the node's content type
 * (use hook_node_prepare() to act on all node preparations).
1086
 *
1087 1088
 * This hook is invoked from NodeFormController::prepareEntity() before the
 * general hook_node_prepare() is invoked.
1089
 *
1090
 * @param Drupal\node\Node $node
1091
 *   The node that is about to be shown on the add/edit form.
1092 1093
 *
 * @ingroup node_api_hooks
1094
 */
1095
function hook_prepare(Drupal\node\Node $node) {
1096 1097 1098
  if ($file = file_check_upload($field_name)) {
    $file = file_save_upload($field_name, _image_filename($file->filename, NULL, TRUE));
    if ($file) {
1099
      if (!image_get_info($file->uri)) {
1100 1101 1102 1103 1104 1105 1106
        form_set_error($field_name, t('Uploaded file is not a valid image'));
        return;
      }
    }
    else {
      return;
    }
1107
    $node->images['_original'] = $file->uri;
1108
    _image_build_derivatives($node, TRUE);
1109 1110 1111 1112 1113 1114 1115 1116
    $node->new_file = TRUE;
  }
}

/**
 * Display a node editing form.
 *
 * This hook, implemented by node modules, is called to retrieve the form
1117 1118 1119 1120 1121 1122 1123 1124 1125
 * that is displayed to create or edit a node. This form is displayed at path
 * node/add/[node type] or node/[node ID]/edit.
 *
 * The submit and preview buttons, administrative and display controls, and
 * sections added by other modules (such as path settings, menu settings,
 * comment settings, and fields managed by the Field UI module) are
 * displayed automatically by the node module. This hook just needs to
 * return the node title and form editing fields specific to the node type.
 *
1126
 * @param Drupal\node\Node $node
1127 1128
 *   The node being added or edited.
 * @param $form_state
1129 1130
 *   The form state array.
 *
1131
 * @return
1132 1133
 *   An array containing the title and any custom form elements to be displayed
 *   in the node editing form.
1134 1135
 *
 * @ingroup node_api_hooks
1136
 */
1137
function hook_form(Drupal\node\Node $node, &$form_state) {
1138
  $type = node_type_load($node->type);
1139

1140 1141 1142 1143 1144 1145 1146
  $form['title'] = array(
    '#type' => 'textfield',
    '#title' => check_plain($type->title_label),
    '#default_value' => !empty($node->title) ? $node->title : '',
    '#required' => TRUE, '#weight' => -5
  );

1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161
  $form['field1'] = array(
    '#type' => 'textfield',
    '#title' => t('Custom field'),
    '#default_value' => $node->field1,
    '#maxlength' => 127,
  );
  $form['selectbox'] = array(
    '#type' => 'select',
    '#title' => t('Select box'),
    '#default_value' => $node->selectbox,
    '#options' => array(
      1 => 'Option A',
      2 => 'Option B',
      3 => 'Option C',
    ),
1162
    '#description' => t('Choose an option.'),
1163 1164 1165 1166 1167 1168
  );

  return $form;
}

/**
1169
 * Respond to creation of a new node.
1170
 *
1171 1172
 * This hook is invoked only on the module that defines the node's content type
 * (use hook_node_insert() to act on all node insertions).
1173
 *
webchick's avatar