Hi, I created a form. It worked once, but then when I submitted the form once to test it, the form components were no longer visible. I changed accounts, and the form was visible again, but once I submitted the form under that new account, the components were again no longer visible. I have unlimited max submissions, so my understanding is that it should still be visible (in fact, it should always be visible, even if I should not be able to submit it). I deleted the content, recreated it, ran cron, cleared caches, nothing helps.

Comments

vernond’s picture

Are you using boost or a similar module which affects caching on your site? Are you accessing the site from behind a proxy server?

What you describe is not normal behaviour, but I can't tell what may be causing the issue.

chrisryan’s picture

I am also experiencing the same problem. I downloaded and installed the module last week and have seen the problem twice. The first time I started receiving errors while trying to update the form after the component fields disappeared. I deleted the form and disabled/uninstalled the module before reenabling the module and enter a while new form. Everything appeared to work but today I noticed all the component fields missing again while I was going through my site verifying the pages where completed.

chrisryan’s picture

And today it is working fine without any obvious changes having been made. I upated the Media module, disabled a css settings option in omega theme, and made other css changes in my subtheme for a different content type. If I see it again I will try to make notes of any recent changes I am aware of then as well. I do not have any caching options enabled.

quicksketch’s picture

Issue summary: View changes
Status: Active » Closed (cannot reproduce)

Usually, this is because of the max or (in 4.x) per-user submission limits. Though the original poster said this wasn't the case for him... we haven't had any confirming reports since @chrisryan's, making me think this is likely a configuration issue rather than a bug in Webform. If more details can be provided on how to reproduce this issue, we can take another look at it.