Help for most common problems and their solutions regarding eForm plugin.
With the release of eForm v3.3 we dumped compatibility with PHP5.3. If you are trying to run eForm v3.3 on the mentioned environment, then it would essentially raise PHP Fatal Error, leaving a White Screen of Death for your entire website. In this case, we heavily recommend updating PHP version to at-least 5.4 (or better…
In some cases, especially with Visual Composer and some theme combination (where the former use a backdated jQuery WayPoints library and later use an updated one), eForm can break. The admin end will work properly, but the frontend will not. It will appear, more or less like this (depending on the theme you are using).…
From July 2018, Google now requires you to enable billing in your cloud account to access places API. Places API is required for eForm GPS Tracker element. #1: Create new project under Google Cloud Console Google Places API now live under newly formed Google Cloud Console. Visit this link to go to the console. You…
In some cases, your theme’s CSS might override some of the styles of FSQM, which would result in broken appearance of text inputs. Although, it is nearly impossible to guess which CSS is responsible (due to a rather wide possible variety of CSS codes), we have found the following two very common. Broken height of…
In some cases, for a rather long form, adding new containers and/or elements will work in the form builder, but when being saved, will not get reflected in the live form. In other words, questions or containers you create will disappear when a form is saved. It can seem that there is a limit to…
