Hi, I have com accross several situations, where Code added to the chronoforms setup (like event switcher, custom code etc.) has invoked a 403 error on trying to save the form. Once it was even a javascript loaded from a CDN URL, and just now, I had code from an event switcher that checked with php isset() on a form field, in $form->data array. This happened on different servers, from different hosting providers.
Is there any one else who experienced the problem? Is it a general problem with code processed though eval()?
I always found a workaround, but it seems it happens after php updates or migrations, so the server environment changes and then suddenly the client cannot save changes any more.
Curious about your answers!
Terry
Is there any one else who experienced the problem? Is it a general problem with code processed though eval()?
I always found a workaround, but it seems it happens after php updates or migrations, so the server environment changes and then suddenly the client cannot save changes any more.
Curious about your answers!
Terry
