FormLift for Keap (Legacy) Web Forms vs Preserved HTML Editor Markup

Need help? Watch Our Tutorials What does it do? See The Features List Need more functionality? Check out our extensions! Not technically inclined? Launch Guided Setup Simply put, this is the easiest, fastest, and most user friendly solution to putting Keap (Infusionsoft) Web Forms on your website. FormLift’s 5 minute setup time allows you to install this plugin and run, not walk. It takes 30 seconds to create a new form and place it on your site! The Free version hosted on WordPress allows for amazing functionality that will make any Keap users’ nightmares disappear in seconds… Unlicensed Features Over 45 global styling options Forms auto populate with contact info From emails Form Validation and spam protection Conversion Rate Tracking Personalized Page Short-codes for thank you pages Import form directly via the Keap API, no copy/pasting Customizable Date Picker that actually works Personal Identifiable Information protection to keep your contacts’ data safe. But if you want to unlock the full automation power of FormLift, you can start your 14 day free trial right now to unlock even more tools! Premium Features Auto population link builder Conditional Thank You Page Redirect Creator Tool In form Google reCAPTCHA integration, works better than the native Keap one. Individual Form Styling Conditional Form Display Tool Require login for submit File Uploads from your web form FormLift empowers regular IFS forms by keeping all the native affiliate tracking & contact tracking intact while allowing you to finally have good looking webforms on your website. See how easy it is to get setup today! Want extra functionality? Level up with extensions! Compliance FormLift, like many other form plugins, collects personally identifiable information to improve a user’s experience, provide them with marketing, transactional emails, and so on and so forth. With the MANY compliance initiatives out there such as GDPR, it is important to understand the following BEFORE using formlift for your business. FormLift is used expressly for Keap, an SMB marketing CRM based in Pheonix Arizona. Keap maintains the compliance of your business with regards to Personally identifiable information in MOST cases, but not all. FormLift has several functions you will either want to disable, or enable depending on your industry or region of the world. Data Collection When a user submits a form, that data is sent to YOUR server for validation and is not necessarily stored. MOST data collected with FormLift after a submission is sent to Keap where it is stored and is then forgotten by your website EXCEPT in the following cases. Session Tracking This feature comes with FormLift and is enable automatically, it allows the persistence of user data from page to page without having to pass UTM variables, almost as if the user is logged in. These sessions are used on secure connections only (SSL) hence if you do not have an SSL certificate this feature will be disabled. This session is stored in your database following the last interaction with the user for 30 days until it expires and is removed automatically. Depending on your level of compliance, you may wish to disable this feature which you can do in the settings, OR you may specify the number of days the user’s information is stored to a smaller number, like 1 day which would be enough for most browsing sessions. Cookies FormLift uses cookies to track user interactions, such as the above session tracking, form submissions, or other form interactions. Saved Submissions This is a premium module, but if you have it enabled there can be serious compliance issues if you are medical practitioner in Canada and in the United States in some cases. File Uploads This premium feature may store files on your server indefinitely. You may turn off this feature in the settings if you have this module installed. GDPR There is a special field you can add to your forms called GDPR which will automatically make your forms GDPR compliant. HIPAA FormLift is NOT HIPAA compliant by default. You can make FormLift HIPAA compliant by installing an SSL certificate and disabling “Session Tracking” and “Saved Submissions”. API Connection OAuth : If you are connected to Keap via the Oauth method, your authentication Tokens are passed through an intermediary server “webhook.site” No personal information is ever passed through this medium however. Hence all API calls made with FormLift are communicated to Keap Directly with the exception of refreshing tokens and the initial authentication request. API Usage: Anonymous API usage statistics are collected if you use the OAuth Method. Legacy: If you are connected to Keap via the Legacy Method, all API calls are made to Keap directly and “webhook.site” is not involved. No usage statistics are collected. Methods: The only API methods FormLift uses are for the uploading of Files to a contact’s FileBox and the retrieval of WebForms. FormLift will never “retrieve” information from Keap. Keap or other CRMs Keap or whichever CRM you use with FormLift is the primary holder of Information collected with FormLift. To ensure you are compliant in regard to the storage of information, please consult them if it’s beyond the scope of the above.

