node.api.php 48.6 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 16 17 18 19 20 21 22 23
 *
 * Each content type is maintained by a primary module, which is either
 * node.module (for content types created in the user interface) or the
 * module that implements hook_node_info() to define the content type.
 *
 * 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
 * - 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
30
 *   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 62
 * - Loading a node (calling node_load(), node_load_multiple(), entity_load()
 *   or entity_load_multiple() with $entity_type of 'node'):
63 64 65 66 67 68 69 70 71 72
 *   - 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
 *   node_view() is a loaded node, so the Loading steps above are already
 *   done):
 *   - hook_view() (node-type-specific)
 *   - field_attach_prepare_view()
73
 *   - hook_entity_prepare_view() (all)
74 75
 *   - field_attach_view()
 *   - hook_node_view() (all)
76 77 78
 *   - hook_entity_view() (all)
 *   - hook_node_view_alter() (all)
 *   - hook_entity_view_alter() (all)
79 80 81 82
 * - 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()
83
 *   - hook_entity_prepare_view() (all)
84 85 86
 *   - hook_view() (node-type-specific)
 *   - field_attach_view()
 *   - hook_node_view() (all)
87
 *   - hook_entity_view() (all)
88
 *   - hook_node_view_alter() (all)
89
 *   - hook_entity_view_alter() (all)
90 91 92
 * - Deleting a node (calling node_delete() or node_delete_multiple()):
 *   - Node is loaded (see Loading section above)
 *   - hook_delete() (node-type-specific)
93 94
 *   - hook_node_predelete() (all)
 *   - hook_entity_predelete() (all)
95
 *   - field_attach_delete()
96
 *   - Node and revision information are deleted from database
97 98
 *   - hook_node_delete() (all)
 *   - hook_entity_delete() (all)
99 100 101 102 103 104 105 106 107
 * - 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()
 * - Preparing a node for editing (calling node_form() - note that if it's
 *   an existing node, it will already be loaded; see the Loading section
 *   above):
 *   - hook_prepare() (node-type-specific)
108
 *   - hook_node_prepare() (all)
109 110 111 112 113 114 115 116 117 118 119 120
 *   - 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)
121
 *   - comment_node_update_index() is called.
122 123 124 125 126 127 128 129
 *   - 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)
 * @}
 */

130 131 132 133 134 135 136 137
/**
 * @addtogroup hooks
 * @{
 */

/**
 * Inform the node access system what permissions the user has.
 *
138 139 140 141
 * 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.
142
 *
143 144 145 146 147
 * The realms and grant IDs can be arbitrarily defined by your node access
 * 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.
148 149
 *
 * A node access module may implement as many realms as necessary to
150 151 152 153
 * 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.
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 182 183
 * 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.
 *
184
 * @param $account
185 186 187
 *   The user object whose grants are requested.
 * @param $op
 *   The node operation to be performed, such as "view", "update", or "delete".
188
 *
189
 * @return
190 191
 *   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.
192 193 194
 *
 * For a detailed example, see node_access_example.module.
 *
195 196
 * @see node_access_view_all_nodes()
 * @see node_access_rebuild()
197 198 199 200 201 202
 * @ingroup node_access
 */
function hook_node_grants($account, $op) {
  if (user_access('access private content', $account)) {
    $grants['example'] = array(1);
  }
203
  $grants['example_owner'] = array($account->uid);
204 205 206 207 208 209
  return $grants;
}

/**
 * Set permissions for a node to be written to the database.
 *
210 211 212
 * 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
213 214
 * node.
 *
215 216 217 218 219 220
 * 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.
 *
221 222 223
 * Note that the grant values in the return value from your hook must be
 * integers and not boolean TRUE and FALSE.
 *
224 225 226 227
 * 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().
228
 * - 'grant_view': If set to 1 a user that has been identified as a member
229 230 231
 *   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.
232
 * - 'grant_update': If set to 1 a user that has been identified as a member
233
 *   of this gid within this realm can edit this node.
234
 * - 'grant_delete': If set to 1 a user that has been identified as a member
235
 *   of this gid within this realm can delete this node.
236
 *
237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257
 *
 * 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.
 *
258
 * @param Drupal\node\Node $node
259 260 261 262 263
 *   The node that has just been saved.
 *
 * @return
 *   An array of grants as defined above.
 *
264
 * @see _node_access_write_grants()
265 266
 * @ingroup node_access
 */
267
function hook_node_access_records(Drupal\node\Node $node) {
268
  // We only care about the node if it has been marked private. If not, it is
269 270 271
  // treated just like any other node and we completely ignore it.
  if ($node->private) {
    $grants = array();
272 273 274 275 276 277 278 279 280 281 282
    // 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,
      );
    }
