Note: This post is over two years old and so the information contained here might be out of date. If you do spot something please leave a comment and we will endeavour to correct.
17th November 2016 - 5 minutes read time
I had to update a Drupal 7 site recently and needed to change the field keys of a list field to be different values. This wasn't possible from within Drupal as it does a pre-check to make sure that the key doesn't already exist. If it finds any values present in the database with that key then it will reject the change. This is absolutely correct but causes a little bit of an issue when you need to update these values.
The solution to this is to alter both the field definition and the field data via directly altering them in the database. The following function provides a neat little way of doing this to a field by just passing in the field name and what the key values need to change to.
/**
* Updates the definitions and data of a multi field based on a search replace array.
*
* For the $search_replace array, the keys must be the current values of the
* field and the values must be the new values to map the existing values to.
*
* @param string $field_name
* The field to act upon.
* @param array $search_replace
* The values to replace.
*/
function mymodule_update_field_definition($field_name, $search_replace) {
$field_table = 'field_data_' . $field_name;
$field_table_value = $field_name . '_value';
// Get the existing field config.
$field_definition = db_query("SELECT id, data FROM field_config WHERE field_name = :field_name LIMIT 1", array(':field_name' => $field_name))->fetchAll();
// Change the data in the allowed_values element.
$data = unserialize($field_definition[0]->data);
foreach ($search_replace as $value => $key) {
unset($data['settings']['allowed_values'][$value]);
$data['settings']['allowed_values'][$key] = $value;
}
// Save the new field config to the database.
db_update('field_config')
->condition('field_name', $field_name)
->fields(['data' => serialize($data)])
->execute();
unset($field_definition);
// Get all the data from the table.
$field_values = db_select($field_table, 't')
->fields('t', ['entity_id', $field_table_value])
->execute()
->fetchAll();
foreach ($field_values as $field_value) {
// If the value exists in our search/replace array then swap it.
if (isset($search_replace[$field_value->$field_table_value])) {
$field_key = $search_replace[$field_value->$field_table_value];
} else {
continue;
}
// Save the change in field data to the database.
db_update($field_table)
->condition('entity_id', $field_value->entity_id)
->fields([$field_table_value => $field_key])
->execute();
}
}
This function takes the field name and first alters the field definitions to be correct. It will then load all data for the field from the database and update the values to be in line with the new values. It doesn't take into account any field revisions and so if you are looking to change all current and past values then you'll need to add this functionality to the function. Also, the function doesn't use transactions and as such if anything fails half-way through you'll have a mess of data on your hands. If this does happen just re-run the function and it will finish things off.
This function is pretty easy to use. Just create an array that allows the old keys to be translated to the new keys and pass this to the mymodule_update_field_definition() function along with the field name.
One of Drupal's strengths is its ability to create communities of users who contribute towards the content of the site. Whether you have an open forum, where users can create their own accounts, or a closed magazine with just a few editors your need to take the security of your users seriously.
Drupal has a quick and convenient way of creating ajax dialogs that gives users the ability to embed links in content that open up dialog boxes when clicked. This is a useful way of presenting a bit of content to a user without them navigating away from the page.
There are a number of different tools that allow you to validate and test a Drupal site. Inspecting your custom code allows you to adhere to coding standards and ensure that you stamp our common coding problems. Adding tests allows you to make certain that the functionality of your Drupal site works correctly.
This year's DrupalCon Europe was hosted between the 17th and 20th of October, in the French city of Lille. My DrupalCon adventure began early on Monday morning when Chris Maiden picked me up to drive to France via the EuroStar train. We arrived in Lille a little after 4pm, which was really good going for a nearly 400+ mile trip.
Add new comment