EntityMetadataWrapper support

Nice, tested on ERPAL, works like a charm!

For me it also looks good, thanks for this patch.

Well, I would also like to see this patch commited.

#1 works perfectly.

Additional info on setting units and values:

// Set field value and measure type for the _first_ time:
$wrapper->field_mvf->set(array('value'=>2, 'target_id'=>35));

// Load the unit by it's machine name using:
$unit_entity = units_unit_machine_name_load([unit machine name]);

// Get Unit Id:
$unit_id = $unit_entity->umid;

Hello!

This is me, whom you are blaming. And you do so rightly. I dedicate to this module less time than I would like to. I maintain other 3 modules on d.org and this one has the least popularity, so I feel obliged to give it only a fraction of my time. But I am willing to sort this issue.

Thank you for the patch. I've reviewed it - you got most of it done. The only suggestion I could come up with is that it would be great to also include into the wrapper API ability to fetch MVF value in a specific unit. Right now using the patch we can fetch both absolute value and the unit that corresponds to that value, but we're basically forced to do the conversion in client code, which is not that nice.

So, let's get one more feature:

$r = $wrapper->field_mvf->value->value(array('unit' => 6));
// Now $r contains field_mvf value converted into EUR. Instead of '6' we could also supply fully loaded unit entity or its machine name.

Or it could be:

$r = $wrapper->field_mvf->value(array('unit' => 6));
// Now $r is array as following:
$r = array(
  'value' => 789, // whatever it is in EUR,
  'target_id' => 6, // target_id should hold the unit ID into which it was converted
);

I've tried to implement this addition tonight, but entity API wrappers abstractions are definitely way too baked for my brain after midnight. I'll get it tomorrow.

In the mean time I only edited 2 lines of code: strictly speaking both 'value' and 'unit' need 'schema field' and we map from 'value' and 'unit' properties to specific columns through mvf_subfield_to_column() function.

I am glad I heard the voice of rationalism in my head and put it off yesterday. No way I would have gotten it done last night. After poking entity API module seems like the best option I can get is:

$r = $wrapper->field_mvf->converted_euro->value();
// Now $r holds the value of MVF field in EUR.

So it takes the form of

$wrapper->field_mvf->converted_{machine_name_of_the_target_unit}->value();

Apart from it nothing is changed. I enclose the 2 patches: against current 7.x-1.x and interdiff against korgik's contribution. Let's see if you like it?

Good point. I've added our PHP snippets from this issue into README.txt (patch enclosed). I also have a rule of thumb of not publishing stable release of any module without up-to-date existing documentation page. So, when MVF gets stable for 7.x-1.0 release, I'll include this info into its documentation page too.

Is is possible to get the converted value's unit label or symbol?

Not really, since you are the one who dictated into what unit to covert, it is assumed you already know its label or unit or anything else about the target unit. I'd do something like the following (load the unit, so later on we can fetch its label, and get MVF converted into it):

$target_unit = units_unit_machine_name_load('euro');
$property = 'converted_' . $target_unit->machine_name;
$r = $wrapper->field_mvf->$property->value();

echo $r . ' ' . check_plain($target_unit->label()); // Outputs "100 Euro".