Bobcares

Drupal Hook Node Presave | All About

by | Aug 14, 2022

Drupal Hook Node Presave acts directly on inserted/updated nodes. Bobcares, as part of our Server Management Service, responds to all Drupal inquiries, large or small.

Drupal Hook Node Presave Function

Hooks give modules access to the Drupal core. The “hooks” concept serves as the foundation for Drupal’s module system. A hook is a PHP function with the name foo_bar(), where “foo” stands for the module’s name and “bar” for the hook’s name. Also, each hook has a specific result type and a defined set of parameters.

All a module needs to do to extend Drupal is to implement a hook. Drupal determines which modules implement a hook and calls that hook in all enabled modules that implement it when it wants to allow module intervention.

Node hooks are functions for defining and modifying content types. The node operations such as create, insert, update, view, delete, etc. call several sets of hooks to let modules alter the base node operation.

 

drupal hook node presave

While updating an existing node (calling $node->save() on an existing node), it invokes hook_node_presave(). This hook invokes node_save() before the node is saved to the database. We can find it at drupal/core/modules/node/node.api.php. It acts directly on the added/updated node.

Implementing Drupal Hook Node Presave() function

The following are the four functions to implement the hook_node_presave(), namely:

  1. book_node_presave, located in drupal/core/modules/book/book.module
  2. entity_crud_hook_test_node_presave, located in drupal/core/modules/system/tests/modules/entity_crud_hook_test/entity_crud_hook_test.module
  3. forum_node_presave, located in drupal/core/modules/forum/forum.module
  4. node_test_node_presave, located in drupal/core/modules/node/tests/modules/node_test/node_test.module

Code To Call hook_node_presave() Function

The following code will invoke the hook_node_presave():

function hook_node_presave(\Drupal\Core\Entity\EntityInterface $node) {
  if ($node->nid && $node->moderate) {

    // Reset votes when node is updated:
    $node->score = 0;
    $node->users = '';
    $node->votes = 0;
  }
}

How To Stop A Node From Saving In hook_node_presave() Function?

We must obviously throw an exception if we want to stop the node from being saved in a presave method or hook.

throw new \Exception(t('Fields are not unique!'));

Regardless of the form, Rest API, or code used, it is still a good idea to double-check this in presave to ensure that no incorrect node content is saved. If someone gets past the first level of checks in the form, then we definitely have to throw an exception.

When an exception raises, then we can catch the database connection exceptions with a custom handler.

[Looking for a solution to another query? We are just a click away.]

Conclusion

In this article, our Support team explains Drupal’s hook_node_presave function including its implementation.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

2 Comments

  1. chance

    is this hook need to be implemented in .module file or .theme file am confused

    Reply
  2. Subbarao Talla

    in module

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF