InSightGraphicDesign

I just got this error after the update to WP 4.8.3. Thanks to Remco Stoffer for finding it was a cache error, I remembered Bluehost has added MU caching Plugins (endurance-browser-cache), and I purged that cache by clicking “Purge All” under their newly added “Caching” tab in the WordPress Toolbar. Error fixed!

• This reply was modified 7 years, 4 months ago by InSightGraphicDesign.

I tested with all plugins disabled before I reviewed. I’m using the Sapor theme, which is a very simple blog theme, built to current standards by Automattic.

Yes, this is fixed in the latest version 1.0.5. Thanks!

(The css issue with .alignright is not yet fixed, though.)

Here’s the documentation for how to set up & use PayPal:
https://formidablepro.com/knowledgebase/formidable-paypal/

This functionality requires the premium add-on. For support, ask your questions in their user forum:
https://formidablepro.com/help-desk/

No documentation and a low level help desk.

You couldn’t be more wrong. I’ve been using Formidable — free as well as pro — for years. The documentation is thorough, and the support is terrific.

I had the same problem today: unable to save the custom background image path. Clicking “insert” in the plugin’s media uploader just leaves the URL box empty. Problem persisted with default theme (Twenty Twelve) and all plugins disabled (except UMM). Tested on local & remote servers. Using WordPress 4.0, with Ultimate Maintenance Mode version 1.5.4 (free version).

Solved by pasting the image URL directly into the box, instead of trying to save from the plugin’s media uploader interface.

(After uploading the image to your library, you can find the image URL in the Media Library.)

It works! Thank you for your super-quick response and solution!

It’s not humanly possible to give support any faster or better!

Thank you very much for your prompt reply. Unfortunately, neither of these 2 solutions is possible in my particular case.

(1) This plugin allows us to change some field names, but not these. It insists on specific IDs & names for First Name (first_name), Last Name (last_name), Name (user_name), and Email (user_email).
(2) My MailChimp list does require First & Last Names.

I’ll keep an eye on both excellent plugins and hope that one becomes compatible with the other in situations like mine. Maybe you could incorporate these IDs/names into your next update, since they are so strict about requiring just these?

Yes, the MailChimp list requires First & Last Names.
Events Manager lets us change the Field ID, which also seems to automatically copy itself into the Field Name — this is how I made the Field Name for the checkbox = mc4wp-try-subscribe

Thank you, JimKubik, for posting that solution! It works great!

I would like to disable that “Loading Events” notification also.

Or: Is it possible to eliminate jGrowl completely? How? What would be lost in that case?