283
    // For the example_author array, the GID is equivalent to a UID, which
284 285 286
    // 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.
287 288 289
    $grants[] = array(
      'realm' => 'example_author',
      'gid' => $node->uid,
290 291 292
      'grant_view' => 1,
      'grant_update' => 1,
      'grant_delete' => 1,
293
    );
294

295 296 297 298
    return $grants;
  }
}

299 300 301 302 303 304 305 306 307 308 309 310 311 312 313
/**
 * 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.
 *
314 315
 * A module may deny all access to a node by setting $grants to an empty array.
 *
316
 * @param $grants
317
 *   The $grants array returned by hook_node_access_records().
318
 * @param Drupal\node\Node $node
319 320 321
 *   The node for which the grants were acquired.
 *
 * The preferred use of this hook is in a module that bridges multiple node
322 323
 * access modules with a configurable behavior, as shown in the example with the
 * 'is_preview' field.
324
 *
325 326 327
 * @see hook_node_access_records()
 * @see hook_node_grants()
 * @see hook_node_grants_alter()
328 329
 * @ingroup node_access
 */
330
function hook_node_access_records_alter(&$grants, Drupal\node\Node $node) {
331 332 333 334 335 336 337 338 339
  // 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);
340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356
  }
}

/**
 * Alter user access rules when trying to view, edit or delete a node.
 *
 * Node access modules establish rules for user access to content.
 * 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.
 *
 * The resulting grants are then checked against the records stored in the
 * {node_access} table to determine if the operation may be completed.
 *
357 358
 * A module may deny all access to a user by setting $grants to an empty array.
 *
359 360 361 362
 * 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
 * permissions assigned to a user role, or specific attributes of a user
 * account.
363
 *
364
 * @param $grants
365 366 367 368 369 370
 *   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'.
 *
371 372 373
 * @see hook_node_grants()
 * @see hook_node_access_records()
 * @see hook_node_access_records_alter()
374 375 376 377 378 379 380 381 382 383
 * @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());
384

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

395 396 397
/**
 * Add mass node operations.
 *
398 399 400 401 402
 * 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.
403 404 405 406
 *
 * @return
 *   An array of operations. Each operation is an associative array that may
 *   contain the following key-value pairs:
407 408 409 410 411
 *   - 'label': Required. The label for the operation, displayed in the dropdown
 *     menu.
 *   - 'callback': Required. The function to call for the operation.
 *   - 'callback arguments': Optional. An array of additional arguments to pass
 *     to the callback function.
412 413 414
 */
function hook_node_operations() {
  $operations = array(
415 416 417 418
    'publish' => array(
      'label' => t('Publish selected content'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('status' => NODE_PUBLISHED)),
419
    ),
420 421 422 423
    'unpublish' => array(
      'label' => t('Unpublish selected content'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('status' => NODE_NOT_PUBLISHED)),
424
    ),
425 426 427 428
    '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)),
429 430
    ),
    'demote' => array(
431 432 433
      'label' => t('Demote selected content from front page'),
      'callback' => 'node_mass_update',
      'callback arguments' => array('updates' => array('promote' => NODE_NOT_PROMOTED)),
434
    ),
435 436 437 438 439 440 441 442 443
    '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)),
444 445
    ),
    'delete' => array(
446 447
      'label' => t('Delete selected content'),
      'callback' => NULL,
448 449 450 451 452
    ),
  );
  return $operations;
}

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

474 475 476 477 478 479
/**
 * 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.
 *
480
 * @param Drupal\node\Node $node
481 482 483 484 485 486
 *   The node that has been deleted.
 *
 * @see hook_node_predelete()
 * @see node_delete_multiple()
 * @ingroup node_api_hooks
 */
487
function hook_node_delete(Drupal\node\Node $node) {
488
  drupal_set_message(t('Node: @title has been deleted', array('@title' => $node->label())));
489 490
}

491
/**
492
 * Respond to deletion of a node revision.
493
 *
494 495 496
 * 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.
497
 *
498
 * @param Drupal\node\Node $node
499
 *   The node revision (node object) that is being deleted.
500 501
 *
 * @ingroup node_api_hooks
502
 */
503
function hook_node_revision_delete(Drupal\node\Node $node) {
504 505 506
  db_delete('mytable')
    ->condition('vid', $node->vid)
    ->execute();
507 508 509
}

