Auto-Close field unchecked itself

I can’t reproduce this, so my best guess would be a plugin conflict. To detect that you need to disable each of the other plugins and see if you still have the same problem — which may temporarily mess up your site unless you can reproduce the effect on a test site.

But just to be sure I understand, is it the Close Automatically checkbox that gets unchecked, or the date or time field that gets unset? And does the setting get disabled as soon as you close and re-open the webforms page, or does it take a while to happen?

My co-admin did the upload forms late night on 29th. The auto-close field was checked and the date/time set, according to him. I checked the forms in the evening of 30th and found only one form had the auto-close enabled and had date/time set. In the other forms, the field was unchecked and date/time fields were empty. So I went ahead to enable the field and input the date and time for all those forms. I don’t remember whether or not I checked again immediately after the save.
This morning, I went in to double check and found only one I did last night retained the settings, the field was unchecked with empty date and time in the others.

Just now, I go in to set the field and input the date and time. Now is 15 mins passed, the settings still hold. I’ll report back tomorrow whether the settings are there or not.

As usual, my server error log always shows the following message:
20220701T185431: mysite.com/wp-admin/admin-ajax.php
EWZ: Ewz_Webform_Input: unexpected input field pll_ajax_backend with value ‘1’

I did a search for pll_ajax_backend, and found that it belongs to the plugin Polylang. If you have that plugin, try disabling it.

Thanks. But I use Polylang to manage my site’s translation. My site is bilingual.
How is it related to EWZ webforms?

So far the auto-close field settings still holds.

the problem may occur when polylang is used in some specific way.

I’ll try to look into it further when I can find time.

One thing though, the message appears only when a webform is saved. This is my observation of the timestamp of the error log coincide with saving of the form. So it is not triggered by Polylang. And I don’t think it affects the saving of the forms. Thanks for looking into this.

I just check the auto-close setting. Out of the three, one retains the setting, while the other two become unchecked and the date and time are empty. This seems to be a pattern: there is alway one form will retain the settings, while the others become unchecked.

One possibility just hit me: you mention a “co-admin”. Is there a chance one of you edited a webform and then the other edited it from an earlier cached copy, thus saving the old value over the new one?

If more than one person is doing updates, each must be very careful to reload the page before making changes. Browsers cache most pages. I’m afraid EntryWizard is not sophisticated enough to detect when an editor is using a cached copy.

I have not come across any browser cache issues within dashboard. All setting/configuration changes are saved and appear in the setting screen of plugins right after, like in webforms. As for editing different versions, I don’t think it was the case. He did the forms one night and I checked on them 18 hours after. I found three out of six forms had auto-close setup. If it was browser problem then I should not see the new webforms or its settings at all.

Yesterday morning, I set the auto=close on the remaining two forms, saved them. Since you mentioned browser cache, I refreshed the webform page. To my surprise, the auto-close on one form became uncheck and empty date/time fields. The other one retained the settings. The one that retained the settings was the one I last one did the setup. As I mentioned in my earlier response, only one form retained the settings. It become more obvious to me that its the last form that I set up will retain the setting.

Hope these observations provide some clues where to look for answers.

Hi Josie,
I went ahead to deactivate Polylang to confirm the conflict.

Then I tested the Entry Wizard and saved the autosave settings on a form. The settings were indeed saved and retained (as oppose to settings were not saved when Polylang is active). Also the error message mentioned in my earlier post no longer appeared in the error log.

So definitely there is some conflict between the two plugins. In EntryWizard’s perspective, is there anything can be done to resolve this? Or is there any workaround.
Please help.`

When I have time, I will take a look at the free part of the plugin, and see if there is anything obvious that EntryWizard could do.
But a quick web search shows several complaints about PolyLang being incompatible with other plugins, and also shows a number of alternatives.

Thanks. I did a little search on error with pll myself, but found no solution. I also have posted the issue on their support forum. Hopefully they can come up with a remedy, not just for ewz but for other plugins.