Closed (fixed)
Project:
Drupal RETS Real Estate Framework (dRealty)
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
10 May 2016 at 21:27 UTC
Updated:
30 Dec 2017 at 19:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
veronicaseveryn commentedIf you first create a field not on a Drealty entity type, e.g. on the node first, then you can re-use it with a Drealty entity configuration.
Otherwise, if you have access to DB (e.g. with a tool like MySQL or something else) you can alter field config in the table that will remove restrictions from the field - but it's ONLY IF YOU KNOW WHAT YOU'RE DOING!!
And the third solution - it needs to be fixed inside Drealty module - which is what I am gonna work on in the nearest future.
Comment #3
veronicaseveryn commentedAdding a patch.
Comment #4
veronicaseveryn commentedThe patch provided above will work for the newly created fields. It will save them in the database without entity type restrictions. This patch is not gonna fix existing fields (if you need to, you'll have to adjust the record in the database manually, as described previously).
Comment #6
veronicaseveryn commentedThe patch has been commited
Comment #8
notanumber6789 commentedI have hundreds of existing fields that I need to re-use in another entity type. Can you describe how I can use sql to remove restrictions on each, for example field_mlsnumber? Is there any way to safely do this for all drealty fields, instead of one by one?