Hi there-

I was trying to export all of my config to features via ctools, and ran into an issue where all of my field mappings disappeared. At least when I tried to edit the settings for any field on my listing entity, none of the dRealty mapping fields came up, and I would get an error when I saved the field of:

Warning: Invalid argument supplied for foreach() in drealty_field_ui_field_edit_form_submit() (line 854 of /Users/stockliasteroid/Sites/mysite/sites/all/modules/contrib/drealty/drealty.module).

I disabled the features to try to go back to the normal DB config, but that didn't work either. I did some checking in drealty_form_field_ui_field_edit_form_default, and none of the loaded classes had a bundle set on them. I then went out and looked in the {drealty_classes} table to see what was up, and there was a ton of duplicate classes for each of my connections, all of which had empty bundles. I deleted all of the DB records with empty entities, reloaded the form, and all of my mapping fields reappeared.

Also as a side issue, when I tried to export all of my dRealty settings to features it was extremely slow to create the feature, and subsequent navigation of the dRealty settings screens while those features were enabled was also very slow. When I disabled them it became super fast again.

CommentFileSizeAuthor
#6 drealty_config.features.inc_.tar_.gz271.42 KBstockliasteroid

Comments

stockliasteroid’s picture

stockliasteroid commented

Sorry above should read: "I deleted all of the DB records with empty bundles, reloaded the form, and all of my mapping fields reappeared."

camidoo’s picture

camidoo commented
Status: Active » Postponed

Drealty hasn't been tested with Features, nor was it designed to, not saying that it shouldn't, just gonna have to postpone this for now. If you would like to submit a patch that fixes the issue i'd be more than happy to review and include it.

camidoo’s picture

camidoo commented
Category: bug » feature

also marking this as a feature request as it's not really a bug, as feature support is unimplemented.

stockliasteroid’s picture

stockliasteroid commented
Title: CTools Export / Feature Issue » Exporting a connection breaks all connections
Category: feature » bug
Status: Postponed » Active

This should probably be renamed, then... I was testing this a bit more as I thought that any module with CTools support should just work with features. While testing the "Export" functionality under Connections, I experienced the same behavior. Click "Export", and then wait a long time, and then it provides the expected PHP for export. After this is complete, I then went back to edit one of my dRealty listing types and saw that the original problem I reported with Features occurred again, all of my dRealty property classes were gone from the mapping fields. After looking at the drealty_classes table again, I saw a ton of empty bundle entries again.

So, this seems to be reproducable simply by trying to export a connection from the dRealty admin, so I don't think this is a Features issue at all. And still seems like a bug? Setting this back to active, for now, feel free to overrule me :). The good news is that I think if this was fixed, Features would probably work fine too, as it's simply automating the process of exporting the settings and creating a module file, which is what you do anyway when you export the settings from dRealty.

camidoo’s picture

camidoo commented

can you remove the login info from an export and attach it please? I'd love to take a look.

stockliasteroid’s picture

stockliasteroid commented
StatusFileSize
new drealty_config.features.inc_.tar_.gz271.42 KB

I've attached the original features export, which looks to be the same as if I just do an export off of the connections listing page in dRealty. Thanks for taking a look!

camidoo’s picture

camidoo commented

trying to clean up the issue queue and was wondering if this is still an issue for you or not, i can't remember what i came up with or if i even had a chance to look at it...

stockliasteroid’s picture

stockliasteroid commented

Haven't tried this lately... It didn't work under the beta3 release, so I expect that it still doesn't work. Pretty easy to reproduce, just try to export a connection as I've outlined in #4, and the connection will get broken.

markusa’s picture

markusa commented

I am using drealty 7.x-3.0-beta3
Found the same problem....and a work around...

I have created field mappings with over 100 fields per class. When I exported the property types as a feature and tried to install the new feature module on a second test site none of the RETS field mappings were there!!!

So I went back the modules page and uninstalled my feature module that had been created from my first test site. I went back to my drealty property types after uninstalling my feature module and the property types and connection were still there and all the RETS field mappings had reappeared! I have tested that connection with drush rets-import and it downloads and creates the listings correctly. Simple enough workaround.

Seems the features functionality gets in the way somehow....

camidoo’s picture

camidoo commented

that's really strange, i haven't had a chance to test this with the features module

markusa’s picture

markusa commented

Little more info for you.....

I separated out the field mappings and connection into separate features modules. It is the connection feature module that breaks the field mappings.....once that was disabled on the module page then the RETS field mappings appeared again!

bleen’s picture

bleen commented

I am seeing the same issue

shauntyndall’s picture

shauntyndall commented
Issue summary: View changes
Status: Active » Closed (outdated)
Issue tags: +CTools exportables, +Features integration

I'm closing this as it seems outdated but if someone has a patch to contribute and test this can certainly reopen.