| Comment | File | Size | Author |
|---|---|---|---|
| #3 | rolereference_field_extract_integration_2.patch | 966 bytes | acrollet |
| #2 | rolereference_field_extract_integration.patch | 949 bytes | acrollet |
| field_extract_rolereference.patch | 508 bytes | acrollet |
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | rolereference_field_extract_integration_2.patch | 966 bytes | acrollet |
| #2 | rolereference_field_extract_integration.patch | 949 bytes | acrollet |
| field_extract_rolereference.patch | 508 bytes | acrollet |
Comments
Comment #1
adaddinsaneCool.
But the correct approach would be to ask the maintainer of that module to include the support at his end by supplying a patch there.
If he's not willing to do that then we can include the patch here.
I'm making this a "won't fix" which sounds very rude - but isn't intended that way :-)
Steve
Comment #2
acrollet commentedHi there,
per the maintainer of the field_extract module, I'm moving this issue to the Role Reference queue and submitting a patch against rolereference.module.
thanks!
Adrian
Comment #3
acrollet commentedlast patch did not work correctly, could swear I had tested it... this patch is better.
Comment #4
deekayen commentedCommitted to 7.x-1.x at 237ba4ce95c11e275b83b503e2eadd75dae84588.