This plugin preserves the user-generated HTML markup in the TinyMCE editor. Unlike other plugins this one allows developers to work in the HTML tab AND end-users to work in the WYSIWYG Visual tab at the same time! No longer will your HTML markup be completely munged into an unrecognizable form when you switch between those tabs. And you don’t have to hang your users/editors out to dry when you hand off the project with a disabled Visual tab. IMPORTANT: Please read the installation instructions carefully. If you have existing content it will not render properly after activating this plugin until you use the Fix It Tools. (One user didn’t read or follow these steps and panicked thinking I ruined their website.) It also supports HTML5 Block Anchor tags in addition to other HTML5 elements, something that is currently not supported in WordPress via any existing plugins. Version 1.5 will probably be the last version I release for a while since my daughter will be born soon. I’ve added support for full JavaScript code blocks in the HTML tab. They are compatible and preserved when switching to Visual mode. This rounds out the support for almost complete html preservation, with full use of the WYSIWYG editor. And you don’t need to wrap comment codes around it per the recommendations located here: https://codex.wordpress.org/Using_Javascript but you can leave them in if you want. Version 1.4 was just a minor patch release. User @denl noticed a problem with the plugin CataBlog which implements its own administrative management features by disabling the ‘show_ui’ flag for its custom post type. I was ignoring any custom post type that didn’t have a GUI, but it was an unecessary filter that probably limited other plugins. This fix allows any post type that supports the TinyMCE editor to be “fixed” using the tools under Admin > Settings > Writing. Since version 1.3 you can now use inline CSS and JavaScript in the HTML editor and everything should be preserved. To be clear, this applies to tags only, like onclick events and style definitions – not script blocks themselves. To enable this feature you must disable the wptexturize and convert_chars filters by adding the following code to your theme’s functions.php: remove_filter("the_content", "wptexturize"); remove_filter("the_content", "convert_chars"); This new feature is pretty experimental at the moment. I tried to make it compatible with wptexturize but that proved close to impossible without duplicating a lot of core code in my plugin. It’s also not compatible with TinyMCE Advanced when the “stop removing p and br tags” setting is enabled. I’ve tested it on a variety of code samples and I’m pleased with the results but if you find any content that isn’t preserved just open a support ticket and I should be able to fix it. Since version 1.2, you now have a little more control over how content is created. And most of the previous caveats to using this plugin are now resolved. You can now choose whether to use BR tags OR P tags for newlines. Even better you can use both, where one return key press injects a BR tag, and two return key presses will wrap a Paragraph tag. This is great for being able to wrap headers at specific break points all while enjoying the semantic perks of paragraphs. In addition to choosing what type of tags to use, you can also change the behavior depending on the type of post, including custom post types. So Pages can default to BR tags, and Blog Posts can default to Paragraph tags. If you have existing content that was created before activating this plugin, you can now use the Fixit feature to convert your existing content in a way that makes it render the same as before. Only use this feature (located under Admin > Settings > Writing: Fixing Existing Content) if you are installing this plugin for the first time, otherwise it will remove all of the formatted white space in your posts. Multi-line HTML comments are now supported (Thanks to @cwlee_klagroup for suggesting the working fix!) The Format drop down in the TinyMCE editor had a bug which is now fixed. It will now select “Format” if you place the cursor on a section of bare text. Currently the editor just leaves the previously selected format option in place. It’s minor but it’s good to know when you have bare text in your content. There was a fairly problematic bug in the old version where in some browsers you couldn’t change the formatting of a single line in the Visual editor if you started from scratch. Choosing a different Format option would change the entire document, with the only work around being to edit the document in HTML mode. That was bad, and somehow went unnoticed for far too long. Anyway, that is fixed now. The caveats that still remains are: With script blocks added to your HTML markup, the right arrow key does not pass over them in the Visual Tab. You can down arrow over them however so this will likely never be addressed. If you use the Paragraph tag setting for newlines there is a minor bug where it will only wrap your content in Paragraph tags if you specify Paragraph in the Format drop down or if you enter more than one paragraph of text. So if you just type one sentence and click save it will not wrap the content in Paragraph tags. I tried to fix this but ran out of my allotted time working on other core issues. Should be fixed in the next release. For performance reasons, it will only preserve spaces if 4 spaces are used consecutively – i.e. an expanded tab in developer terms. It will not preserve intra-tag white space like . If you do add 4 or more spaces inside of an element tag it will corrupt the markup and mangle the output. But as this is intended for developer edits, this should be an extreme rarity given the habit is virtually non-existent in development communities. PRE tags are not affected and behave as you would expect, however due to how browsers parse tags, the first newline in the content of a PRE tag will be wiped out unless it is padded with either another new line or multiple spaces. CODE tags are not preserving white space at all, and when wrapped with PRE tags white space is still removed. I’m working to resolve this problem. Arbitrary section