Hi Danny,
I don’t see this on any of my sites, so it’s not easy to figure out.
Did this problem first occur with the latest entrywizard update (version 1.2.23), or did it appear also with the last version?
The first thing to try would be deactivating all your other plugins, then re-activating them one by one to see if one of them is responsible. If you find such a plugin, please let me know which one.
If that doesn’t work, then an emergency fix would be to edit the
file classes/validation/ewz_input.php. Search for the line containing “unexpected input”, and disable it by putting ‘//’ at the start of the line. ( Make sure you save the file as plain text. )
I’m beginning to wonder if something has changed in the latest version of wordpress that might cause this. If you can narrow down the time period during which the error started to appear, or the versions of wordpress and entrywizard involved, it would be helpful.
Hi Josie, thanks for the reply – sorry I replied to the email that came directly to me which I realise was a no-reply address.
I last used EWZ in May and since then have changed my theme and inserted a couple of plugins but I have in the past 10 minutes deactivated all of my plugins and still it gives me the problem, the new theme is
Photography by ThemeGoods, version 1.7 and my WP version is 4.5.3
I haven’t as yet amended the .php file though.
Thanks Danny
Unfortunately, your theme is not a free one, so I can’t test it or check the code. If you have a test site, or a time when your site is not getting a lot of hits, you could try changing the theme.
It would also be a good idea to upgrade to WordPress 4.6
I’ll try that Josie and also the .php file as well. Thanks for your help – excellent and fast as usual.
Hi Josie, changed to WP4.6 and turned off my plugins – still no luck. But got my IT guys to sort the .php file and it now lets me create a webforms, so thanks very much for that.
If you would like to check my website and theme I will send you the details if you want and can give me a secure place to put them.
All the best, Danny
In the latest version (1.2.24) I’ve changed the code to log such unexpected input in the debug log file, and then ignore it.
