Needs review
Project:
Computed Field
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
4 Apr 2012 at 11:35 UTC
Updated:
25 Nov 2012 at 23:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
skipyT commentedI created a patch which sets the property type even if the field is not stored in the database.
Comment #2
laurentchardin commentedI think the main reason we need to do that is because it raises an EntityMetadataWrapperException : Unknown data property... for such fields.
Am i right skipyT ?
Edit: silly me, it was another issue: #1414282: Support for entity_metadata_wrapper()
Comment #3
jsacksick commentedI think you need to replace that line :
$field['settings']['database']['data_type']by$field_type['property_type'] = $property_types[$field['settings']['database']['data_type']];+ the getter callback should return the value coming from the computed function.Comment #4
skipyT commentedHi,
I modified the previous patch file after jsacksick review.
New patch file attached.
Comment #5
cmoldovan222 commentedIt seems ok for me.
Comment #6
fgmThis patch contains both an error and a performance issue. Rerolling
Comment #7
fgmComment #8
colanNew features go into the latest dev branch. This is not critical as the module will still work without it.