I have a Computed Field which stores a text value which is returned by the following code:

$urlref = $_SERVER['HTTP_REFERER'];

...and stored in the DB as a "Text Field". This appears exactly as you would expect as the URL of the referring page.

However, when I use Rules to "set a data value" by writing the value of this field into an empty text field of another content type I get the following error:

Notice: Array to string conversion in RulesTokenEvaluator->evaluate() (line 199 of /sites/all/modules/rules/modules/system.eval.inc).

The value that ends up in the text field that has been written to is the word "Array".
It would appear that Rules thinks the original value is an array but I'm not sure why.

Comments

kojis’s picture

kojis commented
Component: Rules Core » Rules Engine

I had the same error, updating to the latest *computed_field* (2012-Feb-15) resolved it for me, and the output is now as expected.

mitchell’s picture

mitchell commented
Status: Active » Fixed

Glad this was fixed. Please reopen if the problem continues.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

IgnitedCoder’s picture

IgnitedCoder commented
Version: 7.x-2.0 » 7.x-2.3
Component: Rules Engine » Rules Core
Status: Closed (fixed) » Active

Notice: Array to string conversion in RulesTokenEvaluator->evaluate() (line 203 of /var/www/vhosts/srisk/sites/all/modules/rules/modules/system.eval.inc).

Simple calculated field...

$participant = array_pop(array_pop(field_get_items($entity_type, $entity, 'field_activity_participants')));
$email = db_query("select field_broker_email_email from field_data_field_broker_email where entity_id = :entity_id limit 1", array(":entity_id" => $participant))->fetchField();
$entity_field[0]['value'] = $email;

Please help!!

Thanks

tr’s picture

tr commented
Issue summary: View changes
Status: Active » Closed (outdated)

The initial problem was fixed.

The problem raised by @IgnitedCoder is unclear due to lack of details. At a minimum we need steps to reproduce along with an export of your rule, simplified as much as possible and ideally containing only core Rules events/conditions/actions. If you must use custom fields to reproduce this then they should be standard core Drupal fields applied to core Drupal content types/entities and you should describe how you've configured them.