Flyouts – Off Canvas Custom Content for WordPress Changelog
Every recorded version, newest first, with what changed in each one.
Latest 1.4.215 versions
Undated · 15 versions
1.4.2
Latest
2 improvements2 fixes
Improved
CMB2 Library to v2.7.0
Updater script to v1.4
Fixed
In some cases, a PHP error would throw checking for the Flyout menu.
In some cases, mobile webkit browsers would crash if using over 20 active flyouts due to using the -webkit-overflow-scrolling CSS property.
1.4.1
1 fix
Fixed
Submenu icon indicators were missed in replacing to SVG from previous update.
1.4
2 improvements2 changes
Improved
Update CMB2 Library to v2.4.2
Update Plugin updater library to v4.4 and will check via HTTPS.
Changes
Replace font icons with SVG
Minor CSS adjustments
1.3.9
2 improvements
Improved
Update CMB2 Library to v2.3.0
Compatibility with PHP v7.2
1.3.8
1 new2 improvements1 removed4 changes
New
Add escaping to translation strings
Improved
Updated CMB2 Library to v2.2.6.2
Update translations strings
Removed
Removed the CMB2 alpha colorpicker add-on as it is now merged into CMB2 core.
Changes
Minor adjustments to CSS
Move sidr.js to only enqueue when Flyouts are available within the page.
Attempt to address iOS behavior with the page still being able to scroll while a Flyout is open.
Moved codebase to OOP for future re-write.
1.3.7
3 improvements
Improved
Compatibility with WP v4.9 - colorpicker fields where having too much fun...
jw-cmb2-rgba-picker.js to v2.1.2
CMB2 Library to v2.2.6
1.3.6
1 fix
Fixed
Flyout triggers that were set to a page link were not working due to a bug introduced in the previous update.
1.3.5
4 improvements2 fixes
Improved
CMB2 Library to v2.2.5.3
CMB2 Select2 library to v3.0.3
compatibility with BNE Theme Framework v1.4.8+
Move inline JS to the footer using wp_add_inline_script.
Fixed
Changed the output crop used for trigger images to full from large.
On iOS, the close button was going wonkers due to a webkit/iOS bug with absolute positions.
1.3.4
1 improvement1 fix2 changes
Improved
CMB2 library to v2.2.1.
Fixed
If using a Flyout trigger as a link to a page, the closing container div was missing.
Changes
Enhance: Replace the close button within the Flyout from an anchor to a div tag to prevent possible conflicts with ajax plugins.
Enhance: Adjust where core files are included on admin and frontend pages.
1.3.3
1 new2 changes
New
Replaced the Flyout and Trigger color background options with an RGBA color picker allowing transparency in the background color.
Changes
Enhance: Adjust conditional logic in admin fields, specifically in regards to the trigger type option.
!! Reminder: On October 5, 2015, an important upgrade was required in v1.3.0 to move legacy flyout settings into their new fields in the database that are currently used since then. Make sure you have done this as that upgrade script and legacy Flyout code will be removed from the plugin. This will occur within or after April 2016 providing you a 6 month window from the original announcement. If you have already done this or did not use Flyouts prior to October 5, 2015, then you have nothing to worry about.
1.3.2
1 fix
Fixed
Fix a bug where oembeds were not showing in the flyout.
1.3.1
1 change
Changes
Attempt to correct an issue that caused a few users experiencing a server 500 (white screen) when activating the plugin.
1.3
5 new2 improvements1 removed7 changes
New
Added option to allow Flyouts Triggers to open another page (URL) instead of a Flyout (Found in Trigger Settings).
Added option to restrict Flyouts based on User Roles (Found in Flyout Settings).
Add a global class, "flyout-close", to allow closing an active Flyout from any element. Ex: Close Me
Add support to extend page restrictions for additional post types using the filter bne_flyout_cmb_get_post_types.
Add support to extend custom restrictions even further such as page templates, archive pages, a page meta_key, user ID, etc by using the filter bne_flyout_custom_restrictions.
Improved
Improved overall performance by 40%
Improve translation strings.
Removed
Removed ACF library dependency
Changes
Note #1: This is a major update and requires an update to existing Flyout meta data. This release removes the internal ACF Pro library. By removing the ACF library, we have reduced dependencies, reduce compatibility issues with other plugins, reduce plugin size by 75%, and improved performance by 40%. This is an important change going forward. Upon updating your plugin, you will see notice to upgrade your existing Flyouts to the new field arrays.
Note #2: Before applying this update and upgrading the flyout fields, please take a backup of your database and or test in a staging environment first. In addition, if you are using a management system such as MainWP, you need to go into the site and finish the upgrade as it is not automatic and requires an admin action.
= CORE =
Decreased plugin sized by 75%
Moved Flyout content to the default WP Editor.
Adjust responsive visibility break points to better match responsive standards (480px and 768px).
Moved options out of a tabbed UI in favor of separated metaboxes.
1.2.9
1 fix
Fixed
WordPress v4.3 support and compatibility.
1.2.8
1 new2 fixes
New
If using a custom menu and content within a Flyout, you can now specify the order they appear.
Fixed
Image Triggers will now include alt meta information.
In certain cases, inline CSS styles were being removed from the HTML tag when a flyout closes.
Changelog published by the developer, in their original language.