/**
510
 * Respond to creation of a new node.
511
 *
512 513 514 515 516 517 518 519 520 521 522 523
 * 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.
524
 *
525
 * @param Drupal\node\Node $node
526
 *   The node that is being created.
527 528
 *
 * @ingroup node_api_hooks
529
 */
530
function hook_node_insert(Drupal\node\Node $node) {
531 532 533 534 535 536
  db_insert('mytable')
    ->fields(array(
      'nid' => $node->nid,
      'extra' => $node->extra,
    ))
    ->execute();
537 538
}

539
/**
540 541 542 543 544 545 546
 * Act on arbitrary nodes being loaded from the database.
 *
 * 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.
547 548
 *
 * This hook is invoked during node loading, which is handled by entity_load(),
549
 * via classes NodeController and Drupal\Core\Entity\DatabaseStorageController.
550 551
 * 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
552
 * field_attach_load_revision() or field_attach_load() is called, then
553 554
 * hook_entity_load() is invoked on all implementing modules, and finally
 * hook_node_load() is invoked on all implementing modules.
555
 *
556
 * @param $nodes
557
 *   An array of the nodes being loaded, keyed by nid.
558
 * @param $types
559 560 561 562
 *   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.
563 564
 *
 * For a detailed usage example, see nodeapi_example.module.
565 566
 *
 * @ingroup node_api_hooks
567
 */
568
function hook_node_load($nodes, $types) {
569 570 571 572 573 574 575 576
  // 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;
    }
577 578 579
  }
}

580
/**
581
 * Controls access to a node.
582 583 584 585 586 587 588 589 590 591 592 593 594 595
 *
 * 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.
 *
 * 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"
 * permission may always view and edit content through the administrative
 * interface.
 *
 * 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.
 *
596 597 598 599
 * 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.
 *
600 601
 * @param Drupal\node\Node|string $node
 *   Either a node entity or the machine name of the content type on which to
602
 *   perform the access check.
603
 * @param string $op
604 605 606 607 608
 *   The operation to be performed. Possible values:
 *   - "create"
 *   - "delete"
 *   - "update"
 *   - "view"
609
 * @param object $account
610
 *   The user object to perform the access check operation on.
611 612
 * @param object $langcode
 *   The language code to perform the access check operation on.
613
 *
614
 * @return string
615 616 617
 *   - 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.
618 619
 *
 * @ingroup node_access
620
 */
621
function hook_node_access($node, $op, $account, $langcode) {
622
  $type = is_string($node) ? $node : $node->type;
623

624 625
  $configured_types = node_permissions_get_configured_types();
  if (isset($configured_types[$type])) {
626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647
    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;
}


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

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

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

/**
713 714
 * Respond to updates to a node.
 *
715 716 717 718 719 720 721 722 723 724 725 726
 * 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.
727
 *
728
 * @param Drupal\node\Node $node
729
 *   The node that is being updated.
730 731
 *
 * @ingroup node_api_hooks
732
 */
733
function hook_node_update(Drupal\node\Node $node) {
734 735 736 737
  db_update('mytable')
    ->fields(array('extra' => $node->extra))
    ->condition('nid', $node->nid)
    ->execute();
738 739 740
}

/**
741
 * Act on a node being indexed for searching.
742
 *
743
 * This hook is invoked during search indexing, after node_load(), and after
744
 * the result of node_view() is added as $node->rendered to the node object.
745
 *
746
 * @param Drupal\node\Node $node
747
 *   The node being indexed.
748 749
 * @param $langcode
 *   Language code of the variant of the node being indexed.
750
 *
751 752
 * @return string
 *   Additional node information to be indexed.
753 754
 *
 * @ingroup node_api_hooks
755
 */
756
function hook_node_update_index(Drupal\node\Node $node, $langcode) {
757 758 759
  $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) {
760
    $text .= '<h2>' . check_plain($comment->subject) . '</h2>' . check_markup($comment->comment, $comment->format, '', TRUE);
761 762 763 764 765
  }
  return $text;
}

/**
766 767
 * Perform node validation before a node is created or updated.
 *
768 769 770 771
 * This hook is invoked from NodeFormController::validate(), after a user has
 * has 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.
772
 *
773 774 775 776 777 778
 * 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
 * hook_node_presave() instead. If it is really necessary to change
 * the node at the validate stage, you can use form_set_value().
779
 *
780
 * @param Drupal\node\Node $node
781
 *   The node being validated.
782
 * @param $form
783
 *   The form being used to edit the node.
784 785
 * @param $form_state
 *   The form state array.
786 787
 *
 * @ingroup node_api_hooks
788
 */
789
function hook_node_validate(Drupal\node\Node $node, $form, &$form_state) {
790 791 792 793 794 795 796
  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.'));
    }
  }
}

