= 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 navigate transitions in difficult conversations

    Key takeaways:

    • Understanding emotions is crucial in difficult conversations, fostering empathy and creating space for honest dialogue.
    • Effective transitions in dialogue help maintain clarity and engagement, preventing misunderstandings and fostering collaboration.
    • Using “I” statements and active listening enhances communication, allowing for a more constructive and non-defensive exchange.
    • Techniques like grounding, recognizing emotions, and pausing can manage feelings effectively, improving the outcome of challenging discussions.

    Understanding difficult conversations

    Understanding difficult conversations

    Difficult conversations can feel like walking a tightrope—one misstep might send everything spiraling. I remember a time when I had to address a performance issue with a colleague. My heart raced with anxiety, not just about the conversation itself, but about the potential fallout. Isn’t it interesting how something so crucial can weigh so heavily on our minds?

    Understanding the underlying emotions in these discussions is crucial. When I finally faced my colleague, I could see the tension in his posture, mirroring my own. It made me realize that both parties often enter these conversations with apprehensions. How often do we stop to consider the other person’s perspective before diving in?

    Navigating these conversations requires not just courage but also empathy. I’ve found that acknowledging my feelings and those of the other person helps create a space for honesty. Have you ever noticed how just a hint of vulnerability can transform tense exchanges into more productive dialogues? It’s a game changer, opening doors to understanding that might otherwise remain closed.

    Importance of transitions in dialogue

    Importance of transitions in dialogue

    Transitions in dialogue are like bridges; they guide us smoothly from one point to another. I recall a tense meeting where my supervisor abruptly shifted the conversation from feedback to project deadlines. Without any transition, the change felt jarring, leaving team members confused and defensive. It’s fascinating how a seamless transition can foster a collaborative atmosphere, while a sudden shift can lead to misunderstandings.

    Crafting appropriate transitions helps maintain the flow of conversation and keeps everyone engaged. I remember a time when I asked a probing question mid-conversation that momentarily threw my discussion partner off balance. That small but unexpected shift made me realize how crucial it is to prepare others for topic changes. Have you ever experienced that moment when the dialogue felt like a rollercoaster because the transitions were too abrupt?

    Moreover, effective transitions invite participation and encourage active listening. In one challenging chat with a family member about finances, I found that gently guiding the conversation from emotions to potential solutions made a world of difference. As soon as I acknowledged the emotional weight, both of us could breathe easier, leading us to a constructive dialogue. Don’t you think that when we transition thoughtfully, we create opportunities for shared understanding?

    Strategies for effective communication

    Strategies for effective communication

    When it comes to effective communication, actively listening is one of the most vital strategies. I recall a conversation I had with a colleague about project challenges; instead of interrupting with my solutions, I made it a point to listen intently. This approach not only made my colleague feel heard but also helped me understand the nuances of the issue, which ultimately led to a more relevant and tailored response. Have you noticed how much richer conversations can be when we genuinely focus on understanding the other person’s perspective?

    Another powerful strategy is to use “I” statements to communicate feelings and thoughts without making the other person feel defensive. For instance, during a discussion about team performance, I shared, “I feel concerned when deadlines are missed because it impacts our overall goals.” Framing it this way transformed a potentially confrontational conversation into a collaborative brainstorming session. Isn’t it interesting how a simple shift in language can change the entire dynamic of the discussion?

    Additionally, maintaining a calm and open demeanor can significantly enhance the effectiveness of communication, especially during tough discussions. There was a moment when I had to address a sensitive topic with a friend who was struggling. By keeping my tone steady and my body language open, I created a safe space for them to share their feelings without fear of judgment. Have you ever noticed how your physical presence can change the tone of a conversation?

    Techniques for managing emotions

    Techniques for managing emotions

    When it comes to managing emotions during difficult conversations, one technique I’ve found particularly effective is grounding myself in the moment. Before a challenging discussion, I take a few deep breaths and remind myself of my core intentions. I once prepared for a feedback session by visualizing a positive outcome. This mental exercise calmed my nerves, allowing me to approach the conversation with clarity rather than anxiety. Have you ever tried pausing to reset your mindset before diving into a tough dialogue? It can truly make a difference.

    Another crucial technique is recognizing and validating emotions, both within yourself and the other person. I recall a negotiation where my emotions surged, feeling pushed into a corner. Instead of suppressing those feelings, I acknowledged them by admitting, “I feel overwhelmed right now, and it’s important we address this together.” This small declaration opened the door for my counterpart to express their feelings as well, and it transformed the whole interaction into a more understanding exchange. How often do we miss opportunities for connection by glossing over emotions?

    Moreover, using a buffering strategy—like taking a brief break—can be incredibly helpful. During a particularly heated discussion, I suggested we take a short pause to gather our thoughts. That simple break allowed both parties to process emotions and return with a fresher perspective. Have you noticed how stepping away, even briefly, often helps prevent unnecessary escalation in conflict? It’s a tactic that provides space for reflection and can lead to more constructive outcomes.

    Tips for transitioning topics smoothly

    Tips for transitioning topics smoothly

    To ensure a smooth transition between topics, I often find it helpful to create a bridge that links the current subject with what I want to introduce next. For example, if I’ve been discussing emotions in a conflict, I might say, “Now that we’ve addressed how feelings can shape our conversations, let’s explore how we can shift our focus to solutions.” This technique not only maintains the flow but also reinforces the idea that each point connects and builds upon the previous one. Have you ever considered how linking ideas can create a more cohesive discussion?

    Another tip is to use open-ended questions as a way to segue into new topics. By asking a question, I invite the other person into the conversation, prompting them to share their thoughts while seamlessly guiding them to what I want to discuss. I remember a time when I was shifting from talking about project goals to team dynamics; I asked, “What challenges have you faced in collaboration lately?” This not only shifted the focus but also engaged my colleague right away. Isn’t it fascinating how a simple question can open up a new pathway in dialogue?

    Sometimes, I like to use summarization as a transitional tool. After wrapping up one point, I summarize key takeaways before introducing the next topic. For instance, I might conclude, “So we’ve established the importance of emotional awareness, and that naturally leads us to consider how we can enhance our communication strategies.” This method reinforces understanding while gently guiding the conversation in a new direction. Have you noticed how such clarity can make the transition feel less abrupt and more natural?

    Personal reflections on past experiences

    Personal reflections on past experiences

    Reflecting on my past experiences, I recall a particularly challenging conversation with a colleague about performance issues. It was difficult to approach, but I learned that sharing my own struggles first helped to create an atmosphere of openness. I remember saying, “I’ve faced situations where feedback felt daunting, but I’ve grown so much from those discussions.” This honesty encouraged my colleague to lower their defenses and engage more genuinely.

    There have been times when I transitioned to discussing sensitive topics with hesitation, recalling the tension in the air. However, I’ve discovered that highlighting common objectives can shift the focus significantly. For example, during a heated meeting, I shared how we all sought the same outcome of team success, leading to a more collaborative dialogue. It made me realize how linking our shared goals can foster understanding, even in the most difficult conversations.

    I often think about my early career days when I faced tough discussions without knowing how to steer them. A memorable moment was when I practiced transitions at home with friends, using real scenarios. I felt vulnerable sharing my experiences, but this vulnerability allowed for more meaningful exchanges. Have you ever noticed how sharing personal experiences can transform a conversation from confrontational to conversational? It’s a powerful reminder of how connection can ease tension.

  • How I navigate the emotional landscape during conversations

    Key takeaways:

    • Emotional landscapes influence communication; awareness of these dynamics fosters deeper connections and understanding.
    • Active listening, empathy, and clarity are essential strategies for effective communication that enhance dialogue and collaboration.
    • Managing emotions through techniques like deep breathing and reflection can significantly improve the quality of conversations.
    • Continuous self-improvement, including seeking feedback and setting goals, enhances conversational skills and promotes personal growth.

    Understanding emotional landscapes

    Understanding emotional landscapes

    Understanding emotional landscapes is like navigating a complex map where every emotion represents a different terrain. I remember a time during a group discussion when one participant suddenly became withdrawn. Observing this shift helped me realize how crucial it is to be aware of the emotional currents flowing beneath the surface. Have you ever noticed someone’s energy change mid-conversation? That’s the emotional landscape at play.

    Each person carries their own emotional background, shaped by past experiences, which influences how they communicate. During a workshop, I encountered a participant who seemed skeptical and defensive. By engaging them with empathy and acknowledging their feelings, I found we could dismantle the walls that often surround such emotions. Isn’t it fascinating how simply asking, “What are your thoughts on this?” can open up deeper dialogue?

    Emotional landscapes are not only about individual feelings; they create a collective environment that impacts everyone involved. In leading an educational event, I’ve felt the palpable tension in the room when a controversial topic arises. By recognizing that shared emotional climate, I learned to steer the conversation toward a more constructive path. How do you respond when emotions seem to overwhelm a discussion? Understanding these dynamics is key to fostering meaningful connections.

    Importance of emotional awareness

    Importance of emotional awareness

    Emotional awareness is crucial in fostering authentic communication. I recall a moment during a seminar when a participant expressed frustration about a misunderstanding. Recognizing this unease, I encouraged a brief pause for everyone to reflect. This simple act not only diffused tension but also allowed for a more meaningful exchange of ideas. How often do we overlook these subtle cues that can transform a conversation?

    Being emotionally attuned helps create a safe space where individuals feel valued and heard. I once facilitated a discussion where a quiet attendee gradually opened up after I acknowledged their initial apprehension. By validating their feelings, I could sense a shift in the room’s energy—a collective willingness to engage on a deeper level. It’s amazing how emotional climate can enhance or hinder our ability to connect.

    Moreover, emotional awareness drives better decision-making. In team settings, I’ve found that recognizing when emotions run high can lead to more thoughtful dialogue. For instance, during a heated planning session, I consciously took a step back to gauge reactions. This pause enabled us to refocus our energies and find common ground, ultimately steering us toward a more collaborative outcome. What strategies do you use to maintain emotional awareness in your interactions?

    Strategies for effective communication

    Strategies for effective communication

    Effective communication hinges on active listening. I remember a workshop where participants practiced this skill through role-playing. One person shared their perspective while the partner listened without interrupting. There was a noticeable shift in the atmosphere; as each felt valued and understood, barriers came down and honest dialogue flourished. How often do we truly listen, rather than simply waiting for our turn to speak?

    Another strategy is to mirror body language. I once had a colleague who instinctively mirrored my gestures during a discussion. At first, I was surprised, but I soon realized it created a more relaxed interaction. It’s fascinating how non-verbal cues can convey empathy and connection, often speaking louder than words. Have you ever noticed how even small gestures can deepen understanding between people?

    Clarity in communication is also vital. A few months ago, I led a meeting where key points were muddled, leading to confusion. To prevent this, I started summarizing discussions at the end, which not only reinforced understanding but also kept everyone aligned. I believe it’s essential for us to find ways to express our ideas clearly. How do you ensure your message resonates with others?

    Techniques to manage emotions

    Techniques to manage emotions

    Managing emotions during conversations is a skill I continuously work on. One technique I find immensely helpful is grounding myself through deep breathing. Before engaging in potentially heated discussions, I take a moment to inhale deeply and exhale slowly. This practice centers me, allowing me to approach the conversation with a calm and open mind. Have you ever noticed how just a few deep breaths can change your perspective?

    Another method I often use is to pause and reflect before responding. I recall a time when a friend shared some impactful news, and my initial reaction was to delve in with questions and advice. Instead, I took a moment to process my feelings and simply offered support. That pause transformed our interaction, as it demonstrated my willingness to be present rather than reactive. How do you navigate moments when emotions run high?

    Journaling is also a technique I’ve embraced to help manage my feelings about ongoing conversations. By writing down my thoughts, I can explore different perspectives and clarify my emotions away from the dialogue itself. After a tough discussion, I often pen my feelings, which brings me clarity and helps me approach future interactions with better understanding. Have you ever tried putting your thoughts on paper to untangle your feelings? It can be surprisingly therapeutic.

    Navigating difficult conversations

    Navigating difficult conversations

    Navigating difficult conversations has become a pivotal part of my personal growth. I remember a time when I had to discuss a sensitive topic with a colleague who was struggling with performance issues. Instead of approaching it head-on, I chose to express empathy first. By acknowledging their feelings and concerns, I was able to create a safe space for dialogue. Have you ever considered how a little empathy can change the entire tone of a conversation?

    Another effective strategy is to maintain a curious mindset. There was an instance when a friend and I had a falling out over a misunderstanding. Rather than getting defensive, I chose to ask questions and genuinely listen to their perspective. This choice to be curious rather than combative not only defused the tension but also deepened our understanding of each other. When was the last time you approached a difficult talk with curiosity instead of judgment?

    One thing I’ve learned is the significance of setting boundaries during tough discussions. I had a conversation with a family member about differing values, and it quickly grew overly emotional. To keep the dialogue constructive, I invoked a boundary – asking to take breaks if conversations became too heated. This led to more productive exchanges without the emotional baggage. Do you have boundaries in place to protect your emotional well-being during challenging conversations?

    Reflecting on personal experiences

    Reflecting on personal experiences

    Reflecting on my personal experiences often reveals how our emotional responses can shape conversations. I recall a particularly intense discussion with a close friend where our emotions ran high over a differing opinion. Instead of placing blame, I took a moment to reflect on why this topic evoked such strong feelings in both of us, which helped me see the bigger picture. Have you ever paused in the heat of an argument to understand what underlies your emotional reactions?

    There was also a time during a team project when I realized how my past experiences influenced my current interactions. A colleague mentioned feeling overwhelmed, which reminded me of my first few projects in a new job. By sharing my journey and how I managed to overcome similar feelings, I built a bridge of understanding. This connection not only eased their anxiety but transformed our dialogue into a mutual exchange of support. How do your past experiences inform your current conversations?

    Sometimes, reflecting on past conversations can uncover invaluable lessons. I previously had a discussion with my mentor, where I mistakenly interrupted them in my eagerness to share my ideas. Afterward, I reflected on how that affected the flow of our conversation and made me rethink the importance of active listening. This realization has since inspired me to give others the space to express themselves fully. Have you assessed your conversational habits to find patterns that may disrupt the flow?

    Tips for continuous improvement

    Tips for continuous improvement

    Focusing on continuous improvement in our conversations requires regular introspection. I recall a time at a networking event when I felt anxious during conversations, often stumbling over my words. Instead of shying away, I made a point to practice my speaking skills in lower-stakes environments, which gradually built my confidence. Do you dedicate time to practice and refine your conversational skills?

    An effective strategy I’ve found is seeking feedback from trusted friends or colleagues after important talks. After a presentation, I once asked a coworker how I could improve my delivery. Their constructive criticism helped me identify areas where I was too technical or vague. How often do you invite feedback? It’s a powerful tool for growth that often leads to meaningful insights.

    Lastly, I believe that setting personal goals can significantly enhance our conversational prowess. For example, I aimed to ask one thoughtful question in every discussion for a week. This simple change helped me listen more deeply and uncover fascinating perspectives from others. What specific goals can you set to improve your conversational interactions? By consistently challenging ourselves, we can evolve and foster richer connections.

  • How I navigate the line between personal belief and professional facilitation

    Key takeaways:

    • Educational events should focus on creating immersive experiences and fostering community connections rather than merely delivering content.
    • Facilitators must balance personal beliefs with the need for open dialogue, creating an environment where diverse perspectives can be shared and respected.
    • Effective facilitation relies on emotional intelligence and flexibility, allowing for meaningful discussions even when topics shift unexpectedly.
    • Sharing personal stories can promote vulnerability and empathy, enabling deeper connections among participants and enhancing the facilitation experience.

    Understanding educational events

    Understanding educational events

    Understanding educational events goes beyond just organizing lectures or workshops; it involves creating immersive experiences that resonate with both facilitators and participants. I remember the first event I facilitated, and the anxiety I felt was palpable. Would the attendees connect with the content? This question drove my preparation and underscored the importance of being attuned to the audience’s needs.

    These gatherings can be transformative, often sparking crucial conversations that linger long after the event. I once attended a seminar where a simple icebreaker led to a deep discussion about diversity in education. It struck me how a small moment could unlock someone’s perspective and encourage them to share their experiences openly. Have you ever experienced a turning point in a conversation like that?

    Ultimately, the essence of educational events lies in the interactions they foster. It’s not just about imparting knowledge; it’s about building a community around shared learning goals and experiences. I’ve often left events feeling inspired not only by the material presented but by the connections made with others who share similar passions and aspirations.

    Importance of personal belief

    Importance of personal belief

    Personal belief plays a crucial role in shaping how I engage with others in educational settings. When I reflect on my core values, I realize that they not only influence the content I present but also set the tone for the entire event. For instance, during a workshop I facilitated on inclusive practices, my belief in the importance of every student feeling valued made me approach the session differently. I invited attendees to share their experiences, creating a space where personal stories bolstered our collective understanding.

    When I think about the weight of personal beliefs, I recognize that they can be a double-edged sword. While they guide my facilitation, they also challenge me to remain open to diverse perspectives. One time, during a community event focused on educational equity, a participant passionately disagreed with my viewpoint. Initially, I felt defensive, but then I realized this was an opportunity for deeper dialogue. How often do we let our beliefs cloud our ability to listen? I learned that being rooted in my values doesn’t mean closing myself off; instead, it offers a chance to deepen connections and understanding.

    In my experience, the authenticity that comes from personal belief resonates powerfully with participants. It’s about creating trust and encouraging vulnerability, which can lead to transformative conversations. I recall a moment when a fellow facilitator shared her struggles with self-doubt, and it encouraged others to open up as well. This vulnerability paved the way for rich exchanges that highlighted our shared humanity. Isn’t it remarkable how our beliefs, when shared sincerely, can foster a sense of belonging among diverse groups?

    Role of professional facilitation

    Role of professional facilitation

    The role of professional facilitation is pivotal in guiding discussions and ensuring that all voices are heard. When I facilitate, I consider myself a bridge between diverse viewpoints. For example, during a session on innovative teaching strategies, I noticed one teacher feeling hesitant to share. By gently prompting him and acknowledging his expertise, I transformed the atmosphere, encouraging everyone to contribute their unique insights. Isn’t it fascinating how small interventions can shift group dynamics?

    In my observations, a strong facilitator sets the agenda while remaining flexible. There was a time I hosted a forum on technology in education, and halfway through, a participant raised concerns that weren’t on our agenda. Instead of dismissing it, I shifted gears and allowed that conversation to unfold. It reminded me that sometimes the most meaningful discussions arise from unexpected topics. How often do we stick to our plans, potentially missing out on valuable insights?

    Moreover, professional facilitation requires emotional intelligence. I recall a workshop where tensions rose between two participants with conflicting beliefs about assessment techniques. By recognizing the emotional undertones and addressing them, I created a safe space for resolution. I often ponder how crucial it is to navigate these emotional landscapes with care. How can we ensure that our professional skills complement the emotional needs of our audience? Ultimately, facilitation goes beyond managing logistics; it’s about fostering an environment where learning occurs at multiple levels.

    Balancing beliefs and objectives

    Balancing beliefs and objectives

    Navigating the line between personal belief and professional objectives has always intrigued me. In one workshop, I found it challenging when my own educational philosophy clashed with a participant’s perspective. Instead of forcing my opinion, I chose to highlight the strengths in both viewpoints, which allowed for a more enriched discussion. Did it feel uncomfortable at times? Absolutely, but I learned that my role is not to impose beliefs but to foster understanding.

    On another occasion, while facilitating a seminar on inclusivity, I faced the dilemma of upholding my values while respecting differing opinions. I remember a moment when a participant expressed skepticism about inclusive practices. My instinct was to counter with data and research. Instead, I asked them to share their experiences, opening a dialogue that deepened trust among the group. This taught me that true balance lies in listening as much as asserting; it’s a delicate dance, isn’t it?

    I often reflect on how belief systems can guide or hinder facilitation. During a collaborative planning session, my commitment to student-centered learning was tested when some educators favored traditional approaches. Rather than shutting down their suggestions, I facilitated an exploration of how we could blend methodologies. The process turned out to be enlightening for everyone involved. It reinforced my conviction that effective facilitation thrives on the interplay of beliefs and objectives, creating a tapestry of ideas that ultimately benefits all.

    Strategies for effective navigation

    Strategies for effective navigation

    When it comes to navigating the often murky waters of personal belief and professional facilitation, I’ve found that self-reflection is a powerful tool. In one of my workshops, I realized I needed to assess my emotional responses to differing opinions. By taking a moment to understand why certain beliefs triggered me, I cultivated a more open mindset. Isn’t it amazing how awareness can transform the way we interact with others?

    Establishing ground rules for discussions can significantly enhance the facilitation experience. During a recent event, I introduced a simple guideline: “Respect all opinions, even when you disagree.” This shift created an atmosphere of safety where participants felt comfortable sharing their views, even when they diverged from mine. I watched as the room transformed into a space for constructive debate rather than a battleground of ideas. How often do you see a disagreement lead to real learning? It’s definitely possible when we set the right conditions.

    Finally, bringing in real-world examples can bridge the gap between beliefs and objectives. In a session focused on innovative teaching methods, I shared stories from educators who faced similar dilemmas in their practices. These anecdotes sparked genuine conversations, allowing participants to connect their beliefs to practical applications. It’s moments like these that remind me how storytelling can not only engage but also empower individuals to explore their own beliefs within a professional context. Have you ever noticed how a personal story can shift the tone of a discussion? It’s quite remarkable.

    Case studies of successful facilitation

    Case studies of successful facilitation

    One of my favorite case studies involves a community workshop I facilitated on cultural diversity. We began with participants sharing their own stories related to cultural experiences. What struck me was how quickly the initial tension ebbed away, replaced by a powerful sense of empathy and understanding. Reflecting on these personal stories not only encouraged a deeper connection among the group but also allowed everyone to navigate their beliefs in a supportive environment. Have you ever felt that shift when personal narratives take the lead?

    Another successful facilitation experience happened during a corporate training session focused on team dynamics. I implemented small breakout groups where participants discussed their differing views on collaboration. As I moved between groups, I could sense the energy; participants were not only sharing their perspectives but also actively listening to each other. This relational aspect made me realize that sometimes, as facilitators, our role is simply to create space for these dialogues to flourish. How many times do we avoid these conversations in our everyday lives due to discomfort?

    In a more challenging seminar on ethics, I encountered polarized opinions about a controversial topic. Instead of shutting down discussions, I strategically posed open-ended questions that encouraged reflection. I shared a story about a personal ethical dilemma I faced, which seemed to resonate with the group deeply. It opened the floodgates for participants to express their own uncertainties and fears. I found this approach not only fostered trust but also illuminated the complexity of ethical decision-making. Isn’t it fascinating how sharing your vulnerability can pave the way for open dialogue?

    Reflecting on personal experiences

    Reflecting on personal experiences

    Reflecting on my journey as a facilitator, I often think about a time when I led a group of educators through a session on inclusive teaching practices. As we shared our struggles and triumphs in the classroom, I realized how much our individual experiences shaped our beliefs about inclusivity. It was a reminder that our personal narratives can act as powerful tools to dismantle barriers and foster understanding. Have you ever paused to consider how your own teaching experiences influence your approach to facilitating discussions?

    Another moment that stands out to me was during a workshop focused on conflict resolution. I decided to share a particularly difficult experience I had with a colleague. As I spoke about the emotions involved and the lessons learned, I could see nods of recognition among the participants. It brought to light a shared vulnerability that allowed others to step forward and share their own challenges. This connection was not only cathartic but it also underscored the importance of empathy in navigating differing beliefs. Doesn’t it feel liberating when we realize we’re not alone in our struggles?

    In reflecting on these experiences, I’ve come to appreciate the delicate balance between personal belief and professional facilitation. There was a session where I simply posed the question, “What does respect mean to you?” The responses revealed a multitude of perspectives, enriching our conversation. I found myself invigorated by the diversity of thought and reminded that despite our differences, we all seek understanding. Isn’t it intriguing how the threads of our individual beliefs can weave a stronger fabric of collective insight?

  • How I navigate the complexities of power dynamics in dialogue

    Key takeaways:

    • Power dynamics significantly influence dialogue, and recognizing them can help empower quieter participants to share their insights.
    • Creating a safe dialogue environment relies on establishing trust, setting clear ground rules, and active facilitation to maintain constructive discussions.
    • Active listening and open-ended questions are effective strategies for navigating power dynamics, fostering inclusive and valuable conversations.
    • Acknowledging and addressing discomfort in dialogue can lead to breakthroughs and more honest exchanges between participants.

    Understanding power dynamics

    Understanding power dynamics

    Power dynamics play a crucial role in any dialogue, shaping how participants interact and influence one another. I once facilitated a workshop where one participant dominated the conversation, and it made me realize how subtle shifts in power can impact the flow of discussion. Have you ever felt your voice diminish in a group setting? It’s a common experience, and understanding these dynamics can empower us to speak up.

    Recognizing varying levels of authority and confidence among speakers is essential. In my experience, I’ve noted that those who listen actively often gain more influence than the loudest voice. This realization changed how I engage in conversations; I now focus on asking questions that encourage quieter participants to share their insights. Isn’t it fascinating how a little encouragement can shift the balance of power?

    Emotional awareness is another key aspect of power dynamics. When tensions rise or someone feels unheard, it’s crucial to address these feelings openly. I remember a time when acknowledging a participant’s frustration transformed the atmosphere from one of defensiveness to collaboration. Isn’t it rewarding to see how empathy can lead to more balanced interactions?

    Importance of dialogue in education

    Importance of dialogue in education

    Dialogue serves as the backbone of effective education, fostering an environment where ideas can flourish. I recall a classroom discussion that sparked after a student felt encouraged to share a controversial opinion. The resulting debate not only deepened our understanding but also created a sense of community among the participants, emphasizing that every voice matters.

    When dialogue is prioritized, it promotes critical thinking and engagement. In a recent seminar, I witnessed how a single question posed by a participant transformed a lecture into an interactive experience. This shift illustrated how dialogue can stimulate curiosity and motivate learners to explore topics more deeply than they might in a traditional lecture format.

    Moreover, dialogue nurtures a safe space for vulnerability, where students can express their thoughts without fear of judgment. I often reflect on times when I shared my uncertainties, only to realize that many others were grappling with similar feelings. Isn’t it powerful how sharing our challenges invites deeper connections and collective growth in educational settings?

    Creating a safe dialogue environment

    Creating a safe dialogue environment

    Creating a safe dialogue environment hinges on establishing trust among participants. I remember a workshop where the facilitator began by sharing a personal story about her own struggles with confidence in speaking up. This transparency encouraged others to share their vulnerabilities, allowing everyone to feel less isolated in their experiences. How often do we underestimate the impact of authenticity in fostering connections?

    Another key aspect is setting clear ground rules. In my experience, when a group agrees on norms, such as mutual respect and active listening, the quality of dialogue dramatically improves. It becomes so much easier to navigate sensitive topics when everyone is on the same page. Have you ever noticed how much more comfortable people are when they know the boundaries?

    Additionally, active facilitation is essential in maintaining a safe atmosphere. I once attended a session where the moderator skillfully redirected a potentially heated discussion by reminding participants of the agreed-upon rules. This intervention not only diffused tension but also reinforced the importance of collaborative dialogue. Isn’t it fascinating how a well-timed nudge can reshape conversations into constructive exchanges?

    Identifying power imbalances

    Identifying power imbalances

    Identifying power imbalances in dialogue often starts with observing the dynamics in the room. I recall a discussion where one participant dominated the conversation while others hesitated to voice their opinions. It struck me then how subtle cues—like body language and tone—can reveal who feels empowered to speak. Have you ever noticed how certain voices seem to drown out others, even in mixed groups?

    Moreover, language choice plays a crucial role in signaling power dynamics. I once participated in a forum where one speaker repeatedly used jargon that many attendees didn’t understand. This not only alienated some participants but also created an unintentional hierarchy based on knowledge. Isn’t it interesting how the choice of words can inadvertently reinforce someone’s authority while disempowering others?

    Sometimes, the social context matters more than we realize. Recently, I attended an educational event in a corporate setting where the hierarchy was almost palpable. Some voices were louder simply because of their titles or seniority, highlighting how external factors can create barriers in dialogue. It made me think about the responsibility we each have to level the playing field. What steps can we take to ensure everyone’s voice is heard, regardless of their position?

    Strategies for navigating power dynamics

    Strategies for navigating power dynamics

    Recognizing the importance of active listening is vital when navigating power dynamics. I remember a workshop where I made a conscious effort to listen more than speak. This resulted in quieter participants gradually sharing their insights, bringing forth ideas that enriched the discussion. Have you ever noticed how creating space can empower others to share their thoughts?

    In my experience, asking open-ended questions can also break down barriers. At one seminar, I intentionally posed questions that invited diverse perspectives. The result was a dynamic conversation where everyone felt valued. I found it fascinating how a simple prompt could shift the dialogue from a one-sided lecture to a collaborative exchange. What strategies do you use to encourage participation?

    Another strategy involves reflecting back what I’ve heard to validate others’ contributions. There’s a time when I paraphrased an attendee’s point during a discussion, which not only reassured them that their voice mattered but also prompted further elaboration. This small act can transform the atmosphere and lead to more inclusive dialogues. Have you considered how mirroring someone’s thoughts can empower them to express themselves more freely?

    Personal experiences in dialogue

    Personal experiences in dialogue

    During a panel discussion I attended, I was struck by how power dynamics subtly shaped the interaction. One speaker, despite their authority, encouraged everyone to contribute by genuinely showing curiosity. It changed the atmosphere entirely, making it less about hierarchy and more about shared exploration. Have you ever felt the shift when someone at the top invites open dialogue?

    A memorable moment occurred during a group project meeting where I felt intimidated by a senior member’s presence. As I found my footing, I shared a viewpoint that contrasted with theirs. To my surprise, this sparked a discussion that not only validated my perspective but also prompted the senior member to reflect on their own stance. It was empowering to discover that even amidst higher authority, my voice held weight. How do you navigate those feelings when someone’s power looms over the conversation?

    In another instance, I facilitated a dialogue where there was noticeable tension between two members. Instead of ignoring the discomfort, I addressed it head-on, inviting both sides to articulate their concerns. This move transformed the dialogue from a standoff into a collaborative search for solutions. It felt rewarding to witness how acknowledgment of power dynamics can lead to more honest exchanges. Have you ever facilitated a conversation where addressing discomfort led to breakthroughs?

    Reflections on improving dialogue skills

    Reflections on improving dialogue skills

    Reflecting on my journey to improve dialogue skills, I often find that active listening plays a crucial role. During a workshop I attended, I realized that the more I focused on truly hearing others, the more my responses became meaningful. It was an eye-opener—how often do we listen just to respond, rather than to understand?

    There was a time when I struggled to articulate my thoughts during discussions. I vividly remember a networking event where I stumbled over my words while trying to share an idea. Instead of pulling back, I chose to use that moment as a learning opportunity, honing in on the importance of clarity and simplicity in expression. Have you ever felt that rush of anxiety when speaking up, only to learn that your voice matters?

    I also began experimenting with questions that invite deeper engagement. In my experience, asking open-ended questions not only enriches the conversation but also shares the spotlight. Once, in a community forum, I posed a question that turned the focus toward everyone’s experiences, and it felt like magic watching stories emerge. Isn’t it fascinating how a simple question can shift the dynamics and create a safe space for everyone?

  • How I navigate power dynamics when moderating

    Key takeaways:

    • Power dynamics in discussions can inhibit participation; moderating effectively can create a more inclusive environment.
    • Effective moderation requires strong listening skills, adaptability, and fostering respect to maintain constructive dialogue.
    • Encouraging personal storytelling and open questions can help manage diverse viewpoints and enhance understanding.
    • Establishing trust and addressing disruptive behavior with empathy leads to more collaborative and innovative outcomes during discussions.

    Understanding power dynamics in events

    Understanding power dynamics in events

    Power dynamics in events can change the atmosphere significantly, influencing how participants engage with one another. I remember a workshop where a seasoned expert dominated the conversation, leaving little room for newcomers to express their thoughts. Was this intentional or simply a byproduct of experience? It’s crucial to recognize these dynamics and actively work to balance them.

    When moderating, I often find myself observing the unspoken hierarchies. For instance, at one educational conference, I noticed the reluctance of younger attendees to speak up around established professionals. How can we create an environment where everyone feels valued and empowered to contribute? Acknowledging and addressing these dynamics is essential for fostering inclusive discussions.

    I’ve learned that opening up the floor with questions directed at quieter participants can help break down power barriers. One time, I asked a shy attendee what they thought about a topic that had been dominated by a few loud voices. The shift in energy was palpable. They not only shared their perspective but also inspired others to voice their thoughts, highlighting how a small nudge can reshape the dynamics of any event.

    Importance of moderation in discussions

    Importance of moderation in discussions

    Moderation plays a pivotal role in the success of any discussion. I once moderated a panel where one participant aggressively pushed their agenda, overpowering the others. The energy shifted dramatically when I stepped in to assert that everyone deserved a chance to share their insights. It was a small but vital reminder that a balanced discussion can lead to richer, more diverse perspectives.

    In my experience, good moderation is like a dance—it requires awareness and agility. There was a time during a virtual seminar when I noticed participants chat privately instead of engaging openly. By encouraging dialogue within the group and inviting those on the sidelines to join in, I witnessed the transformation of a silent space into a vibrant exchange of ideas. This power of moderation keeps discussions alive and relevant.

    I often reflect on how moderation fosters not only balance but also understanding among participants. At a recent workshop, I noticed tensions rising when conflicting opinions emerged. By stepping in and facilitating a respectful dialogue, I enabled attendees to articulate their views while discussing opposing perspectives. This created a supportive atmosphere where learning thrived, illustrating that effective moderation can significantly impact the depth and quality of discourse.

    Key skills for effective moderating

    Key skills for effective moderating

    Effective moderating requires strong listening skills, as understanding both verbal and non-verbal cues is essential. I once moderated a workshop where one participant seemed disengaged, their body language screaming disinterest. By pausing and asking for their thoughts, I not only brought them into the conversation, but I also sparked renewed interest from others who had been hesitant. How often do we overlook subtle signs that someone is not fully engaged?

    Another critical skill is adaptability. In a roundtable discussion I led, the original agenda quickly unraveled when a passionate debate erupted. Instead of clinging to a strict schedule, I opted to lean into the moment, allowing the conversation to flow where it needed. This created an atmosphere where participants felt heard, reminding me that flexibility can often lead to deeper connections and insights. Have you ever been surprised by where an open discussion can take you?

    Lastly, establishing a respectful environment is vital for effective moderating. I recall a session where two attendees began interrupting each other, creating a tense atmosphere. I intervened, gently reminding everyone of our commitment to respect and the value of each voice in the room. The shift in energy was palpable, reinforcing for me that creating a safe space encourages authenticity and fosters constructive dialogue. How would our conversations change if we all prioritized respect?

    Strategies for managing diverse viewpoints

    Strategies for managing diverse viewpoints

    When managing diverse viewpoints, active engagement is key. I remember a panel discussion where opinions wildly diverged, causing a rift among attendees. Rather than allowing that tension to escalate, I decided to invite each participant to share a personal story related to their views. This simple tactic not only disarmed the situation but fostered empathy, showing the power of personal narratives in bridging divides. Have you ever noticed how sharing stories can shift the atmosphere in a room?

    Another important strategy is to encourage questions and clarification. In one workshop, I noticed that some participants were nodding along but not fully grasping the concepts discussed. I paused the conversation and opened the floor for questions, emphasizing that every question is valid. The result was enlightening; those who had hesitated began to express their confusion, leading to clarifying discussions that enriched everyone’s understanding. Isn’t it fascinating how inviting curiosity can unlock deeper insights?

    Lastly, it’s essential to synthesize diverse opinions into a cohesive understanding. During a brainstorming session with conflicting ideas about an educational initiative, I paraphrased and reflected on the differing views expressed. By presenting the varied perspectives in a unified manner, I helped the group see common ground, transforming potential conflict into collaborative energy. How often can we turn opposing viewpoints into opportunities for innovation?

    Personal experiences in moderating roles

    Personal experiences in moderating roles

    In my experience as a moderator, I’ve often found that establishing trust early on is crucial. I recall a workshop where tensions flared over differing educational philosophies. I made it a point to share my own vulnerabilities about my educational journey, which unexpectedly opened the floor for participants to express their insecurities and doubts. This moment of honesty changed the atmosphere entirely; I’ve learned that vulnerability can be a powerful catalyst for connection.

    One memorable instance that stands out to me involved handling a heated debate among educators about teaching methodologies. Rather than trying to impose order, I embraced the chaos by introducing an informal “lightning round” where everyone had one minute to voice their thoughts. The energy shifted as participants laughed and engaged in a more relaxed manner. Looking back, it reinforced the idea that sometimes, breaking the rules can create a more inclusive environment for discussion.

    I still think about a challenging session where I had to mediate a disagreement between two strong-willed speakers. Instead of letting them dominate the dialogue, I used a technique I call “reflective listening.” I reiterated their points back to them, which helped them to feel heard and allowed them to find commonalities in their stances. It amazed me how often simply feeling understood can pave the way for collaboration rather than competition. Have you ever tried something similar in your discussions?

    Lessons learned from challenging situations

    Lessons learned from challenging situations

    Navigating difficult situations has taught me that patience can truly be a virtue. I recall a particularly tense moment when two participants began raising their voices over a misunderstanding. Instead of immediately stepping in, I chose to pause and give them a moment to cool down. It turned out that allowing silence in the room gave everyone time to reflect on what was being said. This experience underscored how sometimes less intervention can lead to more productive outcomes.

    One challenging situation I faced involved a participant who consistently interrupted others. It was frustrating, but I learned that addressing disruptive behavior with empathy can be incredibly effective. I approached the individual after the session and expressed my observations, framing it as a concern for the group’s dynamics rather than a personal attack. To my surprise, they shared their anxiety about not being heard. This interaction taught me that understanding the root of someone’s behavior can foster a more collaborative environment.

    I also encountered a situation in which participants felt disillusioned with the event’s direction. Instead of dismissing their concerns, I decided to hold an open forum to discuss their thoughts. The conversations that emerged were raw and revealing, sparking transformative ideas for future sessions. It made me realize that embracing feedback, even in tough moments, can lead to innovation and stronger community ties. Have you found that addressing concerns head-on has led to unexpected results in your experiences?

  • How I navigate technological barriers in discussions

    Key takeaways:

    • Technological barriers in education, such as unreliable internet and unfamiliarity with digital tools, can hinder student participation and engagement.
    • Engaging discussions enhance critical thinking, allow for diverse viewpoints, and prepare students for real-world interactions.
    • Strategies to overcome technological barriers include assessing comfort levels, providing clear guides, and fostering open communication during discussions.
    • Facilitators should create an inclusive atmosphere and actively solicit feedback to enhance participant engagement and comfort.

    Understanding technological barriers in education

    Understanding technological barriers in education

    When I reflect on my experiences in educational settings, I often think about the subtle yet significant technological barriers that can emerge. For instance, I remember a time during a virtual conference when my video froze, leaving me feeling vulnerable and disconnected from the discussion. It made me wonder how many others face similar challenges, perhaps making them feel less confident in sharing their ideas.

    One major barrier I’ve noticed is the varying levels of access to technology among students. Some may struggle with outdated devices or unreliable internet connections, which can hinder their ability to participate fully in discussions. It’s heartbreaking to think of eager learners missing out on opportunities simply because they lack the necessary tools. Have you ever witnessed someone sitting quietly in a virtual meeting, their potential untapped, simply because they couldn’t keep up with technology?

    Moreover, the rapid pace of technological advancements can be overwhelming. I know I’ve felt a sense of anxiety when trying to catch up with new platforms or tools that seem to emerge overnight. This pressure can create a divide, making some feel alienated from the conversation. It’s crucial for educators to foster an inclusive environment where everyone feels empowered to engage, despite the barriers in place. What strategies have you found effective in overcoming these obstacles?

    Importance of discussions in education

    Importance of discussions in education

    Engaging in discussions is essential in education because it fosters critical thinking and collaboration among students. I recall a group project where our debate on a controversial topic ignited passionate exchanges of ideas, allowing us to view the issue from multiple perspectives. This vibrant interaction not only deepened our understanding but also built a sense of community among us, something that mere lectures could never achieve.

    Discussions also provide a platform for students to voice their thoughts and experiences, making learning more personal and relevant. I remember a shy classmate who came alive when discussing a topic he was passionate about; his insights added incredible depth to our learning. Have you ever noticed how sharing personal experiences can spark interest in others? It’s these moments that transform a classroom dynamic and enhance everyone’s engagement.

    Moreover, the importance of discussions lies in nurturing diverse viewpoints, which is essential for preparing students for real-world interactions. During a recent seminar, I was struck by how differing opinions on a subject led to constructive debates. Such exchanges teach us to navigate disagreements respectfully, a vital skill not just in school but in life. How often do we miss opportunities to grow simply because we shy away from discussing uncomfortable topics?

    Common technological barriers faced

    Common technological barriers faced

    Technological barriers often emerge as significant hindrances in discussions, particularly in an educational setting. I once participated in an online seminar where the audio failed midway, which left several participants bewildered and frustrated. Have you experienced that tension when technology doesn’t cooperate? It can derail a conversation completely, making it challenging to maintain the momentum of an engaging dialogue.

    Inadequate access to reliable internet can create disparities, especially if some participants struggle to join or stay connected. I vividly recall a group discussion where a few classmates dropped out due to weak connections. Their absence not only muted diverse perspectives but also created awkward silences, revealing how vital connectivity is to the exchange of ideas. Isn’t it disheartening when the very tools meant to facilitate conversation become barriers?

    Finally, unfamiliarity with the digital platforms used for discussions can create an additional layer of frustration. I’ve seen peers hesitate to engage because they were unsure how to use specific features like screen-sharing or chat functions. This discomfort often leads to valuable contributions being left unvoiced. How many insights do you think go unshared due to a lack of confidence in using technology? These barriers remind us of the importance of digital literacy in today’s educational landscape.

    Strategies for overcoming technological barriers

    Strategies for overcoming technological barriers

    To overcome technological barriers, acknowledging the potential challenges is crucial. I remember a workshop I attended where the facilitator began by assessing everyone’s comfort level with the technology. This simple step made a world of difference; it ensured that everyone felt included and could participate fully instead of struggling silently. Have you ever seen how such an inclusive approach can empower participants to engage more freely?

    Another effective strategy I’ve found is providing a clear guide before discussions. During an online class, the instructor shared a brief video tutorial on using the platform’s features. This proactive measure not only boosted our confidence but also minimized confusion during the session. Isn’t it fascinating how a little preparation can transform the entire interaction?

    Finally, fostering open communication during discussions is key. In one session, I noticed that we had a designated “tech support” person who encouraged participants to voice any issues in real-time. When someone reported a lag or disruption, the group adjusted their pace, allowing for a smoother conversation. Have you considered how this collaborative spirit can alleviate individual frustrations and enhance the overall experience?

    Personal experiences navigating barriers

    Personal experiences navigating barriers

    In my experience, navigating technological barriers often involves a dose of humility. I recall participating in a panel discussion where the internet connection was unreliable. At one point, I lost my connection entirely and my heart raced; I worried I would miss out on sharing valuable insights. But when I rejoined, the moderator reassured me that these hiccups were common. It reminded me how vulnerability in a tech-driven setting can foster understanding among participants.

    Another time, during a virtual conference, I faced issues with audio feedback. I had my microphone positioned incorrectly, creating an echo. It was frustrating, and I felt embarrassed when it disrupted the flow of conversation. However, one of my peers quickly made a light-hearted joke about the situation, and it broke the tension. In hindsight, it taught me the importance of adaptability and not taking myself too seriously in these tech-filled conversations. Have you ever been in a situation where a little humor helped diffuse the stress of technology?

    I also remember an online seminar where several attendees struggled to access shared resources. It felt like a collective challenge, with a few people trying to navigate the tech while others were left in the dark. This experience highlighted how essential it is for facilitators to not only focus on content but also ensure everyone can engage with necessary materials efficiently. Reflecting on that, I often wonder how we can better bridge the gap between technology and participation.

    Tips for facilitating discussions effectively

    Tips for facilitating discussions effectively

    When facilitating discussions, it’s crucial to foster an inclusive atmosphere. I remember leading a workshop where participants were hesitant to share their thoughts at first. To break the ice, I encouraged an informal round of introductions, sparking personal connections among attendees. This simple act transformed the energy in the room, demonstrating how personal interaction can create comfort and invite participation.

    Another effective approach is setting clear expectations about technology usage. During a recent online session, I noticed confusion around screen-sharing protocols. To address this, I walked everyone through the steps beforehand, which not only clarified the process but also alleviated anxiety. Have you ever stepped into a tech-heavy discussion without knowing the ground rules? It can feel overwhelming, but establishing those guidelines upfront helps everyone feel more at ease.

    Lastly, actively soliciting feedback during the discussion can enhance engagement. In one event, I paused to ask for input on a topic we were discussing, which sparked a lively debate. I found that people appreciated being asked for their perspective—it made them feel valued. It’s important to remember that creating space for dialogue isn’t just about sharing information; it’s about listening and learning from each other. How do you encourage others to join the conversation in your experiences?

  • How I navigate sensitive topics effectively

    Key takeaways:

    • Navigating sensitive topics requires emotional sensitivity, fostering respect and understanding to encourage open dialogue.
    • Effective communication involves active listening, establishing ground rules, and asking thought-provoking questions to create a safe space for sharing.
    • Building trust with the audience is achieved through vulnerability, consistent follow-through, and inviting feedback to enhance engagement.
    • Personal stories significantly enrich discussions, as they foster connection and empathy among participants, turning abstract topics into relatable experiences.

    Understanding sensitive topics

    Understanding sensitive topics

    Navigating sensitive topics requires a careful understanding of the emotional weight they carry. I remember a time in a workshop when a participant opened up about their personal loss. The room grew silent, filled with compassion and an unspoken understanding. It was a poignant reminder of how a single story can transform a conversation.

    Recognizing the context surrounding sensitive topics is essential. Have you ever paused to consider why certain issues evoke strong feelings? It’s often due to personal experiences or cultural backgrounds that shape our perspectives. This awareness helps foster a more respectful dialogue, giving people the space to share without fear of judgment.

    I’ve learned that asking open-ended questions can create a safe environment for discussion. For instance, instead of asking, “What do you think about this issue?” I might say, “How has this issue affected you personally?” This subtle shift encourages deeper sharing and promotes empathy, opening pathways to understanding not just the topic, but the individuals involved.

    Importance of effective navigation

    Importance of effective navigation

    Effective navigation through sensitive topics is vital because it sets the tone for open and honest communication. I recall leading a discussion where a participant hesitated to share due to previous experiences of being dismissed. By actively listening and acknowledging her feelings, I created a space that encouraged her to speak freely. This not only made her feel valued but also inspired others to share their stories, reinforcing the power of a supportive environment.

    When we navigate sensitive subjects with care, we foster trust among participants. Have you ever felt more connected to a group simply because everyone was respectful and attentive? I remember attending an educational event where the facilitator skillfully acknowledged our feelings about a challenging issue. This approach not only helped me feel safe but also deepened my engagement with the material, illustrating how the right navigation can significantly enhance the learning experience.

    Moreover, effective navigation isn’t just about the words we choose; it’s about the emotions we evoke. I often reflect on how a kind, understanding tone can diffuse tension. In one instance, during a particularly heated debate, a gentle reminder of our shared goals transformed an adversarial atmosphere into one of cooperation. This experience taught me that the emotional landscape of our discussions can shift dramatically with just a few thoughtful choices in how we communicate.

    Strategies for discussing sensitive topics

    Strategies for discussing sensitive topics

    When discussing sensitive topics, I find that establishing ground rules can set a constructive tone. In one workshop I attended, we agreed to pause whenever someone felt uncomfortable. That small agreement transformed moments of tension into opportunities for reflection, allowing us to approach issues with care. Isn’t it amazing how a simple guideline can empower open dialogue?

    Sharing personal stories can be a powerful strategy. I once shared my own experience with vulnerability during a discussion on mental health, and the silence that followed was palpable. However, it was this openness that encouraged others to step forward, revealing their own struggles. Isn’t it fascinating how relatability can create an instant bond among participants?

    Additionally, framing the conversation with questions can foster engagement and a sense of agency. I’ve learned that asking, “What are your thoughts on this?” can invite a range of perspectives, valuable for a more nuanced understanding of sensitive issues. Through this approach, I’ve witnessed participants unravel their complex feelings, making the discussion richer and more meaningful. Have you ever noticed how a simple question can open doors to deep conversations?

    Preparing for educational events

    Preparing for educational events

    When preparing for educational events, I think about the importance of setting intentions. For instance, before hosting a workshop on emotional intelligence, I took a moment to reflect on what I wanted participants to gain from the experience. This clarity helped shape the content and guided me in creating a welcoming environment. Have you ever noticed how a clear objective can streamline your planning and enhance the overall effectiveness of the event?

    Another crucial preparation step is understanding your audience. In one session I led on cultural sensitivity, I spent time learning about the participants’ backgrounds and concerns. This insight allowed me to tailor my message, making it relatable and relevant to their experiences. It’s interesting how a bit of research can transform the way you engage with a diverse group, isn’t it?

    Lastly, I always emphasize the value of versatile materials. On one occasion, I created handouts that included not just facts, but also reflections and prompts for discussions. This approach not only provided a resource but also encouraged participants to interact with the content on a deeper level. Don’t you think having well-rounded materials can significantly enhance the learning experience?

    Building trust with the audience

    Building trust with the audience

    Building trust with the audience is fundamental in educational settings. I remember an event where the topic was mental health, a sensitive area for many. By openly sharing my own struggles and how I navigated them, I created an atmosphere where participants felt comfortable sharing their own stories. Isn’t it powerful how vulnerability can break barriers and foster genuine connections?

    Another essential strategy is to consistently follow through on promises made during an event. During a workshop on diversity, I committed to providing participants with additional resources afterward. When I delivered on that promise, I noticed an immediate boost in trust. It’s intriguing to see how dependable actions can reinforce your words and deepen relationships, don’t you think?

    Finally, inviting feedback plays a crucial role in building trust. After a session on conflict resolution, I asked attendees to share their thoughts on the material presented and what areas might be improved. Their honest responses not only enhanced my future presentations but also showed them that their opinions mattered. Isn’t it remarkable how simply listening can create a sense of partnership between you and your audience?

    Facilitating open conversations

    Facilitating open conversations

    Facilitating open conversations requires creating a safe space where participants feel empowered to express their thoughts. I vividly recall a workshop focused on race relations, where I encouraged a participant to share their experience. The moment they spoke up, it sparked a chain reaction; others quickly followed, diving into their own stories. It was astonishing to watch how one brave voice catalyzed a deeper discussion among the group. How often do we miss out on these rich dialogues simply because we hesitate to invite them?

    An essential aspect of encouraging open dialogue is asking thought-provoking questions. During a session about trauma-informed teaching, I posed a simple yet powerful question: “What does safety look like for you in the classroom?” The varied responses were eye-opening. They illuminated the diverse experiences and needs of participants, which not only enriched our conversation but also highlighted the mutual respect we were building. Isn’t it fascinating how a single question can open so many doors to understanding?

    Listening actively is another key to facilitating open conversations. One time, I participated in a forum on personal finance, and I made it a point to repeat back what others said before adding my perspective. This practice not only validated their feelings but also encouraged more dialogue. When participants felt heard, they were more willing to share their vulnerabilities and insights. Have you noticed how genuine listening can transform a conversation into something more meaningful and collaborative?

    Reflecting on personal experiences

    Reflecting on personal experiences

    Reflecting on personal experiences can be a powerful way to connect with one another. I remember an event where we asked educators to share the challenges they faced while teaching inclusive curriculums. One teacher recounted her struggles with a lack of resources, and as she spoke, you could feel the weight of her frustration in the room. It made me realize how crucial it is to create not just a space for sharing but also one for genuine understanding and empathy.

    I often reflect on my own journey in these conversations. There was a time when I hesitated to open up about my own experiences with mental health in a workshop setting. The fear of judgment held me back, but once I mustered the courage to share, I was met with such warmth and support. It dawned on me then; vulnerability often acts as the bridge that brings us closer together. How might we foster that same courage in others?

    When I think about the importance of personal stories, I’m reminded of a panel discussion on + representation we hosted. One panelist shared his experience of being bullied and how it shaped his activism. Hearing his story moved everyone in the room. It was a poignant reminder that our individual experiences can resonate deeply and inspire change. Have you ever witnessed how personal narratives turn abstract concepts into tangible experiences that everyone can feel?

  • How I navigate risk-taking in dialogue

    Key takeaways:

    • Risk-taking in dialogue facilitates deeper understanding and connection, often leading to personal growth and profound learning experiences.
    • Types of risks include vulnerability, disagreement, and the risk of being misunderstood, all of which can enhance the quality of conversations.
    • Effective strategies for risk-taking involve preparation, establishing common ground, and embracing curiosity over judgment to foster open dialogue.
    • Creating a supportive environment through trust, inclusivity, and recognizing emotional cues is essential for meaningful discussions.

    Understanding risk-taking in dialogue

    Understanding risk-taking in dialogue

    Risk-taking in dialogue is all about stepping outside of comfort zones. I remember a moment during a workshop where I hesitated to share my unconventional idea. The fear of criticism loomed large, but as I took that plunge, I discovered not only my voice but also a surprising resonance from others. Have you ever held back an idea, wondering if it might be too bold?

    When we take risks in conversations, we open up pathways to deeper understanding and connection. I once engaged in a discussion on a controversial topic, and while it felt precarious at first, the ensuing dialogue led to rich exchanges of perspectives. In those moments, I’ve realized that vulnerability can transform dialogues into profound learning experiences. How can we encourage ourselves to embrace this openness?

    Ultimately, risk-taking in dialogue encourages growth, not just for ourselves, but for everyone involved. I often reflect on how those uncomfortable moments have shaped my approach to discussions. Wouldn’t it be amazing if we could all embrace a little more risk in our conversations to foster genuine connections and insights?

    Types of risks in dialogues

    Types of risks in dialogues

    When considering the types of risks in dialogues, one major concern is the risk of vulnerability. I recall a group discussion where I shared a personal story that highlighted my struggles. The moment felt raw and exposed, but it sparked a wave of authentic sharing among my peers. Isn’t it fascinating how a single act of honesty can inspire others to drop their façades and connect on a deeper level?

    Another type of risk involves the risk of disagreement. I remember a time when I voiced my differing opinion on a project direction during a meeting. The initial tension was palpable, and my heart raced. However, this discomfort eventually led to a more thorough examination of ideas, ultimately enhancing the outcome. Hasn’t there been a point when you’ve stepped into disagreement only to find it enriches the conversation?

    Lastly, there’s the risk of being misunderstood. I once articulated a complex concept during a seminar, only to realize my message was lost on a few attendees. The realization that my words may not have communicated my intent spurred me to clarify and reframe my ideas. How important is it, then, to ensure our dialogue is not just about speaking but also about being comprehended?

    Strategies for effective risk-taking

    Strategies for effective risk-taking

    When it comes to effective risk-taking, one strategy I often employ is preparation. Before engaging in a potentially risky dialogue, I take time to reflect on my objectives and anticipate possible outcomes. I remember a workshop where I prepared controversial viewpoints ahead of time, which allowed me to navigate the conversation with confidence. Doesn’t preparation give you that boost you need to step beyond your comfort zone?

    Another approach I find valuable is to establish common ground early in discussions. By identifying shared values or goals, I create a safe space for dialogue that encourages openness. During a team brainstorming session, I suggested we start by discussing our collective vision, and this simple tactic diffused tension and invited everyone to share their thoughts freely. Isn’t it remarkable how a small shift in focus can transform the dynamics of a conversation?

    Finally, embracing curiosity over judgment is a crucial element in my risk-taking strategy. When I enter discussions with an inquisitive mindset, it helps me listen deeply rather than react defensively. I once found myself in a heated debate that turned constructive as I asked open-ended questions. This not only eased the tension, but also led to richer insights. How often do we let our curiosity guide us, unlocking new perspectives in the process?

    Personal experiences with risk-taking

    Personal experiences with risk-taking

    Risk-taking in dialogue has shaped many of my personal interactions. I vividly recall a time when I hesitated to share an unconventional idea in a meeting, fearing judgment from colleagues. However, I decided to voice my thoughts, which sparked a lively discussion that unveiled unforeseen opportunities. Isn’t it interesting how taking that leap can lead to unexpected revelations and collaboration?

    Another experience that stands out was during a community event where I led discussions on sensitive topics. I approached these dialogues with a blend of vulnerability and authenticity, sharing my own uncertainties. The response was overwhelmingly positive; people appreciated the honesty and reciprocated with their own stories. Don’t you think that vulnerability can be a powerful catalyst for connection?

    I also remember a moment when I chose to challenge an established viewpoint during a panel discussion. My heart raced as I presented my argument, knowing I might provoke dissent. Yet, the ensuing conversation opened the floor to varying perspectives and transformed what could have been a tense encounter into a rich dialogue. How often do we underestimate our ability to shift the course of a conversation just by speaking our truth?

    Lessons learned from risky dialogues

    Lessons learned from risky dialogues

    Risky dialogues often teach me the importance of active listening. I once found myself in a debate about educational reform, where emotions were running high. Instead of retaliating with my stance, I took a step back and genuinely listened to differing opinions. This not only fostered a more respectful environment but also allowed me to understand the nuances of the other perspectives. Isn’t it fascinating how listening can sometimes be more powerful than merely speaking?

    Another lesson I’ve gleaned is the necessity of clear communication. During a workshop, I attempted to introduce a new teaching method that was met with skepticism. I realized my explanation lacked clarity, leading to confusion and resistance. By simplifying my message and illustrating it with relatable examples, I turned the tide of the conversation. How often do we stumble because our ideas are not communicated effectively?

    Lastly, I’ve come to appreciate that vulnerability can be a bridge, rather than a barrier. While presenting at a conference, I openly shared my fears about not meeting expectations. Surprisingly, this openness led to an authentic dialogue with the audience, where many revealed their own struggles. Doesn’t it show that sometimes showing our own cracks can create a stronger foundation for connection?

    Building a supportive dialogue environment

    Building a supportive dialogue environment

    Creating a supportive dialogue environment often starts with establishing trust among participants. I remember attending a roundtable discussion where the organizer set the tone by sharing a personal story of failure. This vulnerability not only broke the ice but also encouraged others to follow suit. Isn’t it interesting how sharing our imperfections can pave the way for openness in conversation?

    Furthermore, it’s essential to emphasize the importance of inclusivity during discussions. In one of my seminars, I actively invited quieter voices to share their thoughts. By doing so, I witnessed a remarkable shift in the group dynamic—those who initially hesitated began to contribute valuable insights. How often do we overlook the wisdom present in every participant’s perspective?

    Equally important is the recognition of emotional cues in dialogue. During a team meeting, I noticed a colleague growing visibly frustrated while discussing project feedback. Instead of pushing through the agenda, I took a moment to address his feelings, allowing space for a meaningful conversation. Doesn’t it remind us that acknowledging emotions can transform a simple exchange into a memorable connection?

  • How I navigate personal biases in discussions

    Key takeaways:

    • Personal biases can cloud judgment and hinder open-mindedness; self-reflection is key to recognizing them.
    • Discussing biases fosters inclusivity, leading to innovative ideas and equitable decision-making in group settings.
    • Engaging actively and empathetically with others through techniques like role reversal and mindfulness improves understanding and communication.
    • Evaluating discussion outcomes, including emotional cues and participant feedback, enhances future interactions and ensures inclusivity.

    Understanding personal biases

    Understanding personal biases

    Personal biases are like invisible glasses that shape the way we perceive the world around us. I’ve often found myself in discussions where my own experiences and beliefs cloud my judgement. It makes me wonder—how many times have I missed valuable insights because I was too focused on defending my viewpoint?

    Understanding these biases requires self-reflection. I recall a moment during a group project where I dismissed an idea simply because it came from someone I didn’t agree with on other topics. Looking back, I realize how restricting that was—not just for me, but for the entire team. Was I truly listening to the merit of the argument, or was I subconsciously filtering it through my biases?

    Sometimes, it helps to acknowledge the emotions tied to these biases. I remember feeling defensive during a debate about educational methods, realizing that my passion was stemming from my own educational experiences rather than the discussion at hand. This discovery pushed me to ask myself: am I fighting for my truth, or am I open to understanding others? It’s a powerful shift when we start prioritizing understanding over being understood.

    Importance of discussing biases

    Importance of discussing biases

    Discussing biases is crucial because it fosters a culture of openness and understanding. I recall a heated debate I had about technology in education, where taking a step back to recognize my bias helped me see the merits in opposing views. It’s a reminder that when we share our biases, we create opportunities for deeper conversations and growth.

    Moreover, discussing biases can lead to more equitable decision-making. In a workshop setting, I saw how revealing personal biases shifted the dynamics and encouraged a more inclusive environment. When participants felt safe to express their thoughts, it sparked innovative ideas that we might have otherwise overlooked.

    Engaging in conversations about biases also allows us to challenge our comfort zones. I often ponder whether I would grow as a person if I only gravitate towards familiar perspectives. Embracing discomfort might be the key to unlocking transformative experiences that enhance both our understanding and relationships.

    Strategies for recognizing biases

    Strategies for recognizing biases

    Recognizing our biases starts with self-reflection. For instance, during a recent group discussion about educational policy, I noticed I was leaning heavily towards my own beliefs without really questioning them. Was I truly open to other viewpoints, or was I just defending my stance? This pause allowed me to explore my motivations and acknowledge where my biases might be influencing my perspective.

    Another effective strategy is seeking feedback from others. I remember a time when a colleague pointed out how my background affected my opinions in a discussion about curriculum changes. Initially, it stung a bit, but I realized this insight was invaluable. Hearing differing opinions helps broaden our understanding and highlights biases we might not notice on our own. How often do we ask others to challenge us?

    Journaling can also be a powerful tool for uncovering biases. When I journal about my thoughts following a contentious discussion, I often find patterns that reveal my preconceived notions. It’s like holding a mirror up to my beliefs. This practice not only helps clarify my thoughts but can also lead to deeper insights about why I hold certain biases. Have you ever tried reflecting in writing to uncover your own biases?

    Techniques to manage biases

    Techniques to manage biases

    When it comes to managing biases, one effective technique is to actively listen during discussions. I recall a moment of clarity when I made a conscious effort to listen, truly listen, to a colleague’s perspective on student engagement strategies. At first, I felt defensive, but the more I listened, the more I realized I was missing a valuable viewpoint. Have you ever truly absorbed someone’s argument, only to discover it reshapes your understanding?

    Another valuable approach is to engage in role reversal. I once participated in a workshop where we debated a hot-button issue from opposing viewpoints. It was uncomfortable to argue against my beliefs, but I found that it deepened my empathy towards others’ positions. How often do we step into another’s shoes to see the world through their eyes? This technique not only highlights our biases but enriches our discussions.

    Finally, practicing mindfulness can significantly mitigate biases in conversations. After I began incorporating short mindfulness exercises before group discussions, I noticed a marked difference in how I engaged with others. I became more aware of my immediate reactions and could pause to respond thoughtfully rather than react impulsively. Have you tried taking a moment to breathe and reset before jumping into a debate? It’s astonishing how a little mindfulness can transform our interactions.

    Personal experiences with biases

    Personal experiences with biases

    I vividly remember a time during a discussion on curriculum changes when my own biases came into stark focus. Someone pointed out how a particular approach could unintentionally alienate students from different backgrounds. At first, I bristled; after all, I had my vision for the curriculum. Yet, that moment prompted me to examine my biases surrounding what “success” in education looked like. Have you ever felt a flicker of defensiveness when challenged on your assumptions, only to realize later that the criticism contained valuable truth?

    In another instance, a colleague and I were brainstorming ways to increase parent engagement. My immediate inclination was to propose digital solutions, due to my own comfort with technology. However, as we delved deeper, I realized my bias toward digital methods was overshadowing the needs of families who might prefer face-to-face interactions. Reflecting on this experience, I wondered—how often do our personal preferences eclipse the diverse needs of those we aim to support?

    I’ve also faced biases in group settings where I noticed myself unconsciously favoring familiar voices over newcomers’. During one meeting, a new team member shared a novel idea that sparked excitement in the room. Initially, I struggled to embrace what felt foreign, but allowing myself to be open to this fresh perspective lifted the entire discussion. It made me question—what hidden gems are we dismissing by holding onto our established comfort zones?

    Engaging others in discussions

    Engaging others in discussions

    Engaging others in discussions can sometimes feel daunting, especially when differing opinions emerge. I recall a workshop where we were encouraged to share thoughts without interruption. It was a refreshing change; I found that when everyone was given space to speak, insightful ideas surfaced that had previously gone unnoticed. Have you ever noticed how productive a conversation can become when everyone feels valued?

    In another session, I experimented with using open-ended questions to draw out quieter participants. One participant, who had been silent, suddenly offered a profound observation that reshaped our entire dialogue. It struck me then how powerful it is to invite others in; it reminds me that diverse input can lead to richer, more nuanced understandings. Isn’t it fascinating how a simple question can unlock so much potential for meaningful connection?

    I often reflect on how the tone of a discussion influences engagement. Once, during a community event, I decided to share a vulnerability related to my own biases. The atmosphere shifted, and others began to share their experiences and concerns as well. This openness not only humanized the conversation but also created a safe space for honest dialogue. When have you witnessed vulnerability transform a discussion into something deeper and more impactful?

    Evaluating outcomes of discussions

    Evaluating outcomes of discussions

    Evaluating the outcomes of discussions can reveal how effectively we communicated and connected with others. I remember attending a panel discussion where we analyzed what worked and what didn’t after the event. It surprised me to see how attendees’ feedback provided insights that we might have overlooked in the moment. Have you ever considered how personal reflections can enhance the overall understanding of a discussion’s success?

    Sometimes, I focus on analyzing the emotional tone of the conversation afterward. In one meeting, I noted that although we reached a consensus, several participants looked visibly uncomfortable. This prompted me to wonder: did we truly address everyone’s concerns, or were some voices drowned out? Evaluating these emotional cues can help ensure future discussions are more inclusive and empathetic, fostering a culture of openness.

    The method of follow-up is equally important. After a brainstorming session, I often send out a brief survey asking participants how they felt about the outcomes. One time, I received responses that highlighted ideas I hadn’t anticipated but could shape future projects significantly. It made me realize that discussion outcomes are not just about immediate results; they extend into ongoing conversations and future collaborations. How might your approach change if you prioritize this kind of reflective evaluation?

  • How I navigate personal narratives in public settings

    Key takeaways:

    • Personal narratives shape identities and foster connections, allowing individuals to find common ground through shared experiences.
    • Vulnerability in storytelling transforms discomfort into deep human connections, empowering self-discovery and encouraging others to share.
    • Techniques such as knowing the audience, engaging senses, and using pauses enhance storytelling effectiveness and audience engagement.

    Understanding personal narratives

    Understanding personal narratives

    Personal narratives are powerful stories that shape our identities and influence how we connect with others. They offer a window into our experiences, revealing not just what we’ve gone through but how those moments have formed our beliefs and values. For instance, I remember sharing a challenging moment from my childhood at a community event, and the warmth and empathy that flowed from the audience made me realize the universal threads that connect us all.

    As I reflect on my own journey, I see how these narratives can evoke strong emotions—joy, sadness, anger, and vulnerability. Each story we tell carries a unique weight; it’s almost like we’re inviting others into our personal world. Have you ever felt hesitant to share your own experiences? I have, yet I found that when I took the leap, others related in ways I never expected, creating a shared sense of understanding.

    Understanding personal narratives not only helps in self-reflection but also fosters deeper connections with others. When I openly discuss my experiences, I often find common ground with strangers who become friends. What’s your story? As we navigate these personal tales, we can appreciate that they aren’t just about us—they’re also a bridge to reinforce our collective humanity.

    Importance of personal narratives

    Importance of personal narratives

    Sharing personal narratives is crucial because they create a sense of authenticity. I recall a time at a workshop when someone shared their struggle with imposter syndrome. The vulnerability in their story resonated with many of us, sparking a discussion that brought everyone closer together. Have you ever been surprised by how your own story can break down barriers?

    Moreover, these narratives serve as a roadmap for others. When I recount the lessons from my failures, I often see eyes widen in understanding. Isn’t it validating to know that our experiences can offer guidance to someone else? By sharing our journeys, we provide support and encouragement, reminding each other that we’re not alone in our struggles.

    Importantly, personal narratives also empower self-discovery. The process of articulating my own story often uncovers insights I didn’t realize were buried deep within me. When was the last time you reflected on a pivotal moment? I find that revisiting these memories can lead to profound revelations about who I am and where I’m headed, enriching my connections with others even more.

    Navigating narratives in public

    Navigating narratives in public

    Navigating narratives in public can be both exhilarating and daunting. I remember attending a community event where the topic was mental health. As speakers shared their experiences, I felt an overwhelming mix of gratitude and fear. Would my story resonate too? I realized that stepping into the spotlight was less about me and more about the shared human experience.

    Engaging with personal stories in public settings requires a blend of courage and compassion. I often find that listening intently to others can open doors to my own vulnerabilities. During a recent panel discussion, I was moved by a participant’s emotional recounting of grief. It reminded me of my own loss and how powerful it can be to express those feelings in a supportive environment. Isn’t it amazing how one story can evoke our own memories and create a sense of community?

    When I reflect on navigating these narratives, I think about the importance of pacing. In a previous workshop, I took a moment to pause after sharing a particularly painful chapter of my life. The silence that followed felt heavy yet healing. It made me wonder—how often do we rush through our stories? Taking the time to breathe allows others to digest and connect with our experiences on a deeper level.

    Engaging audiences with stories

    Engaging audiences with stories

    Engaging audiences with stories is about weaving together emotions and experiences that resonate with others. I recall presenting at a local workshop where I shared my journey of overcoming anxiety. As I spoke, I could see faces lighting up with recognition; it struck me that my struggles mirrored those of many in the room. Have you ever noticed how a heartfelt story can spark a collective sigh of relief, as if we’re all exhaling the weight we’ve held for too long?

    What I’ve learned is that storytelling isn’t just about sharing; it’s about connecting. During a recent outreach program, I invited participants to share their own stories along with mine. I could feel the tension drop as we all found common ground. Stories are like bridges, allowing us to cross over into one another’s worlds and discover that we’re not as alone as we sometimes think. Isn’t it incredible how vulnerability can create a safe space for dialogue?

    In my experience, the key to an engaging story lies in its relatability. I once watched a speaker recount a seemingly mundane moment turning into a life lesson. As they painted the picture, I felt transported back to my own similar incidents. That’s when I realized the magic of storytelling: it doesn’t always have to be dramatic or shocking to leave an impact. Do you remember a time when a simple tale shifted your perspective? Sometimes, the everyday experiences hold the most profound insights.

    Overcoming challenges in sharing

    Overcoming challenges in sharing

    Sharing personal narratives can sometimes feel daunting, especially when fear of judgment looms large. I recall standing before a group, my heart racing as I prepared to reveal a part of myself I usually kept hidden. In those moments, I learned that vulnerability often transforms discomfort into a deep human connection, reminding us that our experiences, however personal, can resonate with others. Have you ever felt that moment of clarity when you realize that your struggles mirror those of someone else?

    Navigating the fear of sharing is a journey of self-discovery. I remember a time when my story of failure became a turning point for me. Instead of shying away from it, I embraced the lessons learned, which turned that fear into empowerment. This shift in perspective not only lightened my burden but also inspired others to share their own setbacks, illuminating the power of transformation in our narratives. Isn’t it fascinating how acknowledging our imperfections can pave the way for genuine connections?

    However, challenges can arise even after you muster the courage to share. There have been instances where I faced resistance or discomfort from the audience, creating an awkward silence that felt almost hollow. In those moments, I took a breath and re-framed my experience, seeking common ground that allowed for a more open dialogue. Every challenge teaches us; I’ve discovered that staying adaptable and receptive during sharing can lead to more significant insights and communal growth. How do you adapt your narrative when the atmosphere shifts unexpectedly?

    Techniques for effective storytelling

    Techniques for effective storytelling

    Effective storytelling begins with knowing your audience. I’ve walked into various speaking engagements, and each time, I take a moment to assess the room—who’s there, what are their expressions, and what might they relate to? Crafting your narrative to align with your audience’s interests not only captures their attention but also fosters a sense of connection. Have you ever noticed how a well-timed joke or a relevant reference can shift the mood of an entire room?

    Another technique is to engage the senses through vivid descriptions. I recall a workshop where I shared a memory from my childhood that involved the aromas of freshly baked cookies wafting through the air and the warmth of the sun peeking through the kitchen window. Those sensory details allowed listeners to visualize and even feel a part of my experience. Isn’t it remarkable how powerful imagery can make a story resonate more deeply?

    Using pauses effectively is another aspect I’ve come to appreciate. There were times when I would rush through my narrative, eager to share every detail, but I found that taking a moment to pause after a key point could amplify its impact. This intentional pacing not only allows the audience to digest the information but also creates a space for reflection. Have you tried incorporating pauses into your storytelling? You might discover that silence speaks volumes.

    Reflecting on personal experiences

    Reflecting on personal experiences

    Reflecting on personal experiences often reveals layers of understanding that I hadn’t recognized before. I remember sharing a challenging moment from my academic journey during a community event. As I spoke about the frustrations of failed attempts and subsequent perseverance, I noticed nods of empathy from the audience. It was a reminder that vulnerability can foster connection, allowing others to see parts of themselves in my story.

    When I think back to moments that shaped my perspective, I’m struck by how they often surface unexpectedly. One time, while discussing a project I was passionate about, I realized how much I had grown from the setbacks I faced. In that moment, I asked myself and the audience: what lessons have our own struggles taught us? This simple question turned a personal narrative into a collective reflection, encouraging others to share their journeys too.

    I’ve learned that reflecting on personal experiences isn’t just about recounting events; it’s about distilling their significance. At one event, I described the fear I felt before a major presentation, only to find the audience resonating with that anxiety. How often do we overlook the power of our stories to inspire courage in others? By revealing my truth, I created an environment where shared fears could transform into collective strength.