twice now I have had the filemaker settings magically disappear after successfully entering records. After going back to the webform settings, I see that somehow the enabled option is set to No after entering several records successfully. What in the world could cause that?
Comments
Comment #1
daengo commentedAHAAAAAHHHH! I just found out that when I go to edit the node, saving it causes the Filemaker settings to disappear. This doesn't happen when adding/changing/deleting form fields or email addresses, but simply editing the node it self and saving will delete the settings under Webform > Form Settings and then Filemaker Settings. Everything else stays in place.
Comment #2
flamingvan commentedThat does indeed seem to be the case!
Thanks for the bug report. I'll get to work on a new release to fix it.
I guess this is why I'm keeping it in beta.
Comment #3
nickorr commentedThis may be related, but I had an issue where the Advanced settings in webform 3.4 wouldn't save for me. So things like the use in block or "Show the notification about previous submissions" options if I changed the defaults, when I saved them, they'd be back to defaults. Disabling and then uninstalling this module got it working again though...
Let me know if you want me to test anything more.
Thanks,
Nick
Comment #4
flamingvan commentedSorry for the delay on this. I need to get on it and will soon.
Comment #5
flamingvan commentedI've released a beta 13 version which should address both issues discussed in this post. I apologize for the long wait.
Comment #6
nickorr commentedThanks, this seems to solve my issue with the block option not showing. I've got one other one, that may be related, or may not. I've got a webform and I'm also using the pathauto module. It seems that at some point when editing a webform, the webform reverts to the auto setting for the path, and so changes to the default of /content/name. I wasn't sure if this was related or not.
I did end up working around it by removing that default option for content, but if you find an issue and have a fix I can put it back to test.
Thanks,
Nick
Comment #7
flamingvan commentedOk thanks for letting me know. Seems lower priority but I will look into it as soon as I get a chance.