Generically detecting changed fields in a custom form prior to saving a node

I’m adding certain fields from a content type into a custom form using field_attach_form(). When the form is submitted I’m processing those fields by calling field_attach_form_validate() and field_attach_submit() from #validate and #submit callbacks.

At that point, I want to compare the post-submit, prepared node object to the original node and only bother to node_save() it if any of the fields have changed. Therefore, I begin by loading the original node using entity_load_unchanged().

Unfortunately, the field arrays in the original node object don’t match the field arrays in the prepared node object which is waiting to be saved, even if no changes have been made to the fields, so a simple “$old_field == $new_field” comparison is impossible. For example, a simple text field appears like this in the original:

$old_node->field_text['und'][0] = array(   'value' => 'Test',   'format' => NULL,   'safe_value' => 'Test', ); 

Whereas in the prepared node it appears like this.

$node->field_text['und'][0] = array(   'value' => 'Test', ); 

You might think to just compare the ‘value’ key, but then you run into fields made up of other elements which don’t have ‘value’ keys. For example, let’s look at an address field where there is no ‘value’ key and there are keys in both the old and prepared nodes which don’t have counterparts.

Old node

$old_node->field_address['und'][0] = array(   'country' => 'GB',   'administrative_area' => 'Test',   'sub_administrative_area' => NULL,   'locality' => 'Test',   'dependent_locality' => NULL,   'postal_code' => 'Test',   'thoroughfare' => 'Test',   'premise' => 'Test',   'sub_premise' => NULL,   'organisation_name' => 'Test',   'name_line' => 'Test',   'first_name' => NULL,   'last_name' => NULL,   'data' => NULL, ); 

Prepared node

$node->field_address['und'][0] = array(   'element_key' => 'node|page|field_address|und|0',   'thoroughfare' => 'Test',   'premise' => 'Test',   'locality' => 'Test',   'administrative_area' => 'Test',   'postal_code' => 'Test',   'country' => 'GB',   'organisation_name' => 'Test',   'name_line' => 'Test', ); 

For empty fields, there is yet another discrepancy.

Old node

$old_node->field_text = array(); 

Prepared node

$node->field_text = array(   'und' => array(), ); 

Can I generically compare any field’s old and new value to detect whether it has changed or not?
Is this just an impossibility?

This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

Generically detecting changed fields in a custom form prior to saving a node

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.