wireB

The dev version 1.5.7 has the same version number as the current public version 1.5.7 – am I correct?

Update: version 2.1.5 is faster than 2.2.1 but still gives the “Unresponsive Script Error.” Using Firefox 43.0.2.

Chrome is much faster while in the editor. Many times Firefox plugins can not be removed unless you go into the Windows registry. I suspect that Firefox is not as fast because of plugins/extensions that can not be removed – not sure.

Want to thank you for your great work in providing thousands with a key plugin for WordPress page layout use.

Confirmed, version 2.1.5 does not give hang up page loads while in editing mode – no “Unresponsive Script Error.”

I do have many PB blocks on this page so possibly the average editor would not get these Unresponsive Script Errors. However, the 2.1.5 is most efficient :).

Will be trying version 2.2 which is the prior update to the current 2.2.1.

Thank you,

wireB

Matthew, it was a php.ini file that got in there some way. Do not know how that got in there. I deleted the file and the site now works

Thank you again for your help.

Hi Matthew, and thank you for your assistance. I do have other sites which are much larger and they do not get the memory limit error.

Will test the recommendation you present.

May I ask if you can give me the link to the archive/older versions?

Confirmed, this is occurring on another site with the same servers. This was not the case a version earlier ago.

Hi Greg,

Let me test that out. Would also like to thank you for a key and quality plugin.

Yes, in the previous version, they were only being shown in the layout not preview. This seemingly has been fixed.

Then at least in the updated version, add some samples conditional statements connected to one of your pre-made forms.

Affirmative, the form has been set to “Update Form.” You only see these fields while in the Conditions mode.

Would like to thank you for your assistance.

Updated: My mistake in understanding how Caldera works. You must also removed the field in the Conditions mode even though they were deleted in the Layout mode.

Hi Josh,

Seems all good so far using the latest version of WP and Caldera v 1.3.0. Thank you for your great contribution creating Caldera Forms. Is is most likely one of the few form tools which if any, possesses conditional statements.

Give me another week to test on other sites to see if this error presents itself again before marking this thread resolved.

Hi Camu,

“Blacklist by Username” was not expecting a label as “Blacklist.” Was looking for something like, “Do not track.” Blacklisting is more rejecting for security or misbehaving, whereas “Do not track” is a filter.

The <a>tag is not being closed – this is my mistake. Problem 1 still exist.

Not going to work. The contact shortcode needs to java itself to the contact form class among other things. InfoPopup is for HTML and not for embedding shortcodes belonging to other scripts.