FlyingPress 4.14.4 NULLED

4.14.4 – 25 June, 2024​

• Improvement: New logo and color scheme to match our updated branding

4.14.2 – 12 June, 2024​

• Fix: Pages got downloaded as gzipped file in OpenLiteSpeed server post v4.14 release
• Fix: FlyingCDN was failing to cache pages due to missing headers in OpenLiteSpeed

4.14.1 – 11 June, 2024​

• Fix: Double GZIP Compression of cached files resulted in gibberish output for some websites post v4.14
• Fix: YouTube placeholder images were not lazily loaded post v4.13.5

4.13.3 – 13 April, 2024​

• Improvement: Better used CSS detection

= 4.11.0 - 18 March, 2024 =

- New: WP CLI commands for preload cache, purge pages , purge everything and activate license , try `wp flying-press`
- Improvement: Efficient logic for checking if WP_CACHE constant is set
- Improvement: Adjusted FlyingPress controls after custom css toggle in Elementor
- Improvement: Higher loading priority for preloaded fonts
- Improvement: Upgraded assets minification library
- Fix: Adding display=swap to encoded Google font URLs resulted in invalid font
- Fix: A warning while fetching WooCommerce product categories

= 4.10.3 - 01 March, 2024 =

- Fix: Error rendering some blocks inside the Gutenberg block editor after v4.10
- Fix: Cache file name change via filter hook resulted in invalid cache file generation

= 4.10.2 - 29 February, 2024 =
- Improvement: Lazy Render toggle for Elementor legacy section elements
- Fix: Post v4.10 release , preload not starting after purging everything

= 4.10.1 - 28 February, 2024 =
- New: Filter hook to disable FlyingPress footprint
- Improvement: Enhanced SVG compatibility for the new Lazy Render
- Fix: A warning regarding cache include queries

= 4.10 - 27 February,2024 =

- Removed: CSS Lazy Render based on content visibility
- New: JS Lazy Render, read more in [docs](https://docs.flyingpress.com/en/article/lazy-render-elements-up666e/)
- New: CDN cache headers to support wide range of CDN/proxy cache providers
- Improvement: Enhanced and more memory efficient capturing of elements in the HTML parser
- Fix: A warning of invalid argument supplied to foreach