797 798 799 800 801 802 803 804 805 806 807
/**
 * 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.
 *
808 809
 * @param Drupal\node\Node $node
 *   The node entity being updated in response to a form submission.
810 811 812 813 814 815 816
 * @param $form
 *   The form being used to edit the node.
 * @param $form_state
 *   The form state array.
 *
 * @ingroup node_api_hooks
 */
817
function hook_node_submit(Drupal\node\Node $node, $form, &$form_state) {
818 819 820 821 822 823 824
  // 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']);
  }
}

825
/**
826
 * Act on a node that is being assembled before rendering.
827
 *
828 829 830 831
 * 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().
 *
832
 * When $view_mode is 'rss', modules can also add extra RSS elements and
833 834
 * namespaces to $node->rss_elements and $node->rss_namespaces respectively for
 * the RSS item generated for this node.
835
 * For details on how this is used, see node_feed().
836
 *
837
 * @param Drupal\node\Node $node
838
 *   The node that is being assembled for rendering.
839 840
 * @param $view_mode
 *   The $view_mode parameter from node_view().
841 842
 * @param $langcode
 *   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
function hook_node_view(Drupal\node\Node $node, $view_mode, $langcode) {
851
  $node->content['my_additional_field'] = array(
852
    '#markup' => $additional_field,
853
    '#weight' => 10,
854
    '#theme' => 'mymodule_my_additional_field',
855
  );
856 857
}

858
/**
859
 * Alter the results of node_view().
860
 *
861 862 863
 * 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.
864 865
 *
 * If the module wishes to act on the rendered HTML of the node rather than the
866
 * structured content array, it may use this hook to add a #post_render
867 868 869
 * callback.  Alternatively, it could also implement hook_preprocess_HOOK() for
 * node.tpl.php. See drupal_render() and theme() documentation respectively
 * for details.
870
 *
871 872
 * @param $build
 *   A renderable array representing the node content.
873 874
 * @param Drupal\node\Node $node
 *   The node being rendered.
875
 *
876
 * @see node_view()
877
 * @see hook_entity_view_alter()
878 879
 *
 * @ingroup node_api_hooks
880
 */
881
function hook_node_view_alter(&$build, Drupal\node\Node $node) {
882
  if ($build['#view_mode'] == 'full' && isset($build['an_additional_field'])) {
883
    // Change its weight.
884
    $build['an_additional_field']['#weight'] = -10;
885
  }
886 887

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

891
/**
892
 * Define module-provided node types.
893
 *
894
 * This hook allows a module to define one or more of its own node types. For
895 896
 * example, the forum module uses it to define a forum node-type named "Forum
 * topic." The name and attributes of each desired node type are specified in
897
 * an array returned by the hook.
898
 *
899 900 901 902 903 904
 * 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
905
 *   An array of information defining the module's node types. The array
906 907 908
 *   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:
909
 *   - "name": the human-readable name of the node type. Required.
910 911 912
 *   - "base": the base string used to construct callbacks corresponding to
 *      this node type.
 *      (i.e. if base is defined as example_foo, then example_foo_insert will
913
 *      be called when inserting a node of that type). This string is usually
914
 *      the name of the module, but not always. Required.
915
 *   - "description": a brief description of the node type. Required.
916 917
 *   - "help": help information shown to the user when creating a node of
 *      this type.. Optional (defaults to '').
918 919 920 921
 *   - "has_title": boolean indicating whether or not this node type has a title
 *      field. Optional (defaults to TRUE).
 *   - "title_label": the label for the title field of this content type.
 *      Optional (defaults to 'Title').
922
 *   - "locked": boolean indicating whether the administrator can change the
923 924
 *      machine name of this type. FALSE = changeable (not locked),
 *      TRUE = unchangeable (locked). Optional (defaults to TRUE).
925
 *
926 927 928
 * 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.
929 930 931 932 933
 *
 * 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.
 *
934
 * @ingroup node_api_hooks
935 936 937
 */
function hook_node_info() {
  return array(
938 939 940 941 942
    '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'),
943 944 945 946
    )
  );
}

947 948 949 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 980 981 982 983
/**
 * 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:
 *   - "title": the human readable name of the ranking mechanism. Required.
 *   - "join": 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. Optional.
 *   - "score": 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
 *     0 and 1; be careful not to cast the entire score to an integer by
984
 *     inadvertently introducing a variable argument. Required.
985 986
 *   - "arguments": if any arguments are required for the score, they can be
 *     specified in an array here.
987 988
 *
 * @ingroup node_api_hooks
989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009
 */
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.