= 5.6 - Aug 1 2023 = * ๐ŸŒฑ**Page Optimize** New JS Delay Includes option. (Mitchell Krog/Gerard Reches/Ignacy Hoล‚oga) * **Crawler** Sitemap can use search for URL now. * **GUI** Restrict the scope of balloon CSS rules to avoid conflicts. (#567) * **Object Cache** Detect Memcached in more situations. (#568) * **API** Support `litespeed_purged_front` hook. (Umberto Fiorelli) = 5.5.1 - Jul 19 2023 = * ๐Ÿž**Image Optimization** Fixed a bug where WebP replacements couldn't be pulled without optimizing the original images. * ๐Ÿž**Image Optimization** Invalid images will now be removed when sending requests to the server. (#138993) * **Cloud** Added support for error codes `unpulled_images` and `blocklisted`. (Tynan) = 5.5 - Jun 20 2023 = * ๐ŸŒฑ**Crawler** Can now use multiple sitemaps. (Tobolo/Tim Nolte) * ๐ŸŒฑ**Crawler** Now runs asynchronously when manually invoked. * ๐ŸŒฑ**Crawler** Now runs asynchronously when invoked from cron. * ๐Ÿž**Crawler** Fixed the realtime status bug when crawling. * **Crawler** Summary page now displays server load. (Ruikai) * ๐Ÿž**Page Optimize** Fixed an issue where UCSS could not be generated for error pages. (james58899) #556 * ๐ŸŒฑ**Image Optimize** Now pulls images asynchronously. * **Image Optimize** Now prevents concurrent requests via a locking mechanism. * **Image Optimize** The process can now bypass invalid image records and continue. * ๐Ÿž**Image Optimize** Fixed an issue where images ready for optimization might have to wait for new images to be added before sending the request. * **Cloud** Replaced dashboard links with login/link to my.quic.cloud actions. * **GUI** Added indicators to show when certain options are passively enabled by Guest Mode. * **Htaccess** Added a noabort rule to support asynchronous crawling. * **Htaccess** The "Do Not Cache User Agents" option is now case-insensitive. (Ellen Dabo) * **General** The "Server IP" option now allows IPv4 format only. (Ruikai) * **Misc** Every page's closing HTML comments now displays UCSS/CCSS status. * **Object** Fixed a warning for null get_post_type_object. * **Object** Object_Cache::delete now always returns a boolean value. * **Cache** Fixed advanced-cache.php file warnings for WordPress versions less than 5.3. * **Debug** Added debug logging to record the plugin's total processing time. * **API** HTML minification can now be bypassed via the litespeed_html_min filter. = 5.4 - Apr 19 2023 = * **Image Optimize** Refactored DB storage for this feature. * **Image Optimize** Reduced DB table size. * **Image Optimize** Existing `img_optm` DB tables will have their data gradually transitioned to the new storage format with this update. Once an `img_optm` table is empty, it won't be used anymore. * **Page Optimize** Enabled WebP support for Googlebot User Agent. = 5.3.3 - Feb 22 2023 = * **Page Optimize** Excluded Jetpack stats JS. * **DB Optimize** Fixed DB Optm SQL for revision postmeta. * **Cache** Fixed an undefined array key warning. * **Purge** Prevented undefined array key warning when widgets are disabled. * **Object** Fixed dynamic property deprecation warnings. * **Admin** Safely redirect to homepage if referer is unknown. * **Activation** Check that item slug exists first. * **Cache** Prevented cache header to send globally if header part already closed. * **CSS** Improved string handling for CSS minifier. * **Debug** Fixed undefined array key warnings. * **Misc** Fixed implicit conversion in random string generation function `Str::rrand`. = 5.3.2 - Jan 10 2023 = * **Object** Fixed object cache lib incr, decr functions (thanks bdrbros/DANIEL) #516 * **Database Optimize** Database optimizer now handles postmeta when cleaning revisions #515 * **Cache** Made nocache the default for 4xx/5xx response codes. * **Cache** Default cache TTL settings removed for 403 response code, changed to 10 mins for 500 response code. * **GUI** Added a description for the redetect nodes function. * **GUI** Added a description for the refresh button sync function. = 5.3.1 - Dec 12 2022 = * **CLI** Presets feature is now usable from the CLI. (xLukii) * **CLI** Added 'import_remote' for litespeed-option to enable importing options from URLs. (xLukii) * **Cache** Added LiteSpeed headers to site health check for full page cache. * **Crawler* Fixed unauthorized crawler toggle operation. (#CVE-2022-46800) * **UCSS** Fixed a bug where items weren't added back to the UCSS queue after purging. * **Page Optimize** Fixed a bug where generated CSS would return 404 after upgrading via CLI. * **3rd** Fixed a bug where a WooCommerce session doesn't exist when checking cart, notices (Jason Levy/Gilles) * **GUI** Made LiteSpeed admin notice icon grayscale to avoid distraction. (martinsauter) * **GUI** Fixed RTL style for notification icon. * **API** Added a new hook `litespeed_optm_uri_exc` to exclude URI from page optimization. * **API** Excluded `.well-known` path from page optimization. = 5.3 - Oct 31 2022 = * ๐ŸŒฑ**Presets** New `Presets` feature and menu item. * ๐ŸŒฑ**UCSS** New option `UCSS File Excludes and Inline` to increase page score. (Ankit) * **UCSS** When UCSS is purged, automatically append URL to UCSS generation queue. (Ankit) * **Page Optimize** Removed a redundant `defer` attribute from Lazy Load image library usage. (#928019) * **Image Optimize** Dropped `Create WebP Versions` setting. Will automatically enable when `Image WebP Replacement` is activated. * **Cloud** Fixed a bug where internal updates were delayed for API keys. * **Cloud** Improved auto alias feature by waiting for second request from alias domain validation before removing a pending alias. * **Purge** Automatically Purge All when plugin auto update is done. * **Purge** Fixed a potential PHP8 error that occurred when removing unused widgets. (acsnaterse) * **Cache** Fixed an infinite 301 redirection caused by UTM-encoded link. * **CLI** Added syntax examples for values that include line breaks (xLukii) * **CLI** Purge requests will now be included with the original request to avoid potential CSS/JS 404 issues. * **ESI** Check all user roles for cache vary and page optimization excludes. * **GUI** Added a LiteSpeed icon to admin message banners to indicate the banners are from our plugin. (Michael D) * **Crawler** Fixed a cache-miss issue that occurred when Guest Mode was ON and WebP Replacement was OFF. * **3rd** Remove WooCommerce private cache. * **3rd** Removed LiteSpeed metabox from ACF field group edit page. (keepmovingdk) = 5.2.1 - Sep 7 2022 = * ๐Ÿž**Core** Fixed a fatal error that occurred when uninstalling. (#894556 Hostinger) * **Dash** Show partner info on the dashboard for partner-tier QC accounts. * **UCSS** Auto-purge UCSS on post update. (Ankit) * ๐Ÿ•ธ๏ธ**Crawler** Respect the `LITESPEED_CRAWLER_DISABLE_BLOCKLIST` constant for unexpected results too. (Abe) = 5.2 - Aug 17 2022 = * ๐ŸŒฑ**UCSS** Added UCSS message queue to improve service quality and reliability * ๐Ÿž**VPI** Fixed conflict w/ image lazyload; used HTML before image lazyload to avoid invalid `data:base64` results. * **VPI** Changed VPI Cron default setting to OFF. * **VPI** Automatically resend requests when VPI result contains invalid `data:` image value. * **Conf** Fixed an issue with URI Excludes, where paths using both ^ and $ were not correctly excluded (Eric/Abe) * **Conf** Auto corrected `WP_CONTENT_URL` protocol if it was explicitly set to `http://`. * **Cloud** No longer sync the configuration to QUIC.cloud if configuration is unchanged. * **Cloud** Appended home_url value into synced configuration data for wp-content folder path correction. * ๐Ÿ•ธ๏ธ**Crawler** Improved compatibility with server `open_basedir` PHP setting limit when detecting load before crawling. (Tom Robak/mmieszalski) = 5.1 - Aug 1 2022 = * ๐ŸŒฑ**Toolbox** Debug log can now show Purge/Crawler logs as well. (Tynan) * **UCSS** Prepared for future message queue. * **UCSS** Moved UCSS class to its own file. * **3rd** Added 3rd-party support for WC PDF Product Vouchers. (Tynan) * **Core** Fixed potential PHP warning when saving summary data. (Sarah Richardson) * **Purge** Purge can now clear the summary correctly. (Kevin) * **VPI** Added `queue_k` to API notification. = 5.0.1 - Jul 27 2022 = * ๐Ÿž**Cloud** Fixed a potential PHP error that could occur with the cloud service summary. (Bruno Cantuaria) * **3rd** Added Autoptimize back to compatibility list. = 5.0.0.1 - Jul 26 2022 = * ๐Ÿ”ฅ๐Ÿž**Cloud** Fixed an issue with the cloud request timestamp update which causes a usage sync failure. (great thanks to Kevin) = 5.0 - Jul 25 2022 = * ๐ŸŒฑ**VPI** Added Viewport Images feature to LiteSpeed Options metabox on Post Edit page. * ๐ŸŒฑ**CDN** Added Auto CDN Setup feature for simple QUIC.cloud CDN setup. (Kevin) * ๐ŸŒฑ**Page Optimize** Automatically cache remote CSS/JS files when fetching for optimization (Lauren) * ๐ŸŒฑ**Cache** Added LiteSpeed Options for page-level cache control on Post Edit page. (denisgomesfranco) * ๐ŸŒฑ**Cloud** Auto Alias feature. * ๐ŸŒฑ**Debug** Added `Debug String Excludes` option. (Hanna) * ๐ŸŒฑ**UCSS** Added `Purge this page - UCSS` option to Admin Bar dropdown menu. (Ankit) * ๐ŸŒฑ**Guest** Added `litespeed_guest_off=1` URL query string parameter to bypass Guest Mode. (cbdfactum) * ๐Ÿž**Page Optimize** Fixed an issue where CSS anchors could be wrongly converted to a full path when minifying. (Tynan) * **Page Optimize** Bypass CCSS/UCSS generation when a self-crawled CSS resource returns a 404 code. (Abe) * **Object** Allow `LSCWP_OBJECT_CACHE` predefined to turn off Object Cache. (knutsp) * **Data** Fixed an issue where empty version tags in the database repeatedly toggled the upgrade banner and reset settings to default. * **Purge** Fixed an issue where the site's index page could be purged upon deletion of an unviewable post. (Kevin) * **Toolbox** Added `View site before optimization` button under `Debug` tab. (Ryan D) * **Admin** Switch to using the `DONOTCACHEPAGE` constant to indicated WP-Admin pages are not cacheable. * **Admin** Moved no-cache header to very beginning to avoid caching unexpected exits. * **Cloud** Added message queue service for VPI. (Abe) * **Cloud** Bypassed 503 error nodes from node redetection process. (Abe) * **Cloud** Fixed a failure to detect `out_of_quota`. (Lauren) * **Cloud** Added ability to display dismissable banners generated by QUIC.cloud. * ๐Ÿ•ธ๏ธ**Crawler** Added realtime load detection before crawl. * ๐Ÿ•ธ๏ธ**Crawler** Adjusted crawler behavior for Divi pages to allow for Divi's CCSS generation process. (miketemby) * ๐Ÿ•ธ๏ธ**API** PHP constant `LITESPEED_CRAWLER_DISABLE_BLOCKLIST` and filter `litespeed_crawler_disable_blocklist` to disable blocklist. (Tobolo) * **CDN** Automatically add a trailing slash to `CDN URL` and `Original URLs` if user didn't provide one. (Lucas) * **Cache** When a URL redirects to a URL with a query string, consider these as different for caching purposes. (Shivam) * **Media** Added ability to disable lazyload from the LiteSpeed Options metabox on Post Edit page. * **Media** Added new default values to `WebP Attribute to Replace` setting for WPBakery and Slider Revolution. (JibsouX) * **Image Optimize** Dropped redundant `Page Speed` user agent when serving WebP images. (serpentdriver) * **GUI** Fixed an issue where manually dismissable admin messages were instead being treated as one-time messages. (Tynan Beatty) * **GUI** Fixed an issue where subsequent admin alerts would overwrite existing alerts in the queue. (Kevin/Tynan) * **GUI** Updated time offset in log. (Ruikai #PR444 #PR445) * **GUI** Added `litespeed_media_ignore_remote_missing_sizes` API description. * **CCSS** Fixed an issue where CCSS was unexpectedly bypassed if `CSS Combine` was OFF and `UCSS Inline` was ON. (Ruikai) * **Debug** Added response headers to debug log. (Kevin) = 4.6 - Mar 29 2022 = * **Page Optimize** Improved compatibility for JS Delay. * ๐Ÿž**Page Optimize** Fixed an issue for network subsites that occurred when only CSS/JS Minify are enabled. * **Localization** Added query string compatibility for Resource URLs. * **Vary** Fixed a potential PHP warning when server variable `REQUEST_METHOD` is not detected. * **Cache** Guest Mode now respects Cache Excludes settings. * **GUI** Added warning notice when enabling `Localize Resources` feature; each localized JS resource requires thorough testing! * **GUI** Fixed a PHP Deprecated warning that occurred with the Mobile Cache User Agent setting on PHP v8.1+. (jrmora) * **Conf** Removed Google related scripts from default `Localization Files` value. * **Media** WordPress core Lazy Load feature is now automatically disabled when LiteSpeed Lazy Load Images option is enabled. (VR51 #Issue440) * ๐Ÿž**API** Filter `litespeed_ucss_per_pagetype` for UCSS now also applies to CSS Combine to avoid UCSS failure. (Ankit) * **API** Added a filter `litespeed_media_ignore_remote_missing_sizes` to disable auto detection for remote images that are missing dimensions. (Lucas) = 4.5.0.1 - Feb 24 2022 = * ๐Ÿ”ฅ๐Ÿž**Media** Fixed an issue where lazy-loaded images would disappear when using custom CSS image loading effects. = 4.5 - Feb 23 2022 = * ๐ŸŒฑ**Page Optimize** Localization is back. * **Guest** Fixed organic traffic issue as different browsers may fail to set `document.referrer`. * **Image Optimize** Improved wp_postmeta table compatibility when gathering images. (Thanks to Thomas Stroemme) * ๐Ÿž**Page Optimize** Fixed a potential CSS/JS 404 issue for existing records that have been marked as expired. * **ESI** `LITESPEED_ESI_OFF` now affects `litespeed_esi_url` API filter too. * **Guest** Added a check to determine if Guest Mode is blocked by a third-party, and display warning if it is (Ruikai) * **Guest** To support WP sites with multiple domains, Guest Mode detection URL no longer uses domain. * **Report** Network now shows Toolbox page when having a large number of subsites. * **DB Optimize** Reduced default subsites count from 10 to 3 under Network Admin -> DB Optimize page to avoid timeout. * **Cloud** Fixed potential `lack_of_token` error when requesting domain key for cases where local summary value was not historically included in the array. * **Cloud** Fixed a PHP fatal error that occurred when encountering a frequency issue under CLI. (Dean Taylor #Issue410) * **Avatar** Force gravatar cache refresh in browsers and on CDN (rafaucau #PR430) * **API** New filter `litespeed_purge_ucss` to purge a single page UCSS. (#376681) * **API** New filter `litespeed_ucss_per_pagetype` for UCSS per page type generation. (Ankit) * **GUI** Replaced some GUI text and settings with more inclusive language (kebbet #PR437 #PR435) * **3rd** Excluded `WP Statistics` from inline JS optimize. (Ryan D) * **3rd** Added API filter `litespeed_3rd_aelia_cookies` for Aelia CurrencySwitcher. * **Media** Updated image lazyload library to 17.5.0. = 4.4.7 - Jan 11 2022 = * **Page Optimize** Dropped `Inline Lazy Load Images Library` option. Now will always inline lazyload library. (Ankit) * **3rd** Prevented JavaScript files from being appended to Rank Math SEO sitemap. * **Purge** Dropped default stale purge when purging a post. * **Cloud** Dropped unused API calls. * **Cloud** Dropped redundant IP validation in API calls. = 4.4.6 - Dec 27 2022 = * **Guest** Restored `document.referrer` for organic traffic purposes when Guest Mode is enabled. (michelefns) * **Image Optimize** Fixed a potential PHP notice when uploading images in WP w/ PHP7.4+. (titsmaker) * **ESI** Fixed an issue where ESI settings were not updated on customized widgets(#422 Abe) * **3rd** Reverted ESI Adminbar change on Elementor front pages for backward compatibility (#423 Abe) * **3rd** Fixed an issue where disabling ESI potential caused a PHP warning when using `Perfmatters`. (Jeffrey Zhang) * **Misc** Check whether HTTP_REFERER is set or not before using it in Router class. (#425 Abe) = 4.4.5 - Dec 1 2021 = * **Data** Fixed potential PHP notice when generating CSS/JS optimized files w/ PHP v7.4+. (Sarah Richardson/silencedgd/slr1979) * **API** Added `LITESPEED_ESI_OFF` constant to disable ESI, when defined before the WP `init` hook. * **API** Added `LSCWP_DEBUG_PATH` constant to specify debug log path. (khanh-nt) * ๐Ÿž**GUI** Fixed an issue where admin messages were not displayed. (Daniel McD) * **CDN** Used WP remote function to communicate w/ Cloudflare per WP guidance. * **3rd** Added compatibility for Perfmatters plugin's script manager (#417 Abe) * **3rd** Added compatibility for Elementor's Editor button when ESI is on (#418 Abe) = 4.4.4 - Nov 23 2021 = * **Page Optimize** Delay deletion of outdated CSS/JS files for a default of 20 days to avoid 404 errors with cached search engine copies. * **Cache** When caching, no longer send a purge request for CSS/JS removal to avoid cache engine conflicts. * ๐Ÿž**Core** Optimized SQL queries while autoloading if expected options are missing; reduced by 7 and 3 queries on backend and frontend respectively. (#396425 Jackson) * **Page Optimize** Fixed a 404 issue that occurred when upgrading the plugin manually, with a package upload or through the plugin manager. (Tobolo/Maล‚gorzata/Abe) * **API** Added `litespeed_ccss_url` and `litespeed_ucss_url` API to manipulate the request URL for CCSS and UCSS. * **REST** Fixed a potential warning when detecting cacheable status on REST call. (rafaucau) * **OLS** Fixed an issue where the `COOKIEHASH` constant was undefined when used with OpenLiteSpeed as an MU plugin or with network activation. * **3rd** Sanitized POST data for nextgengallery. * **Cloud** Sanitized GET data when linking to QUIC.cloud. (#591762 WPScan) = 4.4.3 - Oct 13 2021 = * ๐Ÿž**Media** Fixed an issue where WebP is served erroneously under Guest Mode on older versions of Safari. (hash73) * ๐Ÿž**Media** Reverted regex change to fix `Lazy Load Image Parent Class Name Excludes` failure. (thpstock) * **Purge** Disabled `Purge Delay` in the optimization process by default. * **Conf** Dropped `.htaccess Path Settings` options for security concern. (WP) * **Conf** Dropped `CSS HTTP/2 Push`/`JS HTTP/2 Push` options. (Kevin) * **Conf** Set `Guest Optimization` default to OFF. * **Conf** Set `CCSS Per URL` default to OFF to avoid consuming more quota than intended after upgrade to v4. (n111) * **Object** Fixed an issue with Object Cache warnings during upgrade, when Guest Mode is enabled. * โ˜๏ธ**Cloud** Fixed an issue with PHP notices when inquiring about quota usage for a service not currently in use. * **GUI** Added GO detail warning. (n111) * **GUI** Moved "quota will be still in use" warning from Guest Mode to Guest Optimization section. * **API** Added `LITESPEED_CFG_HTACCESS` PHP Constant to specify .htaccess path. * **API** Added `litespeed_qs_forbidden` hook to bypass `?LSCWP_CTRL=` query string. (minhduc) * **API** Added `litespeed_delay_purge` hook to delay the following Purge header until the next request. * **API** Added `litespeed_wpconfig_readonly` hook to disable `WP_CACHE` constant update based on the wp-config.php file. (#633545) = 4.4.2 - Sep 23 2021 = * **Purge** In order to clear pages containing 404 CSS/JS, the purge header will always be sent even in cases where purge must be delayed. * ๐Ÿž**Purge** Fixed a potential PHP warning caused when generating different optimized filenames. * **Cron** Dropped unnecessary HTML response in cron which sometimes resulted in wp-cron report email. (Gilles) * **Page Optimize** Purge caused by CSS/JS file deletion will now be silent. * **Page Optimize** Fixed an issue where the homepage failed to purge when addressing the 404 CSS/JS issue. * **Avatar** Fixed potential localized Avatar folder creation warning. (mattk0220/josebab) * **API** Added filter `litespeed_optm_html_after_head` to move all optimized code(UCSS/CCSS/Combined CSS/Combined JS) to be right before the `` tag. (ducpl/Kris Regmi) * **Debug** Under debug mode, cache/purge tags will be plaintext. = 4.4.1 - Sep 16 2021 = * ๐Ÿž**ESI** Fixed ESI failure on non-cached pages caused by `DONOTCACHEPAGE` constant. * ๐Ÿž**Page Optimize** Fixed an issue where the minified CSS/JS file failed to update when the file was changed. (ceap80) * ๐Ÿž**Page Optimize** Fixed an issue where the combined CSS/JS file randomly returned a 404 error when visiting the same URL with different query strings. (Abe) * **API** Added `litespeed_const_DONOTCACHEPAGE` hook to control the cache-or-not result of the `DONOTCACHEPAGE` constant. = 4.4 - Sep 8 2021 = * ๐ŸŒฑ**Crawler** Added the ability to enable or disable specific crawlers. (โญ Contributed by Astrid Wang #PR390) * ๐ŸŒฑ**UCSS** Added `UCSS Inline` option. (Ankit). * ๐ŸŒฑ**UCSS** Added `UCSS URI Excludes` option. (RC Verma). * ๐Ÿž**Page Optimize** Fixed an issue where combined CSS/JS files would potentially return 404 errors after a Purge All. (Special thanks to Abe & Ruikai) * **Page Optimize** Minimized the potential for 404 errors by query string when Purging All. * **Page Optimize** Dropped redundant query strings for minified CSS/JS files. * **Conf** Ugrade configuration safely to avoid the issue of new functions not being found in old codebase. * **Conf** Configuration upgrade process now adds a notification to admin pages and disables configuration save until upgrade is complete. (Lisa) * **JS** Fixed an issue where JS Defer caused a `litespeed_var_1_ is not defined` error when enabled w/ ESI options. (Tobolo) * ๐Ÿž**JS** Fixed an issue where `JS Delay` doesn't work for combined JS when `JS Combine` is enabled. (Special thanks to Joshua & Ankit) * **JS** `JS Delay` now will continue loading JS, even if there is an error in the current JS loading process. * ๐Ÿž**CCSS** If CCSS fails to generate, Load CSS Asynchronously will now be disabled. (Stars #54074166) * ๐Ÿž**UCSS** If UCSS generation fails the generated error will no longer be served inside the file. (Ryan D) * **Log** Updated the Debug log to use less code for prefix. * **3rd** Always respect `DONOTCACHEPAGE` constant definition to fix DIVI dynamic css calculation process. = 4.3 - Aug 16 2021 = * **UCSS** Separated UCSS Purge from CCSS Purge. (โญ Contributed by Alice Tang #PR388) * ๐Ÿž**Cloud** Fixed an issue where CCSS/UCSS quota data failed to update locally. * **Cloud** Added server load as a factor when detecting node availability. * **Cloud** Improved the speed of checking daily quota and showing the related error message. * **Cloud** Added ability to re-detect node availability if the current node is responding w/ a heavy load code. * **Cloud** CCSS/UCSS/LQIP queue now exits immediately when quota is depleted. * **Cloud** Replaced separate `d/regionnodes` with a single `d/nodes` in the node list API for image optimization. * **LQIP** Fixed an issue with LQIP network compatibility. (โญ Contributed by Alice Tang #PR387) * **GUEST** JS no longer preloads for Guest Optimization. (Ankit) * ๐Ÿž**Data** Fixed an issue where deleting the `cssjs` data folder causes a failure in the upgrade process. (Joshua #PR391) * **GUI** Fixed a potential dashboard PHP warning when no queue existed. (jrmora) * **GUI** Added daily quota on dashboard. * **GUI** Added downgrade warning to Toolbox -> Beta Test. * **GUI** Tuned `.litespeed-desc` class to full width in CSS. * **Conf** `Preserve EXIF/XMP data` now defaults to ON due to copyright concerns. (Tobolo) * ๐Ÿž**3rd** Fixed a PHP warning when using Google AMP w/ /amp as structure. (thanhstran98) = 4.2 - Jul 29 2021 = * **Cloud** Auto redirect to a new node if the current node is not available anymore. * **Cloud** Combined CCSS/UCSS to sub services of Page Optimization. * **Cloud** Added a daily quota rate limit to help mitigate the heavy service load at the beginning of the month. * **Cloud** Cached the node IP list in order to speed up security check. (Lucas) * ๐Ÿž**GUEST** Fixed an issue where Guest Mode remained enabled even when the UA setting is empty. (Stars) * **GUEST** Guest Mode will no longer cache POST requests. * **UCSS** Purging CSS/JS now purges the UCSS queue as well, to avoid failure when generating UCSS. * **UCSS** Separated service entry `UCSS` from `CCSS`. * **CCSS** Simplified `load_queue/save_queue/build_filepath_prefix` functions. (โญ Contributed by Alice Tang #PR373) * **CCSS** If CCSS request fails, details are now saved in the CSS file. * **CCSS** Renamed CCSS ID in inline HTML from `litespeed-optm-css-rules` to `litespeed-ccss`. (Alice) * **Page Optimize** CCSS/UCSS now supports Cloud queue/notify for asynchronous generation. * **Page Optimize** Simplified CCSS/UCSS generation function. * **Page Optimize** Added the ability to cancel CCSS/UCSS Cloud requests. * **Page Optimize** Unnecessary quesry strings will now be dropped from CSS/JS combined files. * **Crawler** Reset position now resets crawler running status too. * **REST** Cloud request to REST will now detect whether an IP in in the Cloud IP list for security reasons. * **Object** Enhanced Object Cache compatibility for `CONF_FILE` constant detection. * **API** Added shorter alias `litespeed_tag` and other similar aliases for Cache Tag API. * **API** Renamed `LITESPEED_BYPASS_OPTM` to `LITESPEED_NO_OPTM` for Page Optimization. * **Toolbox** Dropped v3.6.4- versions in Beta Test as they will cause a fatal error in downgrade. * **GUI** Added shortcut links to each section on the Dashboard. * **GUI** Added UCSS whitelist usage description. (wyb) * **GUI** Showed the default recommended values for Guest Mode UA/IPs. * **3rd** Fixed AMP plugin compatibility. (โญ Contributed by Alice Tang #PR368) * **3rd** Bypassed all page optimization including CDN/WebP for AMP pages. * **3rd** Improved compatibility with All in One SEO plugin sitemap. (arnaudbroes/flschaves #Issue372) * **3rd** Added wsform nonce. (#365 cstrouse) * **3rd** Added Easy Digital Download (EDD) & WP Menu Cart nonce. (#PR366 AkramiPro) * **3rd** Improved compatibility w/ Restrict Content Pro. (Abe #PR370) * **3rd** Improved compatibility w/ Gravity Forms. (Ruikai #371) = 4.1 - Jun 25 2021 = * ๐ŸŒฑ**UCSS/CCSS/LQIP** Moved queue storage to file system from database wp-options table to lessen the IO load. (#633504) * ๐ŸŒฑ**3rd** Added an option to disable ESI for the WooCommerce Cart. (#358 Anna Feng/Astrid Wang) * **ESI** Fixed an ESI nonce issue introduced in v4.0. (Andrew Choi) * **Object** Used new `.litespeed_conf.dat` instead of `.object-cache.ini` for object cache configuration storage. * **Conf** Now updating related files after plugin upgrade and not just after activation. * ๐ŸŒฑ**Guest** Added a Guest Mode JS Excludes option. (Ankit/Mamac/Rcverma) * **Guest** Guest Mode now uses a lightweight script to update guest vary for reduced server load. * **Guest** Guest Mode now adds missing image dimensions. * **Guest** Guest vary will no longer update if there's already a vary in place to address the infinite loop caused by CloudFlare's incorrect cache control setting for PHP. * **Guest** Guest vary update request will no longer be sent if `lscache_vary` is already set. * **Guest** Added a Configurable Guest Mode UA/IP under the Tuning tab in the General menu. * **Guest** Guest Mode now allows cron to be hooked, even when UCSS/CCSS options are off. (#338437 Stars) * **Guest** Simplified the vary generation process under Guest Mode. * **Guest** Added a Guest Mode HTML comment for easier debugging. (Ruikai) * **Guest** Guest vary update ajax now bypasses potential POST cache. * **CCSS** Added back the options `Separate CCSS Cache Post Types` and `Separate CCSS Cache URIs`. (Joshua/Ankit) * **CCSS** CCSS/UCSS queue is now limited to a maximum of 500 entries. * **Control** The cache control constant `LSCACHE_NO_CACHE` will now have a higher priority than the Forced Public Cache setting. * **Crawler** The Crawler can now crawl Guest Mode pages. * **Crawler** Fixed a potential XSS vulnerability in the Crawler settings. (#927355) * **Crawler** The Crawler now supports a cookie value of `_null`. (Tobolo) * **Media** Updated the default value for the Responsive Placeholder SVG to be transparent. * **Media** WebP images in the background may now be served in Guest Mode. * **Media** WebP images in CSS may now be bypassed if the requesting Guest Mode client doesn't support WebP. * **Media** Fixed empty default image placeholder under Guest Mode. * ๐Ÿž**Image Optimize** Changed the missing `$_POST` to `$post_data` so the database status is properly updated. (#345 Lucas) * **Import** Export file is now readable to allow importing of partial configurations. (Ryan D/Joshua) * **Page Optimize** Fixed W3 validator errors in Guest Mode. (#61393817) * **3rd** A fatal WooCommerce error is no longer triggered by a custom theme reusing a previous LSCWP cache detection tag. * **3rd** AMP may now bypass Guest Mode automatically. * **Localize** Dropped the `Localize Resources` option as Guest Mode is a sufficient replacement. (Note: Due to user feedback during the development period, we have decided to reinstate this option in a future version.) * **Cloud** Changed the WP API url. * **Lang** Corrected a missing language folder. * **GUI** Added a CCSS/UCSS loading page visualization. (โญ Contributed by Astrid Wang & Anna Feng #PR360) * **GUI** Added a warning to indicate when Guest Mode CCSS/UCSS quota is in use. (Contributed by Astrid Wang & Anna Feng #PR361) * **GUI** Added a `litespeed-info` text color. (Astrid Wang) * **GUI** Implemented various UI/UX improvements. (Joshua/Lisa) * **GUI** Duplicate cloud service messages with the same content will only display once now. (Marc Dahl) * **GUI** Added a WebP replacement warning for Guest Mode Optimization if WebP replacement is off. * **Misc** Dropped `wp_assets` from distribution to reduce the package size. (lowwebtech) * **Misc** Increased the new version and score detection intervals. * **Misc** Optimized WP Assets images. (#352 lowwebtech) * **Debug** Dropped the redundant error_log debug info. = 4.0 - Apr 30 2021 = * ๐ŸŒฑ๐ŸŒฑ๐ŸŒฑ**Guest** Introduced `Guest Mode` for instantly cacheable content on the first visit. * ๐ŸŒฑ**UCSS** Added a new service: `Unique CSS`, to drop unused CSS from elements from combined CSS * ๐ŸŒฑ**CCSS** Added `HTML Lazyload` option. (Ankit) * ๐ŸŒฑ**CCSS** Added `CCSS Per URL` option to allow Critical CSS to be generated for each page instead of for each Post Type. * ๐ŸŒฑ**Media** Added `Add Missing Sizes` setting for improving Cumulative Layout Shift. (Fahim) * ๐ŸŒฑ**JS** Switched to new JS minification library for better compression and compatibility w/ template literals. (LuminSol) * **Media** WebP may now be replaced in CSS. * **Media** Can now drop image tags in noscript to avoid lazyload. (Abe #314 /mattthomas-photography) * **Media** Bypass optimization if a page is not cacheable. * **Image Optimize** Auto hook to `wp_update_attachment_metadata` to automate image gathering process, and to handle the new thumbnail generation after images are uploaded. (smerriman). * **Image Optimize** Repeated image thumbnails won't be gathered anymore. * **Image Optimize** Simplified the rescan/gather/upload_hook for existing image detection. * **Image Optimize** Fixed the duplicated optimize size records in the postmeta table. (Abe #315) * **Image Optimize** Allow either JSON POST request or normal form request in `notify_img`. (Lucas #313) * **Image Optimize** Optimized SQL query for better efficiency. (lucas/Lauren) * **Image Optimize** Fixed issue where rescan mass created duplicate images. (#954399) * **Image Optimize** Image optimization pie will not show 100% anymore if there is still a small amount in the unfinished queue. * **Image Optimize** WebP generation defaults to ON for Guest Mode. * **Image Optimize** `Priority Line` package now can have smaller request interval. * **ESI** Disable ESI when page is not cacheable. (titsmaker) * **ESI** Fixed an issue where Divi was disabling all in edit mode, but couldn't disable ESI. (Abe) * **ESI** ESI init moved under `init` hook from `plugin_loaded` hook. * **CDN** Add basic support for CloudFlare API Tokens (Abe #320) * **CSS** Simplified `Font Display Optimization` option. * **CSS** Fixed manual cron timeout issue. (jesse Distad) * **CSS** Inline CSS may now use `data-no-optimize` to be excluded from optimization. (popaionut) * **JS** Combined `Load JS Defer` and `Load Inline JS Defer` options. * **JS** Forced async to defer. * **JS** Moved Google Analytics JS from constant default to setting default for removal. * **JS** Fixed potential JS parsing issue caused by JS src being changed to data-src by other plugins. (ankit) * **JS** Excluded spotlight from JS optimize. (tobolo) * **CCSS** Fixed CCSS/UCSS manual cron timeout issue. * **CCSS** Only 10 items will be kept for CCSS history. * **CCSS** The appearance of CCSS Purge in the topbar menu will be determined by the existence of CCSS cache, and not the setting only. * **CCSS** To avoid stuck queues when the current request keeps failing, the CCSS queue will always drop once requested. * **CCSS** CCSS will no longer hide adminbar. * **CCSS** CCSS may now be separate for network subsites. (Joshua) * **CCSS** Gave CCSS a unique filename per URL per user role per subsite. * **CCSS** Dropped `Separate CCSS Cache Post Types` option. * **CCSS** Dropped `Separate CCSS Cache URIs` option. * **CCSS** Subsites purge Avatar/CSS/JS/CCSS will not affect the whole network anymore. * **CCSS** Implemented a better queue list for CCSS that auto collapses if there are more than 20 entries, and shows the total on top. * **CSSJS** Now using separate CSS and JS folders instead of `cssjs`. * **CSSJS** Automatically purge cache after CCSS is generated. * **Network** Dropped network CSS/JS rewrite rules. * **Cache** Send cache tag header whenever adding a tag to make it effective in the page optimization process. * **Core** Used hook for buffer optimization; Used `init()` instead of `constructor`. * **Object** Used `cls` instead of `get_instance` for init. * **Cloud** Replaced one-time message with a dismissible-only message when the domain key has been automatically cleared due to domain/key dismatch. * **API** Dropped function `hook_vary_add()`. * **API** Dropped function `vary_add()`. * **API** Dropped function `filter_vary_cookies()`. * **API** Dropped function `hook_vary()`. * **API** Dropped action `litespeed_vary_add`. * **API** Dropped filter `litespeed_api_vary`. * **API** Use `litespeed_vary_curr_cookies` and `litespeed_vary_cookies` for Vary cookie operations instead. * **API** Dropped action `litespeed_vary_append`. * **Vary** 3rd party vary cookies will not append into .htaccess anymore but only present in response vary header if in use. * **Vary** Dropped function `append()`. * **Vary** Commenter cookie is now considered cacheable. * **Crawler** Minor update to crawler user agent to accommodate mobile_detect.php (Abe #304) * **Data** Added a table truncate function. * **Data** Added new tables url & url_file. * **Data** Dropped cssjs table. * **Data** Options/Summary data is now stored in JSON format to speed up backend visit. (#233250) * **Data** Default `CSS Combine External and Inline` and `JS Combine External and Inline` to On for new installations for better compatibility. * **Purge** Fixed potential purge warning for certain themes. * **Purge** Purge will be stored for next valid visit to trigger if it is initially generated by CLI. * **Page Optimize** `CSS Combine`/`JS Combine` will now share the same file if the contents are the same. Limited disk usage for better file usage and fewer issues with random string problems. * **Page Optimize** Dropped option CSS/JS Cache TTL. * **Page Optimize** Bypass optimization if page not cacheable. * **Page Optimize** Purge CSS/JS will purge the `url_file` table too. * **Page Optimize** Optionally store a vary with a shorter value. * **Page Optimize** Removing query strings will no longer affect external assets. (ankit) * **Page Optimize** Better regex for optimization parsing. * **Page Optimize** Eliminated w3 validator for DNS prefetch and duplicated ID errors. (sumit Pandey) * **Page Optimize** New Optimization for Guest Only option under Tuning. * **Page Optimize** Now forbidding external link redirection for localization. * **Debug** Implemented a better debug format for the 2nd parameter in the log. * **GUI** Bypass page score banner when score is not detected (both 0). (ankit) * **GUI** Fixed deprecated JQuery function warning in WP-Admin. (krzxsiek) = 3.6.4 - Mar 15 2021 = * **Toolbox** Fixed Beta Test upgrade error when upgrading to v3.7+. = 3.6.3 - Mar 10 2021 = * **Core** Fixed potential upgrade failure when new versions have changes in activation related functions. * **Core** Upgrade process won't get deactivated anymore on Network setup. = 3.6.2 - Feb 1 2021 = * **Page Optimize** Fixed an issue where network purge CSS/JS caused 404 errors for subsites. * **Page Optimize** Fixed an issue where purge CSS/JS only caused 404 errors. * **Page Optimize** Added a notice for CSS/JS data detection and potential random string issue. * **Page Optimize** Limited localization resources to specified .js only. (closte #292/ormonk) * **JS** Data src may now be bypassed from JS Combine. (ankit) * **CLI** Fixed a message typo in Purge. (flixwatchsupport) * **Browser** Added font/otf to Browser Cache expire list. (ruikai) * **Data** Updated data files to accept PR from dev branch only. * **3rd** Add data-view-breakpoint-pointer to js_excludes.txt for the Events Calendar plugin. (therealgilles) * **Cloud** Bypassed invalid requests. * **Doc** CDN Mapping description improvement. (mihai A.) = 3.6.1 - Dec 21 2020 = * **WP** Tested up to WP v5.6. * **WebP** Reverted WebP support on Safari Big Sur and Safari v14.0.1+ due to an inability to detect MacOS versions from UA. (@antomal) * **CDN** Dropped the option `Load JQuery Remotely`. * **CDN** Fixed CDN URL replacement issue in optimized CSS files. (@ankit) * **CDN** Fixed an issue where CDN CLI wouldn't set mapping image/CSS/JS to OFF when `false` was the value. * **CDN** Started using React for CDN Mapping settings. * **GUI** Secured Server IP setting from potential XSS issues. (@WonTae Jang) * **Toolbox** Supported both dev and master branches for Beta Test. Latest version updated to v3.6.1. * **Purge** Purge Pages now can purge non-archive pages too. * **Admin** Simplified the admin JS. * **Admin** Limited crawler-related react JS to crawler page only. = 3.6 - Dec 14 2020 = * ๐ŸŒฑ**WebP** Added WebP support on Safari Big Sur or Safari v14.0.1+. (@ruikai) * ๐Ÿž**Config** Fixed an issue where new installations were not getting the correct default .htaccess content. * **Crawler** Will auto bypass empty sub-sitemap instead of throwing an exception. (@nanoprobes @Tobolo) * **Crawler** Now using React for Cookie Simulation settings instead of Vue.js. Dropped Vue.js. * **Crawler** Dropped `Sitemap Generation` (will only use 3rd party sitemap for crawler). * **CSS** Added `CSS Combine External and Inline` option for backward compatibility. (@lisa) * **Object** Forbid .object-cache.ini visits. (@Tarik) * **Page Optimize** Dropped `Remove Comments` option to avoid combine error. * **CSS** Added a predefined CSS exclude file `data/css_excludes.txt`. * **CSS** Excluded Flatsome theme random inline CSS from combine. * **CSS** Excluded WoodMart theme from combine. (@moemauphie) * **Page Optimize** Excluded tagDiv.com Newspaper theme dynamic CSS/JS from CSS/JS Combine. * **CSS** Added predefined JS defer excludes list. (@Shivam) * **JS** `data-no-defer` option now supports inline JS. (@rafaucau) * **Media** Lazyload inline library is now bypassed by JS Combine. * **Admin** Fixed WP-Admin console ID duplicate warnings. * **Cloud** Dropped QUIC.cloud sync options that have long been unused. * **CSS** Dropped `Unique CSS File` option (UCSS will always generate unique file, will use whitelist to group post type to one CSS). * **GUI** Dropped Help tab. * **Toolbox** Added 3.5.2 to version list. = 3.5.2 - Oct 27 2020 = * **CSS** `CSS Combine` is now compatible w/ inline noscript CSS. (@galbaras) * **GUI** Added ability to manually dismiss the JS option reset message in v3.5.1 upgrade process. (#473917) * ๐Ÿž**CSS** `CSS Excludes` setting will no longer lose items beginning w/ `#`. (@ankit) * **API** New `litespeed_media_reset` API function for image editing purposes. (@Andro) = 3.5.1 - Oct 20 2020 = * **JS** Inline JS containing nonces can now be combined. * **JS** Reset JS Combine/Defer to OFF when upgrading to avoid breaking sites. * **JS** Added new option JS Combine External and Inline to allow backwards compatibility. * **JS** Added Inline JS Defer option back. (@ankit) * **Page Optimize** Dropped Inline JS Minify option and merged the feature into JS Minify. * **JS** Pre-added jQuery to the default JS excludes/defer list for better layout compatibility for new users. * **JS** Excluded Stripe/PayPal/Google Map from JS optimization. (@FPCSJames) * **JS** Allowed excluded JS to still be HTTP2 pushed. (@joshua) * **CCSS** Critical CSS now can avoid network pollution from other sites. (@ankit) * **Toolbox** Beta Test now displays recent public versions so it is easier to revert to an older version * **Vary** Server environment variable Vary can now be passed to original server from QUIC.cloud for non-LiteSpeed servers. * **ESI** Improved backward compatibility for ESI nonce list. (@zach E) * ๐Ÿž**Misc** Fixed failure of upgrade button on plugin news banner and made cosmetic improvements. * **Doc** Added note that LSCWP works with ClassicPress. = 3.5.0.2 - Sep 30 2020 = * This is a temporary revert fix. Code is SAME as v3.4.2. = 3.5.0.1 - Sep 29 2020 = * ๐Ÿ”ฅ๐Ÿž**CSS** Fixed print media query issue when having CSS Combine. (@paddy-duncan) = 3.5 - Sep 29 2020 = * **Page Optimize** Refactored CSS/JS optimization. * **Page Optimize** CSS and JS Combine now each save to a single file without memory usage issues. * **CSS** Inline CSS Minify is now a part of CSS Minify, and will respect the original priorities. (thanks to @galbaras) * **JS** JS Combine now generates a single JS file in the footer. (Special thanks to @ankit) * **JS** JS Combine now combines external JS files, too. (Thanks to @ankit) * **JS** JS Deferred Excludes now uses the original path/filename as keywords instead of the minified path/filename, when JS Minify is enabled. * **JS** JS Combine now combines inline JS, too. * **JS** JS Excludes may now be used for inline JS snippet. * **Page Optimize** Inline CSS Minify and Max Combined File Size retired due to changes listed above. * **CSS** Combined CSS Priority retired due to changes listed above. * **JS** Exclude JQuery, Combined JS Priority, Load Inline JS Deferred, and Inline JS Deferred Excludes retired due to changes listed above. * **JS** Predefined data file data/js_excludes.txt now available for JS Excludes. * **ESI** Predefined data file data/esi.nonces.txt now available for ESI Nonces. * **ESI** Remote Fetch ESI Nonces functionality retired. * **API** Added support for new litespeed_esi_nonces filter. * **Object** Object Cache will not try to reconnect after failure to connect in a single process. * **CCSS** Remote read CSS will add the scheme if it is missing from the URL. * **CCSS** CSS will no longer be prepared for a URL if 404 result is detected. * **CCSS** Fixed most failures caused by third party CSS syntax errors. * **CCSS** Remote read CSS will fix the scheme if the URL doesn't have it. * **CCSS** Excluded 404 when preparing CSS before request. * **CCSS** Adjusted CCSS timeout from 180 seconds to 30 seconds. * **Image Optimize** Fixed the delete attachment database error that occurred when not using the image optimization service yet. * **Media** Added iOS 14 WebP support. * **Data** Fixed database creation failure for MySQL v8. * **Cloud** Error code err_key will clear the domain key in order to avoid duplicate invalid requests. * **Network** Fixed issue with object cache password file storage that occurred when resaving the settings. (#302358) * **Misc** Fixed IP detect compatibility w/ Apache. * **GUI** Fixed the description for Do Not Cache Categories. * **Preload** Upgraded Instant Click to a new stable preload library. (@stasonua0) = 3.4.2 - Sep 8 2020 = * **CCSS** Corrected the issue that wrongly appended non-CSS files to CSS in links before sending request. * **3rd** YITH wishlist now sends a combined single sub request for all widgets contained in one page. (LSWS v5.4.9 build 3+ required) * **ESI** Added support for ESI combine feature. * **GUI** Dropped banner notification for missing domain key when domain key is not initialized. * **Log** When QC whitelist check fails, a detailed failure log is now appended. = 3.4.1 - Sep 2 2020 = * ๐Ÿž**CCSS** Fixed an issue where dynamically generated CSS failed with `TypeError: Cannot read property type of undefined`. * ๐Ÿž**Page Optimize** Fixed CSS optimization compatibility for CSS dynamically generated with PHP. * **Page Optimize** Added the ability to defer JS even when the resource is excluded from other JS optimizations. (@slr1979) * **ESI** Added support for ESI last parameter inline value. * **3rd** YITH Wishlist, when cached for the first time, will no longer send sub requests. = 3.4 - Aug 26 2020 = * ๐ŸŒฑ**LQIP** New setting **LQIP Excludes**. * ๐ŸŒฑ**LQIP** Added a Clear LQIP Queue button. * ๐ŸŒฑ**CCSS** Added a Clear CCSS Queue button. * **CCSS** Fixed an issue which wrongly included preloaded images in CCSS. (@pixtweaks) * **Network** Primary site and subsite settings now display correctly. * **Page Optimize** Noscript tags generated by LSCWP will only be dropped when the corresponding option is enabled. (@ankit) * **DB Optimize** Fixed database optimizer conflicts w/ object cache transient setting. (#752931) * **3rd** Fixed an issue with WooCommerce product purge when order is placed. * **3rd** Improved WooCommerce product comment compatibility with **WooCommerce Photo Reviews Premium** plugin when using ESI. * **CDN** Fixed Remote jQuery compatibility with WordPress v5.5. (@pixtweaks) * **API** New API `litespeed_purge_all_object` and `litespeed_purged_all_object` action hooks. = 3.3.1 - Aug 12 2020 = * ๐ŸŒฑ**Page Optimize** New option to Remove Noscript Tags. (@phuc88bmt) * ๐Ÿž**LQIP** Fixed a critical bug that bypassed all requests in v3.3. * **LQIP** Requests are now bypassed if domain has no credit left. * **Page Optimize** Inline defer will be bypassed if document listener is detected in the code. (@ssurfer) * **CCSS** Print-only styles will no longer be included in Critical CSS. * **API** Added hooks to Purge action to handle file deletions. (@biati) * **Cloud** Plain permalinks are no longer required for use of cloud services. * **Data** Added an access denial to work with OpenLiteSpeed. (@spenweb #PR228) * **GUI** Spelling and grammar adjustments. (@blastoise186 #PR253) = 3.3 - Aug 6 2020 = * ๐ŸŒฑ**Page Optimize** Added a new setting, Inline JS Deferred Excludes. (@ankit) * **Page Optimize** CSS/JS Combine/Minify file versions will be differentiated by query string hash instead of new filename to reduce DB/file system storage. * **Page Optimize** Added the ability to use local copies of external JS files for better control over page score impacts. * **Page Optimize** Improved combination of CSS media queries. (@galbaras) * **Page Optimize** Reprioritized Inline JS Defer to be optimized before encoding, for a significantly smaller result. * **LQIP** Detect if the file exists before sending LQIP request to QUIC.cloud. * **CCSS** Sped up CCSS process significantly by sending HTML and CSS in request. * **CCSS** Improvements to mobile CSS support in CCSS. * **CCSS** Minimize CCSS failures by attempting to automatically fix CSS syntax errors. * **Cloud** Domain Key will be deleted after QUIC.cloud site_not_registered error to avoid endless repeated requests. * **CDN** CDN Original URL will default to WP Site URL if not set. (@ruikai) * **CLI** Global output format `--format=json/yaml/dump` and `--json` support in CLI. (@alya1992) * **CDN** Improved handling of non-image CSS `url()` sources in CDN. (@daniel McD) * ๐Ÿž**CDN** Fixed CDN replacement conflict w/ JS/CSS Optimize. (@ankit) * **Crawler** Only reset Crawler waiting queues when crawling begins. (@ruikai) * **Network** Network Enable Cache is no longer reset to ON Use Network Settings in enabled. (@RavanH) * ๐Ÿž**Activation** Fixed a PHP warning that appeared during uninstall. (@RavanH) * **Debug** Automatically omit long strings when dumping an array to debug log. * **Report** Subsites report now shows overwritten values along w/ original values. (#52593959) * **REST** Improved WP5.5 REST compatibility. (@oldrup) * **GUI** Server IP setting moved from Crawler menu to General menu. * **GUI** Localize resources moved to Localization tab. * **Config** News option now defaults to ON. = 3.2.4 - Jul 8 2020 = * **Object** New installations no longer get custom data.ini reset, as this could cause lost configuration. (@Eric) * **ESI** Now using `svar` to load nonces more quickly. (@Lauren) * **ESI** Fixed the conflicts between nonces in inline JS and ESI Nonces when Inline JS Deferred is enabled. (@JesseDistad) * ๐Ÿž**ESI** Fixed Fetch Latest Predefined Nonce button. * ๐Ÿž**Cache** Fixed an issue where mobile visits were not being cached when Cache Mobile was disabled. * **CDN** Bypass CDN constant `LITESPEED_BYPASS_CDN` now will apply to all CDN replacements. * **Router** Dropped `Router::get_uid()` function. * **Crawler** Updated role simulator function for future UCSS usage. * **GUI** Textarea will now automatically adjust the height based on the number of rows input. * **CLI** Fixed an issue that caused WP-Cron to exit when a task errored out. (@DovidLevine @MatthewJohnson) * **Cloud** No longer communcate with QUIC.cloud when Domain Key is not set and Debug is enabled. * **Cloud** Score banner no longer automatically fetches a new score. (@LucasRolff) = 3.2.3.2 - Jun 19 2020 = * ๐Ÿ”ฅ๐Ÿž**Page Optimize** Hotfix for CSS/JS minify/combine. (@jdelgadoesteban @martin_bailey) = 3.2.3.1 - Jun 18 2020 = * **API** New filter `litespeed_buffer_before` and `litespeed_buffer_after`. (#PR243 @joejordanbrown) = 3.2.3 - Jun 18 2020 = * ๐ŸŒฑ**Page Optimize** Added Unique CSS option for future removal of unused CSS per page. (@moongear) * **Page Optimize** Fixed an issue where Font Optimization could fail when having Load JS Deferred and Load Inline JS Deferred. (#PR241 @joejordanbrown) * ๐Ÿž**Page Optimize** Fixed an issue with Font Display Optimization which caused Google Fonts to load incorrectly. (#PR240 @joejordanbrown @haidan) * ๐Ÿž**Network** Use Primary Site Configuration setting for network sites now works properly with Object Cache and Browser Cache. (#56175101) * **API** Added filter `litespeed_is_from_cloud` to detect if the current request is from QC or not. (@lechon) * **ESI** ESI Nonce now can fetch latest list with one click. * **GUI** Updated remaining documentation links & some minor UI tweaks. (@Joshua Reynolds) = 3.2.2 - Jun 10 2020 = * ๐ŸŒฑ**Purge** Scheduled Purge URLs now supports wildcard. (#427338) * ๐ŸŒฑ**ESI** ESI Nonce supports wildcard match now. * **Network** Use Primary Site Settings now can support Domain Key, and override mechanism improved. (@alican532 #96266273) * **Cloud** Debug mode will now have no interval limit for most cloud requests. (@ruikai) * **Conf** Default Purge Stale to OFF. * **GUI** Purge Stale renamed to Serve Stale. * **Data** Predefined nonce list located in `/litespeed-cache/data/esi.nonce.txt`. Pull requests welcome. * **Debug** Limited parameter log length. * ๐Ÿž**CDN** Fixed an issue where upgrading lost value of CDN switch setting. (#888668) * **3rd** Caldera Forms ESI Nonce enhancement. (@paconarud16 @marketingsweet) * **3rd** Elementor now purges correctly after post/page updates. * **3rd** Disabled Page Optimization features on AMP to avoid webfont JS inject. (@rahulgupta1985) = 3.2.1 - Jun 1 2020 = * **Cloud** LQIP/CCSS rate limit tweaks. (@ianpegg) * **Admin** Improved frontend Admin Bar menu functionality. (#708642) * **Crawler** Fixed an issue where cleaning up a crawler map with a leftover page number would cause a MySQL error. (@saowp) * **Image Optimize** Added WP default thumbnails to image optimization summary list. (@johnny Nguyen) * **REST** Improved REST compatibility w/ WP4.4-. (#767203) * **GUI** Moved Use Primary Site Configuration to General menu. (@joshua) = 3.2 - May 27 2020 = * **Image Optimize** Major improvements in queue management, scalability, and speed. (@LucasRolff) * **Cloud** Implemented a series of communication enhancements. (@Lucas Rolff) * **Crawler** Enhanced PHP 5.3 compatibility. (@JTS-FIN #230) * **Page Optimize** Appended image template in wpDiscuz script into default lazyload image exclude list. (@philipfaster @szmigieldesign) * **Page Optimize** Eliminated the 404 issue for CSS/JS in server environments with missing SCRIPT_URI. (@ankit) * **Data** ENhanced summary data storage typecasting. = 3.1 - May 20 2020 = * ๐ŸŒฑ**Network** Added Debug settings to network level when on network. * ๐Ÿž**Purge** Network now can purge all. * ๐Ÿž**Network** Fixed issue where saving the network primary site settings failed. * **Network** Moved Beta Test to network level when on network. * ๐Ÿž**Cache** Fixed issue in admin where new post editor was wrongly cached for non-admin roles. (@TEKFused) * ๐Ÿž**Data** Fixed issue with crawler & img_optm table creation failure. (@berdini @piercand) * ๐Ÿž**Core** Improved plugin activation compatibility on Windows 10 #224 (@greenphp) * **Core** Improved compatibility for .htaccess path search. * **Object** Catch RedisException. (@elparts) * Fixed Script URI issue in 3.0.9 #223 (@aonsyed) * **Image Optimize** Show thumbnail size set list in image optimization summary. (@Johnny Nguyen) * **Debug** Parameters will now be logged. = 3.0.9 - May 13 2020 = * **Purge** Comment cache can be successfully purged now. * **Data** Better MySQL charset support for crawler/image optimize table creation. (@Roshan Jonah) * **API** New hook to fire after Purge All. (@salvatorefresta) * **Crawler** Resolve IP for crawler. * **Task** PHP5.3 Cron compatibility fix. * **3rd** Elementor edit mode compatibility. * **Page Optimize** Fixed an issue where Purge Stale returned 404 for next visitor on CSS/JS. * **Page Optimize** Fixed the PHP warning when srcset doesn't have size info inside. (@gvidano) * **Cloud** Fixed the potential PHP warning when applying for the domain key. * **Core** PHP __DIR__ const replacement. (@MathiasReker) = 3.0.8.6 - May 4 2020 = * **CCSS** Bypassed CCSS functionality on frontend when domain key isn't setup yet. * **Cloud** Fixed WP node redetection bug when node expired. (@Joshua Reynolds) * **Crawler** Fixed an issue where URL is wrongly blacklisted when using ADC. = 3.0.8.5 - May 1 2020 = * ๐Ÿ”ฅ๐Ÿž**3rd** Hotfix for WPLister critical error due to v3.0.8.4 changes. * **Image Optimize** Unfinished queue now will get more detailed info to indicate the proceeding status on node. * **CLI** Options can now use true/false as value for bool. (@gavin) * **CLI** Detect error if the ID does not exist when get/set an option value. * **Doc** An API comment typo for `litespeed_esi_load-` is fixed. = 3.0.8.4 - Apr 30 2020 = * ๐ŸŒฑ**Crawler** New setting: Sitemap timeout. (#364607) * **Image Optimize** Images that fail to optimize are now counted to increase next request limit. * **Cloud** Redetect fastest node every 3 days. * **Cloud** Suppressed auto upgrade version detection error. (@marc Dahl) * **3rd** 3rd party namespace compatibility. (#366352) = 3.0.8.3 - Apr 28 2020 = * **Cloud** Better compatibility for the Link to QUIC.cloud operation. (@Ronei de Sousa Almeida) * **Image Optimize** Automatically clear invalid image sources before sending requests. (@Richard Hordern) = 3.0.8.2 - Apr 27 2020 = * **GUI** Corrected the Request Domain Key wording. = 3.0.8.1 - Apr 27 2020 = * **Object** Object cache compatibility for upgrade from v2.9.9- versions. = 3.0.8 - Apr 27 2020 = * Released v3 on WordPress officially. = 3.0.4 - Apr 23 2020 = * **Cloud** Apply Domain Key now receives error info in next apply action if failed to generate. * **GUI** Apply Domain Key timeout now displays troubleshooting guidance. * **REST** Added /ping and /token to REST GET for easier debug. * **Cache** Dropped `advanced-cache.php` file detection and usage. = 3.0.3 - Apr 21 2020 = * **Conf** Settings from all options (data ini, defined constant, and forced) will be filtered and cast to expected type. * **Upgrade** CDN mapping and other multiple line settings will now migrate correctly when upgrading from v2 to v3. = 3.0.2 - Apr 17 2020 = * **GUI** More guidance on domain key setting page. * **Cloud** Now Apply Domain Key will append the server IP if it exists in Crawler Server IP setting. = 3.0.1 - Apr 16 2020 = * **Data** Increased timeout for database upgrade related to version upgrade. Display a banner while update in progress. * **Page Optimize** All appended HTML attributes now will use double quotes to reduce the conflicts when the optimized resources are in JS snippets. = 3.0 - Apr 15 2020 = * ๐ŸŒฑ**Media** LQIP (Low Quality Image Placeholder). * ๐ŸŒฑ**Page Optimize** Load Inline JS Deferred Compatibility Mode. (Special thanks to @joe B - AppsON) * ๐ŸŒฑ**Cloud** New QUIC.cloud API key setting. * ๐ŸŒฑ**ESI** New ESI nonce setting. * ๐ŸŒฑ**Media** JPG quality control. (@geckomist) * ๐ŸŒฑ**Media** Responsive local SVG placeholder. * ๐ŸŒฑ**Discussion** Gravatar warmup cron. * ๐ŸŒฑ**DB** Table Engine Converter tool. (@johnny Nguyen) * ๐ŸŒฑ**DB** Database summary: Autoload size. (@JohnnyNguyen) * ๐ŸŒฑ**DB** Database summary: Autoload entries list. * ๐ŸŒฑ**DB** Revisions older than. (@thememasterguru) * ๐ŸŒฑ**Cache** Forced public cache setting. (#308207) * ๐ŸŒฑ**Crawler** New timeout setting to avoid incorrect blacklist addition. (#900171) * ๐ŸŒฑ**Htaccess** Frontend & backend .htaccess path customize. (@jon81) * ๐ŸŒฑ**Toolbox** Detailed Heartbeat Control (@K9Heaven) * ๐ŸŒฑ**Purge** Purge Stale setting. * ๐ŸŒฑ**Page Optimize** Font display optimization. (@Joeee) * ๐ŸŒฑ**Page Optimize** Google font URL display optimization. * ๐ŸŒฑ**Page Optimize** Load Inline JS deferred. * ๐ŸŒฑ**Page Optimize** Store gravatar locally. (@zzTaLaNo1zz @JohnnyNguyen) * ๐ŸŒฑ**Page Optimize** DNS prefetch control setting. * ๐ŸŒฑ**Page Optimize** Lazy Load Image Parent Class Name Excludes. (@pako69) * ๐ŸŒฑ**Page Optimize** Lazy load iframe class excludes. (@vnnloser) * ๐ŸŒฑ**Page Optimize** Lazy load exclude URIs. (@wordpress_fan1 @aminaz) * ๐ŸŒฑ**GUI** New Dashboard and new menus. * ๐ŸŒฑ**Image Optimize** Supported GIF WebP optimization. (@Lucas Rolff) * ๐ŸŒฑ**Image Optimize** New workflow for image optimization (Gather first, request second). * ๐ŸŒฑ**Image Optimize** The return of Rescan. * ๐ŸŒฑ**CLI** Get single option cmd. * ๐ŸŒฑ**CLI** QUIC.cloud cmd supported. * ๐ŸŒฑ**CLI** CLI can send report now. * ๐ŸŒฑ**Health** Page speed and page score now are in dashboard. * ๐ŸŒฑ**Conf** Supported consts overwritten of `LITESPEED_CONF__` for all settings. (@menathor) * ๐ŸŒฑ**REST** New REST TTL setting. (@thekendog) * ๐ŸŒฑ**CDN** New setting `HTML Attribute To Replace`. CDN can now support any HTML attribute to be replaced. (@danushkaj91) * ๐ŸŒฑ**Debug** Debug URI includes/excludes settings. * ๐ŸŒฑ**Crawler** ๐Ÿž Support for multiple domains in custom sitemap. (@alchem) * ๐ŸŒฑ**Crawler** New Crawler dashboard. New sitemap w/ crawler status. New blacklist w/ reason. * ๐ŸŒฑ**Media** LQIP minimum dimensions setting. (@Lukasz Szmigiel) * **Crawler** Able to add single rows to blacklist. * **Crawler** Crawler data now saved into database instead of creating new files. * **Crawler** Larger timeout to avoid wrongly added to blacklist. * **Crawler** Manually changed the priority of mobile and WebP. (@rafaucau) * **Browser** Larger Browser Cache TTL for Google Page Score improvement. (@max2348) * **Task** Task refactored. Disabled cron will not show in cron list anymore. * **Task** Speed up task load speed. * **ESI** Added Bloom nonce to ESI for Elegant Themes. * **Cloud** Able to redetect cloud nodes now. * **Img_optm** Fixed stale data in redirected links. * **Lazyload** CSS class `litespeed_lazyloaded` is now appended to HTML body after lazyload is finished. (@Adam Wilson) * **Cache** Default drop qs values. (@gijo Varghese) * **LQIP** Show all LQIP images in Media column. * **CDN** Can now support custom REST API prefix other than wp-json. (#174 @therealgilles) * **IAPI** Used REST for notify/destroy/check_img; Removed callback passive/aggreesive IAPI func * **CSSJS** Saved all static files to litespeed folder; Uninstallation will remove static cache folder too; Reduced .htaccess rules by serving CSS/JS directly. * **Object** Fixed override different ports issue. (@timofeycom #ISSUE178) * **Conf** DB Tables will now only create when activating/upgrading/changing settings. * **DB** Simplified table operation funcs. * **CSSJS** Bypassed CSS/JS generation to return 404 if file is empty (@grubyy) * **CSSJS** Inline JS defer will not conflict with JS inline optm anymore. * **CDN** settings will not be overwritten by primary settings in network anymore. (@rudi Khoury) * **OPcache** Purged all opcache when updating cache file. (@closte #170) * **CLI** CLI cmd renamed. * **CLI** Well-formatted table to show all options. * **Purge** Only purge related posts that have a status of "published" to avoid unnecessary "draft" purges. (@Jakub Knytl) * **GUI** Removed basic/adv mode for settings. Moved non-cache settings to its own menu. * **Htaccess** Protected .htaccess.bk file. Only kept one backup. (@teflonmann) * **Crawler** Crawler cookie now support `_null` as empty value. * **Crawler** Avoid crawler PHP fatal error on Windows OS. (@technisolutions) * **Admin** Simplified admin setting logic. * **Conf** Multi values settings now uniformed to multi lines for easier setting. * **Conf** New preset default data file `data/consts.default.ini`. * **Conf** Config setting renamed and uniformed. * **Conf** Dropped `Conf::option()`. Used `Conf::val()` instead. * **Conf** Improved conf initialization and upgrade conversion workflow. * **Core** Code base refactored. New namespace LiteSpeed. * **API** New API: iframe lazyload exclude filter. * **GUI** human readable seconds. (@MarkCanada) * **API** API refactored. * NOTE: All 3rd party plugins that are using previous APIs, especially `LiteSpeed_Cache_API`, need to be adjusted to the latest one. Same for ESI blocks.* ESI shortcode doesn't change. * **API** New hook `litespeed_update_confs` to settings update. * **API** New Hooks `litespeed_frontend_shortcut` and `litespeed_backend_shortcut` for dropdown menu. (@callaloo) * **API** Removed `litespeed_option_*` hooks. Use `litespeed_force_option` hook insteadly * **API** Renamed `litespeed_force_option` to `litespeed_conf_force`. * **API** Removed function `litespeed_purge_single_post`. * **REST** New rest API to fetch public IP. * **GUI** Hiding Cloudflare/Object Cache/Cloud API key credentials. (@menathor) * **GUI** Renamed all backend link tag from lscache to litespeed. * **GUI** fixed duplicated form tag. * **GUI** Fix cron doc link. (@arnab Mohapatra) * **GUI** Frontend adminbar menu added `Purge All` actions. (@Monarobase) * **GUI** Localized vue.js to avoid CloudFlare cookie. (@politicske) * **GUI** Always show optm column in Media Library for future single row optm operation. (@mikeyhash) * **GUI** Displayed TTL range below the corresponding setting. * **GUI** GUI refactored. * **Debug** Report can now append notes. * **3rd** Default added parallax-image to webp replacement for BB. * **3rd** User Switching plugin compatibility. (@robert Staddon) * **3rd** Beaver Builder plugin compatibility with v3.0. * **3rd** Avada plugin compatibility w/ BBPress. (@pimg) * **3rd** WooCommerce PayPal Checkout Gateway compatibility. (#960642 @Glen Cabusas) * **Network** Fixed potential timeout issue when containing a large volume of sites. (@alican532) * **Debug** `Disable All Features` now will see the warning banner if ON. * **Debug** Dropped `log filters` section. * **Debug** Debug and Tools sections combined into new `Toolbox` section. * ๐Ÿž**Crawler** Multi sites will now use separate sitemap even when `Use Primary Site` is ON. (@mrhuynhanh) * ๐Ÿž**Img_optm** Fixed large volume image table storage issue. (#328956) * ๐Ÿž **Cloud** Cloud callback hash validation fixed OC conflict. (@pbpiotr) * ๐ŸŽŠ Any user that had the contribution to our WP community or changelog (even just bug report/feedback/suggestion) can apply for extra credits in QUIC.cloud. = 2.9.9.2 - Nov 24 2019 = * ๐ŸŒฑ**GUI** New settings to limit News Feed to plugin page only. = 2.9.9.1 - Nov 18 2019 = * ๐ŸŒฑ**Env** Environment Report can now append a passwordless link for support access without wp-admin password. * **Admin** The latest v3.0 beta test link may now be shown on the admin page when it's available. * **3rd** Compatibility with [DoLogin Security](https://wordpress.org/plugins/dologin/). * ๐Ÿž**ESI** Fixed a failure issue with Vary Group save. (@rafasshop) * ๐Ÿž**3rd** In browsers where WebP is not supported, Divi image picker will no longer serve WebP. (@Austin Tinius) = 2.9.9 - Oct 28 2019 = * Core: Preload all classes to avoid getting error for upcoming v3.0 upgrade. * Object: Improved compatibility with upcoming v3.0 release. * ESI: Unlocked ESI for OLS in case OLS is using QUIC.cloud CDN which supports ESI. * 3rd: Elementor Edit button will now show when ESI enabled. (#PR149 #335322 @maxgorky) * ๐ŸžMedia: Fixed missing Media optimization column when Admin role is excluded from optimization in settings. (@mikeyhash @pako69 @dgilfillan) = 2.9.8.7 - Oct 11 2019 = * 3rd: Enhanced WP stateless compatibility. (#PR143) * 3rd: Fixed a PHP warning caused by previous PR for AMP. (#PR176) = 2.9.8.6 - Sep 24 2019 = * 3rd: Bypassed page optimizations for AMP. (#359748 #PR169) * GUI: Firefox compatibility with radio button state when reloading pages. (#288940 #PR162) * GUI: Updated Slack invitation link. (#PR173) = 2.9.8.5 - Aug 21 2019 = * CCSS: Removed potential PHP notice when getting post_type. (@amcgiffert) * CDN: Bypassed CDN replacement on admin page when adding media to page/post. (@martin_bailey) * ๐ŸžMedia: Fixed inability to update or destroy postmeta data for child images. (#167713) = 2.9.8.4 - Jul 25 2019 = * Object: Increased compatibility with phpredis 5.0. * Object: Appended `wc_session_id` to default Do Not Cache Groups setting to avoid issue where WooCommerce cart items were missing when Object Cache is used. NOTE: Existing users must add `wc_session_id` manually! (#895333) * CSS: Added null onload handler for CSS async loading. (@joejordanbrown) * ๐Ÿ•ท๏ธ: Increased crawler timeout to avoid wrongly adding a URL to the blacklist. * 3rd: WooCommerce Advanced Bulk Edit can now purge cache automatically. = 2.9.8.3 - Jul 9 2019 = * CSS: Enhanced the CSS Minify compatibility for CSS with missing closing bracket syntax errors. (@fa508210020) * ๐Ÿ•ท๏ธ: Crawler now supports both cookie and no-cookie cases. (@tabare) * CCSS: Enhanced compatibility with requested pages where meta info size exceeds 8k. (@Joe B) * CCSS: No longer processing "font" or "import" directives as they are not considered critical. (@Ankit @Joe B) * IAPI: Removed IPv6 from all servers to avoid invalid firewall whitelist. = 2.9.8.2 - Jun 17 2019 = * ๐Ÿ”ฅ๐Ÿž 3rd: Fixed PHP 5.3 compatibility issue with Facetwp. = 2.9.8.1 - Jun 17 2019 = * 3rd: Set ESI template hook priority to highest number to prevent ESI conflict with Enfold theme. (#289354) * 3rd: Improved Facetwp reset button compatibility with ESI. (@emilyel) * 3rd: Enabled user role change to fix duplicate login issue for plugins that use alternative login processes. (#114165 #717223 @sergiom87) * GUI: Wrapped static text with translate function. (@halilemreozen) = 2.9.8 - May 22 2019 = * Core: Refactored loading priority so user related functions & optimization features are set after user initialization. (#717223 #114165 #413338) * Media: Improved backup file calculation query to prevent out-of-memory issue. * Conf: Feed cache now defaults to ON. * API: Fully remote attachment compatibility API of image optimization now supported. * ๐Ÿ•ท๏ธ: Bypassed vary change for crawler; crawler can now simulate default vary cookie. * ESI: Refactored ESI widget. Removed `widget_load_get_options()` function. * ESI: Changed the input name of widget fields in form. * 3rd: Elementor can now save ESI widget settings in frontend builder. * 3rd: WP-Stateless compatibility. * IAPI: Image optimization can now successfully finish the destroy process with large volume images with automatic continual mode. * ๐ŸžCDN: Fixed issue with Load JQuery Remotely setting where WP 5.2.1 provided an unexpected jQuery version. * ๐Ÿž3rd: Login process now gets the correct role; fixed double login issue. = 2.9.7.2 - May 2 2019 = * Conf: Enhanced compatibility when an option is not properly initialized. * Conf: Prevent non-array instance in widget from causing 500 error. (#210407) * CCSS: Increase CCSS generation timeout to 60s. * Media: Renamed lazyload CSS class to avoid conflicts with other plugins. (@DynamoProd) * JS: Improved W3 validator. (@istanbulantik) * QUIC: Synced cache tag prefix for static files cache. * ESI: Restored query strings to ESI admin bar for accurate rendering. (#977284) * ESI: Tweaked ESI init priority to honor LITESPEED_DISABLE_ALL const. ESI will now init after plugin loaded. * ๐ŸžESI: No longer initialize ESI if ESI option is OFF. * API: New "Disable All" API function. * API: New "Force public cache" API function. * ๐ŸžVary: Fixed an issue with saving vary groups. * ๐ŸžIAPI: Fixed an issue where image md5 validation failed due to whitespace in the image path. * ๐Ÿž3rd: Bypass all optimization/ESI/Cache features when entering Divi Theme Builder frontend editor. * ๐Ÿž3rd: Fixed an issue where DIVI admin bar exit button didn't work when ESI was ON. = 2.9.7.1 - Apr 9 2019 = * Purge: Purge All no longer includes Purge CCSS/Placeholder. * 3rd: Divi Theme Builder no longer experiences nonce expiration issues in the contact form widget. (#475461) = 2.9.7 - Apr 1 2019 = * ๐ŸŒฑ๐ŸŒฑ๐ŸŒฑ QUIC.cloud CDN feature. Now Apache/Nginx can use LiteSpeed cache freely. = 2.9.6 - Mar 27 2019 = * ๐ŸŒฑIAPI: Appended XMP to `Preserve EXIF data` setting. WebP will now honor this setting. (#902219) * Object: Fixed SASL connection with LSMCD. * ESI: Converted ESI URI parameters to JSON; Added ESI validation. * Import: Import/Export will now use JSON format. Please re-export any backed up settings. Previous backup format is no longer recognized. * Media: WebP replacement will honor `Role Excludes` setting now. (@mfazio26) * Data: Forbid direct visit to const.default.ini. * Utility: Can handle WHM passed in `LITESPEED_ERR` constant now. * IAPI: Communicate via JSON encoding. * IAPI: IAPI v2.9.6. = 2.9.5 - Mar 14 2019 = * ๐ŸŒฑ Auto convert default WordPress nonce to ESI to avoid expiration. * ๐ŸŒฑ API: Ability to easily convert custom nonce to ESI by registering `LiteSpeed_Cache_API::nonce_action`. * OPTM: Tweaked redundant attr `data-no-optimize` in func `_analyse_links` to `data-ignore-optimize` to offer the API to bypass optimization but still move src to top of source code. * API: Renamed default nonce ESI ID from `lscwp_nonce_esi` to `nonce`. * API: Added WebP generation & validation hook API. (@alim #wp-stateless) * API: Added hook to bypass vary commenter check. (#wpdiscuz) * Doc: Clarified Cache Mobile description. (@JohnnyNguyen) * Doc: Replaced incorrect link in description. (@JohnnyNguyen) * 3rd: Improved wpDiscuz compatibility. * ๐Ÿž3rd: Fixed Divi Theme Builder comment compatibility on non-builder pages. (#410919) * 3rd: Added YITH ESI adjustment. = 2.9.4.1 - Feb 28 2019 = * ๐Ÿ”ฅ๐ŸžTag: Fixed issue where unnecessary warning potentially displayed after upgrade process when object cache is enabled. = 2.9.4 - Feb 27 2019 = * ๐ŸžREST: New REST class with better WP5 Gutenberg and internal REST call support when ESI is embedded. * ESI: ESI block ID is now in plain text in ESI URL parameters. * ๐ŸžESI: Fixed a redundant ESI 301 redirect when comma is in ESI URL. * ESI: REST call can now parse shortcodes in ESI. * API: Changed ESI `parse_esi_param()` function to private and `load_esi_block` function to non-static. * API: Added `litespeed_is_json` hook for buffer JSON conversion. * GUI: Prepended plugin name to new version notification banner. * 3rd: WPML multi domains can now be handled in optimization without CDN tricks. = 2.9.3 - Feb 20 2019 = * ESI: ESI shortcodes can now be saved in Gutenberg editor. * ESI: ESI now honors the parent page JSON data type to avoid breaking REST calls (LSWS 5.3.6+). * ESI: Added is_json parameter support for admin_bar. * ESI: Simplified comment form code. * 3rd: Better page builder plugin compatibility within AJAX calls. * 3rd: Compatibility with FacetWP (LSWS 5.3.6+). * 3rd: Compatibility with Beaver Builder. * Debug: Added ESI buffer content to log. * Tag: Only append blog ID to cache tags when site is part of a network. * IAPI: Optimized database query for pulling images. * GUI: Added more plugin version checking for better feature compatibility. * GUI: Ability to bypass non-critical banners with the file .litespeed_no_banner. * Media: Background image WebP replacement now supports quotes around src. = 2.9.2 - Feb 5 2019 = * API: Add a hook `litespeed_esi_shortcode-*` for ESI shortcodes. * 3rd: WooCommerce can purge products now when variation stock is changed. * ๐Ÿž๐Ÿ•ท๏ธ: Forced HTTP1.1 for crawler due to a CURL HTTP2 bug. = 2.9.1 - Jan 25 2019 = * Compatibility: Fixed fatal error for PHP 5.3. * Compatibility: Fixed PHP warning in htmlspecialchars when building URLs. (@souljahn2) * Media: Excluded invalid image src from lazyload. (@andrew55) * Optm: Improved URL compatibility when detecting closest cloud server. * ESI: Supported JSON format comment format in ESI with `is_json` parameter. * API: Added filters to CCSS/CSS/JS content. (@lhoucine) * 3rd: Improved comment compatibility with Elegant Divi Builder. * IAPI: New Europe Image Optimization server (EU5). Please whitelist the new [IAPI IP List](https://wp.api.litespeedtech.com/ips). * GUI: No longer show banners when `Disable All` in `Debug` is ON. (@rabbitwordpress) * GUI: Fixed button style for RTL languages. * GUI: Removed unnecessary translation in report. * GUI: Updated readme wiki links. * GUI: Fixed pie styles in image optimization page. = 2.9 - Dec 31 2018 = * ๐ŸŒฑMedia: Lazy Load Image Classname Excludes. (@thinkmedia) * ๐ŸŒฑ: New EU/AS cloud servers for faster image optimization handling. * ๐ŸŒฑ: New EU/AS cloud servers for faster CCSS generation. * ๐ŸŒฑ: New EU/AS cloud servers for faster responsive placeholder generation. * ๐ŸŒฑConf: Ability to set single options via link. * ๐ŸŒฑCache: Ability to add custom TTLs to Force Cache URIs. * Purge: Added post type to Purge tags. * Purge: Redefined CCSS page types. * Core: Using Exception for .htaccess R/W. * IAPI: New cloud servers added. Please whitelist the new [IAPI IP List](https://wp.api.litespeedtech.com/ips). * Optm: Trim BOM when detecting if the page is HTML. * GUI: Added PageSpeed Score comparison into promotion banner. * GUI: Refactored promotion banner logic. * GUI: Removed page optimized comment when ESI Silence is requested. * GUI: WHM transient changed to option instead of transient when storing. * GUI: Appending more descriptions to CDN filetype setting. * IAPI: Removed duplicate messages. * IAPI: Removed taken_failed/client_pull(duplicated) status. * Debug: Environment report no longer generates hash for validation. * 3rd: Non-cacheable pages no longer punch ESI holes for Divi compatibility. * ๐ŸžNetwork: Added slashes for mobile rules when activating plugin. * ๐ŸžCCSS: Eliminated a PHP notice when appending CCSS. = 2.8.1 - Dec 5 2018 = * ๐Ÿž๐Ÿ•ท๏ธ: Fixed an activation warning related to cookie crawler. (@kacper3355 @rastel72) * ๐ŸžMedia: Replace safely by checking if pulled images is empty or not first. (@Monarobase) * 3rd: Shortcode ESI compatibility with Elementor. = 2.8 - Nov 30 2018 = * ๐ŸŒฑ: ESI shortcodes. * ๐ŸŒฑ: Mobile crawler. * ๐ŸŒฑ: Cookie crawler. * API: Can now add `_litespeed_rm_qs=0` to bypass Remove Query Strings. * Optm: Removed error log when minify JS failed. * ๐ŸžCore: Fixed a bug that caused network activation PHP warning. * Media: Removed canvas checking for WebP to support TOR. (@odeskumair) * Media: Eliminated potential image placeholder PHP warning. * 3rd: Bypassed Google recaptcha from Remove Query Strings for better compatibility. * IAPI: Showed destroy timeout details. * Debug: Moved Google Fonts log to advanced level. * GUI: Replaced all Learn More links for functions. * GUI: Cosmetic updates including Emoji. * ๐Ÿ•ท๏ธ: Removed duplicated data in sitemap and blacklist. = 2.7.3 - Nov 26 2018 = * Optm: Improved page render speed with Web Font Loader JS library for Load Google Fonts Asynchronously. * Optm: Directly used JS library files in plugin folder instead of short links `/min/`. * Optm: Handled exceptions in JS optimization when meeting badly formatted JS. * 3rd: Added Adobe Lightroom support for NextGen Gallery. * 3rd: Improved Postman app support for POST JSON requests. * IAPI: US3 server IP changed to 68.183.60.185. = 2.7.2 - Nov 19 2018 = * ๐ŸŒฑ: Auto Upgrade feature. * CDN: Bypass CDN for cron to avoid WP jQuery deregister warning. = 2.7.1 - Nov 15 2018 = * ๐ŸŒฑCLI: Ability to set CDN mapping by `set_option litespeed-cache-cdn_mapping[url][0] https://url`. * ๐ŸŒฑCDN: Ability to customize default CDN mapping data in default.ini. * ๐ŸŒฑAPI: Default.ini now supports both text-area items and on/off options. * Vary: Refactored Vary and related API. * Vary: New hook to manipulate vary cookies value. * Core: Activation now can generate Object Cache file. * Core: Unified Object Cache/rewrite rules generation process across activation/import/reset/CLI. * Core: Always hook activation to make activation available through the front end. * ๐ŸžIAPI: Fixed a bug where environment report gave incorrect image optimization data. * ๐ŸžOLS: Fixed a bug where login cookie kept showing a warning on OpenLiteSpeed. * ๐ŸžCore: Fixed a bug where Import/Activation/CLI was missing CDN mapping settings. * API: Filters `litespeed_cache_media_lazy_img_excludes/litespeed_optm_js_defer_exc` passed-in parameter is changed from string to array. = 2.7 - Nov 2 2018 = * ๐ŸŒฑ: Separate Purge log for better debugging. * 3rd: Now fully compatible with WPML. * IAPI: Sped up Image Optimization workflow. * GUI: Current IP now shows in Debug settings. * GUI: Space separated placeholder queue list for better look. * IAPI: EU3 server IP changed to 165.227.131.98. = 2.6.4.1 - Oct 25 2018 = * ๐Ÿ”ฅ๐ŸžMedia: Fixed a bug where the wrong table was used in the Image Optimization process. * IAPI: IAPI v2.6.4.1. = 2.6.4 - Oct 24 2018 = * ๐ŸŒฑ: Ability to create custom default config options per hosting company. * ๐ŸŒฑ: Ability to generate mobile Critical CSS. * ๐ŸžMedia: Fixed a bug where Network sites could incorrectly override optimized images. * ๐ŸžCDN: Fixed a bug where image URLs containing backslashes were matched. * Cache: Added default Mobile UA config setting. * GUI: Fixed unknown shortcut characters for non-English languages Setting tabs. = 2.6.3 - Oct 18 2018 = * ๐ŸŒฑ: Ability to Reset All Options. * ๐ŸŒฑCLI: Added new `lscache-admin reset_options` command. * GUI: Added shortcuts for more of the Settings tabs. * Media: Updated Lazy Load JS library to the most recent version. * There is no longer any need to explicitly Save Settings upon Import. * Remove Query String now will remove *all* query strings in JS/CSS static files. * IAPI: Added summary info to debug log. = 2.6.2 - Oct 11 2018 = * Setting: Automatically correct invalid numeric values in configuration settings upon submit. * ๐ŸžMedia: Fixed the issue where iframe lazy load was broken by latest Chrome release. (@ofmarconi) * ๐Ÿž: Fixed an issue with Multisite where subsites failed to purge when only primary site has WooCommerce . (@kierancalv) = 2.6.1 - Oct 4 2018 = * ๐ŸŒฑ: Ability to generate separate Critical CSS Cache for Post Types & URIs. * API: Filter `litespeed_frontend_htaccess` for frontend htaccess path. * Media: Removed responsive placeholder generation history to save space. = 2.6.0.1 - Sep 24 2018 = * ๐Ÿ”ฅ๐Ÿž: Fixed an issue in responsive placeholder generation where redundant history data was being saved and using a lot of space. = 2.6 - Sep 22 2018 = * Vary: Moved `litespeed_cache_api_vary` hook outside of OLS condition for .htaccess generation. * CDN: Trim spaces in original URL of CDN setting. * API: New filter `litespeed_option_` to change all options dynamically. * API: New `LiteSpeed_Cache_API::force_option()` to change all options dynamically. * API: New `LiteSpeed_Cache_API::vary()` to set default vary directly for easier compaitiblity with WPML WooCommerce Multilingual. * API: New `LiteSpeed_Cache_API::nonce()` to safely and easily allow caching of wp-nonce. * API: New `LiteSpeed_Cache_API::hook_vary_add()` to add new vary. * Optm: Changed HTML/JS/CSS optimization options assignment position from constructor to `finalize()`. * Doc: Added nonce to FAQ and mentioned nonce in 3rd Party Compatibility section. * GUI: Moved inline minify to under html minify due to the dependency. * 3rd: Cached Aelia CurrencySwitcher by default. * ๐Ÿž: Fixed issue where enabling remote JQuery caused missing jquery-migrate library error. = 2.5.1 - Sep 11 2018 = * ๐ŸŒฑ Responsive placeholder. (@szmigieldesign) * Changed CSS::ccss_realpath function scope to private. * ๐Ÿž Detected JS filetype before optimizing to avoid PHP source conflict. (@closte #50) = 2.5 - Sep 6 2018 = * [IMPROVEMENT] CLI can now execute Remove Original Image Backups. (@Shon) * [UPDATE] Fixed issue where WP-PostViews documentation contained extra slashes. (#545638) * [UPDATE] Check LITESPEED_SERVER_TYPE for more accurate LSCache Disabled messaging. * [IAPI] Fixed a bug where optimize/fetch error notification was not being received. (@LucasRolff) = 2.4.4 - Aug 31 2018 = * [NEW] CLI can now support image optimization. (@Shon) * [IMPROVEMENT] GUI Cron/CLI will not create admin message anymore. * [UPDATE] Media Fixed a PHP notice that appeared when pulling optimized images. * [UPDATE] Fixed a PHP notice when detecting origin of ajax call. (@iosoft) * [DEBUG] Debug log can now log referer URL. * [DEBUG] Changes to options will now be logged. = 2.4.3 - Aug 27 2018 = * [NEW] Media Ability to inline image lazyload JS library. (@Music47ell) * [IMPROVEMENT] Media Deleting images will now clear related optimization file & info too. * [IMPROVEMENT] Media Non-image postfix data will now be bypassed before sending image optimization request. * [BUGFIX] CDN CDN URL will no longer be replaced during admin ajax call. (@pankaj) * [BUGFIX] CLI WPCLI can now save options without incorrectly clearing textarea items. (@Shon) * [GUI] Moved Settings above Manage on the main menu. = 2.4.2 - Aug 21 2018 = * [IMPROVEMENT] Media Sped up Image Optimization process by replacing IAPI server pull communication. * [IMPROVEMENT] Media Ability to delete optimized WebP/original image by item in Media Library. (@redgoodapple) * [IMPROVEMENT] CSS Optimize Generate new optimized CSS name based on purge timestamp. Allows CSS cache to be cleared for visitors. (@bradbrownmagic) * [IMPROVEMENT] API added litespeed_img_optm_options_per_image. (@gintsg) * [UPDATE] Stopped showing "No Image Found" message when all images have finished optimization. (@knutsp) * [UPDATE] Improved a PHP warning when saving settings. (@sergialarconrecio) * [UPDATE] Changed backend adminbar icon default behavior from Purge All to Purge LSCache. * [UPDATE] Clearing CCSS cache will clear unfinished queue too. * [UPDATE] Added "$" exact match when adding URL by frontend adminbar dropdown menu, to avoid affecting any sub-URLs. * [UPDATE] Fixed IAPI error message showing array bug. (@thiomas) * [UPDATE] Debug Disable All will do a Purge All. * [UPDATE] Critical CSS server IP changed to 142.93.3.57. * [GUI] Showed plugin update link for IAPI version message. * [GUI] Bypassed null IAPI response message. * [GUI] Grouped related settings with indent. * [IAPI] Added 503 handler for IAPI response. * [IAPI] IAPI v2.4.2. * [IAPI] Center Server IP Changed from 34.198.229.186 to 142.93.112.87. = 2.4.1 - Jul 19 2018 = * [NEW FEATURE] Media Auto Level Up. Auto refill credit. * [NEW FEATURE] Media Auto delete original backups after pulled. (@borisov87 @JMCA2) * [NEW FEATURE] Media Auto request image optimization. (@ericsondr) * [IMPROVEMENT] Media Fetch 404 error will notify client as other errors. * [IMPROVEMENT] Media Support WebP for PageSpeed Insights. (@LucasRolff) * [BUGFIX] CLI Fixed the issue where CLI import/export caused certain textarea settings to be lost. (#767519) * [BUGFIX] CSS Optimize Fixed the issue that duplicated optimized CSS and caused rapid expansion of CSS cache folder. * [GUI] Media Refactored operation workflow and interface. * [UPDATE] Media Set timeout seconds to avoid pulling timeout. (@Jose) * [UPDATE] CDNFixed the notice when no path is in URL. (@sabitkamera) * [UPDATE] Media Auto correct credits when pulling. * [UPDATE] GUI Removed redundant double quote in gui.cls. (@DaveyJake) * [IAPI] IAPI v2.4.1. * [IAPI] Allow new error status notification and success message from IAPI. = 2.4 - Jul 2 2018 = * [NEW FEATURE] Media Added lossless optimization. * [NEW FEATURE] Media Added Request Original Images ON/OFF. * [NEW FEATURE] Media Added Request WebP ON/OFF. (@JMCA2) * [IMPROVEMENT] Media Improved optimization tools to archive maximum compression and score. * [IMPROVEMENT] Media Improved speed of image pull. * [IMPROVEMENT] Media Automatically recover credit after pulled. * [REFACTOR] Config Separated configure const class. * [BUGFIX] Report Report can be sent successfully with emoji now. (@music47ell) * [IAPI] New Europe Image Optimization server (EU3/EU4). * [IAPI] New America Image Optimization server (US3/US4/US5/US6). * [IAPI] New Asian Image Optimization server (AS3). * [IAPI] Refactored optimization process. * [IAPI] Increased credit limit. * [IAPI] Removed request interval limit. * [IAPI] IAPI v2.4. * We strongly recommended that you re-optimize your image library to get a better compression result. = 2.3.1 - Jun 18 2018 = * [IMPROVEMENT] New setting to disable Generate Critical CSS. (@cybmeta) * [IMPROVEMENT] Added filter to can_cdn/can_optm check. (@Jacob) * [UPDATE] *Critical CSS* Added 404 css. Limit cron interval. * [UPDATE] AJAX will not bypass CDN anymore by default. (@Jacob) * [GUI] Show Disable All Features warning if it is on in Debug tab. = 2.3 - Jun 13 2018 = * [NEW FEATURE] Automatically generate critical CSS. (@joeee @ivan_ivanov @3dseo) * [BUGFIX] "Mark this page as..." from dropdown menu will not reset settings anymore. (@cbratschi) = 2.2.7 - Jun 4 2018 = * [IMPROVEMENT] Improved redirection for manual image pull to avoid too many redirections warning. * [IAPI] Increased credit limit. * [BUGFIX] Fixed 503 error when enabling log filters in Debug tab. (#525206) * [UPDATE] Improve compatibility when using sitemap url on servers with allow_url_open off. * [UPDATE] Removed Crawler HTTP2 option due to causing no-cache blacklist issue for certain environments. * [UPDATE] Privacy policy can be now translated. (@Josemi) * [UPDATE] IAPI Increased default img request max to 3000. = 2.2.6 - May 24 2018 = * [NEW FEATURE] Original image backups can be removed now. (@borisov87 @JMCA2) * [BUGFIX] Role Excludes in Tuning tab can save now. (@pako69) * [UPDATE] Added privacy policy support. = 2.2.5 - May 14 2018 = * [IAPI] Image Optimization New Asian Image Optimization server (AS2). * [INTEGRATION] Removed wpForo 3rd party file. (@massimod) = 2.2.4 - May 7 2018 = * [IMPROVEMENT] Improved compatibility with themes using the same js_min library. (#129093 @Darren) * [BUGFIX] Fixed a bug when checking image path for dynamic files. (@miladk) * [INTEGRATION] Compatibility with Universal Star Rating. (@miladk) = 2.2.3 - Apr 27 2018 = * [NEW FEATURE] WebP For Extra srcset setting in Media tab. (@vengen) * [REFACTOR] Removed redundant LS consts. * [REFACTOR] Refactored adv_cache generation flow. * [BUGFIX] Fixed issue where inline JS minify exception caused a blank page. (@oomskaap @kenb1978) * [UPDATE] Changed HTTP/2 Crawl default value to OFF. * [UPDATE] Added img.data-src to default WebP replacement value for WooCommerce WebP support. * [UPDATE] Detached crawler from LSCache LITESPEED_ON status. * [API] Improved ESI API to honor the cache control in ESI wrapper. * [API] Added LITESPEED_PURGE_SILENT const to bypass the notification when purging * [INTEGRATION] Fixed issue with nonce expiration when using ESI API. (#923505 @Dan) * [INTEGRATION] Improved compatibility with Ninja Forms by bypassing non-javascript JS from inline JS minify. * [INTEGRATION] Added a hook for plugins that change the CSS/JS path e.g. Hide My WordPress. = 2.2.2 - Apr 16 2018 = * [NEW FEATURE] WebP Attribute To Replace setting in Media tab. (@vengen) * [IMPROVEMENT] Generate adv_cache file automatically when it is lost. * [IMPROVEMENT] Improved compatibility with ajax login. (@veganostomy) * [UPDATE] Added object cache lib check in case user downgrades LSCWP to non-object-cache versions. * [UPDATE] Avoided infinite loop when users enter invalid hook values in Purge All Hooks settings. * [UPDATE] Updated log format in media&cdn class. * [UPDATE] Added more items to Report. = 2.2.1 - Apr 10 2018 = * [NEW FEATURE] Included Directories setting in CDN tab. (@Dave) * [NEW FEATURE] Purge All Hooks setting in Advanced tab. * [UPDATE] Added background-image WebP replacement support. (@vengen) * [UPDATE] Show recommended values for textarea items in settings. * [UPDATE] Moved CSS/JS optimizer log to Advanced level. * [INTEGRATION] Added WebP support for Avada Fusion Sliders. (@vengen) = 2.2.0.2 - Apr 3 2018 = * [HOTFIX] Object Cache Fixed the PHP warning caused by previous improvement to Object Cache. = 2.2.0.1 - Apr 3 2018 = * [HOTFIX] Object parameter will no longer cause warnings to be logged for Purge and Cache classes. (@kelltech @khrifat) * [UPDATE] Removed duplicated del_file func from Object Cache class. * [BUGFIX] `CLI` no longer shows 400 error upon successful result. = 2.2 - Apr 2 2018 = * [NEW FEATURE] Debug Disable All Features setting in Debug tab. (@monarobase) * [NEW FEATURE] Cache Force Cacheable URIs setting in Excludes tab. * [NEW FEATURE] Purge Purge all LSCache and other caches in one link. * [REFACTOR] Purge Refactored Purge class. * [BUGFIX] Query strings in DoNotCacheURI setting now works. * [BUGFIX] Cache Mobile cache compatibility with WebP vary. (@Shivam #987121) * [UPDATE] Purge Moved purge_all to Purge class from core class. * [API] Set cacheable/Set force cacheable. (@Jacob) = 2.1.2 - Mar 28 2018 = * [NEW FEATURE] Image Optimization Clean Up Unfinished Data feature. * [IAPI] IAPI v2.1.2. * [IMPROVEMENT] CSS/JS Minify Reduced loading time significantly by improving CSS/JS minify loading process. (@kokers) * [IMPROVEMENT] CSS/JS Minify Cache empty JS Minify content. (@kokers) * [IMPROVEMENT] Cache Cache 301 redirect when scheme/host are same. * [BUGFIX] Media Lazy load now can support WebP. (@relle) * [UPDATE] CSS/JS Optimize Serve static files for CSS async & lazy load JS library. * [UPDATE] Report Appended Basic/Advanced View setting to Report. * [UPDATE] CSS/JS Minify Removed zero-width space from CSS/JS content. * [GUI] Added Purge CSS/JS Cache link in Admin. = 2.1.1.1 - Mar 21 2018 = * [BUGFIX] Fixed issue where activation failed to add rules to .htaccess. * [BUGFIX] Fixed issue where 304 header was blank on feed page refresh. = 2.1.1 - Mar 20 2018 = * [NEW FEATURE] Browser Cache Unlocked for non-LiteSpeed users. * [IMPROVEMENT] Image Optimization Fixed issue where images with bad postmeta value continued to show in not-yet-requested queue. = 2.1 - Mar 15 2018 = * [NEW FEATURE] Image Optimization Unlocked for non-LiteSpeed users. * [NEW FEATURE] Object Cache Unlocked for non-LiteSpeed users. * [NEW FEATURE] Crawler Unlocked for non-LiteSpeed users. * [NEW FEATURE] Database Cleaner and Optimizer Unlocked for non-LiteSpeed users. * [NEW FEATURE] Lazy Load Images Unlocked for non-LiteSpeed users. * [NEW FEATURE] CSS/JS/HTML Minify/Combine Optimize Unlocked for non-LiteSpeed users. * [IAPI] IAPI v2.0. * [IAPI] Increased max rows prefetch when client has additional credit. * [IMPROVEMENT] CDN Multiple domains may now be used. * [IMPROVEMENT] Report Added WP environment constants for better debugging. * [REFACTOR] Separated Cloudflare CDN class. * [BUGFIX] Image Optimization Fixed issue where certain MySQL version failed to create img_optm table. (@philippwidmer) * [BUGFIX] Image Optimization Fixed issue where callback validation failed when pulling and sending request simultaneously. * [GUI] Added Slack community banner. * [INTEGRATION] CDN compatibility with WPML multiple domains. (@egemensarica) = 2.0 - Mar 7 2018 = * [NEW FEATURE] Image Optimization Added level up guidance. * [REFACTOR] Image Optimization Refactored Image Optimization class. * [IAPI] Image Optimization New European Image Optimization server (EU2). * [IMPROVEMENT] Image Optimization Manual pull action continues pulling until complete. * [IMPROVEMENT] CDN Multiple CDNs can now be randomized for a single resource. * [IMPROVEMENT] Image Optimization Improved compatibility of long src images. * [IMPROVEMENT] Image Optimization Reduced runtime load. * [IMPROVEMENT] Image Optimization Avoid potential loss/reset of notified images status when pulling. * [IMPROVEMENT] Image Optimization Avoid duplicated optimization for multiple records in Media that have the same image source. * [IMPROVEMENT] Image Optimization Fixed issue where phantom images continued to show in not-yet-requested queue. * [BUGFIX] Core Improved compatibility when upgrading outside of WP Admin. (@jikatal @TylorB) * [BUGFIX] Crawler Improved HTTP/2 compatibility to avoid erroneous blacklisting. * [BUGFIX] Crawler Changing Delay setting will use server variable for min value validation if set. * [UPDATE] Crawler Added HTTP/2 protocol switch in the Crawler settings. * [UPDATE] Removed unnecessary translation strings. * [GUI] Display translated role group name string instead of English values. (@Richard Hordern) * [GUI] Added Join LiteSpeed Slack link. * [GUI] Import / Export Cosmetic changes to Import Settings file field. * [INTEGRATION] Improved compatibility with WPML Media for Image Optimization. (@szmigieldesign) = 1.9.1.1 - February 20 2018 = * [Hotfix] Removed empty crawler when no role simulation is set. = 1.9.1 - February 20 2018 = * [NEW FEATURE] Role Simulation crawler. * [NEW FEATURE] WebP multiple crawler. * [NEW FEATURE] HTTP/2 support for crawler. * [BUGFIX] Fixed a js bug with the auto complete mobile user agents field when cache mobile is turned on. * [BUGFIX] Fixed a constant undefined warning after activation. * [GUI] Sitemap generation settings are no longer hidden when using a custom sitemap. = 1.9 - February 12 2018 = * [NEW FEATURE] Inline CSS/JS Minify. * [IMPROVEMENT] Removed Composer vendor to thin the plugin folder. * [UPDATE] Tweaked H2 to H1 in Admin headings for accessibility. (@steverep) * [GUI] Added Mobile User Agents to basic view. * [GUI] Moved Object Cache & Browser Cache from Cache tab to Advanced tab. * [GUI] Moved LSCache Purge All from Adminbar to dropdown menu. = 1.8.3 - February 2 2018 = * [NEW FEATURE] Crawler server variable limitation support. * [IMPROVEMENT] Added Store Transients option to fix transients missing issue when Cache Wp-Admin setting is OFF. * [IMPROVEMENT] Tweaked ARIA support. (@steverep) * [IMPROVEMENT] Used strpos instead of strncmp for performance. (@Zach E) * [BUGFIX] Transient cache can now be removed when the Cache Wp-Admin setting is ON in Object Cache. * [BUGFIX] Network sites can now save Advanced settings. * [BUGFIX] Media list now shows in network sites. * [BUGFIX] Show Crawler Status button is working again. * [UPDATE] Fixed a couple of potential PHP notices in the Network cache tab and when no vary group is set. * [GUI] Added Learn More link to all setting pages. = 1.8.2 - January 29 2018 = * [NEW FEATURE] Instant Click in the Advanced tab. * [NEW FEATURE] Import/Export settings. * [NEW FEATURE] Opcode Cache support. * [NEW FEATURE] Basic/Advanced setting view. * [IMPROVEMENT] Added ARIA support in widget settings. * [BUGFIX] Multiple WordPress instances with same Object Cache address will no longer see shared data. * [BUGFIX] WebP Replacement may now be set at the Network level. * [BUGFIX] Object Cache file can now be removed at the Network level uninstall. = 1.8.1 - January 22 2018 = * [NEW FEATURE] Object Cache now supports Redis. * [IMPROVEMENT] Memcached Object Cache now supports authorization. * [IMPROVEMENT] A 500 error will no longer be encountered when turning on Object Cache without the proper PHP extension installed. * [BUGFIX] Object Cache settings can now be saved at the Network level. * [BUGFIX] Mu-plugin now supports Network setting. * [BUGFIX] Fixed admin bar showing inaccurate Edit Page link. * [UPDATE] Removed warning information when no Memcached server is available. = 1.8 - January 17 2018 = * [NEW FEATURE] Object Cache. * [REFACTOR] Refactored Log class. * [REFACTOR] Refactored LSCWP basic const initialization. * [BUGFIX] Fixed Cloudflare domain search breaking when saving more than 50 domains under a single account. * [UPDATE] Log filter settings are now their own item in the wp-option table. = 1.7.2 - January 5 2018 = * [NEW FEATURE] Cloudflare API support. * [IMPROVEMENT] IAPI key can now be reset to avoid issues when domain is changed. * [BUGFIX] Fixed JS optimizer breaking certain plugins JS. * [UPDATE] Added cdn settings to environment report. * [GUI] Added more shortcuts to backend adminbar. * [INTEGRATION] WooCommerce visitors are now served from public cache when cart is empty. = 1.7.1.1 - December 29 2017 = * [BUGFIX] Fixed an extra trailing underscore issue when saving multiple lines with DNS Prefetch. * [UPDATE] Cleaned up unused dependency vendor files. = 1.7.1 - December 28 2017 = * [NEW FEATURE] Added DNS Prefetch setting on the Optimize page. * [NEW FEATURE] Added Combined File Max Size setting on the Tuning page. * [IMPROVEMENT] Improved JS/CSS minify to achieve higher page scores. * [IMPROVEMENT] Optimized JS/CSS files will not be served from private cache for OLS or with ESI off. * [UPDATE] Fixed a potential warning for new installations on the Settings page. * [UPDATE] Fixed an issue with guest users occasionally receiving PHP warnings. * [BUGFIX] Fixed a bug with the Improve HTTPS Compatibility setting failing to save. * Thanks to all of our users for your encouragement and support! Happy New Year! * PS: Lookout 2018, we're back! = 1.7 - December 22 2017 = * [NEW FEATURE] Drop Query Strings setting in the Cache tab. * [NEW FEATURE] Multiple CDN Mapping in the CDN tab. * [IMPROVEMENT] Improve HTTP/HTTPS Compatibility setting in the Advanced tab. * [IMPROVEMENT] Keep JS/CSS original position in HTML when excluded in setting. * [IAPI] Reset client level credit after Image Optimization data is destroyed. * [REFACTOR] Refactored build_input/textarea functions in admin_display class. * [REFACTOR] Refactored CDN class. * [GUI] Added a notice to Image Optimization and Crawler to warn when cache is disabled. * [GUI] Improved image optimization indicator styles in Media Library List. = 1.6.7 - December 15 2017 = * [IAPI] Added ability to scan for new image thumbnail sizes and auto-resend image optimization requests. * [IAPI] Added ability to destroy all optimization data. * [IAPI] Updated IAPI to v1.6.7. * [INTEGRATION] Fixed certain 3rd party plugins calling REST without user nonce causing logged in users to be served as guest. = 1.6.6.1 - December 8 2017 = * [IAPI] Limit first-time submission to one image group for test-run purposes. * [BUGFIX] Fixed vary group generation issue associated with custom user role plugins. * [BUGFIX] Fixed WooCommerce issue where logged-in users were erroneously purged when ESI is off. * [BUGFIX] Fixed WooCommerce cache miss issue when ESI is off. = 1.6.6 - December 6 2017 = * [NEW FEATURE] Preserve EXIF in Media setting. * [NEW FEATURE] Clear log button in Debug Log Viewer. * [IAPI] Fixed notified images resetting to previous status when pulling. * [IAPI] Fixed HTTPS compatibility for image optimization initialization. * [IAPI] An error message is now displayed when image optimization request submission is bypassed due to a lack of credit. * [IAPI] IAPI v1.6.6. * [IMPROVEMENT] Support JS data-no-optimize attribute to bypass optimization. * [GUI] Added image group wiki link. * [INTEGRATION] Improved compatibility with Login With Ajax. * [INTEGRATION] Added function_exists check for WooCommerce to avoid 500 errors. = 1.6.5.1 - December 1 2017 = * [HOTFIX] Fixed warning message on Edit .htaccess page. = 1.6.5 - November 30 2017 = * [IAPI] Manually pull image optimization action button. * [IAPI] Automatic credit system for image optimization to bypass unfinished image optimization error. * [IAPI] Notify failed images from LiteSpeed's Image Server. * [IAPI] Reset/Clear failed images feature. * [IAPI] Redesigned report page. * [REFACTOR] Moved pull_img logic from admin_api to media. * [BUGFIX] Fixed a compatibility issue for clients who have allow_url_open setting off. * [BUGFIX] Fixed logged in users sometimes being served from guest cache. * [UPDATE] Environment report is no longer saved to a file. * [UPDATE] Removed crawler reset notification. * [GUI] Added more details on image optimization. * [GUI] Removed info page from admin menu. * [GUI] Moved environment report from network level to single site level. * [GUI] Crawler time added in a user friendly format. * [INTEGRATION] Improved compatibility with FacetWP json call. = 1.6.4 - November 22 2017 = * [NEW FEATURE] Send env reports privately with a new built-in report number referral system. * [IAPI] Increased request timeout to fix a cUrl 28 timeout issue. * [BUGFIX] Fixed a TTL max value validation bug. * [INTEGRATION] Improved Contact Form 7 REST call compatibility for logged in users. * Thanks for all your ratings. That encouraged us to be more diligent. Happy Thanksgiving. = 1.6.3 - November 17 2017 = * [NEW FEATURE] Only async Google Fonts setting. * [NEW FEATURE] Only create WebP images when optimizing setting. * [NEW FEATURE] Batch switch images to original/optimized versions in Image Optimization. * [NEW FEATURE] Browser Cache TTL setting. * [NEW FEATURE] Cache WooCommerce Cart setting. * [IMPROVEMENT] Moved optimized JS/CSS snippet in header html to after meta charset. * [IMPROVEMENT] Added a constant for better JS/CSS optimization compatibility for different dir WordPress installation. * [IAPI] Take over failed callback check instead of bypassing it. * [IAPI] Image optimization requests are now limited to 500 images per request. * [BUGFIX] Fixed a parsing failure bug not using attributes in html elements with dash. * [BUGFIX] Fixed a bug causing non-script code to move to the top of a page when not using combination. * [UPDATE] Added detailed logs for external link detection. * [UPDATE] Added new lines in footer comment to avoid Firefox crash when enabled HTML minify. * [API] `Purge private` / `Purge private all` / `Add private tag` functions. * [GUI] Redesigned image optimization operation links in Media Lib list. * [GUI] Tweaked wp-admin form save button position. * [GUI] Added "learn more" link for image optimization. = 1.6.2.1 - November 6 2017 = * [INTEGRATION] Improved compatibility with old WooCommerce versions to avoid unknown 500 errors. * [BUGFIX] Fixed WebP images sometimes being used in non-supported browsers. * [BUGFIX] Kept query strings for HTTP/2 push to avoid re-fetching pushed sources. * [BUGFIX] Excluded JS/CSS from HTTP/2 push when using CDN. * [GUI] Fixed a typo in Media list. * [GUI] Made more image optimization strings translatable. * [GUI] Updated Tuning description to include API documentation. = 1.6.2 - November 3 2017 = * [NEW FEATURE] Do Not Cache Roles. * [NEW FEATURE] Use WebP Images for supported browsers. * [NEW FEATURE] Disable Optimization Poll ON/OFF Switch in Media tab. * [NEW FEATURE] Revert image optimization per image in Media list. * [NEW FEATURE] Disable/Enable image WebP per image in Media list. * [IAPI] Limit optimized images fetching cron to a single process. * [IAPI] Updated IAPI to v1.6.2. * [IAPI] Fixed repeating image request issue by adding a failure status to local images. * [REFACTOR] Refactored login vary logic. = 1.6.1 - October 29 2017 = * [IAPI] Updated LiteSpeed Image Optimization Server API to v1.6.1. = 1.6 - October 27 2017 = * [NEW FEATURE] Image Optimization. * [NEW FEATURE] Role Excludes for Optimization. * [NEW FEATURE] Combined CSS/JS Priority. * [IMPROVEMENT] Bypass CDN for login/register page. * [UPDATE] Expanded ExpiresByType rules to include new font types. ( Thanks to JMCA2 ) * [UPDATE] Removed duplicated type param in admin action link. * [BUGFIX] Fixed CDN wrongly replacing img base64 and "fake" src in JS. * [BUGFIX] Fixed image lazy load replacing base64 src. * [BUGFIX] Fixed a typo in Optimize class exception. * [GUI] New Tuning tab in admin settings panel. * [REFACTOR] Simplified router by reducing actions and adding types. * [REFACTOR] Renamed `run()` to `finalize()` in buffer process. = 1.5 - October 17 2017 = * [NEW FEATURE] Exclude JQuery (to fix inline JS error when using JS Combine). * [NEW FEATURE] Load JQuery Remotely. * [NEW FEATURE] JS Deferred Excludes. * [NEW FEATURE] Lazy Load Images Excludes. * [NEW FEATURE] Lazy Load Image Placeholder. * [IMPROVEMENT] Improved Lazy Load size attribute for w3c validator. * [UPDATE] Added basic caching info and LSCWP version to HTML comment. * [UPDATE] Added debug log to HTML detection. * [BUGFIX] Fixed potential font CORS issue when using CDN. * [GUI] Added API docs to setting description. * [REFACTOR] Relocated all classes under includes with backwards compatibility. * [REFACTOR] Relocated admin templates. = 1.4 - October 11 2017 = * [NEW FEATURE] Lazy load images/iframes. * [NEW FEATURE] Clean CSS/JS optimizer data functionality in DB Optimizer panel. * [NEW FEATURE] Exclude certain URIs from optimizer. * [IMPROVEMENT] Improved optimizer HTML check compatibility to avoid conflicts with ESI functions. * [IMPROVEMENT] Added support for using ^ when matching the start of a path in matching settings. * [IMPROVEMENT] Added wildcard support in CDN original URL. * [IMPROVEMENT] Moved optimizer table initialization to admin setting panel with failure warning. * [UPDATE] Added a one-time welcome banner. * [UPDATE] Partly relocated class: 'api'. * [API] Added API wrapper for removing wrapped HTML output. * [INTEGRATION] Fixed WooCommerce conflict with optimizer. * [INTEGRATION] Private cache support for WooCommerce v3.2.0+. * [GUI] Added No Optimization menu to frontend. = 1.3.1.1 - October 6 2017 = * [BUGFIX] Improved optimizer table creating process in certain database charset to avoid css/js minify/combination failure. = 1.3.1 - October 5 2017 = * [NEW FEATURE] Remove WP Emoji Option. * [IMPROVEMENT] Separated optimizer data from wp_options to improve compatibility with backup plugins. * [IMPROVEMENT] Enhanced crawler cron hook to prevent de-scheduling in some cases. * [IMPROVEMENT] Enhanced Remove Query Strings to also remove Emoji query strings. * [IMPROVEMENT] Enhanced HTML detection when extra spaces are present at the beginning. * [UPDATE] Added private cache support for OLS. * [BUGFIX] Self-redirects are no longer cached. * [BUGFIX] Fixed css async lib warning when loading in HTTP/2 push. = 1.3 - October 1 2017 = * [NEW FEATURE] Added Browser Cache support. * [NEW FEATURE] Added Remove Query Strings support. * [NEW FEATURE] Added Remove Google Fonts support. * [NEW FEATURE] Added Load CSS Asynchronously support. * [NEW FEATURE] Added Load JS Deferred support. * [NEW FEATURE] Added Critical CSS Rules support. * [NEW FEATURE] Added Private Cached URIs support. * [NEW FEATURE] Added Do Not Cache Query Strings support. * [NEW FEATURE] Added frontend adminbar shortcuts ( Purge this page/Do Not Cache/Private cache ). * [IMPROVEMENT] Do Not Cache URIs now supports full URLs. * [IMPROVEMENT] Improved performance of Do Not Cache settings. * [IMPROVEMENT] Encrypted vary cookie. * [IMPROVEMENT] Enhanced HTML optimizer. * [IMPROVEMENT] Limited combined file size to avoid heavy memory usage. * [IMPROVEMENT] CDN supports custom upload folder for media files. * [API] Added purge single post API. * [API] Added version compare API. * [API] Enhanced ESI API for third party plugins. * [INTEGRATION] Compatibility with NextGEN Gallery v2.2.14. * [INTEGRATION] Compatibility with Caldera Forms v1.5.6.2+. * [BUGFIX] Fixed CDN&Minify compatibility with css url links. * [BUGFIX] Fixed .htaccess being regenerated despite there being no changes. * [BUGFIX] Fixed CDN path bug for subfolder WP instance. * [BUGFIX] Fixed crawler path bug for subfolder WP instance with different site url and home url. * [BUGFIX] Fixed a potential Optimizer generating redundant duplicated JS in HTML bug. * [GUI] Added a more easily accessed submit button in admin settings. * [GUI] Admin settings page cosmetic changes. * [GUI] Reorganized GUI css/img folder structure. * [REFACTOR] Refactored configuration init. * [REFACTOR] Refactored admin setting save. * [REFACTOR] Refactored .htaccess operator and rewrite rule generation. = 1.2.3.1 - September 20 2017 = * [UPDATE] Improved PHP5.3 compatibility. = 1.2.3 - September 20 2017 = * [NEW FEATURE] Added CDN support. * [IMPROVEMENT] Improved compatibility when upgrading by fixing a possible fatal error. * [IMPROVEMENT] Added support for custom wp-content paths. * [BUGFIX] Fixed non-primary network blogs not being able to minify. * [BUGFIX] Fixed HTML Minify preventing Facebook from being able to parse og tags. * [BUGFIX] Preview page is no longer cacheable. * [BUGFIX] Corrected log and crawler timezone to match set WP timezone. * [GUI] Revamp of plugin GUI. = 1.2.2 - September 15 2017 = * [NEW FEATURE] Added CSS/JS minification. * [NEW FEATURE] Added CSS/JS combining. * [NEW FEATURE] Added CSS/JS HTTP/2 server push. * [NEW FEATURE] Added HTML minification. * [NEW FEATURE] Added CSS/JS cache purge button in management. * [UPDATE] Improved debug log formatting. * [UPDATE] Fixed some description typos. = 1.2.1 - September 7 2017 = * [NEW FEATURE] Added Database Optimizer. * [NEW FEATURE] Added Tab switch shortcut. * [IMPROVEMENT] Added cache disabled check for management pages. * [IMPROVEMENT] Renamed .htaccess backup for security. * [BUGFIX] Fixed woocommerce default ESI setting bug. * [REFACTOR] Show ESI page for OLS with notice. * [REFACTOR] Management Purge GUI updated. = 1.2.0.1 - September 1 2017 = * [BUGFIX] Fixed a naming bug for network constant ON2. = 1.2.0 - September 1 2017 = * [NEW FEATURE] Added ESI support. * [NEW FEATURE] Added a private cache TTL setting. * [NEW FEATURE] Debug level can now be set to either 'Basic' or 'Advanced'. * [REFACTOR] Renamed const 'NOTSET' to 'ON2' in class config. = 1.1.6 - August 23 2017 = * [NEW FEATURE] Added option to privately cache logged-in users. * [NEW FEATURE] Added option to privately cache commenters. * [NEW FEATURE] Added option to cache requests made through WordPress REST API. * [BUGFIX] Fixed network 3rd-party full-page cache detection bug. * [GUI] New Cache and Purge menus in Settings. = 1.1.5.1 - August 16 2017 = * [IMPROVEMENT] Improved compatibility of frontend&backend .htaccess path detection when site url is different than installation path. * [UPDATE] Removed unused format string from header tags. * [BUGFIX] 'showheader' Admin Query String now works. * [REFACTOR] Cache tags will no longer output if not needed. = 1.1.5 - August 10 2017 = * [NEW FEATURE] Scheduled Purge URLs feature. * [NEW FEATURE] Added buffer callback to improve compatibility with some plugins that force buffer cleaning. * [NEW FEATURE] Hide purge_all admin bar quick link if cache is disabled. * [NEW FEATURE] Required htaccess rules are now displayed when .htaccess is not writable. * [NEW FEATURE] Debug log features: filter log support; heartbeat control; log file size limit; log viewer. * [IMPROVEMENT] Separate crawler access log. * [IMPROVEMENT] Lazy PURGE requests made after output are now queued and working. * [IMPROVEMENT] Improved readme.txt with keywords relating to our compatible plugins list. * [UPDATE] 'ExpiresDefault' conflict msg is now closeable and only appears in the .htaccess edit screen. * [UPDATE] Improved debug log formatting. * [INTEGRATION] Compatibility with MainWP plugin. * [BUGFIX] Fixed WooCommerce order not purging product stock quantity. * [BUGFIX] Fixed WooCommerce scheduled sale price not updating issue. * [REFACTOR] Combined cache_enable functions into a single function. = 1.1.4 - August 1 2017 = * [IMPROVEMENT] Unexpected rewrite rules will now show an error message. * [IMPROVEMENT] Added Cache Tag Prefix setting info in the Env Report and Info page. * [IMPROVEMENT] LSCWP setting link is now displayed in the plugin list. * [IMPROVEMENT] Improved performance when setting cache control. * [UPDATE] Added backward compatibility for v1.1.2.2 API calls. (used by 3rd-party plugins) * [BUGFIX] Fixed WPCLI purge tag/category never succeeding. = 1.1.3 - July 31 2017 = * [NEW FEATURE] New LiteSpeed_Cache_API class and documentation for 3rd party integration. * [NEW FEATURE] New API function litespeed_purge_single_post($post_id). * [NEW FEATURE] PHP CLI support for crawler. * [IMPROVEMENT] Set 'no cache' for same location 301 redirects. * [IMPROVEMENT] Improved LiteSpeed footer comment compatibility. * [UPDATE] Removed 'cache tag prefix' setting. * [BUGFIX] Fixed a bug involving CLI purge all. * [BUGFIX] Crawler now honors X-LiteSpeed-Cache-Control for the 'no-cache' header. * [BUGFIX] Cache/rewrite rules are now cleared when the plugin is uninstalled. * [BUGFIX] Prevent incorrect removal of the advanced-cache.php on deactivation if it was added by another plugin. * [BUGFIX] Fixed subfolder WP installations being unable to Purge By URL using a full URL path. * [REFACTOR] Reorganized existing code for an upcoming ESI release. = 1.1.2.2 - July 13 2017 = * [BUGFIX] Fixed blank page in Hebrew language post editor by removing unused font-awesome and jquery-ui css libraries. = 1.1.2.1 - July 5 2017 = * [UPDATE] Improved compatibility with WooCommerce v3.1.0. = 1.1.2 - June 20 2017 = * [BUGFIX] Fixed missing form close tag. * [UPDATE] Added a wiki link for enabling the crawler. * [UPDATE] Improved Site IP description. * [UPDATE] Added an introduction to the crawler on the Information page. * [REFACTOR] Added more detailed error messages for Site IP and Custom Sitemap settings. = 1.1.1.1 - June 15 2017 = * [BUGFIX] Hotfix for insufficient validation of site IP value in crawler settings. = 1.1.1 - June 15 2017 = * [NEW] As of LiteSpeed Web Server v.5.1.16, the crawler can now be enabled/disabled at the server level. * [NEW] Added the ability to provide a custom sitemap for crawling. * [NEW] Added ability to use site IP address directly in crawler settings. * [NEW] Crawler performance improved with the use of new custom user agent 'lsrunner'. * [NEW] "Purge By URLs" now supports full URL paths. * [NEW] Added thirdparty WP-PostRatings compatibility. * [BUGFIX] Cache is now cleared when changing post status from published to draft. * [BUGFIX] WHM activation message no longer continues to reappear after being dismissed. * [COSMETIC] Display recommended values for settings. = 1.1.0.1 - June 8 2017 = * [UPDATE] Improved default crawler interval setting. * [UPDATE] Tested up to WP 4.8. * [BUGFIX] Fixed compatibility with plugins that output json data. * [BUGFIX] Fixed tab switching bug. * [BUGFIX] Removed occasional duplicated messages on save. * [COSMETIC] Improved crawler tooltips and descriptions. = 1.1.0 - June 6 2017 = * [NEW] Added a crawler - this includes configuration options and a dedicated admin page. Uses wp-cron * [NEW] Added integration for WPLister * [NEW] Added integration for Avada * [UPDATE] General structure of the plugin revamped * [UPDATE] Improved look of admin pages * [BUGFIX] Fix any/all wp-content path retrieval issues * [BUGFIX] Use realpath to clear symbolic link when determining .htaccess paths * [BUGFIX] Fixed a bug where upgrading multiple plugins did not trigger a purge all * [BUGFIX] Fixed a bug where cli import_options did not actually update the options. * [REFACTOR] Most of the files in the code were split into more, smaller files = 1.0.15 - April 20 2017 = * [NEW] Added Purge Pages and Purge Recent Posts Widget pages options. * [NEW] Added wp-cli command for setting and getting options. * [NEW] Added an import/export options cli command. * [NEW] Added wpForo integration. * [NEW] Added Theme My Login integration. * [UPDATE] Purge adjacent posts when publish a new post. * [UPDATE] Change environment report file to .php and increase security. * [UPDATE] Added new purgeby option to wp-cli. * [UPDATE] Remove nag for multiple sites. * [UPDATE] Only inject LiteSpeed javascripts in LiteSpeed pages. * [REFACTOR] Properly check for zero in ttl settings. * [BUGFIX] Fixed the 404 issue that can be caused by some certain plugins when save the settings. * [BUGFIX] Fixed mu-plugin compatibility. * [BUGFIX] Fixed problem with creating zip backup. * [BUGFIX] Fixed conflict with jetpack. = 1.0.14.1 - January 31 2017 = * [UPDATE] Removed Freemius integration due to feedback. = 1.0.14 - January 30 2017 = * [NEW] Added error page caching. Currently supports 403, 404, 500s. * [NEW] Added a purge errors action. * [NEW] Added wp-cli integration. * [UPDATE] Added support for multiple varies. * [UPDATE] Reorganize the admin interface to be less cluttered. * [UPDATE] Add support for LiteSpeed Web ADC. * [UPDATE] Add Freemius integration. * [REFACTOR] Made some changes so that the rewrite rules are a little more consistent. * [BUGFIX] Check member type before adding purge all button. * [BUGFIX] Fixed a bug where activating/deactivating the plugin quickly caused the WP_CACHE error to show up. * [BUGFIX] Handle more characters in the rewrite parser. * [BUGFIX] Correctly purge posts when they are made public/private. = 1.0.13.1 - November 30 2016 = * [BUGFIX] Fixed a bug where a global was being used without checking existence first, causing unnecessary log entries. = 1.0.13 - November 28 2016 = * [NEW] Add an Empty Entire Cache button. * [NEW] Add stale logic to certain purge actions. * [NEW] Add option to use primary site settings for all subsites in a multisite environment. * [NEW] Add support for Aelia CurrencySwitcher * [UPDATE] Add logic to allow third party vary headers * [UPDATE] Handle password protected pages differently. * [BUGFIX] Fixed bug caused by saving settings. * [BUGFIX] FIxed bug when searching for advanced-cache.php = 1.0.12 - November 14 2016 = * [NEW] Added logic to generate environment reports. * [NEW] Created a notice that will be triggered when the WHM Plugin installs this plugin. This will notify users when the plugin is installed by their server admin. * [NEW] Added the option to cache 404 pages via 404 Page TTL setting. * [NEW] Reworked log system to be based on selection of yes or no instead of log level. * [NEW] Added support for Autoptimize. * [NEW] Added Better WP Minify integration. * [UPDATE] On plugin disable, clear .htaccess. * [UPDATE] Introduced URL tag. Changed Purge by URL to use this new tag. * [BUGFIX] Fixed a bug triggered when .htaccess files were empty. * [BUGFIX] Correctly determine when to clear files in multisite environments (wp-config, advanced-cache, etc.). * [BUGFIX] When disabling the cache, settings changed in the same save will now be saved. * [BUGFIX] Various bugs from setting changes and multisite fixed. * [BUGFIX] Fixed two bugs with the .htaccess path search. * [BUGFIX] Do not alter $_GET in add_quick_purge. This may cause issues for functionality occurring later in the same request. * [BUGFIX] Right to left radio settings were incorrectly displayed. The radio buttons themselves were the opposite direction of the associated text. = 1.0.11 - October 11 2016 = * [NEW] The plugin will now set cachelookup public on. * [NEW] New option - check advanced-cache.php. This enables users to have two caching plugins enabled at the same time as long as the other plugin is not used for caching purposes. For example, using another cache plugin for css/js minification. * [UPDATE] Rules added by the plugin will now be inserted into an LSCACHE START/END PLUGIN comment block. * [UPDATE] For woocommerce pages, if a user visits a non-cached page with a non-empty cart, do not cache the page. * [UPDATE] If woocommerce needs to display any notice, do not cache the page. * [UPDATE] Single site settings are now in both the litespeed cache submenu and the settings submenu. * [BUGFIX] Multisite network options were not updated on upgrade. This is now corrected. = 1.0.10 - September 16 2016 = * Added a check for LSCACHE_NO_CACHE definition. * Added a Purge All button to the admin bar. * Added logic to purge the cache when upgrading a plugin or theme. By default this is enabled on single site installations and disabled on multisite installations. * Added support for WooCommerce Versions < 2.5.0. * Added .htaccess backup rotation. Every 10 backups, an .htaccess archive will be created. If one already exists, it will be overwritten. * Moved some settings to the new Specific Pages tab to reduce clutter in the General tab. * The .htaccess editor is now disabled if DISALLOW_FILE_EDIT is set. * After saving the Cache Tag Prefix setting, all cache will be purged. = 1.0.9.1 - August 26 2016 = * Fixed a bug where an error displayed on the configuration screen despite not being an error. * Change logic to check .htaccess file less often. = 1.0.9 - August 25 2016 = * [NEW] Added functionality to cache and purge feeds. * [NEW] Added cache tag prefix setting to avoid conflicts when using LiteSpeed Cache for WordPress with LiteSpeed Cache for XenForo and LiteMage. * [NEW] Added hooks to allow third party plugins to create config options. * [NEW] Added WooCommerce config options. * The plugin now also checks for wp-config in the parent directory. * Improved WooCommerce support. * Changed .htaccess backup process. Will create a .htaccess_lscachebak_orig file if one does not exist. If it does already exist, creates a backup using the date and timestamp. * Fixed a bug where get_home_path() sometimes returned an invalid path. * Fixed a bug where if the .htaccess was removed from a WordPress subdirectory, it was not handled properly. = 1.0.8.1 - July 28 2016 = * Fixed a bug where check cacheable was sometimes not hit. * Fixed a bug where extra slashes in clear rules were stripped. = 1.0.8 - July 25 2016 = * Added purge all on update check to purge by post id logic. * Added uninstall logic. * Added configuration for caching favicons. * Added configuration for caching the login page. * Added configuration for caching php resources (scripts/stylesheets accessed as .php). * Set login cookie if user is logged in and it isnโ€™t set. * Improved NextGenGallery support to include new actions. * Now displays a notice on the network admin if WP_CACHE is not set. * Fixed a few php syntax issues. * Fixed a bug where purge by pid didnโ€™t work. * Fixed a bug where the Network Admin settings were shown when the plugin was active in a subsite, but not network active. * Fixed a bug where the Advanced Cache check would sometimes not work. = 1.0.7.1 - May 26 2016 = * Fixed a bug where enabling purge all in the auto purge on update settings page did not purge the correct blogs. * Fixed a bug reported by user wpc on our forums where enabling purge all in the auto purge on update settings page caused nothing to be cached. = 1.0.7 - May 24 2016 = * Added login cookie configuration to the Advanced Settings page. * Added support for WPTouch plugin. * Added support for WP-Polls plugin. * Added Like Dislike Counter third party integration. * Added support for Admin IP Query String Actions. * Added confirmation pop up for purge all. * Refactor: LiteSpeed_Cache_Admin is now split into LiteSpeed_Cache_Admin, LiteSpeed_Cache_Admin_Display, and LiteSpeed_Cache_Admin_Rules * Refactor: Rename functions to accurately represent their functionality * Fixed a bug that sometimes caused a โ€œno valid headerโ€ error message. = 1.0.6 - May 5 2016 = * Fixed a bug reported by Knut Sparhell that prevented dashboard widgets from being opened or closed. * Fixed a bug reported by Knut Sparhell that caused problems with https support for admin pages. = 1.0.5 - April 26 2016 = * [BETA] Added NextGen Gallery plugin support. * Added third party plugin integration. * Improved cache tag system. * Improved formatting for admin settings pages. * Converted bbPress to use the new third party integration system. * Converted WooCommerce to use the new third party integration system. * If .htaccess is not writable, disable separate mobile view and do not cache cookies/user agents. * Cache is now automatically purged when disabled. * Fixed a bug where .htaccess was not checked properly when adding common rules. * Fixed a bug where multisite setups would be completely purged when one site requested a purge all. = 1.0.4 - April 7 2016 = * Added logic to cache commenters. * Added htaccess backup to the install script. * Added an htaccess editor in the wp-admin dashboard. * Added do not cache user agents. * Added do not cache cookies. * Created new LiteSpeed Cache Settings submenu entries. * Implemented Separate Mobile View. * Modified WP_CACHE not defined message to only show up for users who can manage options. * Moved enabled all/disable all from network management to network settings. * Fixed a bug where WP_CACHE was not defined on activation if it was commented out. = 1.0.3 - March 23 2016 = * Added a Purge Front Page button to the LiteSpeed Cache Management page. * Added a Default Front Page TTL option to the general settings. * Added ability to define web application specific cookie names through rewrite rules to handle logged-in cookie conflicts when using multiple web applications. [Requires LSWS 5.0.15+] * Improved WooCommerce handling. * Fixed a bug where activating lscwp sets the โ€œenable cacheโ€ radio button to enabled, but the cache was not enabled by default. * Refactored code to make it cleaner. * Updated readme.txt. = 1.0.2 - March 11 2016 = * Added a "Use Network Admin Setting" option for "Enable LiteSpeed Cache". For single sites, this choice will default to enabled. * Added enable/disable all buttons for network admin. This controls the setting of all managed sites with "Use Network Admin Setting" selected for "Enable LiteSpeed Cache". * Exclude by Category/Tag are now text areas to avoid slow load times on the LiteSpeed Cache Settings page for sites with a large number of categories/tags. * Added a new line to advanced-cache.php to allow identification as a LiteSpeed Cache file. * Activation/Deactivation are now better handled in multi-site environments. * Enable LiteSpeed Cache setting is now a radio button selection instead of a single checkbox. * Can now add '$' to the end of a URL in Exclude URI to perform an exact match. * The _lscache_vary cookie will now be deleted upon logout. * Fixed a bug in multi-site setups that would cause a "function already defined" error. = 1.0.1 - March 8 2016 = * Added Do Not Cache by URI, by Category, and by Tag. URI is a prefix/string equals match. * Added a help tab for plugin compatibilities. * Created logic for other plugins to purge a single post if updated. * Fixed a bug where woocommerce pages that display the cart were cached. * Fixed a bug where admin menus in multi-site setups were not correctly displayed. * Fixed a bug where logged in users were served public cached pages. * Fixed a compatibility bug with bbPress. If there is a new forum/topic/reply, the parent pages will now be purged as well. * Fixed a bug that didn't allow cron job to update scheduled posts. = 1.0.0 - January 20 2016 = * Initial Release. Welcome To – Frugalinnovationhub.com

Blog

  • How I advocate for diverse representation

    Key takeaways:

    • Diverse representation in education enriches discussions and fosters critical thinking and empathy among students.
    • Involving a diverse planning committee and engaging with the community are crucial for organizing inclusive events.
    • Collaborating with diverse speakers transforms narratives and encourages deeper discussions, impacting audience perceptions.
    • Creating accessible materials enhances engagement and inclusivity, catering to varied learning preferences and communication styles.

    Understanding diverse representation in education

    Understanding diverse representation in education

    Diverse representation in education is about more than just checking boxes; itโ€™s about creating an environment where all voices are heard and valued. I recall a time when I attended a workshop where the speaker, a member of an underrepresented group, shared their unique journey. It struck me how their perspective not only enriched the discussion but also created an immediate connection with the audience, proving that everyoneโ€™s experience contributes to the educational tapestry.

    When I think about the impact of diverse representation, I often ask myself: how can students truly thrive if they donโ€™t see themselves reflected in the curriculum? One time, I volunteered at a school where a curriculum was being developed. It was eye-opening to witness how including authors and historical figures from various backgrounds transformed classroom discussions, making them more engaging and relatable for students.

    Moreover, embracing diverse representation fosters critical thinking and empathy among all students. I remember a class discussion in which a student shared their cultural background while discussing literature. This not only opened up dialogue but also prompted others to reflect on their own experiences. Isnโ€™t it powerful to think about how these interactions can shape future generations?

    Strategies for organizing inclusive events

    Strategies for organizing inclusive events

    One effective strategy for organizing inclusive events is to actively involve a diverse planning committee. In my own experience, having team members from different backgrounds not only broadened our perspectives but also helped us identify potential blind spots. I remember a conference where the committee included voices from various communities, leading us to choose topics that resonated with a wider audience. It’s fascinating how a variety of viewpoints can shape the agenda and ensure that everyone feels represented.

    Another crucial aspect is to engage with the community you want to serve before the event. During a recent seminar I helped organize, we reached out to local organizations that support underrepresented groups. This collaboration uncovered valuable insights about what the community deemed important. It made me wonder: how often are we truly listening to the needs of those we aim to engage? The feedback we received led to a significant increase in attendance and participation, demonstrating the power of dialogue.

    Additionally, creating accessible spaces is paramount. I once attended an event held in a venue that wasnโ€™t equipped for individuals with disabilities. The discomfort of those attendees was palpable, and it highlighted for me how important it is to consider physical accessibility as part of inclusivity. By ensuring that the location is welcoming to everyone, we can foster an environment where everyone can engage freely. Isn’t it essential to think about how every small detail impacts the overall experience of attending an event?

    Collaborating with diverse speakers

    Collaborating with diverse speakers

    Collaborating with diverse speakers can fundamentally transform the narrative of any educational event. I recall a workshop where we invited speakers from various cultural backgrounds, each sharing their unique experiences and knowledge. The authenticity in their voices was palpable, and attendees were not just passive listeners; they were engaged and inspired. It really made me think: how often do we miss out on enriching conversations simply by not diversifying our speaker lineup?

    Moreover, creating an environment that celebrates diverse perspectives encourages deeper discussions. In one event, a speaker from an underrepresented community shared a poignant story that resonated with many attendees, including myself. Witnessing the connections formed in that space reminded me of the importance of representation. It begs the question: how much more powerful can our messages be when they reflect the diversity of our audience?

    Additionally, I find that working with diverse speakers challenges preconceived notions within the audience. For instance, a panel I organized with speakers from various professional fields sparked unexpected dialogues about intersectionality. Participants left with not only new knowledge but also a shifted mindset. Isnโ€™t it fascinating that the inclusion of varied voices does more than inform โ€” it builds bridges between communities?

    Creating accessible event materials

    Creating accessible event materials

    Creating accessible event materials starts with understanding the diverse needs of your audience. When I organized a recent workshop, I made it a point to provide materials in various formats, including large print and digital copies. Not everyone absorbs information in the same way, and I remember how grateful some attendees were for options that suited their specific learning preferences.

    I also believe that incorporating visuals, like infographics or video summaries, can make a world of difference. At one event, we shared a short video overview which allowed attendees who might struggle with dense texts to engage more comfortably. It was a reminder that accessibility isnโ€™t just about meeting minimum standards; itโ€™s about inviting everyone into the conversation. Have you ever noticed how a well-designed graphic can communicate complex ideas more clearly than words alone?

    Moreover, simple language can often be overlooked but is equally crucial. I recall feedback from a participant who appreciated our effort to avoid jargon in our materials. It struck me that even small adjustments in language can create a more inclusive atmosphere. Isnโ€™t it empowering to consider that when we prioritize accessibility, we genuinely enhance the learning experience for all?

    Personal experiences with advocacy

    Personal experiences with advocacy

    When I first stepped into the world of advocacy, I attended an event where a panel focused on cultural diversity in education. I was deeply moved by the stories shared by speakers who represented historically marginalized groups. It made me realize how vital it is to amplify these voices and address the systemic barriers they face. Have you ever felt the energy in a room filled with people sharing their truths? Itโ€™s electric and reaffirming.

    In my own organizing efforts, I once worked with a group of college students from various backgrounds to brainstorm ideas for a community event. One participant, who was often quiet, expressed how hesitant they were to speak up because they felt their perspective was underrepresented. Listening to them made me rethink how I approached group discussions. Have you ever noticed how just one voice can shift the dynamics of a conversation? It was a powerful reminder of our responsibility to create spaces where everyone feels valued.

    I also recall a particularly impactful moment when I collaborated with a local nonprofit to host a workshop tailored for underserved communities. The hesitance and reluctance of potential participants were palpable, stemming from various past experiences. It was a challenge to address their skepticism and ensure that they felt welcome. How do we build trust in these situations? For me, the key was consistent follow-up and showing genuine interest in their stories. It taught me that advocacy is not a one-time event but an ongoing dialogue that requires patience and understanding.

  • How I advocate for transparent dialogue practices

    Key takeaways:

    • Transparent dialogue fosters trust and collaboration in educational settings, encouraging diverse perspectives and vulnerability among participants.
    • Regular feedback sessions and anonymous platforms can enhance communication, making individuals feel safe to share their thoughts.
    • Challenges such as traditional hierarchies, varying comfort with vulnerability, and logistical barriers can hinder effective dialogue practices.

    Understanding transparent dialogue practices

    Understanding transparent dialogue practices

    Transparent dialogue practices are at the heart of effective communication, especially in educational settings. I remember a workshop I attended where open discussions led to unexpected insights. It was remarkable how sharing diverse perspectives created an atmosphere that encouraged honesty. Doesnโ€™t it make you wonder how such an environment fosters both learning and trust?

    When I think about transparency in dialogue, I often reflect on the concept of vulnerability. For instance, during a panel discussion I participated in, sharing my own uncertainties about teaching methods prompted others to open up about their challenges. This exchange was not just liberating but also built connections that enriched our collective learning experience. Have you ever witnessed how sharing personal challenges can deepen understanding among peers?

    A key aspect of transparent dialogue is active listening. I’ve found that giving others space to voice their thoughts without interruption shapes the discussion. There was a moment in a community forum where allowing silence after a question prompted thoughtful responses that transformed our approach to a project. Isnโ€™t it fascinating how creating space for others not only enhances understanding but also brings forth innovative ideas?

    Importance of transparency in education

    Importance of transparency in education

    Transparency in education is crucial for fostering a culture of trust and collaboration. I recall a time when I organized an open session for students to voice their concerns about a new curriculum. The honesty that emerged was profound; students felt valued and their feedback directly influenced teaching strategies. Can you see how such openness not only enriches the educational experience but also empowers learners?

    Moreover, transparency encourages accountability among educators and institutions. I once observed a school board meeting where leaders openly shared performance data with parents. The conversation that followed was illuminating. Parents appreciated the vulnerability of the educators and actively engaged in finding solutions together. Doesnโ€™t this raise the question of how accountability can actually strengthen relationships within the educational community?

    Lastly, transparent practices can spark innovation in teaching approaches. I experienced this firsthand during a collaborative workshop where educators shared both their successes and failures. This honest exchange led to the creation of new strategies tailored to meet students’ individual needs. Have you ever thought about how vulnerability can open doors to creative thinking in education? Itโ€™s clear that transparency not only enhances dialogue but also drives progress.

    Methods for fostering open dialogue

    Methods for fostering open dialogue

    One powerful method for fostering open dialogue is the establishment of regular feedback sessions. I remember when I facilitated monthly gatherings where participants could share their experiences and suggestions regarding curriculum changes. The energy in the room was palpable; people felt heard, and that collective ownership sparked insightful discussions. Have you ever felt the relief that comes with simply being able to voice your thoughts in a supportive environment?

    Another effective approach is to create anonymous platforms for feedback. In one of my previous roles, we implemented an online anonymous survey that allowed everyone to contribute their ideas without fear of judgment. The responses were candid and often surprising, revealing issues we hadn’t even considered. Isnโ€™t it fascinating how anonymity can sometimes bring forth the most authentic thoughts, making everyone feel safer to speak up?

    Additionally, incorporating interactive workshops can significantly enhance dialogue. During a recent event I led, we organized group activities that encouraged participants to collaborate on problem-solving. I noticed that when individuals worked together, they were more willing to share their perspectives and challenge one another constructively. Isnโ€™t it amazing how hands-on experiences can break down barriers and foster a sense of community?

    Challenges in promoting dialogue practices

    Challenges in promoting dialogue practices

    Promoting transparent dialogue practices often encounters resistance due to deeply ingrained communication norms. I recall a workshop where, despite my efforts to encourage open sharing, many participants hesitated to speak up, bound by the fear of challenging authority. Isnโ€™t it eye-opening how traditional hierarchies can stifle thoughts even in a space meant for dialogue?

    Another challenge lies in the varying levels of comfort with vulnerability among participants. At an event I attended, I noticed that while some individuals eagerly shared personal insights, others clung to silence. This disparity can create a divide, leaving some voices amplified while others fade into the background. How can we cultivate an environment where everyone feels equally empowered to contribute?

    Lastly, logistical barriers such as time constraints and lack of resources can significantly hinder effective dialogue. I remember trying to implement dialogue circles in a busy school schedule; it was a struggle to find an hour that worked for everyone. Have you ever felt the frustration of wanting deeper discussions but being constantly overshadowed by pressing commitments? This reality poses a challenge that requires creative solutions to ensure that dialogue is not just a luxury but a priority.

  • How I advocate for grace in challenging conversations

    Key takeaways:

    • Grace in conversations fosters vulnerability and authenticity, transforming exchanges into supportive dialogues.
    • Incorporating grace in education creates an environment where students feel valued, allowing mistakes to be viewed as growth opportunities.
    • Effective strategies for advocating grace include modeling vulnerability, asking open-ended questions, and taking pauses during discussions.
    • Encouraging grace in educational settings involves active listening, acknowledging feelings, and recognizing the humanity of all participants.

    Understanding grace in conversations

    Understanding grace in conversations

    Grace in conversations is often misunderstood; it’s not simply about politeness but entails a deeper understanding of human emotions. I recall a heated discussion I once had with a colleague about differing teaching methods. Instead of focusing on winning the argument, I chose to listen deeply, allowing grace to guide the exchange, and it transformed the conversation entirely.

    When we approach conversations with grace, we open ourselves to vulnerability and authenticity. I remember navigating a tough topic with a friend who was visibly upset. Instead of responding immediately, I paused, recognizing their pain. Isnโ€™t it interesting how that simple act can shift the focus from being defensive to being supportive?

    Incorporating grace into our dialogues means allowing space for others’ perspectives and emotions. I often think about how easily conversations can derail when we forget this. Have you ever found yourself regretting how you responded in a moment of tension? I have, and it has taught me the importance of embracing grace to foster more meaningful connections.

    Importance of grace in education

    Importance of grace in education

    When grace is woven into the fabric of education, it creates an environment where students feel valued and heard. I vividly remember a time when a student struggled to express their thoughts during class. Instead of dismissing their hesitation, I encouraged them with patience. That grace not only helped the student articulate their ideas but also fostered a sense of belonging in the classroom.

    Grace allows for mistakes to be seen as opportunities for growth rather than failures. I once made a miscalculation while teaching a complex concept, and rather than glossing over it, I acknowledged my error. I asked the class how we could correct it together. The resulting discussion was enlightening, and it reinforced the idea that learning is a journey best traveled with compassion and understanding.

    The impact of grace extends beyond the classroom; it ripples through the educational community. When educators model grace in their interactions, it cultivates a culture of respect and empathy. Have you seen the difference a kind word can make after a challenging lesson? I have, and these moments remind me that grace is not just an ideal; it’s a practical tool that enriches our educational experiences.

    Challenges in difficult conversations

    Challenges in difficult conversations

    Engaging in difficult conversations often brings a whirlwind of emotionsโ€”frustration, fear, and even defensiveness can surface easily. I recall a time when I approached a colleague about a sensitive issue concerning student behavior. As I navigated that fraught exchange, I realized how my own anxiety tainted the discussion, making it more about my discomfort than the issue at hand. Have you ever found yourself in a similar position, caught up in your emotions instead of focusing on a solutions-based dialogue? Itโ€™s a challenge that requires self-reflection to overcome.

    Another significant challenge is the tendency to interrupt or speak over others during challenging dialogues. I remember discussing curriculum changes with a group, and despite my intent to foster collaboration, I noticed I often interrupted others to share my thoughts quickly. Stepping back to listen was not just about good manners; it became a vital part of ensuring that everyone felt heard and respected. How can we create a space for genuine dialogue if we donโ€™t actively listen? This realization pushed me to actively practice patience in those settings.

    Lastly, external pressures can complicate difficult conversations. Once, while addressing a conflict among students, I felt overwhelmed by time constraints and the expectation to resolve everything swiftly. In that intense moment, I realized that rushing through the conversation would rob both parties of the opportunity to genuinely understand each other. Itโ€™s crucial to remember that sometimes, taking a moment to breathe and gather our thoughts can lead to a more productive outcome. How often do we prioritize speed over depth in our discussions? This balancing act can be particularly challenging but is essential for fostering a more authentic connection.

    Strategies for advocating grace

    Strategies for advocating grace

    When it comes to advocating for grace in challenging conversations, a powerful strategy is to model vulnerability. I recall a meeting where I admitted my own missteps in a project decision. This openness not only diffused tension but also encouraged others to share their experiences without fear of judgment. Do you think vulnerability could create a bridge in conversations laden with stress? It sure feels that way to me.

    Another effective approach is to ask open-ended questions that invite reflection. Instead of stating my perspective outright, Iโ€™ve often found success in asking, “What do you think is the best way forward?” This shift not only empowers others but also fosters a collaborative environment. I cherish those moments when a simple question leads to unexpected insights. Donโ€™t you find that sometimes the right question can open doors we didnโ€™t even know existed?

    Lastly, taking a pause can be transformative. During a particularly heated discussion about policy changes, I felt the urge to react immediatelyโ€”but I chose to take a deep breath instead. This brief moment of stillness allowed me to respond with intention rather than emotion. How often do we give ourselves permission to pause? I believe that cultivating this practice not only enhances our responses but also promotes a sense of grace in the dialogue.

    Personal experiences with grace advocacy

    Personal experiences with grace advocacy

    When I think back on my journey of advocating for grace, one incident stands out. During a community workshop, a participant shared a deeply personal story that triggered a tense reaction from another attendee. In that moment, I instinctively leaned in and echoed what I heard, asking everyone to reflect on the emotions involved. It was a small act, but the room’s atmosphere shiftedโ€”suddenly, we were no longer in opposition but were engaged in a shared human experience. Have you ever noticed how one empathetic response can transform an entire conversation?

    There was another time at a team meeting where frustration simmered beneath the surface. Instead of dismissing the growing tension, I decided to highlight the strengths each person brought to the table. It was enlightening to hear colleagues acknowledging each otherโ€™s contributions, fostering an environment where grace flourished amidst conflict. Doesnโ€™t it feel rewarding to witness individuals shift from confrontation to collaboration?

    In times when I felt overwhelmed, I have relied on moments of intentional silence. I remember a particularly challenging debate around curriculum changes, where I simply invited a short pause for reflection. This abrupt stillness dissolved the hostility, allowing us to approach the conversation with curiosity rather than defensiveness. Have you ever realized how powerful silence can be in cultivating mindfulness and grace? Itโ€™s a tool that can easily be overlooked but holds immense potential.

    Tips for implementing grace

    Tips for implementing grace

    Finding opportunities to reframe tension is vital in promoting grace during tough discussions. I remember a time when a colleague’s harsh criticism caught me off guard. Instead of retaliating, I took a breath and asked, “What led you to that conclusion?” This simple question shifted the dynamic, transforming a defensive exchange into a constructive dialogue. Have you considered how reframing can align opposing viewpoints toward common goals?

    Creating a safe space is another essential tip. During a workshop on educational equity, I encouraged participants to share their thoughts without fear of judgment. I noticed everyone’s body language improved; people leaned in, engaged, and spoke with authenticity. When you make it clear that all voices are valued, doesnโ€™t it seem easier to foster grace among diverse perspectives?

    Empathy can also serve as a bridge in difficult conversations. I often remind myself that behind every disagreement lies a personal story. One time, while discussing sensitive policy changes, I shared my own challenges navigating similar waters. When I opened up, others followed suit, leading to a deeper understanding of each other’s struggles. Isnโ€™t it fascinating how vulnerability can pave the way for grace?

    Encouraging grace in educational events

    Encouraging grace in educational events

    Encouraging grace in educational events often requires active listening. I recall a time during a heated faculty meeting when emotions were running high over a new curriculum change. By focusing on truly hearing my colleagues’ concerns instead of simply waiting for my turn to speak, I discovered underlying fears and hopes that changed the discussion’s direction. Isnโ€™t it amazing how taking a moment to listen can transform the energy in the room?

    Modeling gracious responses is also a powerful way to influence the atmosphere. At a recent parent-teacher conference, a parent expressed frustration regarding my teaching methods. Instead of becoming defensive, I acknowledged their feelings and thanked them for sharing their perspective. That acknowledgment seemed to cool the tension and fostered a respectful conversation. Have you ever realized that a kind word can diffuse a looming conflict?

    Recognizing the humanity in each participant is crucial when aiming for grace. During a professional development session, I once shared my experience as a struggling educator. This vulnerability opened the door for others to share their own challenges, breaking down barriers. By acknowledging our common humanity, donโ€™t you think we can create a more empathetic and gracious environment?

  • How I address power dynamics in dialogue

    Key takeaways:

    • Power dynamics in dialogue can marginalize quieter voices; fostering inclusive environments encourages active participation.
    • Dialogue enhances education by promoting critical thinking and emotional connections among participants, allowing for diverse perspectives.
    • Facilitating inclusive dialogue requires establishing ground rules, actively inviting input, and being aware of power imbalances.
    • Creating a safe space and practicing active listening fosters open conversations, leading to richer exchanges of ideas.

    Understanding power dynamics in dialogue

    Understanding power dynamics in dialogue

    Power dynamics in dialogue often manifest through the positioning and tone of the participants. In my experience, when I engage in discussions, I notice how initial assumptions can shape the interaction. Have you ever felt overshadowed in a group setting? Itโ€™s common when one voice dominates, leaving others hesitant to contribute.

    I remember a workshop where the facilitator empowered quieter participants to share their thoughts by actively inviting them into the conversation. This shift created a palpable change in the room. Suddenly, those who often felt neglected revealed profound insights, reminding me of the importance of ensuring everyone has a seat at the table.

    Furthermore, context plays a critical role in power dynamics. For example, in educational settings, authority can be concentrated among instructors, unintentionally discouraging student participation. It’s essential to recognize this imbalance and actively seek ways to level the playing field. How do we create a space where every opinion is valued? It starts with awareness and a commitment to fostering inclusive dialogue.

    Importance of dialogue in education

    Importance of dialogue in education

    Dialogue is a powerful tool in education, serving as a catalyst for deep learning and understanding. I recall an instance during a peer-led discussion where students were encouraged to share their perspectives on a complex topic. The energy in the room shifted dramatically, as previously silent individuals transformed into eager contributors, demonstrating that dialogue can unlock potential and foster a sense of community.

    In my experience, meaningful dialogue has the ability to challenge assumptions and promote critical thinking. I remember a debate I participated in where different viewpoints clashed vigorously. Yet, those differences sparked curiosity and pushed each participant to explore their beliefs more deeply. How often do we take the time to listen and truly engage with opposing ideas? This process of exploration can lead to richer learning experiences and greater empathy among participants.

    Moreover, dialogue facilitates emotional connection in educational contexts. Itโ€™s not just about exchanging ideas; it’s about creating an environment where students feel safe to express vulnerability. I once facilitated a discussion on mental health, and the openness from my peers was both surprising and heartwarming. When we share our stories and actively listen, we enhance our collective learning while reinforcing the value of every individual’s experience.

    Techniques for facilitating inclusive dialogue

    Techniques for facilitating inclusive dialogue

    One effective technique for facilitating inclusive dialogue is to establish ground rules at the beginning of discussions. I remember a workshop where we agreed on simple yet powerful guidelines, such as “no interrupting” and “respect differing opinions.” This approach not only created a safer space but also encouraged all participants to speak up, fostering a sense of belonging that thrives when everyone knows their voice matters.

    Another method is to actively seek out quieter participants by using prompts or direct invitations to share their thoughts. During a recent seminar, I noticed a few students who had insightful ideas but were hesitant to contribute. When I made it a point to ask for their perspectives directly, the atmosphere shifted. Their enthusiasm was palpable, reminding me that sometimes, a little nudge is all it takes to bring forward unspoken thoughts.

    Lastly, incorporating diverse perspectives is crucial to inclusive dialogue. In a recent discussion on cultural differences, I encouraged attendees to share their personal stories related to the topic. I was genuinely moved to hear how varied experiences shaped their views, reinforcing the idea that each story adds a vital layer to our collective understanding. Have you ever experienced a moment when a unique perspective shifted your own? Those moments remind us that dialogue, rich with diverse backgrounds and experiences, is essential for deepening our educational interactions.

    Strategies for recognizing power imbalances

    Strategies for recognizing power imbalances

    Recognizing power imbalances is an essential skill in facilitating productive dialogue. One strategy that has proven effective for me is to observe body language and engagement levels among participants. During a community workshop, I noticed one individual consistently dominating the conversation while another sat silently. By drawing attention to that imbalance and prompting equal sharing, it became evident how powerful it can be to adjust the dynamics simply through awareness.

    Additionally, I encourage attendees to reflect on their own positions of power before entering discussions. It was eye-opening for me to conduct an exercise where participants identified aspects of their identities that influenced their voicesโ€”for instance, professional titles or cultural backgrounds. This self-awareness can spark crucial conversations and promote empathy, helping individuals recognize not only their own power but also how it may overshadow others.

    Finally, creating a feedback loop can significantly uncover underlying power imbalances. After a recent panel discussion, I facilitated a debrief where participants expressed what they felt about the interaction dynamics. Hearing their varied perspectives not only revealed subtle inequalities I hadnโ€™t noticed but also encouraged a more equitable approach in future conversations. Have you ever considered how feedback could change the power dynamics in your own discussions? Itโ€™s a powerful reminder that collectively reflecting can shine a light on these critical issues.

    Personal experiences with dialogue dynamics

    Personal experiences with dialogue dynamics

    In my experience, Iโ€™ve often found that the tone of my voice can significantly impact dialogue dynamics. During a heated discussion at an educational event, I realized that raising my voice seemingly shifted the atmosphere. Participants responded more attentively but also felt intimidated, and that’s when I understood that itโ€™s not just what I say, but how I say it that shapes engagement.

    I remember a time when a colleague and I teamed up for a discussion panel, and our different communication styles highlighted an interesting power dynamic. While my calm, methodical approach invited thoughtful reflection, my colleague’s passionate delivery energized the audience. This contrast not only made the conversation more vibrant but also prompted me to consider how varying styles can either elevate or diminish voices in a dialogue.

    Itโ€™s also crucial for me to remain aware of my own biases during conversations. For instance, in a recent workshop, I noticed myself gravitating towards participants who shared similar viewpoints. I took a step back, reminded myself to engage with those whose perspectives challenged me, and discovered a rich layer of insights I would have otherwise missed. Have you ever caught yourself in a similar situation? Recognizing those moments can truly reshape our understanding of dialogue dynamics.

    Tips for fostering open conversations

    Tips for fostering open conversations

    When fostering open conversations, one strategy that has worked for me is actively inviting input from quieter participants. I once moderated a session where a few individuals were hesitant to share their thoughts. By directly addressing them, I noticed they began to open up, enriching the dialogue with perspectives that would have otherwise remained unheard. Have you ever felt that your voice wasnโ€™t appreciated in a discussion? I believe creating a safe space where everyone feels valued is fundamental to invigorating the exchange of ideas.

    Moreover, practicing active listening has transformed the quality of conversations I’ve had. In a training seminar, I learned to paraphrase what others said before responding. This simple technique not only showed my engagement but also encouraged participants to delve deeper into their thoughts. Itโ€™s fascinating how much more willing people are to share when they know their words are truly being heard. Have you tried this method? I find that it cultivates an atmosphere of trust and openness, making dialogue flow seamlessly.

    Lastly, maintaining a curious mindset can be incredibly powerful. I recall an informal gathering where I approached every opinion with genuine curiosity rather than judgment. I asked open-ended questions, like, โ€œWhat led you to that conclusion?โ€ Suddenly, the conversation transformed into a rich exploration of ideas instead of a debate. How often do we allow curiosity to guide our discussions? Approaching conversations with a desire to learn from each other can dismantle barriers and foster deeper connections.

  • How I address ownership of ideas in discussions

    Key takeaways:

    • Ownership of ideas evolves through collaboration, requiring clear communication and acknowledgment of contributions to inspire innovation.
    • Engaging discussions in educational settings promote critical thinking, community support, and a deeper connection to the material.
    • Creating a respectful environment encourages open dialogue and enhances collaboration, reinforcing the value of each participant’s input.
    • Sharing credit in collaborative projects fosters positive relationships and motivates team members by recognizing everyone’s contributions.

    Understanding ownership of ideas

    Understanding ownership of ideas

    Ownership of ideas can often feel like a murky concept, especially in collaborative discussions. I remember a workshop where multiple participants contributed exciting concepts, only to leave the event unsure of who would be credited for what. It made me question: when ideas bounce around in an open space, how do we ensure everyone feels valued and recognized for their contributions?

    When we talk about owning an idea, itโ€™s essential to understand the difference between a spark of inspiration and the finished product. For instance, I once had a colleague who had an incredible initial concept for a project. Over time, it morphed through various discussions until it became something entirely different. This experience led me to appreciate how ideas evolve and how the journey can complicate our sense of ownership. Who should claim ownership thenโ€”the one who originated the spark or the collective that nurtured it?

    Navigating the nuances of idea ownership requires clear communication and respect among collaborators. I find that setting ground rules at the beginning of discussions can help prevent misunderstandings later. Have you ever experienced an idea theft? I have, and it opened my eyes to the importance of acknowledging contributions in every step to give everyone their proper due. By creating a culture that fosters open acknowledgment, we not only protect individual creativity but also inspire further innovation.

    Importance of discussions in education

    Importance of discussions in education

    Engaging in discussions is vital in education because they create a platform for diverse perspectives. I recall attending a seminar where an open discussion led to a breakthrough understanding of a challenging topic. The energy in the room transformed; when students shared their views, it sparked curiosity and built a deeper connection to the material that wouldnโ€™t have been possible in a lecture format.

    What I often find fascinating is how discussions encourage critical thinking. One time, during a group project, our initial debate led to questioning established assumptions. This process not only improved our project but also instilled a sense of pride in our collective effort, demonstrating how dialogue can elevate both learning and confidence.

    Moreover, discussions help foster a community of learners who support one another. Iโ€™ve seen this first-hand in study groups where individuals feel safe expressing uncertainties or misconceptions. Itโ€™s empowering to witness how opening up can turn confusion into clarity, and I believe this dynamic is what enhances educational experiences across the board. Isnโ€™t it refreshing when you see a peer light up with understanding? That spark often comes directly from the power of discussion.

    Strategies for encouraging idea ownership

    Strategies for encouraging idea ownership

    Encouraging idea ownership begins with creating a safe and welcoming environment. I remember leading a workshop where I had students share their thoughts without the fear of being judged. The moment someone expressed a radical idea, the energy shifted; others were eager to build on it. Suddenly, that one idea transformed into a collective exploration, and each participant felt a sense of pride and responsibility for what emerged.

    Active listening is another powerful strategy that promotes ownership. During class discussions, I often make it a point to reflect back what I hear before responding. This practice not only validates the speaker but also invites them to elaborate further on their ideas. I once had a shy student who, after feeling heard, blossomed into a confident contributor. Itโ€™s incredible how simply giving someone your full attention can empower them to own their contributions.

    Lastly, providing constructive feedback fosters a sense of accountability. I used to hold follow-up sessions where we discussed each otherโ€™s ideas in depth, highlighting strengths and areas for growth. It was inspiring to see individuals take ownership of their thoughts, motivated to refine and expand their concepts. Have you ever noticed how feedback can turn a spark of an idea into a flame of creativity? Encouraging this process can truly empower learners to take pride in their ownership of an idea.

    Techniques for addressing ownership issues

    Techniques for addressing ownership issues

    Techniques for addressing ownership issues can be as nuanced as the ideas themselves. One approach Iโ€™ve found effective is establishing clear ground rules at the beginning of a discussion. During a recent seminar, I encouraged participants to attribute ideas clearly when expanding on them, which helped them feel more connected to their contributions. It was eye-opening to see how everyone began to feel a deeper sense of ownership when they were reminded to acknowledge one anotherโ€™s inputs.

    Another technique Iโ€™ve embraced is collaborative summarization. At the conclusion of brainstorming sessions, I often invite each participant to share a brief summary of what they learned or contributed. I recall a workshop where one participant said, โ€œI never realized my ideas could connect like this.โ€ This not only reinforces their involvement but also helps clarify ownership. Have you experienced a moment where hearing your thoughts echoed back made you realize their value?

    Lastly, employing digital platforms to document shared ideas in real-time can bridge the gap between spoken words and ownership. I once used a collaborative tool during a group project to track everyoneโ€™s input, and it was fascinating to see contributors referring back to their ideas, claiming them with excitement. Itโ€™s remarkable how technology can enhance accountability and pride in ownership, wouldnโ€™t you agree?

    Creating a respectful discussion environment

    Creating a respectful discussion environment

    Creating a respectful discussion environment is essential for fostering open dialogue. I remember attending a conference where the moderator emphasized the importance of active listening. It completely shifted the atmosphereโ€”participants were engaged, and you could feel the respect blossoming as everyone fully absorbed one another’s ideas before responding. Have you ever noticed how much easier it is to share your thoughts when you feel heard?

    Encouraging questions can also significantly enhance the respect within a discussion. During one panel, I observed how inviting participants to ask clarifying questions rather than jumping straight into critiques created a more constructive space. Itโ€™s amazing what happens when curiosity takes precedence over criticism. When was the last time you felt comfortable querying someoneโ€™s idea instead of just disagreeing?

    Lastly, the tone and language we use play a crucial role in maintaining respect. I find that using โ€œweโ€ statements often opens doors rather than putting up walls. For instance, when I address differing viewpoints with phrases like “we can explore this together,” it fosters collaboration and reduces defensiveness. Being mindful of our words can transform a discussion from a debate into a shared learning experience. Isn’t it wonderful how something as simple as language can change the dynamics?

    Sharing credit in collaborative settings

    Sharing credit in collaborative settings

    Sharing credit in collaborative settings is crucial for maintaining positive relationships and encouraging creativity. I recall a team project where we put in equal effort, yet only one person’s name ended up on the final report. It was disheartening for the rest of us, highlighting how undervaluing contribution can stifle future collaboration. Have you ever felt overlooked for something you worked hard on?

    In my experience, making a conscious effort to acknowledge each person’s contribution can transform dynamics. During another group project, we decided to take turns presenting our ideas in team meetings. By inviting everyone to share their insights, we not only elevated the discussion but also reinforced the understanding that every voice matters. Doesnโ€™t it feel fulfilling when contributions are recognized and celebrated?

    Additionally, Iโ€™ve seen that establishing clear expectations around credit from the beginning can set a positive tone. In one volunteer group I joined, we collaboratively created guidelines on how we would acknowledge each other’s input. This approach not only minimized conflict but also enhanced our collective enthusiasm for working together. Have you considered how much stronger a team can become when everyone feels valued?

    Personal experiences with idea ownership

    Personal experiences with idea ownership

    During a brainstorming session for an educational event, I once pitched an idea that resonated with everyone. Later, when a colleague expanded on it during a presentation, I felt a mix of pride and frustration. It was reassuring that my idea sparked creativity, but hearing it rephrased without my name felt unjust. Have you ever experienced the bittersweet feeling of witnessing your contributions go unrecognized?

    In another instance, I worked on a community project where we implemented a shared document for tracking ideas. This simple tool was a game-changer; it ensured that everyone could see their input acknowledged. Seeing my suggestions written there brought a genuine sense of ownership. I learned that visibility in collaborative efforts can cultivate a deeper emotional investment. Isnโ€™t it powerful when we can trace our thoughts and feel part of something bigger?

    I’ve also participated in a panel discussion where I was so eager to share my thoughts that I forgot to pause and empower others. The realization hit me when I noticed audience curiosity about my peersโ€™ insights, which made me reassess the flow of the conversation. Engaging others not only enriches our dialogue but also fosters a culture where ownership of ideas is collectively celebrated. Doesnโ€™t a vibrant exchange make for a richer learning environment?

  • How I address controversial topics thoughtfully

    Key takeaways:

    • Engaging with controversial topics requires an open mind and the ability to understand diverse perspectives.
    • Thoughtful discussions create a safe space for vulnerability, enabling deeper connections and critical thinking.
    • Active listening and establishing respectful ground rules are essential for productive dialogue on sensitive issues.
    • Sharing personal experiences fosters a sense of community and encourages others to engage more openly in discussions.

    Understanding controversial topics

    Understanding controversial topics

    Controversial topics often provoke strong emotions, making them complex and multi-faceted. I believe that delving into these subjects requires us to approach them with an open mind and a willingness to understand different perspectives. Have you ever found yourself in a heated discussion about a topic that both sides felt passionately about? Itโ€™s eye-opening, isn’t it?

    For instance, I once participated in a community debate about education reform. The room was filled with people from various backgrounds, and everyone had a different viewpoint shaped by their unique experiences. It struck me how important it is to listen and acknowledge those diverse experiences, as theyโ€™re often at the heart of what makes a topic controversial.

    Understanding controversial topics isn’t just about recognizing opposing views; itโ€™s also about examining our biases. Iโ€™ve caught myself assuming the validity of my own perspective without considering the context others might be coming from. This reflection process not only enriches our understanding but also fosters more meaningful conversations. How can we grow if we donโ€™t challenge our own assumptions?

    Importance of thoughtful discussions

    Importance of thoughtful discussions

    Engaging in thoughtful discussions can transform our understanding of complex issues. I remember a panel discussion I attended on climate change where experts from varied fields shared their insights. Each speaker brought a unique angle, which not only broadened my perspective but also deepened my empathy for those affected by environmental policies. Have you ever left a conversation feeling as though youโ€™ve gained a new lens through which to view a topic?

    It’s essential to recognize that thoughtful discussions create a safe space for vulnerability. I once facilitated a workshop on social justice, where participants openly shared their personal stories and struggles. The atmosphere was charged with emotion as people connected on a human level, illuminating how our experiences shape our beliefs. How often do we allow ourselves to truly listen to others, creating opportunities for genuine connection?

    Moreover, these conversations promote critical thinking skills. By challenging each other in a respectful manner, we can uncover underlying assumptions and refine our viewpoints. Reflecting on a debate I had with a friend about technology’s role in education, I found that both of us walked away with more nuanced perspectives. Isnโ€™t it fascinating how dialogue can help us explore the gray areas that often exist in controversial topics?

    Strategies for addressing sensitive issues

    Strategies for addressing sensitive issues

    When addressing sensitive issues, it’s crucial to approach conversations with empathy and openness. I remember attending a community forum about mental health, where attendees were encouraged to share their stories. The vulnerability displayed created a profound connection, allowing us to explore difficult subjects responsibly and authentically. How often do we take the time to truly consider another person’s feelings before voicing our opinions?

    Active listening is another essential strategy in these discussions. During a discussion on racial inequality, I practiced listening intently, resisting the urge to interject with my own thoughts. This simple act not only encouraged others to speak freely but also allowed me to fully grasp their experiences and emotions. Isnโ€™t it remarkable how pausing to absorb someone else’s perspective can reshape the narrative of a conversation?

    It’s also vital to establish ground rules that promote respect and understanding. In an online seminar I conducted on gender dynamics, we set guidelines for how we would engage with one another. This structure created a space where participants felt safe to express differing viewpoints. Have you experienced the transformative power of a respectful framework during heated discussions?

    Creating a safe environment

    Creating a safe environment

    Creating a safe environment is foundational for meaningful discussions around sensitive topics. I recall a workshop where participants were invited to anonymously submit their concerns on sticky notes. This anonymity acted as a shield, allowing individuals to voice their fears without the pressure of immediate judgment. Have you ever noticed how removing the spotlight can embolden people to speak more freely?

    Another effective tactic I’ve discovered is to foster connections among participants. I once organized a small group activity where individuals shared a personal story related to the theme of the event. By building this rapport, participants felt more at ease, leading to deeper, more heartfelt exchanges. Isnโ€™t it fascinating how shared vulnerability can bridge gaps and transform the atmosphere?

    Additionally, it’s essential to acknowledge the emotional weight of these discussions. During a panel on environmental sustainability, I noticed how the topic affected people’s feelings. By validating their concerns, I created space for authentic emotions to surface. How can we engage in these topics thoughtfully if we overlook the powerful feelings they evoke?

    Encouraging open dialogue

    Encouraging open dialogue

    Encouraging open dialogue requires thoughtful facilitation and a genuine willingness to listen. I remember a time when I was moderating a discussion about mental health in educational settings. I made sure to invite participants to express their views freely while reminding them that differing opinions were not just welcome but necessary for growth. Have you ever felt how the atmosphere shifts when people realize their voices truly matter?

    One strategy that resonated with me was inviting questions throughout the discussion, rather than waiting for a designated Q&A session. In a recent seminar on social justice issues, I encouraged participants to raise their hands whenever they had a thought or query. This fluid exchange allowed for a richer dialogue, ensuring that everyone felt involved. Isnโ€™t it incredible how a simple change in structure can lead to more active engagement?

    Iโ€™ve found that sharing my own uncertainties encourages others to do the same. During a workshop on technology use in classrooms, I revealed my ambivalence about certain tools. This honesty sparked unexpected conversations, as others opened up about their own hesitations. Itโ€™s fascinating to think how vulnerability can create pathways for deeper understanding and connection, isn’t it?

    Sharing personal experiences

    Sharing personal experiences

    When I think about sharing personal experiences, I remember the first time I discussed my struggles with balancing work and family during a parenting workshop. The moment I opened up about my own challenges, the room filled with nods and murmurs of agreement. Isn’t it interesting how vulnerability can transform a group of strangers into a supportive community?

    During a recent panel discussion on educational equity, I shared a moment from my early career where I faced significant bias. The reaction from the audience was powerful; many approached me afterward, each eager to share their own stories of overcoming obstacles. Reflecting on this experience made me realize just how much we all long for connection through shared struggles.

    Iโ€™ve noticed that when I share my journey, it invites others to reflect on their own paths, too. Last summer, while facilitating a workshop on inclusivity, I spoke candidly about my missteps in promoting diversity. Watching participants relate their personal stories added another layer of depth to the conversation. Have you noticed how personal anecdotes can breathe life into discussions, making them more relatable and engaging?

    Lessons learned from discussions

    Lessons learned from discussions

    Engaging in discussions around controversial topics often reveals unexpected lessons. I remember attending a conference on mental health where a spirited debate arose regarding treatment approaches. While the differing opinions initially sparked tension, it soon became clear that each perspective was rooted in a genuine desire to help. This experience taught me that even in disagreement, we can find common ground if we focus on our shared goals.

    During a workshop on environmental issues, I facilitated a role-playing exercise that opened several eyes. As participants took on various stakeholdersโ€™ viewpoints, they began to appreciate the complexities of the topic. Seeing them transform from adversaries to collaborators made me realize that empathy can be fostered through thoughtful dialogue. Have you noticed how stepping into someone elseโ€™s shoes can drastically shift your perspective?

    In my experience, discussions that delve into controversy often yield personal revelations. After a heated debate about educational policies at a forum, one participant shared their fear of the unknown inevitable changes could bring to schools. This moment reminded me that behind every opinion is a deeply personal story, and embracing these narratives can foster understanding and respect. How do you think sharing these stories could change the dynamics of future discussions?

  • How I address fragmentation in diverse narrative spaces

    Key takeaways:

    • Narrative fragmentation in education highlights the importance of integrating diverse cultural perspectives to create an inclusive learning environment.
    • Diverse narrative spaces foster empathy, understanding, and help individuals find their voice, enhancing the educational experience.
    • Effective storytelling techniques, such as vivid imagery and conflict resolution, can make narratives more engaging and relatable.
    • Encouraging active participation and vulnerability in storytelling transforms passive listeners into dynamic contributors, enriching shared experiences.

    Understanding narrative fragmentation in education

    Understanding narrative fragmentation in education

    Narrative fragmentation in education often arises from the diverse backgrounds and experiences of learners. I remember attending a workshop aimed at incorporating multicultural perspectives into the curriculum. It was fascinating to see how fragmented stories from various cultures brought a rich complexity to our understanding of history and personal identity. How can we effectively weave these diverse threads into a cohesive narrative that resonates with all students?

    When I reflect on my own educational experiences, I see the moments where fragmented narratives left me feeling disconnected. For instance, in a literature class, we studied texts from different cultures, yet each piece felt like a separate island with little connection between them. This made me wonder: how can educators create bridges between these narratives, so that students can appreciate the bigger picture while still honoring individual stories?

    Furthermore, fragmentation can lead to opportunities for deeper engagement. Iโ€™ve seen firsthand how learners thrive when they can share their own fragmented narratives in a supportive environment. This raises an important question: how can educators foster spaces where students feel safe to express their diverse experiences? By embracing and acknowledging these fragments, we can encourage a more inclusive and enriching learning experience.

    Importance of diverse narrative spaces

    Importance of diverse narrative spaces

    Diverse narrative spaces are essential because they allow multiple voices and perspectives to emerge, creating a tapestry of experiences that enrich the learning environment. I vividly recall a community event where participants shared stories from their heritage. The personal anecdotes not only fostered understanding but also highlighted the common threads that connect us, transforming individual experiences into a shared journey.

    When I think about the importance of these spaces, it becomes clear that they promote empathy and understanding among learners. For instance, during a collaborative project, my classmates and I had to navigate differing viewpoints on a historical event. This process encouraged us to listen actively and appreciate the complexity of each otherโ€™s narratives, leaving us with a deeper respect for diverse perspectives. Isnโ€™t it fascinating how these conversations can shape our worldview?

    Moreover, nurturing diverse narrative spaces empowers individuals to find their voice and assert their identity. I remember a student who was initially hesitant to share her story due to fear of rejection. Once she felt welcomed into a space that celebrated her uniqueness, her contributions became transformative for the entire group. How might we create more opportunities like this in our educational settings, where every voice matters?

    Strategies for effective storytelling

    Strategies for effective storytelling

    One effective strategy for storytelling is harnessing the power of vivid imagery. When I shared my own education journey at a recent workshop, I painted a picture of my childhood classroom, bustling with laughter and energy. By describing the colors on the walls and the sounds of eager voices, I could transport my audience to that moment, sparking their imagination and connection to my experience. How often do we underestimate the impact of these sensory details in making stories resonate?

    Another approach is to incorporate conflict and resolution, as these elements drive engagement. In my experience, when discussing challenges faced in group projects, I find that people lean in, wanting to understand how obstacles were overcome. For example, I recounted a time when our team struggled with differing ideas and how we ultimately transformed that friction into a creative solution. This not only makes the narrative more relatable but also highlights the beauty of collaboration.

    Finally, I believe integrating interactive elements can enhance storytelling. At a recent educational event, we used storytelling circles, allowing participants to share their narratives while others actively listened and responded. This back-and-forth dialogue created a vibrant atmosphere, where stories morphed and intertwined, demonstrating that every contribution matters. Have you ever experienced the magic that happens when storytelling becomes a shared journey rather than a one-sided narrative?

    Engaging participants in narrative experiences

    Engaging participants in narrative experiences

    Engaging participants in narrative experiences requires creating a sense of ownership and personal connection. I recall a workshop where participants were invited to bring a meaningful object that represented their educational journey. The moment someone held up an old textbook or a cherished trophy, I could feel the energy shift. It was as if the room blossomed with shared stories, reminding us all how deeply our experiences shape who we are. Isnโ€™t it fascinating how something as simple as an object can unlock a flood of memories?

    Another vital aspect is the practice of vulnerability in storytelling. I remember a time when I shared my insecurities about facilitating discussions in large groups. The palpable silence turned into an emotional wave as others began to share their struggles too. Vulnerability invites authenticity, fostering a safe space where participants feel empowered to share their own narratives. How often do we allow ourselves such openness in a public setting?

    Moreover, I think encouraging active participation transforms passive listeners into dynamic storytellers. During one event, I divided attendees into small groups and assigned them the task of creating a short skit around a common educational challenge. As they experimented with roles and perspectives, laughter and collaboration erupted. It became a living narrative, not just a script, as people connected through shared humor and experience. Isnโ€™t it incredible to see how engagement can turn an idea into a collective story that resonates far beyond the initial concept?

    Techniques for integrating diverse narratives

    Techniques for integrating diverse narratives

    Integrating diverse narratives requires a careful balance of respect and creativity. In one workshop, I experimented with storytelling pairsโ€”participants were tasked to share their backgrounds and then retell each other’s stories. Observing their reactions was enlightening; it revealed how often we overlook the richness in othersโ€™ experiences. Isnโ€™t it surprising what fresh perspectives can emerge when we listen deeply?

    Another technique Iโ€™ve utilized is thematic clustering. During a collaborative project, I gathered stories centered around the theme of resilience in education. This allowed participants to see common threads in what initially seemed like disparate experiences. It was quite powerful to witness individuals recognize how their challenges were echoed in others’ journeys. How often do we miss these connections in our narratives?

    Additionally, Iโ€™ve embraced multimedia tools to amplify diverse voices. For example, I once facilitated a digital storytelling session where participants created short videos incorporating images and sound from their lives. The fusion of different mediums not only enriched their narratives but also made the experience more accessible. Have you ever noticed how visual elements can evoke emotions that words sometimes canโ€™t capture?

    Personal reflections on narrative approaches

    Personal reflections on narrative approaches

    While reflecting on narrative approaches, I often find myself thinking about the power of vulnerability in storytelling. There was a time in a workshop when I shared a personal struggle related to my own educational journey. The room fell silent, and suddenly, others felt compelled to open up about their experiences. Isnโ€™t it amazing how sharing our authentic selves can create a deep connection and encourage others to do the same?

    I also believe that the structure of a story plays a crucial role in how narratives resonate. During a retreat focused on educational events, we challenged ourselves to write our stories in non-linear formats. This approach led to unexpected discoveries about our own paths. Have you ever noticed how breaking free from traditional storytelling can illuminate aspects of your experience that you never thought to explore?

    Additionally, Iโ€™ve come to appreciate the role of audience engagement in shaping narrative forms. In one event, we created a living narrative where participants would add lines to a collective story based on their interpretations. The energy in the room was palpable, as everyone eagerly contributed. How often do we forget that stories are dynamic, and our involvement can shape their evolution?

  • How I adapt to my audience’s needs in discussions

    Key takeaways:

    • Understanding audience needs is essential for fostering meaningful discussions, including tailoring content to match their expertise and emotional connections.
    • Adapting communication style enhances engagement, clarity, and trust among participants, highlighting the importance of adjusting language and delivery based on audience reactions.
    • Incorporating open-ended questions and relatable examples fosters deeper engagement, allowing participants to feel invested in the conversation.
    • Feedback is crucial for continuous improvement, enabling facilitators to adjust their approaches based on participant experiences and create more inclusive learning environments.

    Understanding audience needs

    Understanding audience needs

    Understanding my audience’s needs is crucial in fostering meaningful discussions. I remember a time when I misjudged the expertise of a group, presenting information that was far too basic. The disappointment in their eyes was hard to miss, and it taught me the importance of tailoring my content to match their knowledge levels.

    As I engage with different groups, I often find that asking open-ended questions can reveal their true interests and concerns. For instance, during a workshop, I realized that many participants were more interested in practical applications rather than theoretical concepts. This insight reshaped my approach, making our conversations more relevant and impactful.

    Emotional connection plays a vital role in understanding needs as well. I once had a participant share a personal story about how a lack of resources had hindered their learning experience. This moment not only deepened my empathy but also highlighted the vital role of flexibility in my approach. When I see a genuine desire to learn and grow, I feel more compelled to adapt my methods to better serve their unique journeys.

    Importance of adapting communication

    Importance of adapting communication

    Adapting communication is essential because it directly influences the effectiveness of our interactions. I recall a situation where I rushed through a presentation, eager to share everything I had prepared. The puzzled expressions on my audienceโ€™s faces were enough to make me realize that my delivery style didnโ€™t resonate with them. Moments like this remind me that slowing down and adjusting my approach can be the key to keeping everyone engaged and comprehending the material.

    In my experience, the ability to adapt communication fosters trust and rapport. During a recent dialogue with educators, I noticed they were struggling with some of the terms I used. Instead of persisting with jargon, I chose to explain the concepts in simpler language, and the relief on their faces was palpable. Have you ever found yourself in a similar situation? Itโ€™s a powerful reminder that clarity can bridge gaps and open doors to meaningful conversations.

    Moreover, recognizing emotional cues enhances the adaptability of our communication. I remember facilitating a session where one participant appeared visibly frustrated. By acknowledging their emotions and adjusting my approach to address their specific concerns, the energy shifted in the room. This taught me that being attuned to my audience’s feelings not only facilitates better understanding but can significantly transform the dynamics of any discussion.

    Techniques for engaging discussions

    Techniques for engaging discussions

    One effective technique for engaging discussions is to invite participation through open-ended questions. I remember a workshop where I asked participants how they felt about a particular teaching method rather than just seeking a yes or no answer. The shift in energy was electric as they shared personal stories and experiences, and I realized that people are more invested when they feel their voices contribute to the conversation.

    Another tactic that works wonders is utilizing relatable examples to illustrate points. I once used a scenario from my own life to explain an educational concept, and I saw a spark of recognition in my audience’s eyes. It became apparent that connecting the subject matter to their everyday experiences made it more tangible. Have you noticed how a good story can bridge understanding in discussions? It can turn abstract ideas into relatable content that fosters deeper engagement.

    Incorporating visual aids can also enhance engagement tremendously. During a recent session, I used a simple PowerPoint with vivid images and graphics instead of relying solely on text. The room transformed; visual learners were more focused, and discussions flourished as people connected the visuals to their knowledge. Ultimately, these techniques create a dynamic discussion environment that encourages collaboration and exploration.

    Strategies for diverse audiences

    Strategies for diverse audiences

    Understanding the diversity of an audience is essential for effective discussions. I recall a time when I tailored my approach during a panel discussion that included educators from various cultural backgrounds. By incorporating aspects of different teaching philosophies in my examples, I could see how everyone felt a connection to the topic. It struck me that embracing cultural relevance not only made the discussion more engaging but also fostered mutual respect among participants.

    Another strategy I’ve found helpful is adjusting my communication style based on the audienceโ€™s familiarity with the subject matter. For instance, during a presentation aimed at new educators, I simplified my language and avoided jargon. I noticed how their expressions changed from confusion to clarity, emphasizing the importance of accessibility. Have you experienced the moment when your message truly resonates? Itโ€™s incredibly rewarding to witness those lightbulb moments.

    Incorporating flexibility in my discussion format has also proven beneficial. During a recent workshop, I provided participants the option to break into smaller groups based on their interests. This adjustment transformed the energy in the room; suddenly, people were more animated and engaged in discussions that mattered to them. The diversity of perspectives that emerged was eye-opening, revealing just how powerful tailored interactions can be in meeting varied audience needs.

    Tailoring content for clarity

    Tailoring content for clarity

    To ensure clarity in discussions, I always start by assessing my audience’s prior knowledge. I remember one session where I adjusted my presentation on educational technology based on the varied expertise of attendees. As I watched some educators nod while others looked puzzled, I decided to take a step back and break down concepts. That pivot transformed the atmosphere; suddenly, everyone was on the same page, fostering collaboration rather than confusion.

    It’s fascinating how visuals can enhance clarity. During another event, I replaced dense text with simple infographics and bullet points, which helped illustrate complex ideas. When I saw how quickly participants were grasping the information, I couldn’t help but smile. Donโ€™t you think images can often convey ideas faster than words? This experience reinforced my belief that clarity sometimes lies in the simplicity of presentation.

    Another tactic I find invaluable is encouraging questions throughout the discussion. I often share a personal story that prompts an open dialogueโ€”like the time I realized I was talking over the heads of my audience. By inviting feedback, I not only clarified misunderstandings but also created a sense of community and shared learning. Isnโ€™t it amazing how fostering an interactive environment can enhance understanding and engagement?

    Personal experiences in adaptation

    Personal experiences in adaptation

    Adapting to my audience’s needs has often required me to reflect on my teaching approach. I recall one particularly memorable workshop where the participants were a mix of seasoned educators and fresh graduates. Initially, I was tempted to dive deep into advanced strategies; however, noticing the apprehension on some faces prompted me to shift the focus. I decided to share foundational concepts first, which not only eased the newcomers but also encouraged seasoned attendees to share their insights, enriching the collective experience.

    One time, at a conference, I introduced an unexpected role-playing activity to break the ice. I remember standing in front of the group, feeling a mix of excitement and anxiety as I explained the concept. After a few initial hesitations, participants began to engage and share their experiences in a way I had never anticipated. The laughter and collaboration that unfolded made it clear: when I adapt my methods to create a more relatable environment, I not only reach them better, but I also enhance my own energy and enthusiasm for the subject matter.

    On another occasion, during a discussion on inclusive teaching strategies, I sensed that some were afraid to share their thoughts. I decided to share my own stumbling blocks first, allowing vulnerability to usher in openness. It was remarkable how quickly others joined in, sharing their challenges. This taught me a powerful lesson: by revealing my own struggles, I encouraged others to adapt alongside me, turning a simple discussion into a meaningful dialogue where everyone’s experiences were valued. Isn’t it incredible how openness can transform a learning environment?

    Feedback and continuous improvement

    Feedback and continuous improvement

    Gathering feedback is a crucial part of my adaptation process. I remember after one workshop, I made it a point to circulate a quick survey asking participants about their experiences. Some pointed out that the pacing was a bit fast for newcomers. Their feedback made me realize that even small adjustments, like allowing more time for questions, could make a significant difference in how included everyone felt. Have you ever noticed how a simple question can lead to deeper insights?

    Continuous improvement is an ongoing journey in my practice. After every event, I reflect on what went well and what didnโ€™t. One time, I revisited a session where I felt the energy was lacking. By analyzing participant feedback, I discovered that integrating more interactive components could have ignited enthusiasm in the room. Each piece of feedback is like a puzzle piece that helps me see the bigger picture, even if I sometimes struggle to fit them together. How do you ensure that youโ€™re growing and evolving in your own discussions?

    The beauty of feedback lies in its immediate effect on the learning environment. During a discussion on technology in education, I asked attendees to share their thoughts anonymously. The raw honesty in the responses surprised me and revealed gaps I hadnโ€™t considered. This allowed me to pivot my approach in real-time, which made the session feel alive and dynamic. Itโ€™s fascinating how, when we embrace feedback, we not only improve but also create spaces where participants feel empowered to voice their thoughts. How can we leverage these insights for future interactions?

  • How I adapt to generational communication styles

    Key takeaways:

    • Each generation has distinct communication preferences, with Baby Boomers valuing direct interactions and Gen Z favoring digital and humorous exchanges.
    • Adapting communication styles enhances collaboration and understanding among diverse generational groups, as demonstrated in workshops and mentoring experiences.
    • Utilizing a mix of traditional and modern teaching methods can lead to more engaging educational environments, benefiting from each generation’s unique strengths.
    • Active listening, visual aids, and humor are effective strategies for fostering inclusive discussions across different age groups in educational settings.

    Understanding generational communication styles

    Understanding generational communication styles

    Understanding generational communication styles is essential as each generation has developed distinct ways of connecting and expressing themselves. For instance, when I first started collaborating with Millennials, I noticed they preferred texting and quick digital interactions. It made me wonderโ€”do face-to-face conversations feel overbearing to them, or do they simply value efficiency?

    As I navigated the communication preferences of Gen Z, I found that their familiarity with social media influenced their approach to dialogue. I recall a discussion where they seamlessly switched between platforms, using memes to convey complex ideas. It struck me that humor and relatability are pivotal for them, which led me to rethink how I presented information.

    In contrast, baby boomers often value direct, personal interactions, favoring dialogue that allows for deeper relationship building. I remember hearing a baby boomer say that they feel more respected during a phone call than through a text message. This contrast made it clear to me that appreciating these differences is crucial in fostering effective communication in diverse groups. How do you adjust your style when interacting with someone from a different generation?

    Importance of adapting communication

    Importance of adapting communication

    Adapting communication styles is vital in today’s multifaceted environment, where diverse generational perspectives converge. I recall working with a Gen X colleague who had a strong preference for thorough explanations and detailed emails. Initially, I would send quick messages, thinking they were efficient, but soon realized that taking the time to craft detailed responses not only demonstrated respect for their style but also fostered a much richer dialogue between us. Have you ever felt frustrated when your message doesn’t get the response you anticipated?

    The importance of adapting communication truly hit home during a recent workshop I facilitated, where participants spanned multiple generations. When I offered a mixture of interactive discussions and traditional presentations, I saw how each individual engaged differently. The enthusiasm of younger participants, who thrived on collaboration, inspired me to incorporate more interactive elements in my future workshops. Wouldn’t it be exciting to see everyone’s ideas flourish when we tailor our approach?

    Another instance that reinforced this idea was when I began mentoring a Millennial intern. I initially relied on verbal check-ins, but soon discovered she preferred concise text updates. Switching to this method not only improved our efficiency but also increased her comfort level in sharing ideas. It made me appreciate how important it is to acknowledge and adapt to these preferences. How has adjusting your communication helped you connect better with others?

    Different generations in education

    Different generations in education

    When it comes to the educational landscape, understanding the various generational groupsโ€”Baby Boomers, Gen X, Millennials, and Gen Zโ€”can truly enhance collaboration. I recently teamed up with a Baby Boomer educator who relied heavily on traditional teaching methods. Our contrasting styles sparked some lively discussions, making me realize how vital it is to blend experience with modern approaches to maximize learning outcomes. Isnโ€™t it fascinating how each generation brings unique strengths to the table?

    One striking example was during a seminar where I witnessed Gen Z students utilizing technology in ways I had never imagined. They were effortlessly blending social media applications into their presentations, which caught my attention. It reminded me of my early teaching days, when I often resisted change. This interaction made me reflect on how essential it is to remain open-minded and receptive to new ideas to better engage students. Have you ever thought about how innovations in communication can transform the classroom experience?

    Iโ€™ve also noticed that Gen X educators often prefer a hybrid approach to teaching. They appreciate the stability of proven methods while recognizing the benefits of incorporating modern technologies. I remember collaborating with a Gen X peer on a project where we created a blended learning environment. It was rewarding to harmonize our different strengths, creating a richer learning experience for students. How does merging various generational insights shape your own educational practices?

    Characteristics of each generation

    Characteristics of each generation

    Baby Boomers are known for their strong work ethic and loyalty, often valuing face-to-face communication and structured environments. Reflecting on my experiences working alongside them, Iโ€™ve found that they appreciate clear directions and a respect for hierarchy. I remember a project meeting where my Baby Boomer colleague emphasized the importance of thorough preparationโ€”an approach that taught me the value of detail-oriented planning, especially in educational settings.

    Gen X, on the other hand, tends to embrace a balanced approach, blending traditional and innovative teaching methods. During a recent workshop, I noticed how my Gen X partners encouraged open discussions while still respecting established protocols. It struck me how their ability to navigate both worlds enabled us to create an engaging atmosphere that appealed to varied learning preferences. Isn’t it refreshing to see how this generation values flexibility and adaptation?

    Millennials, characterized by their tech-savviness and collaborative nature, often thrive in environments that foster creativity. Iโ€™ve had the opportunity to work with Millennials who introduced me to online platforms that facilitate real-time collaboration. Their enthusiasm for group projects and peer feedback sparked a wave of creativity in our lessons. Have you ever considered how much energy and innovation this generation can bring into educational events?

    Strategies for effective communication

    Strategies for effective communication

    Effective communication begins with understanding the preferences of each generation. I remember a significant workshop with a team comprising Baby Boomers, Gen X, and Millennials. By adjusting my styleโ€”using visuals for the younger members while providing clear, concise summaries for the older colleaguesโ€”I noticed how much smoother our discussions became. This experience reinforced my belief that adapting my communication method can significantly enhance collaboration.

    Another strategy I employ is leveraging technology to connect with diverse age groups. During an educational event focused on interactive learning, I used a mix of traditional presentations and digital tools. I saw how much more engaged the Gen Z participants became when I incorporated gamification elements. It was a reminder that when you align your communication strategy with your audience’s preferences, you can create a more inclusive and impactful environment.

    Listening actively is also paramount in fostering effective communication. In a recent team meeting, I made a point to pause and invite feedback from each generation. By showing that I genuinely valued their insights, the conversation flourished, leading to ideas that I hadn’t even considered. How often do we underestimate the power of simply hearing others out? Each generation brings unique perspectives that can enrich discussions and drive innovation in educational contexts.

    Personal experiences with adaptation

    Personal experiences with adaptation

    I remember a time when I organized a workshop that brought together a group of educators from different generations. Initially, I felt a bit overwhelmed by the varying communication styles, but I quickly adapted. By inviting everyone to share their experiences through storytelling, I noticed how the room lit up. It became apparent that once we connected on a personal level, the barriers related to age started to fade.

    There was another instance during a virtual seminar where I had to engage participants ranging from seasoned professionals to digital natives. I decided to implement breakout rooms, pairing individuals from different age groups. Watching them collaborate sparked an unexpected sense of camaraderie, and it reminded me how often we overlook the value of peer interactions that transcend generational divides. How can we foster such connections in our everyday engagements?

    Reflecting on my experiences, I also realized the importance of patience. In conversations, especially with older generations, I learned that sometimes itโ€™s essential to take a step back and allow silence to breathe. I vividly recall a senior colleague who initially seemed resistant to new ideas. However, after embracing a slower, more thoughtful communication approach, I found that he opened up with insights that were incredibly enriching. Isnโ€™t it fascinating how a little patience can transform our understanding of one another?

    Lessons learned from educational events

    Lessons learned from educational events

    Engaging with participants across generations has taught me the value of active listening. In one workshop, I noticed that a younger participant often interrupted an older educator. I paused the discussion and encouraged the younger individual to express their thoughts after letting the elder finish. It struck me that it’s not just about exchanging ideas; it’s about respecting the flow of conversation. How often do we miss meaningful contributions because we’re too eager to jump in?

    Another lesson that stands out is the power of visual aids, especially in mixed-age settings. I recall a presentation where I incorporated infographics and videos. The diverse group reacted positively, bridging gaps between those who preferred traditional lecture methods and those attracted to multimedia. It was a clear reminder that varied communication tools cater to different learning styles, allowing everyone to engage in their comfort zone. Isnโ€™t it rewarding when we can unite different perspectives through creative means?

    Finally, I’ve learned that humor can be an incredible icebreaker. During a particularly tense discussion about technology in education, I shared a light-hearted anecdote from my teaching days. The laughter that followed not only lightened the mood but also opened the floor for more candid exchanges. It made me reflect on how essential it is to bring warmth into our conversations, especially when addressing complex or intimidating topics. Can humor, in its simplicity, truly be the key to unlocking deeper dialogues?

  • How I adapt to changing discussion energies

    Key takeaways:

    • Discussion energies in education are influenced by participant engagement and facilitator enthusiasm, with the potential for transformative learning experiences.
    • Observing body language and timing can indicate shifts in discussion dynamics, allowing educators to adapt their approach to maintain engagement.
    • Techniques like open-ended questions, interactive activities, and sharing personal stories enhance participant involvement and foster a sense of connection.
    • Adapting to changes in energy during discussions, such as introducing hands-on experiences or structured speaking methods, can revitalize engagement and promote deeper connections among participants.

    Understanding discussion energies in education

    Understanding discussion energies in education

    Discussion energies in education refer to the dynamic atmosphere created during conversations in a learning environment. I remember a session where the energy was palpable; students were leaning in, eyes bright with curiosity. This often magical interaction can be driven by the enthusiasm of the facilitator or the interest level of the participants.

    Iโ€™ve noticed that a shift in energies can be triggered by various factors, such as the subject matter or the diversity of participants. For example, during a workshop on digital literacy, the energy surged as we included real-life applications, engaging studentsโ€™ emotions and experiences. Have you ever felt that spark when connecting a topic to something deeply personal? It transforms the discussion from mere exchange of ideas to a vibrant, shared learning journey.

    Moreover, understanding these energies is crucial for educators. Recognizing when the room has fizzled out or is on fire with enthusiasm can shape how I approach the discussion. Iโ€™ve learned that sometimes pausing for reflection or injecting a thought-provoking question can reignite that energy, keeping the dialogue not only alive but thriving. What strategies have you found effective in tapping into the collective energy of your classroom discussions?

    Observing changes in discussion dynamics

    Observing changes in discussion dynamics

    Observing changes in discussion dynamics is an intuitive process for me. I recall one particularly lively group discussion where the tone shifted dramatically when a quiet student finally spoke up. Their comment not only changed the trajectory of the conversation but also sparked a wave of animated responses from others. Have you noticed how a single voice can alter the collective mood?

    I’ve found that body language often provides valuable clues about shifting dynamics. For instance, during a debate about ethical dilemmas, the room filled with tension as some participants crossed their arms or leaned back, indicating resistance. In contrast, those who leaned forward and maintained eye contact seemed immersed and engaged. This contrast not only highlights the energy in the room but also signals me to adapt my approachโ€”either to encourage quieter voices or to address the resistance head-on.

    One lesson that stands out to me is the importance of timing. I’ve experienced that a conversation can enter a lull right after a heavy topic. I remember pausing to share a light-hearted personal story, which lightened the mood and rejuvenated the discussion. Isn’t it fascinating how a simple shift in tone can breathe new life into the dialogue? It reinforces my belief that being attuned to these subtle changes is vital for fostering a thriving learning environment.

    Techniques for engaging participants effectively

    Techniques for engaging participants effectively

    One effective technique I’ve found is incorporating open-ended questions into discussions. When I pose a question that invites more than just a yes or no answer, I often see participants light up with ideas and insights. For example, during a workshop on creative problem-solving, I asked, “What are some unconventional solutions you’ve seen work in your field?” The varied responses not only showcased diverse experiences but also sparked a deeper exploration of the topic among participants.

    Another method I utilize is incorporating interactive activities, such as small group discussions or role-playing scenarios. I remember one educational event where we divided participants into groups to brainstorm solutions. The atmosphere shifted from passive listening to active engagement. It was inspiring to see individuals who were initially hesitant fully immerse themselves in the activity. Have you ever noticed how collaboration can ignite enthusiasm?

    Lastly, Iโ€™ve learned that sharing personal experiences can create a sense of connection and encourage openness. During a recent panel discussion, I recounted a past failure and the lessons I learned from it. The vulnerability seemed to resonate with the audience, prompting them to share their own challenges. This exchange not only transformed the dynamic but also built trust among participants, fostering a richer dialogue. Isnโ€™t it remarkable how sharing our stories can bridge gaps and enhance engagement?

    Case studies of successful adaptations

    Case studies of successful adaptations

    In my experience, adapting to shifting energies during discussions can be pivotal for maintaining engagement. For instance, at an educational seminar on digital literacy, I noticed a drop in energy as a lengthy presentation progressed. Recognizing the shift, I suddenly pivoted to a live demonstration and invited participants to try out a digital tool. This hands-on experience not only rejuvenated the room but also transformed the atmosphere into one of collaborative exploration. Have you ever seen how a simple change in approach can completely revitalize a discussion?

    Another case that stands out to me occurred during a community workshop on public speaking. Initially, participants seemed hesitant to share their thoughts. I decided to implement a ‘talking stick’ method, where only the person holding the stick could speak. This strategy created a sense of safety and respect, allowing individuals to express their ideas without interruption. The result was a lively exchange of perspectives, infused with both excitement and confidence. I couldn’t help but feel that this small adjustment opened the door for deeper connections among participants.

    One time, while facilitating a training session on leadership skills, I sensed the audience becoming disengaged during a lengthy Q&A. Instead of pushing through, I called for a quick energizerโ€”an impromptu group activity where everyone had to share a leadership lesson learned in under a minute. The shift was palpable. Participants were not only more engaged but also eager to connect their experiences with the topic at hand. It was a reminder that our discussions can thrive when we embrace flexibility and encourage spontaneous interaction. Isn’t it fascinating how a small change can unlock such potential?