= 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

  • My commitment to accessibility in dialogue

    Key takeaways:

    • Accessibility in education requires providing materials in various formats and using adaptive technologies to support diverse learning needs.
    • Inclusive dialogue fosters trust and engagement, allowing voices from different backgrounds to contribute meaningfully.
    • Accessible events must include physical accessibility, diverse formats for materials, and proactive training for staff on accessibility practices.
    • Sharing success stories in accessibility highlights the positive impact of inclusive practices and motivates others to innovate and improve accessibility efforts.

    Understanding accessibility in education

    Understanding accessibility in education

    Accessibility in education is about creating an inclusive environment where every student can thrive, regardless of their individual needs. I remember when I volunteered at a local school; I saw firsthand how crucial it was to ensure that all materials were available in various formats. It made me think: if one student struggles to understand content because it’s not in a suitable format, aren’t we failing them?

    Consider the various barriers that can hinder learning—physical, technological, or pedagogical. I once participated in a workshop that highlighted the importance of adaptive technologies, like screen readers or Braille displays. These tools transformed how students engaged with material, which reinforced my belief that accessibility isn’t just an add-on; it’s essential for meaningful education.

    When we talk about accessibility, we must also reflect on our teaching methods. Do we provide enough support for students with disabilities? In my experience, fostering a dialogue about diverse learning styles opens up much deeper understanding. The goal is to empower all learners, ensuring they feel valued and capable in their educational journey.

    Importance of accessibility in dialogue

    Importance of accessibility in dialogue

    Accessibility in dialogue is vital for fostering genuine understanding and engagement. I recall a time when I was part of a panel discussion that sought to include voices from different backgrounds. It struck me how quickly the conversation flowed when we made a conscious effort to ensure everyone felt comfortable expressing themselves. Without that accessibility, important perspectives might have been lost, leaving us with a conversation that lacked depth.

    Ensuring that dialogue is accessible can also mean adapting our language and approach to suit diverse audiences. During a community event, I once used jargon-heavy terms that left some attendees puzzled. Realizing this, I made it a point to simplify my language. This small change not only clarified my message but also created an atmosphere where everyone could contribute, regardless of their background.

    Lastly, think about the emotional impact of inclusive dialogue. When participants feel heard and understood, it fosters trust and connection. I’ve seen how powerful it is when someone who usually hesitates to speak up shares their thoughts because they feel safe in the conversation. Isn’t it incredible how accessibility can transform dialogue from a one-sided exchange into a rich tapestry of ideas and experiences?

    Key features of accessible events

    Key features of accessible events

    Accessible events are all about creating environments where everyone can participate fully. For instance, I once attended a workshop designed for individuals with hearing impairments. The organizers provided real-time captioning, which made a world of difference. It allowed participants to engage with the content without missing a beat, reinforcing how simple adjustments can enhance everyone’s experience.

    Another essential feature is physical accessibility. I remember attending a conference where the venue had thoughtfully included ramps and accessible restrooms. This consideration made it easy for all attendees, including those with mobility challenges, to move around freely. However, it made me wonder—how often do we overlook these basics in planning events?

    Lastly, offering materials in multiple formats is crucial for inclusivity. At one educational seminar, I noticed that handouts were available both in print and as downloadable PDFs. This flexibility allowed individuals to choose what best suited their needs. It reminded me that when we prioritize access in our planning, we not only enrich the event but also cultivate a sense of belonging among all participants.

    Strategies for implementing accessibility

    Strategies for implementing accessibility

    When it comes to implementing accessibility, it’s vital to involve individuals with disabilities in the planning stages. During one event I helped organize, we invited a few participants with different accessibility needs to share their perspectives. Their feedback was eye-opening; it reminded me that the best solutions often come directly from those who experience the barriers.

    Using technology is another strategic approach to enhance accessibility. I once joined an online seminar where speakers were equipped with microphones, and their voices were transcribed in real-time on a chat feature. This made the event accessible to participants not just with hearing impairments but also those who might struggle with concentration. Wouldn’t it be great if all events embraced such tech-savvy conveniences?

    Training staff members on accessibility practices can significantly impact an event’s success. At one conference, I noticed the staff were well-informed about the accommodations available, from sign language interpreters to sensory-friendly spaces. This proactive approach not only eased concerns for attendees but fostered an atmosphere of support and care. I often ask myself: how can we ensure all event staff are similarly equipped to prioritize accessibility?

    My personal commitment to accessibility

    My personal commitment to accessibility

    I’ve always felt a deep sense of responsibility when it comes to accessibility. Last year, while volunteering at a local community event, I witnessed firsthand how small adjustments can create meaningful experiences. When a visually impaired attendee expressed frustration with the layout, I was reminded that what may seem like a minor detail to some can be a significant obstacle for others.

    My commitment to accessibility extends beyond mere compliance; it’s about fostering genuine inclusion. During one workshop, I turned to a participant who was deaf and asked about their experience. Their smile as we discussed the benefits of providing information in multiple formats inspired me. It made me see accessibility as not just a requirement but as the very essence of creating welcoming spaces.

    When I think about future events, I can’t help but wonder: are we doing enough to empower all voices? I want to create an environment where everyone feels heard and valued. Accessibility isn’t just an afterthought; it should be woven into the fabric of every dialogue we have.

    Sharing success stories in accessibility

    Sharing success stories in accessibility

    Sharing success stories in accessibility can be incredibly impactful. Last summer, I attended a symposium where a team shared their journey of making an annual festival accessible for everyone. They implemented tactile maps and sign language interpreters, transforming the event from exclusionary to inclusive. Hearing feedback from participants who felt truly welcome warmed my heart and reaffirmed that our efforts can create significant change.

    One moment that stands out to me was when a family shared how their child, who uses a wheelchair, could finally enjoy activities without barriers. Their genuine gratitude made it clear that these adjustments weren’t just logistical; they were life-changing. I often find myself reflecting on how many professionals might not see the immediate effects of their innovations, yet these stories remind us that real connections are forged in spaces where all are welcome.

    I believe that sharing these success stories not only celebrates progress but also inspires others to act. What obstacles have you come across in your journey toward accessibility? It’s essential to recognize the impact of sharing our experiences, as it can motivate others to contribute and innovate, further enriching our communities.

    Future goals for accessible dialogue

    Future goals for accessible dialogue

    Future goals for accessible dialogue include fostering environments where all voices are heard and valued. I recently participated in a workshop where we brainstormed ways to include diverse communication styles, such as visual storytelling and audio descriptions. It was enlightening to see how these methods can help bridge gaps and enhance understanding, making dialogue not just accessible, but more enriching for everyone involved.

    As I reflect on my own experiences, I realize that incorporating technology can play a crucial role in our future goals. Imagine a platform where real-time translation and speech-to-text options are just the norm. Wouldn’t that open doors for so many? I can already picture lively discussions where nuances aren’t lost in translation, allowing for deeper connections.

    Additionally, I think about the importance of continuous education on accessibility practices. In my journey, I’ve learned that knowledge-sharing among professionals can spark innovative ideas. What if we dedicated time at every educational event to workshops on accessibility? This would not only elevate our collective understanding but also empower everyone to contribute to creating a more inclusive dialogue.

  • My challenges in cross-disciplinary discussions

    Key takeaways:

    • Cross-disciplinary discussions enrich ideas and innovation but can be hindered by jargon and communication gaps.
    • Educational events foster community and collaboration by connecting diverse backgrounds and teaching methods.
    • Establishing a common language, encouraging questions, and nurturing trust are key strategies for effective communication.
    • Personal experiences and inclusivity enhance understanding and promote constructive dialogue in discussions.

    Understanding cross-disciplinary discussions

    Understanding cross-disciplinary discussions

    Cross-disciplinary discussions bring together diverse perspectives, creating a tapestry of ideas that can lead to innovative solutions. I remember sitting in a seminar where an engineer and a historian debated how technology shapes societal narratives. It struck me how often we overlook the value of blending fields; what insights might we gain if we embraced these dialogues more widely?

    Navigating these discussions can be challenging. Sometimes, I find myself grappling with jargon from fields outside my expertise. Have you ever felt lost in a conversation full of unfamiliar terms? I’ve realized that asking questions not only clarifies but also fosters a sense of collaboration, allowing us to learn from one another.

    It’s fascinating how cross-disciplinary exchanges can spark creativity. I once collaborated with a visual artist during a project, and together we explored how art can communicate complex scientific concepts. Engaging with different disciplines challenged my thinking and opened up new avenues for understanding. Isn’t it exciting to consider what might happen when we step outside our comfort zones to embrace these enriching conversations?

    Importance of educational events

    Importance of educational events

    Educational events play a pivotal role in fostering an open-minded approach to learning. I once attended a conference where experts in education shared their diverse strategies for engaging students. Witnessing their passion and varying methodologies made me realize that these gatherings serve as a powerful catalyst for inspiration and growth, pushing us beyond our traditional boundaries.

    Connecting with others at educational events goes beyond mere knowledge transfer. I vividly remember a workshop focused on problem-based learning; participants shared challenges in their own contexts. By exchanging stories and solutions, we didn’t just learn from the speakers. Instead, we created a supportive community that enriched our experiences. Isn’t it remarkable how shared spaces can amplify our understanding?

    Moreover, the importance of educational events lies in their ability to ignite collaboration. During one particular session, I teamed up with individuals from unconventional backgrounds to brainstorm ideas for a local outreach program. The synergy in that room was palpable. It made me think—how often do we tap into these collaborative opportunities to enhance our educational journeys and broaden our horizons?

    Common challenges in discussions

    Common challenges in discussions

    Engaging in cross-disciplinary discussions can often feel like navigating a maze with no clear path. For instance, I once participated in a seminar where experts from technology and humanities came together. Despite the wealth of knowledge, I noticed a communication gap; technical jargon left some participants puzzled. Have you ever found yourself in a similar situation, where you’re not quite sure what’s being discussed? It’s frustrating, but it highlights the need for clarity and common ground in such diverse groups.

    Another challenge we face during discussions is the tendency to get stuck in our silos. I recall a panel where educators from various fields shared their insights, but despite their expertise, they struggled to find common themes. As each person focused solely on their discipline, the conversation drifted and lacked cohesion. This experience made me wonder—how can we foster an environment where diverse voices not only coexist but also amplify each other’s ideas?

    Emotional barriers often play a significant role in discussions as well. During a workshop focused on interdisciplinary collaboration, I witnessed participants hesitate to fully share their perspectives due to fear of judgment. This hesitation can stifle innovation and creativity, as valuable ideas remain unspoken. How can we create a safe space for vulnerable conversations that encourage everyone to contribute openly? It’s a challenge that calls for intentionality in our approach to group dynamics.

    Strategies for effective communication

    Strategies for effective communication

    Establishing a common language is one of the most vital strategies for effective communication across disciplines. I remember attending a workshop where scientists and artists collaborated on a project. Initially, their conversation was filled with confusion, as they used terminology that simply didn’t resonate with one another. By spending a few minutes figuring out definitions and agreeing on terms, they transformed that initial ambiguity into a fruitful dialogue. Have you ever witnessed how simply clarifying terms can change the course of a discussion?

    Active listening cannot be overlooked in cross-disciplinary conversations. I’ve found that when I consciously focus on not just hearing but understanding others’ perspectives, it cultivates a sense of trust and respect. Once, during a brainstorming session, I practiced this by paraphrasing what others said before sharing my thoughts. That small effort made people feel heard, which encouraged more openness in sharing their ideas. Have you noticed how attentiveness can sometimes invite deeper engagement in discussions?

    In my experience, encouraging questions and curiosity plays a pivotal role in facilitating productive dialogue. During a recent collaboration between educators and tech developers, I noticed that participants were more eager to engage when they felt it was acceptable to ask “why” or “how” instead of just agreeing. This open-spirited approach welcomed a creative flow of ideas and even led to unexpected solutions! What if we embraced questioning as a core component of our discussions, rather than seeing it as a challenge to authority?

    Building a collaborative environment

    Building a collaborative environment

    Creating a collaborative environment begins with fostering trust among participants. I’ve been in situations where team members hesitated to share their thoughts for fear of judgment. By initiating team-building activities that encourage vulnerability, I witnessed how laughter and shared experiences broke down barriers. I often wonder, what if we invested as much effort in building bonds as we do in crafting the agenda?

    Nurturing inclusivity is another essential piece of the puzzle. I recall a project where diverse perspectives — from experienced professionals to fresh graduates — were invited to contribute. The resulting discussions were dynamic, and it was inspiring to see how different backgrounds enriched our approach. Have you experienced the transformative power of inclusivity in team settings?

    Finally, I believe that celebrating small wins can significantly boost morale. I once helped manage a cross-disciplinary initiative where we recognized contributions during each phase of the project. This practice not only motivated the team but also reinforced a sense of shared ownership. Isn’t it intriguing how a simple acknowledgment can elevate engagement and commitment?

    Personal experiences in discussions

    Personal experiences in discussions

    In my experience, discussions across disciplines often reveal a fascinating array of viewpoints. I once participated in a brainstorming session that included engineers, educators, and psychologists. The conversation quickly became a tapestry of ideas, showcasing how each discipline approached problem-solving differently. I found myself captivated by the engineers’ analytical precision and the psychologists’ human-centric insights, reminding me that collaboration can lead to truly innovative solutions.

    Once, during a heated debate about educational methodologies, I felt a mix of excitement and anxiety. Some colleagues were passionate about traditional methods, while others advocated for modern technology-based approaches. I shared a personal story about a student who thrived in a hands-on, tech-enabled learning environment. To my surprise, my anecdote softened the atmosphere, opening the floor for a more constructive dialogue. It made me realize how personal experiences can serve as bridges, fostering understanding in tense discussions.

    Reflecting on another occasion, I noticed that navigating cultural differences in discussions added a layer of complexity. During an international conference, I felt honored to share insights with participants from various backgrounds. There were moments when language barriers created confusion, and yet, I found joy in the camaraderie that emerged as we worked through misunderstandings together. Have you ever experienced that exhilarating moment when a shared laugh transcends those barriers? It’s a reminder that empathy can be a powerful tool in any discussion.

    Lessons learned for future events

    Lessons learned for future events

    When planning future events, I’ve learned the importance of establishing a common language among participants early on. In one session, I witnessed a scholar and a corporate consultant struggle to convey their ideas due to differing terminologies. I had to step in and clarify. This experience taught me that investing time in setting shared definitions enhances communication and prevents frustration, ultimately enriching the discussion.

    I also realized that creating a relaxed environment is crucial for open dialogue. At a recent workshop, I noticed how informal icebreakers helped participants share their unique perspectives without hesitation. I remember one participant sharing a personal failure that taught them invaluable lessons about resilience, which shifted the entire session’s tone. Have you experienced how a simple introduction can foster trust and lead to deeper discussions?

    Moreover, I now believe that gathering preliminary insights from participants before the event can shape the agenda to better address their needs. I once sent out a brief survey asking about attendees’ expectations and preferences. It not only tailored our discussions but also empowered individuals to voice their insights right from the start. Isn’t it fascinating how a small gesture can elevate the entire learning experience?

  • My approaches to fostering trustworthiness

    Key takeaways:

    • Trustworthiness in education fosters a collaborative learning environment through vulnerability and shared challenges between educators and students.
    • Transparent communication, including clear expectations and openness, empowers students and enhances their engagement in the learning process.
    • Building personal relationships with attendees and encouraging informal interactions can significantly boost engagement and foster a sense of community.
    • Actively seeking and valuing feedback nurtures trust, allowing for adaptive learning experiences that respond to the needs of participants.

    Understanding trustworthiness in education

    Understanding trustworthiness in education

    Trustworthiness in education is fundamental, as it lays the groundwork for effective learning. I recall the first workshop I attended as a budding educator; the speaker’s transparent sharing of their successes and failures instantly drew me in. Wasn’t it refreshing to see a professional openly admit that their journey wasn’t perfect? This honesty can inspire students and create a safe space for learning.

    When we think of trustworthiness, it’s essential to consider the relationship between educators and learners. It’s not just about proven expertise but also about how vulnerable we can be with our learners. I’ve found that when I share my own learning challenges, it fosters a deeper connection with my students, encouraging them to be open about their struggles too. Doesn’t that make the learning environment more collaborative and supportive?

    Lastly, evaluating trustworthiness is about consistency in actions and words. I remember a candidate for a teaching role who emphasized the importance of follow-through on commitments; it resonated with me. Trust flourishes when educators model reliability, transforming the educational experience into one that students can count on, where they feel valued and respected. How can we cultivate an atmosphere of trust that empowers everyone involved?

    Creating transparent communication practices

    Creating transparent communication practices

    Creating transparent communication practices is essential for building trust in educational environments. I remember a time when I implemented an open feedback system in my classroom. Encouraging students to voice their thoughts and concerns led to unexpected insights; it was enlightening to see how much they valued having a say in their learning process. Have you ever considered how empowering it can be for learners to share their perspectives?

    Transparency also means being clear and honest about intentions and expectations. I’ve found that when I outline my teaching goals and the rationale behind them, students feel more engaged and involved. It’s like we’re partners in the learning journey; they know what to anticipate and can better support their own progress. Isn’t it reassuring for students to know exactly what is expected of them?

    Moreover, embracing vulnerability in our communication can foster a culture of openness. I once shared a personal story about a failure I faced in my own education—something I didn’t think would resonate. Surprisingly, it opened the floodgates for my students to share their struggles. This level of transparency not only strengthens our bond but cultivates an environment where everyone feels it’s okay to be imperfect. Wouldn’t you agree that acknowledging our challenges humanizes the educational experience?

    Building relationships with attendees

    Building relationships with attendees

    Building meaningful relationships with attendees goes beyond just providing information; it’s about connecting on a personal level. I recall a workshop I facilitated where I took the time to mingle and learn about individual participants’ interests before we started. It was eye-opening to see how those personal connections transformed the energy of the room; when attendees felt acknowledged, they were more engaged and willing to share their thoughts. Have you ever noticed how a simple conversation can ignite someone’s passion for learning?

    Creating opportunities for interaction can significantly enhance these relationships. After a session, I often invite attendees to informal Q&A discussions where they can express their opinions without the pressure of a formal setting. I remember one participant who, after a casual chat, opened up about their aspirations and challenges. By fostering an environment where attendees feel safe to share, I’ve seen collaborative ideas blossom that wouldn’t have surfaced otherwise. Isn’t it fascinating how often we overlook the power of dialogue?

    In my experience, following up with attendees post-event can solidify those connections. I started sending personalized thank-you emails, referencing specific conversations we had. It felt rewarding to invest in these relationships beyond the event itself, and I would often receive responses expressing how much they appreciated the gesture. Isn’t it thoughtful to show that you value their participation in this way? This approach not only nurtures trust but also creates a community of learners eager for future interactions.

    Encouraging feedback and active participation

    Encouraging feedback and active participation

    Encouraging feedback is pivotal for creating an engaging environment. I remember a panel discussion I hosted where we set up a live poll to gather attendees’ opinions in real-time. The excitement in the room was palpable as they watched their input shape the conversation. Have you ever felt that rush when your thoughts influence the direction of a discussion? This interactive experience not only demystified the topic but also made everyone feel like co-creators in the learning process.

    Active participation often flourishes when people feel their voices truly matter. During one workshop, I initiated small group discussions around specific themes, allowing attendees to share their insights. What surprised me was how, as they listened and built on one another’s ideas, a genuine camaraderie developed. It’s moments like these that make me wonder: how many insightful ideas remain hidden when we don’t foster a space for collaboration? By encouraging these exchanges, I often find that the knowledge shared during these sessions far exceeds the original agenda.

    Additionally, creating a space where feedback is not just welcomed but actively sought can lead to profound transformations. After a series of events, I began distributing anonymous feedback forms, and the responses were enlightening. One attendee expressed gratitude for addressing their learning needs, which encouraged me to adjust future content accordingly. This deepened trust; it made me realize how valuable every voice is in shaping our collective educational journey. Wouldn’t you agree that when we listen, we empower each other to grow?

    Personal experiences in fostering trust

    Personal experiences in fostering trust

    One memorable experience I had while fostering trust occurred during a multi-day seminar. At the start, I made a point to share my own learning struggles, which resonated strongly with the audience. I could see the relief wash over their faces, as if to say, “I’m not alone in this.” It was an important reminder that vulnerability can lay the groundwork for trust; sometimes, it takes admitting our challenges for others to feel comfortable opening up.

    Another instance that stands out happened during a Q&A session. A particularly hesitant attendee finally mustered the courage to voice a question they had been holding back. The atmosphere shifted dramatically; their courage sparked a cascade of inquiries from others who had similar thoughts. It made me think: what if we all took a moment to reflect on the barriers that prevent open dialogue? That experience not only enriched the discussion but also constructed a foundation of respect and trust among the participants.

    I also learned that transparency plays a crucial role in fostering trust. During an event evaluation, I openly shared the statistics of past turnout rates and what I hoped to improve upon. Rather than feeling defensive, attendees were surprisingly engaged, sharing their insights and suggestions. It hit me then that when I lay my cards on the table, it invites others to do the same. Isn’t it fascinating how honesty can create a bridge of trust, transforming a simple event into a shared learning experience?

  • My approaches to encouraging diverse input

    Key takeaways:

    • Diverse input in education enriches discussions, fostering innovation and community among learners.
    • Implementing strategies like breakout sessions and active outreach can enhance participation from underrepresented voices.
    • Creating inclusive events requires understanding attendees’ needs through surveys and offering multiple participation modes.
    • Utilizing technology and structured frameworks facilitates smoother discussions, ensuring all voices are heard and valued.

    Understanding diverse input in education

    Understanding diverse input in education

    When we think about education, it’s easy to overlook the importance of diverse input. I remember attending a workshop where educators shared their unique backgrounds and teaching styles. It struck me how each perspective enriched the conversation, illustrating that varied voices can illuminate different aspects of learning that might remain hidden otherwise.

    Diverse input doesn’t just happen by chance; it requires intentionality. Have you ever noticed how group discussions tend to echo the same few ideas? In my experience, when educators actively seek out diverse viewpoints, it leads to more innovative solutions and a deeper understanding of complex issues. It’s fascinating how hearing a new perspective can challenge our assumptions and enhance our problem-solving abilities.

    Moreover, embracing diverse input can foster a sense of community among learners. During a recent educational event, I saw firsthand how collaboration among individuals from various backgrounds resulted in a project that was richer and more nuanced than any one person could have created alone. It made me reflect on how creating spaces for diverse voices not only promotes inclusivity but also drives collective success.

    Importance of diverse perspectives

    Importance of diverse perspectives

    Diverse perspectives are crucial for fostering creativity in educational settings. I recall a group project where students from different cultures contributed their unique views on history, and it transformed our understanding of the subject. It was eye-opening to see how their backgrounds influenced their interpretations, prompting me to ask: wouldn’t we all benefit from a broader lens when tackling complex topics?

    The richness that variety brings to discussions can’t be overstated. In one of my own teaching experiences, inviting guest speakers from various fields brought fresh insights that my students and I had not considered before. This not only energized the classroom but also sparked lively debates, showcasing how differences can ignite passion and curiosity among learners.

    Ultimately, embracing diverse viewpoints enhances empathy and understanding. During a recent panel discussion, hearing stories from individuals with distinct experiences made me realize how limited my perspective had been. It’s amazing how nurturing a culture of openness can lead to deeper connections and drive collaboration, making education not just a process of learning facts but a journey of shared experiences.

    Strategies for promoting diverse input

    Strategies for promoting diverse input

    Creating an inclusive atmosphere where diverse voices are encouraged requires intentional strategies. In one of my workshops, I implemented breakout sessions where participants shared their unique perspectives in smaller groups. This approach fostered an environment where individuals felt safe to express their thoughts, leading to richer discussions that would have been stifled in a larger setting.

    One effective strategy I’ve found is to actively seek input from individuals who may not typically participate. I once reached out to students who were quieter during class discussions and invited them to share their insights in a more personal setting. The feedback I received was incredibly valuable, and it prompted me to reconsider how I could adapt my teaching methods to capture those quieter voices, ultimately enriching the overall learning experience.

    Furthermore, providing platforms for sharing diverse input can make a significant difference. For example, during a recent educational conference, I facilitated an open mic session where attendees could freely share their experiences and perspectives. The energy in the room was palpable; it reminded me how powerful it is to hear stories from a variety of backgrounds. This exchange not only enlightened those present but also encouraged ongoing dialogue, reinforcing the idea that when we actively promote diverse input, we grow collectively as a community.

    Creating inclusive educational events

    Creating inclusive educational events

    Creating inclusive educational events hinges on understanding the needs of different participants. I remember a particular seminar where we had diverse attendees, each bringing unique backgrounds to the table. It struck me that by simply sending out a pre-event survey, I could gauge their interests and experiences, allowing me to tailor the program in a way that resonated with everyone. Isn’t it fascinating how a simple question can open doors to deeper understanding?

    Another approach is to curate a diverse panel of speakers representing various perspectives. During one event, I had the opportunity to collaborate with experts from different fields, including those outside the traditional academic structure. This not only sparked enlightening discussions but also created a sense of community among attendees. It made me wonder—what conversations might we miss if we only stick to familiar voices?

    Lastly, I’ve seen the value in offering multiple modes of participation. For example, I often provide options for attendees to engage in discussions through chat features or online forums, especially for those who may find speaking up challenging. I recall a shy participant who later shared their thoughts in writing, which led to a powerful exchange. Reflecting on this, I realized that inclusivity comes from facilitating varied pathways for expression, ultimately enriching the learning landscape for all involved.

    Engaging underrepresented voices

    Engaging underrepresented voices

    Engaging underrepresented voices requires a proactive approach to invitation and participation. I once organized a workshop specifically targeting minority communities in my area, and I was amazed at the raw talent and insight that surfaced. It made me reflect: how often do we overlook brilliant voices simply by failing to reach out?

    Creating safe spaces for sharing is essential. At one event, I facilitated small group discussions where participants felt comfortable expressing their views without fear of judgment. I noticed how a quiet participant shared a story that resonated deeply with everyone, and it dawned on me that offering a supportive environment can transform hesitant voices into powerful narratives.

    Another effective strategy has been to incorporate storytelling as a central component of events. During a panel discussion, I encouraged attendees to share personal experiences related to the topic, which led to unexpected connections and emotional moments. This experience reinforced my belief that when we ask participants to bring their own stories to the forefront, we not only validate their experiences but also enrich the collective conversation. It’s a profound reminder that everyone has something valuable to contribute.

    Tools for facilitating discussion

    Tools for facilitating discussion

    Utilizing technology can significantly ease the way discussions flow. For instance, I implemented a virtual collaboration tool during a recent event that allowed participants to share their thoughts in real-time. Watching the chat light up with diverse perspectives made me realize how powerful it can be to break down barriers that traditional methods impose.

    In my experience, using visual aids like sticky notes or online whiteboards can enhance engagement tremendously. At one of my workshops, participants could anonymously post ideas and questions, which sparked deeper conversations. It’s fascinating to see how a simple visual tool can draw even the shyest participants into the discussion, encouraging contributions from all corners of the group.

    Another invaluable tool in facilitating discussion is the use of structured frameworks. I remember when I introduced a round-robin format during a brainstorming session. This method ensured that everyone had a chance to speak without interruption. It struck me then how effectively this simple structure can create an equal platform, ensuring no one is overshadowed and every voice matters. What if we all adopted such methods to foster more inclusive conversations?

    Personal experiences in encouraging diversity

    Personal experiences in encouraging diversity

    One of my most memorable experiences in promoting diversity was during a panel discussion I organized for aspiring educators. I specifically reached out to speakers from various cultural backgrounds and teaching philosophies. As I watched them interact, I felt a rush of excitement; it was like witnessing a mosaic coming together. Each voice brought something unique to the table, proving the importance of representation in educational dialogue.

    At another event, I decided to host breakout groups focused on different themes related to diversity, such as gender equality and cultural inclusivity. I vividly recall one participant sharing their personal journey of overcoming obstacles related to their identity. Their story resonated deeply with others, sparking a cascade of shared experiences. In that moment, I realized how vital it is to create spaces where people feel safe to express their truths; it not only enriches the conversation but can also lead to meaningful connections.

    I also find that actively inviting feedback on how to improve inclusivity can be a game-changer. After a workshop, I took the time to gather input from participants about their experiences. A few expressed that they felt overlooked or hesitant to share. This feedback was eye-opening for me. It prompted me to reflect: How can we ensure that every voice feels validated? The evolution of my events relies on continual pursuit of improvement, and that feedback is crucial in shaping a more inclusive environment for all.

  • My approaches to developing a compassionate dialogue

    Key takeaways:

    • Compassionate dialogue involves genuine understanding and emotional connection, fostering empathy and creating safe spaces for vulnerability.
    • Key principles include active listening, expressing empathy through personal stories, and maintaining a non-judgmental attitude.
    • Strategies for compassionate dialogue include asking open-ended questions, utilizing pauses for reflection, and validating emotions as they arise.
    • Positive outcomes of compassionate dialogue manifest in improved interpersonal relationships, increased psychological safety, and lasting changes incommunity dynamics.

    Understanding compassionate dialogue

    Understanding compassionate dialogue

    Compassionate dialogue is about more than just exchanging words; it involves genuinely understanding and connecting with the emotions of others. I remember a time when a colleague shared a personal struggle during a team meeting. Rather than glossing over her feelings, the room shifted to foster a sense of empathy, enabling us to support her more effectively. It struck me how powerful it can be when we truly listen.

    Have you ever felt like someone was really hearing you? That’s the essence of compassionate dialogue. It’s not always easy; it requires us to set aside our judgments and focus on the person in front of us. In my experience, this creates a safe space where vulnerability is met with kindness, leading to deeper conversations and more meaningful connections.

    When I think about the moments where I’ve witnessed or engaged in compassionate dialogue, it’s those exchanges laden with understanding and warmth that resonate the most. For instance, during a conflict resolution session, I noticed how simply acknowledging each other’s feelings transformed the atmosphere. Suddenly, instead of hostility, there was a camaraderie built on shared human experience. Isn’t it remarkable how just a few compassionate words can bridge gaps?

    Key principles of compassionate communication

    Key principles of compassionate communication

    Compassionate communication thrives on active listening. I remember a workshop I attended where the facilitator encouraged us to repeat back what we heard, not just to show we were listening, but to confirm our understanding. This simple practice transformed how I engaged with others; it made me more aware of their feelings and perspectives, turning dialogues into genuine exchanges rather than mere conversations.

    Another key principle is expressing empathy. Once, while mentoring a student who was struggling academically, I shared my own experiences of failure and frustration. By admitting my vulnerabilities, she felt safe to share her own challenges, leading to a deeper connection. Have you ever noticed how sharing a personal story can bridge divides? It’s amazing how vulnerability fosters trust and encourages openness in communication.

    Additionally, maintaining a non-judgmental attitude is crucial. I recall a time when a friend confided in me about their insecurities. Instead of offering immediate solutions or judgments, I practiced patience and simply listened. This approach not only validated their feelings but also allowed them to explore their thoughts freely. Isn’t it interesting how withholding judgment can lead to more profound understanding? It’s in these moments that compassionate communication truly flourishes.

    Strategies for initiating compassionate dialogues

    Strategies for initiating compassionate dialogues

    To initiate a compassionate dialogue, starting with an open-ended question can be incredibly effective. I remember sitting down with a colleague who was visibly upset about a recent project setback. Instead of jumping into problem-solving mode, I asked her, “What has been weighing on your mind?” This simple question invited her to express her feelings fully and set a tone of openness. Have you ever noticed how much people appreciate the chance to articulate their thoughts?

    Another strategy is to share a moment of silence before responding. While it might feel uncomfortable at times, I’ve found that taking even a brief pause allows for deeper reflection, both for myself and the other person. I once practiced this during a particularly heated discussion, and it transformed the atmosphere. Instead of diving straight into my next point, I took a breath and gave my counterpart time to express more of their perspective. Does silence not sometimes speak louder than words?

    Lastly, recognizing and validating emotions as they arise can be a game-changer in promoting compassionate dialogue. I often say, “I can see how much this matters to you,” when someone shares their struggles. This affirmation creates a safe space for further discussion and shows that I genuinely care. It’s moments like these that can shift conversations from transactional to transformational. Have you felt the difference when someone truly acknowledges your emotions?

    Personal experiences with compassionate dialogue

    Personal experiences with compassionate dialogue

    Engaging in compassionate dialogue has shaped many of my relationships. I recall a time when a friend was going through a tough breakup. Instead of offering advice or my opinions, I focused on listening and genuinely understanding her feelings. “What do you need right now?” I asked, showing her that her experience was paramount. Just being there, lending my ears without judgment, opened the door for a deeper connection. Have you ever experienced the power of simply being present for someone?

    One memorable instance was during a family gathering where tensions were running high. My cousin and I had differing views on a sensitive topic that usually leads to conflict. I decided to approach it differently and said, “Help me understand your perspective.” This invitation shifted the conversation from defensiveness to a more curious exchange. I was amazed at how our dialogue unfolded in a way that left us both feeling respected and heard. Isn’t it interesting how a change in approach can completely transform the dynamics?

    Lastly, I’ve learned that sharing personal experiences can foster empathy and vulnerability. In one enlightening conversation about mental health, I shared my struggles with anxiety. By being open about my own challenges, I noticed others began to open up too. “You’re not alone in this,” I reassured one participant who looked relieved. Those simple words helped create an environment where everyone felt safe to share their experiences. Have you noticed how relatable stories can bridge gaps and affirm that we’re all human?

    Evaluating outcomes of compassionate dialogue

    Evaluating outcomes of compassionate dialogue

    Evaluating the outcomes of compassionate dialogue reveals profound transformations in interpersonal relationships. In a recent group discussion, I noticed that participants who initially held opposing viewpoints began to empathize with one another. After sharing their thoughts in a respectful manner, they expressed surprise in realizing how much they had in common. Isn’t it fascinating how a simple shift in communication can unveil shared experiences that lead to understanding?

    One notable outcome I observed was the increase in psychological safety within the group. By modeling compassionate dialogue, individuals felt more inclined to express their emotions candidly. I remember one participant, who initially seemed withdrawn, gradually shared her perspective. This moment not only reinforced her value in the conversation but also encouraged others to open up, enriching the group’s dynamics. Could reaching out with kindness be the key to unlocking deeper connections?

    Moreover, I have seen how the practice of compassionate dialogue leads to lasting change beyond immediate interactions. In a workshop I facilitated, participants reflected on their newfound skills in empathy. They reported that these conversations influenced their daily interactions, fostering a greater sense of community in their personal lives. How empowering is it to know that by engaging compassionately, we can ripple out positive change in the world around us?

  • My approach to sustained audience focus

    Key takeaways:

    • Understanding audience focus enhances learning experiences by accommodating various learning styles and emotional connections.
    • Engaging the audience through personal experiences and interactive elements fosters a collaborative learning environment and motivates participation.
    • Utilizing feedback and adapting content to audience needs leads to more impactful and relatable educational sessions.
    • Incorporating technology and gamification can transform standard formats into dynamic, interactive experiences that encourage deeper understanding and participation.

    Understanding audience focus in education

    Understanding audience focus in education

    Understanding audience focus in education is essential for creating effective learning experiences. I remember attending a workshop where the facilitator kept referencing the needs of different learners. It struck me how a simple shift in focus to address various learning styles made the content far more engaging and impactful.

    When we talk about audience focus, it’s not just about demographics; it’s about understanding motivations and barriers. Have you ever noticed how a student’s engagement can dramatically change based on whether they feel seen and heard? I’ve witnessed firsthand how small adjustments, like incorporating relatable examples or interactive activities, can ignite a spark in learners who might otherwise feel disconnected.

    Emotional connection plays a crucial role in education. Reflecting on my own experiences, I recall the profound effect a teacher had when they shared their struggles in learning a new language. It reminded me that everyone has their battles, and acknowledging that vulnerability fosters a deeper connection, allowing students to feel safe and encouraged to participate.

    Importance of audience engagement

    Importance of audience engagement

    Engaging your audience is vital because it creates a sense of belonging and enhances learning outcomes. I vividly remember a seminar where the facilitator invited participants to share their own experiences related to the topic. It not only drew us in but also made us feel like an integral part of the conversation, transforming the event from a mere presentation into a collaborative learning experience.

    Furthermore, audience engagement can be a powerful motivator. I once attended a lecture that initially felt dry until the speaker posed a thought-provoking question about our future aspirations. Suddenly, I felt personally invested in the topic. It reminded me of how essential it is to invite participants to reflect and contribute; not only does it enrich the discussion, but it also empowers learners by validating their perspectives.

    Lastly, I believe that sustained engagement can lead to long-lasting impacts. Have you ever left an event feeling inspired and eager to apply what you’ve learned? I have, and those moments stick with me. By focusing on engaging the audience, we create memorable experiences that extend beyond the event itself, fostering a lifelong passion for learning.

    Strategies for sustained audience interest

    Strategies for sustained audience interest

    One effective strategy I’ve found for maintaining audience interest is incorporating interactive elements throughout the event. At a recent workshop I attended, the organizers divided us into small groups for hands-on activities. This not only broke the monotony but allowed us to engage with the material on a deeper level. Have you ever noticed how much more connected you feel to the content when you can actively participate?

    Additionally, regularly updating the content to reflect current trends keeps audiences intrigued. I remember when a local educational event introduced trending topics from social media, which instantly grabbed my attention. By relating material to the real world, we give participants a sense of relevance, making them more likely to stay engaged and invested. It’s fascinating how a simple shift in perspective can capture the audience’s curiosity.

    Finally, storytelling can be a powerful tool to maintain interest. During one event, a speaker shared a personal journey that resonated with many in the room. Listening to their struggles and triumphs made the topic relatable and memorable. So, how can we infuse our presentations with stories to create that same lasting impact? By weaving personal anecdotes into our sessions, we invite our audience into a narrative, making the learning experience much more profound.

    Techniques for interactive educational events

    Techniques for interactive educational events

    Utilizing technology to facilitate real-time feedback can elevate an educational event. In a seminar I once attended, the organizers employed live polls and Q&A sessions using a simple app. I was amazed at how quickly insights from the audience shaped the conversation. Have you ever felt heard when your opinions are factored in live? It’s an exhilarating feeling, and it makes the learning atmosphere both dynamic and responsive.

    Moreover, gamification can transform standard educational formats into interactive experiences. I recall a conference that included trivia games related to our subject matter. Not only did it enhance engagement, but it also fostered a bit of friendly competition. Wouldn’t it be refreshing to learn while having fun? This approach turned factual recall into an enjoyable challenge, reinforcing the material in a way that felt both entertaining and educational.

    Incorporating collaborative projects is another impactful technique. At a recent event, we were tasked with developing a group presentation based on the day’s teachings. The energy in the room was palpable, as ideas flowed freely and creativity took center stage. Have you ever noticed that collaboration sparks innovation? By allowing participants to work together, we not only deepen our understanding but also build connections that extend beyond the event itself.

    Personal experiences with audience feedback

    Personal experiences with audience feedback

    During one of the workshops I facilitated, I encouraged participants to share their thoughts via an online feedback form. The responses flooded in, and I was genuinely surprised by the range of insights. It struck me how a simple request for feedback could unlock such valuable perspectives. Have you ever considered how your audience’s experiences can drastically reshape your approach?

    At another event, I experimented with an open suggestion box, both digital and physical. Some of the comments surprised me—people shared ideas I hadn’t even considered. I realized that my audience was not just passive recipients of information; they were active contributors with unique viewpoints. This made me wonder, how often do we underestimate the knowledge sitting right in front of us?

    Reflecting on a particularly heated discussion during an educational seminar, I engaged with the audience’s differing opinions in real time. Their passionate feedback not only enriched the dialogue but also created a vibrant learning community. It was eye-opening to see how embracing varied perspectives can lead to deeper understanding. Have you felt that sense of connection when diverse viewpoints are acknowledged and discussed? It truly fosters a richer educational experience.

    Adapting content to audience needs

    Adapting content to audience needs

    Adapting content to meet audience needs is imperative in the realm of education. I remember a time when I redesigned a workshop to include more interactive components after noticing lingering disengagement. By incorporating group activities and discussions, I saw a remarkable shift in energy and participation. Isn’t it fascinating how a small tweak in delivery can transform the entire learning experience?

    One particular instance that stands out was when I adjusted the tone and complexity of my materials based on the audience’s background. During a session aimed at newcomers, I simplified my language and used relatable examples from everyday life. The instant feedback was palpable; you could practically see the light bulbs go on as participants connected the dots. Have you ever observed that spark of understanding in your audience?

    Moreover, I’ve learned the importance of monitoring audience engagement in real-time. During a virtual event, I leveraged interactive polls to gauge interest in various topics. This adjustment allowed me to pivot on the fly, diving deeper into areas that ignited curiosity. It made me realize that staying in tune with my audience not only keeps them engaged but also enriches the content delivery significantly. How often do we miss those opportunities to connect more deeply?

  • My approach to setting discussion goals

    Key takeaways:

    • Establishing clear discussion goals aligns participants and enhances engagement, transforming conversations into productive exchanges.
    • Using SMART criteria for goal-setting and involving participants fosters ownership and motivation, leading to better outcomes.
    • Personalizing goals based on audience needs increases relevance and boosts enthusiasm, highlighting the importance of empathy and active listening.
    • Adapting goals based on feedback enriches discussions and promotes collaborative ownership, enhancing the overall learning experience.

    Understanding discussion goals

    Understanding discussion goals

    When I think about discussion goals, it’s like setting a compass for a journey. Have you ever entered a conversation without a clear idea of what you wanted to achieve? I remember a group discussion I attended where everyone had different expectations, which led to confusion and frustration. Establishing clear goals helps to keep everyone aligned and focused.

    Defining discussion goals means understanding what you truly want to gain from the dialogue, whether it’s generating ideas, resolving conflicts, or simply sharing knowledge. I once joined a roundtable where the facilitator emphasized the importance of a clear objective. It transformed the conversation and made it incredibly productive. I could feel the energy shift as participants began to contribute more thoughtfully, all because we were united by a common purpose.

    The emotional aspect of setting goals can be profound. Have you ever felt that sense of accomplishment when a discussion completely met your expectations? I certainly have. It’s not just about the outcomes; it’s also about the connections we build along the way. When our discussion goals are clear, it allows for richer interactions and deeper insights, creating an environment where everyone feels valued and engaged.

    Strategies for setting effective goals

    Strategies for setting effective goals

    Setting effective goals begins with clarity. I’ve found that using the SMART criteria—Specific, Measurable, Achievable, Relevant, and Time-bound—serves as a reliable framework. For instance, I once led a workshop where we aimed to develop practical solutions for enhancing student engagement. By breaking down our goal into specific actions, everyone knew exactly what success would look like, which made the entire process more focused.

    Another strategy I embrace is involving all participants in the goal-setting process. During a team meeting, we brainstormed what we wanted to achieve collectively, and it was amazing to witness the synergy that emerged. By allowing everyone to contribute their ideas, I felt a unique sense of ownership amongst the group, which genuinely motivated us to attain our shared objectives.

    Lastly, I believe in flexibility. While it’s crucial to set ambitious goals, being adaptive to the group’s needs can lead to unexpected and fruitful outcomes. I recall a debate that started with one agenda but evolved into a deeper exploration of related issues. That shift not only enriched our discussion but also reinforced my belief that effective goal-setting is a dynamic process that thrives on responsiveness and collaboration.

    Personalizing goals for your audience

    Personalizing goals for your audience

    When it comes to personalizing goals for your audience, understanding their unique needs and motivations is essential. I often ask myself, how well do I really know the group I’m working with? For instance, during a recent seminar, I made it a point to survey attendees beforehand to identify their interests. This simple step transformed our goals from vague aspirations into meaningful objectives that resonated with everyone involved.

    One memorable experience that stands out is when I tailored a workshop for new educators. Initially, I had planned to emphasize teaching strategies, but after speaking with participants, I discovered they were more interested in classroom management techniques. Adjusting the focus not only made the goals more relevant, but it also sparked lively discussions. It’s fascinating how minor changes can significantly enhance engagement and motivation within the group, don’t you think?

    I’ve learned that personalizing goals often requires a dash of empathy and active listening. I make it a habit to check in regularly and adjust our objectives as needed. For example, I remember a project where initial excitement waned after a few weeks. By soliciting feedback and revising our goals collaboratively, we reignited enthusiasm—reminding me how deeply connected goal-setting is to fostering a supportive environment.

    Adjusting goals based on feedback

    Adjusting goals based on feedback

    Adjusting goals based on feedback is a crucial step in ensuring our objectives remain relevant and effective. I recall a time when I hosted a multiple-session educational event, only to find that feedback from the first session revealed participants were craving more interactive elements. It was a wake-up call for me. By incorporating their suggestions for hands-on activities in subsequent sessions, I could see their engagement levels soar. Isn’t it rewarding to see people truly involved and benefiting from what you’ve tailored for them?

    Feedback creates a dynamic where goals can evolve rather than remain static. During a recent online workshop, I implemented a real-time polling feature to gauge audience sentiment. The responses guided me to tweak the discussion topics on the fly. This adaptability made the experience so much richer because it reflected the group’s interests. Have you ever seen how quickly a conversation can shift in a group setting? Recognizing those shifts and aligning our goals accordingly can significantly enhance learning outcomes.

    I’ve also found that when feedback is welcomed and acted upon, it fosters a sense of ownership among participants. In one case, I held a follow-up discussion where I invited attendees to share their thoughts on our objectives. The ideas they brought to the table were not only insightful but also inspiring. Looking back, that collaborative spirit transformed our group dynamic in ways I hadn’t initially anticipated. Don’t you think that including others in the goal-setting process not only empowers them but also enriches the educational experience for everyone involved?

  • My approach to selecting panel themes

    Key takeaways:

    • Panel themes significantly shape educational events by resonating with audience interests and current trends, fostering engaging discussions and connections.
    • Key factors in selecting effective themes include alignment with audience needs, diversity of perspectives, and potential for actionable takeaways.
    • Analyzing audience demographics and feedback, alongside researching relevant topics, ensures that themes are impactful and reflective of participants’ challenges.
    • Finalizing themes should involve collaboration, feedback, and consideration of practical constraints to enhance the overall learning experience.

    Understanding panel themes

    Understanding panel themes

    Panel themes play a crucial role in shaping the overall experience of an educational event. I remember attending a conference where the panel theme sparked discussions that were not only relevant but also incredibly engaging. It made me wonder, what elements contribute to a theme that captures attention and invites deeper conversation?

    When I think about the nuances of panel themes, I realize they must resonate with the audience’s interests and the current educational landscape. For instance, a theme centered on innovative teaching methods not only attracts educators but also encourages them to share their own experiences. Have you ever participated in a discussion where the theme felt tailor-made for you? It can be a transformative experience, fostering connections and igniting new ideas.

    Diving deeper into what constitutes a strong panel theme, it becomes clear that clarity and relevance are key. A well-defined theme helps guide the discussion and encourages diverse perspectives. I recall a panel where the theme’s focus on STEM education opened the floor for not just teachers but also industry professionals to weigh in. This blend of voices enriched the dialogue, proving that the right theme can create a space for collaborative learning and exploration.

    Importance of panel themes

    Importance of panel themes

    When selecting panel themes, their importance can’t be overstated. I once attended a workshop centered around the theme of “Learning in the Digital Age,” and it struck me how effectively it resonated with the audience’s current challenges. Participants were eager to share their struggles and triumphs, creating a vibrant atmosphere of collective growth.

    A strong panel theme not only sets the stage for dialogue but also fosters connections among attendees. I can still remember the excitement of a session focused on “Educational Equity,” where educators from diverse backgrounds gathered to discuss strategies and share personal stories. The energy in the room was palpable, and it made me reflect: when we choose themes that highlight shared experiences, isn’t it easier to learn from one another?

    Moreover, the relevance of a theme to ongoing educational trends enhances its impact. For example, during a recent event on “Sustainable Practices in Education,” educators exchanged innovative ideas that took on a life of their own. This made me think about how well-chosen themes can transcend the event itself, inspiring continued discussions long after the panels conclude. Isn’t that the ultimate goal—sparking lasting change and thought?

    Factors to consider for selection

    Factors to consider for selection

    When selecting panel themes, the alignment with the audience’s needs is crucial. One time, I attended a session about “Mental Health in Education” that truly resonated with attendees. The room was filled with focused faces, nodding in agreement—everyone had a story to share. It was a vivid reminder of how important it is to choose themes that mirror the realities of participants.

    Another critical factor is the diversity of perspectives within the theme. I recall a panel on “Innovative Learning Approaches” that included voices from various educational settings. The exchange of ideas from both urban and rural educators created a rich tapestry of insights. This experience made me realize: isn’t it vital to ensure that every voice can contribute to and enrich the conversation?

    Finally, the potential for actionable takeaways should never be overlooked. A panel I once experienced on “Creating Inclusive Classrooms” ended with practical strategies that educators could implement immediately. That evening, I felt empowered by what I learned—how often do we walk away from an event feeling equipped to enact real change? Themes that inspire practical applications can spark real transformation, pushing us to turn conversation into action.

    Analyzing audience interests

    Analyzing audience interests

    When analyzing audience interests, I often reflect on the specific demographics and backgrounds of the participants. I remember attending a conference where the majority of the audience comprised younger educators just starting their careers. Their eagerness for tools and strategies tailored to their unique challenges drove a significant focus on themes like “Technology in the Classroom” and “Building Strong Classroom Communities.” It struck me how critical it is to connect deeply with what the audience genuinely needs.

    Listening to feedback is another essential layer in this analysis. After a workshop I led on “Engagement Strategies for Diverse Learners,” attendees shared their biggest hurdles—many spoke of feeling unprepared to address individual learning styles. Their candidness highlighted a clear demand for more customizable approaches. This situation led me to ask: how can we listen and adapt our themes to address these direct concerns and inspire our audience to overcome their challenges?

    Finally, I’ve learned that past attendance trends can provide powerful insights. At one event, I noticed a surge in interest around issues of equity and inclusion, sparking lively discussions among attendees. This pattern illuminated a persistent desire for deeper explorations of these topics across various panels. Reflecting on this, I found it crucial to not only analyze current interests but also to anticipate emerging trends, triggering a desire for ongoing dialogue and growth within the educational community.

    Researching relevant topics

    Researching relevant topics

    Researching relevant topics involves diving into resources that inspire and inform. I often utilize online forums and social media groups where educators gather to share their thoughts and experiences. Recently, while scrolling through a Twitter chat on teaching methodologies, I discovered a conversation about the impact of mindfulness in education. That moment made me realize how vital these platforms are for uncovering themes that resonate deeply with educators.

    Another effective strategy is sifting through academic journals and publications related to education. I remember reading an article that highlighted the increasing importance of mental health resources in schools. Not only did it ignite my curiosity, but it also prompted me to consider how we can weave such pressing issues into our event themes. It raised a reflective question: how often do we prioritize emotional well-being alongside traditional learning?

    I also find it invaluable to reach out directly to educators for their input. A few months back, I hosted a focus group with teachers from various backgrounds, inviting them to share their experiences and concerns. Their authentic stories about grappling with remote learning challenges illuminated gaps in our event themes. This interaction reinforced my belief that engaging in direct dialogue with the audience nurtures deeper connections and ensures the topics we present are genuinely impactful.

    Evaluating potential speakers

    Evaluating potential speakers

    When I consider potential speakers, I look for those who not only possess expertise but also demonstrate a genuine passion for their subject. A few years back, I attended a seminar where the speaker shared their personal journey with educational reform. Their heartfelt storytelling not only captivated the audience but also made the topic relatable and memorable. Have you ever sat through a presentation where the speaker seemed disconnected? It’s a reminder of how vital authenticity is in connecting with the audience.

    I also pay attention to how speakers engage with their previous audiences. I recall a webinar I led where we reviewed participants’ feedback on various speakers. The ones who sparked discussions and encouraged questions always had the best responses. It became clear to me that a speaker’s ability to facilitate dialogue can significantly enhance the learning experience. Who wouldn’t want to be part of a conversation where ideas flow freely?

    Additionally, I think about a speaker’s adaptability in addressing current trends. One time, I booked a speaker who had successfully navigated a last-minute shift in their presentation topic to reflect emerging educational technologies. Their ability to pivot while maintaining the audience’s engagement truly impressed me. It reinforced my belief that selecting speakers who are not only knowledgeable but also flexible can elevate the overall quality of our events. Wouldn’t you agree that today’s educators appreciate speakers who resonate with their evolving needs?

    Finalizing theme selection process

    Finalizing theme selection process

    When it comes to finalizing the theme selection process, I always return to the core objectives of the event. A couple of years ago, I faced a dilemma when trying to choose between two equally compelling themes for an educational conference. I found that visualizing the potential impact each theme would have on the audience helped clarify my decision. Have you ever felt torn between two great options? It’s in those moments of reflection that the theme that resonates with your audience usually becomes apparent.

    I also gather feedback from collaborative brainstorming sessions with my team. I remember a time when we were deliberating between a theme focused on innovative teaching methods and another on student-centered learning. By discussing our individual impressions and preferences, we uncovered insights that we wouldn’t have recognized alone. Isn’t it fascinating how different perspectives can illuminate the best path forward? This collaborative approach often leads to a unanimous theme choice that excites everyone involved.

    Ultimately, I weigh practical considerations such as the resources available and the target audience. For instance, when selecting a theme for a short series of workshops, I made sure it aligned with both the interests of participants and our logistical constraints. I’ve learned that a well-chosen theme not only drives engagement but also sets the stage for a memorable learning experience. Do you think that aligning a theme with practicalities can sometimes be just as important as its creative appeal?

  • My approach to challenging the status quo

    Key takeaways:

    • Educational events can inspire transformation by challenging assumptions and providing interactive learning experiences.
    • Engaging participants through diverse discussions and technology, like live polling, enhances the overall learning atmosphere.
    • Gathering participant feedback and observing engagement can identify areas for improvement, leading to more effective events.
    • Sharing personal experiences and inviting diverse speakers can broaden perspectives and foster deeper connections among attendees.

    Understanding educational events

    Understanding educational events

    Educational events serve as dynamic platforms for learning and engagement, transforming traditional educational experiences. Reflecting on my own experiences, I can recall a workshop that sparked a passion within me, reminding me of how such events can change perspectives. Have you ever walked into a session unsure and left feeling inspired?

    These events often combine interactive elements, expert speakers, and networking opportunities, enriching the learning experience far beyond a typical classroom setting. I remember attending a conference where I met like-minded individuals who shared my interests and challenged my thinking. It’s fascinating to realize how a single conversation can lead to significant personal and professional growth.

    Consider the potential of participating in these events. Are you ready to step outside your comfort zone? When I attended my first seminar, I felt the initial anxiety, but it quickly turned into excitement as I absorbed new ideas and pushed my boundaries. The essence of educational events lies in this very transformation—an invitation to challenge your assumptions and explore uncharted territories of knowledge.

    Strategies for effective educational events

    Strategies for effective educational events

    Engaging participants is crucial for the success of any educational event. One memorable experience I had was during a breakout session where we were encouraged to debate real-world scenarios. This lively exchange sparked a debate that ignited everyone’s passion, proving that when people feel involved, learning becomes not just enlightening but exhilarating. How could we harness that energy in our events to foster deeper understanding?

    Incorporating technology can also enhance the educational experience. For instance, I once attended a workshop that used live polling to gauge participant opinions throughout the session. This not only made the atmosphere more interactive but also helped the speaker adapt their content in real-time. Reflecting on that experience, it’s clear that embracing technology can transform how knowledge is disseminated. Are we leveraging all the tools at our disposal to create that dynamic atmosphere?

    Another strategy is to create diverse networking opportunities. At one conference, I remember a dedicated session for small group discussions, which allowed participants to share insights and form connections that extended beyond the event itself. This kind of connection can lead to collaborations and friendships that enrich professional lives. Are we facilitating these invaluable interactions in the events we design?

    Identifying areas of improvement

    Identifying areas of improvement

    Identifying areas that could use improvement starts with a careful evaluation of participant feedback. Once, after a seminar I attended, I gathered informal impressions from attendees during lunch. Their insights uncovered unexpected pain points in the session’s pacing and content depth. Isn’t it fascinating how direct conversations can reveal layers of experience that surveys might miss?

    Another effective method is to analyze engagement metrics from past events. I remember tracking attendance and participation rates for a workshop series. It was eye-opening to see how certain topics resonated more than others. This data not only guides future content creation but also highlights where we need to be bolder. Are we paying close enough attention to the numbers that could lead to meaningful changes?

    Finally, observing event dynamics live can unveil subtle yet impactful areas for growth. During one conference, I noticed participants disengaging during a long lecture segment. By introducing shorter, interactive segments, we sparked renewed interest. Why not commit to consistently refining our approach based on these real-time observations? Embracing this mindset can drive significant improvements, transforming ordinary events into extraordinary learning experiences.

    Engaging participants in dialogue

    Engaging participants in dialogue

    Creating an engaging dialogue with participants is key to enhancing their overall experience. I recall one event where I opened the floor for a Q&A after each presentation rather than just at the end. The immediate feedback was refreshing; it sparked lively discussions and allowed attendees to connect with the material in a way that felt personal and relevant. When was the last time you felt truly heard in a large group setting?

    In another instance, I experimented with breakout sessions that encouraged smaller group conversations. This approach has been a game-changer for fostering deeper connections among participants. I noticed that when people feel comfortable sharing their thoughts in a more intimate environment, they are more likely to voice their ideas and concerns. Isn’t it amazing how the right setting can transform hesitance into vibrant dialogue?

    Moreover, I’ve found that using open-ended questions can significantly deepen discussions. One time, I posed a broad question about participants’ expectations for the day. The variety of answers surprised me, revealing insights I had never considered. Engaging participants in this way not only enriches the dialogue but often leads to unexpected collaborations. Don’t you find it intriguing how a simple question can unlock new avenues of thought and exploration?

    Personal experiences in changing perspectives

    Personal experiences in changing perspectives

    During one workshop, I introduced a method where participants could anonymously share their preconceived notions about the topic before we delved into it. I watched as their faces shifted from skepticism to curiosity as we examined those assumptions together. Isn’t it interesting how peeling back layers of preconceived beliefs can foster a more open-minded environment?

    In another experience, I shared a personal story about my own biases and how they initially hindered my learning journey. This vulnerability opened the floodgates; attendees felt encouraged to share their experiences and recognize their blind spots. It was remarkable to see how personal storytelling can serve as a bridge, connecting us all in our struggles—who would have thought that honesty could be so liberating?

    I also made it a practice to invite guest speakers from diverse backgrounds to challenge our collective views. One speaker, in particular, left a lasting impression with their unconventional approach to problem-solving. Their fresh perspective transformed my thinking and sparked new ideas among the group. How often do we miss out on uncharted territories because we stick to familiar narratives instead of embracing diversity in thought?

  • My approach for softening hard topics

    Key takeaways:

    • Softening hard topics involves using personal stories and empathetic language to create a supportive environment for open dialogue.
    • Educational events are crucial for fostering diverse perspectives, community, and collaborative learning through effective communication techniques.
    • Facilitating difficult conversations requires establishing ground rules, practicing active listening, and acknowledging emotions to create a safe space for participants.

    Understanding softening hard topics

    Understanding softening hard topics

    Softening hard topics is essential for creating a comfortable environment where individuals feel safe to engage and share their thoughts. I remember a time when I had to address a sensitive issue in a workshop. Instead of diving directly into the topic, I started by sharing a personal story that reflected vulnerability. This approach instantly shifted the atmosphere, allowing participants to let their guard down and be more receptive.

    When navigating challenging subjects, it’s helpful to frame the conversation with empathy and understanding. I often ask myself, “How would I want someone to approach this with me?” One moment that stands out was when I facilitated a discussion on failure in a leadership event. By first acknowledging my own setbacks and highlighting shared experiences, I noticed the room transforming as others felt empowered to share their own stories.

    The goal of softening hard topics isn’t to avoid difficult conversations; it’s about making them more approachable. I find it crucial to use language that resonates, steering clear of jargon that could alienate others. For example, instead of discussing a conflict in abstract terms, I might discuss specific feelings and outcomes, inviting participants to reflect on their experiences. Isn’t it remarkable how simply choosing our words can foster deeper understanding?

    Importance of educational events

    Importance of educational events

    Educational events play a vital role in expanding knowledge and fostering intellectual growth. I recall attending a seminar where the speaker tackled complex economic theories. Instead of overwhelming us with jargon, he used relatable analogies that brought the concepts to life. It was a reminder of how effective communication can transform confusion into clarity, leading to genuine understanding.

    In my experience, these events also provide a platform for diverse perspectives. I once participated in a panel discussion where attendees came from various backgrounds, each sharing unique insights on environmental issues. The different viewpoints not only enriched the conversation but also highlighted the importance of collaboration in tackling real-world challenges. How often do we truly listen to voices that differ from our own?

    Furthermore, educational gatherings foster a sense of community and support among participants. I remember feeling hesitant to voice my ideas during a workshop, but when others shared their thoughts first, it created a safe space. This collective vulnerability encouraged me to engage more deeply, demonstrating that learning often flourishes in a collaborative environment where people feel valued and heard.

    Strategies for engaging discussions

    Strategies for engaging discussions

    Engaging discussions are often about creating the right atmosphere. I remember attending a community forum where the facilitator encouraged everyone to share their experiences first. This approach not only broke the ice but also built trust among participants. It made me wonder: how often do we hold back our thoughts because we don’t feel safe? By sharing personal anecdotes upfront, discussions can become more inviting, inviting others to feel comfortable joining in.

    A strategic way to spark engagement is through open-ended questions. I once moderated a workshop where I posed a thought-provoking question: “What does success look like to you?” The answers ranged from personal goals to community achievements. It was fascinating to see how this single question opened up a rich dialogue that uncovered diverse motivations and aspirations. What I realized is that when we invite participants to define their own narratives, the conversation deepens and expands naturally.

    In my experience, incorporating multimedia can also enhance discussions significantly. During a session, we watched a short documentary clip related to our topic. The visuals and stories in the film captivated everyone’s attention and ignited passionate debates afterward. It made me think about how powerful visuals can help convey emotions that words sometimes struggle to express. Have you ever noticed how a good video can turn a quiet room into a lively exchange of ideas?

    Building a supportive environment

    Building a supportive environment

    Creating a supportive environment begins with genuine acknowledgment of each participant’s feelings. I recall a time when I participated in a workshop focused on difficult themes, and the facilitator took a moment to validate our emotions before diving into the subject matter. It was a simple gesture, but it helped me feel seen and heard, allowing me to open up more than I initially intended. Have you ever felt more willing to share in a space where your thoughts and feelings are recognized?

    Another important aspect is setting ground rules that promote respect and confidentiality. I once led a group discussion where we agreed that all comments would remain within the room. This commitment helped foster a sense of safety and created deeper connections among participants. It’s interesting how clear guidelines can uplift the conversation, making individual voices resonate more powerfully. Have you noticed a difference when participants feel assured that their privacy is protected?

    Additionally, providing opportunities for small group interactions can significantly enhance comfort levels. In a recent event, we broke into pairs to discuss sensitive topics before rejoining the larger group. This approach allowed me to express my thoughts in a less intimidating setting, paving the way for more fruitful contributions later. Isn’t it fascinating how a simple shift in format can lead to more meaningful conversations?

    Techniques for presenting sensitive content

    Techniques for presenting sensitive content

    One effective technique for presenting sensitive content is using storytelling to convey complex emotions in a relatable way. I remember attending a seminar where the speaker shared a personal story about overcoming adversity. This narrative allowed me to connect with the topic on an emotional level, making it easier to engage with the more challenging aspects of the discussion. Have you ever found that a well-told story can transform how you perceive a difficult subject?

    Incorporating visuals can also play a significant role in softening hard topics. During a recent workshop, the facilitator used impactful images and infographics to illustrate key points. This approach not only broke up the text-heavy content but also evoked powerful emotions, making it easier for participants to digest the material. I often find that visuals can bridge the gap between complex ideas and personal understanding. Do you think a simple image can sometimes speak louder than words?

    Moreover, inviting participation through open-ended questions helps participants reflect and share their thoughts at their own pace. At one event, I was struck by how asking, “What does this topic mean to you personally?” opened up the floor to deeper conversations. It encouraged people to connect their experiences to the discussion, fostering a sense of community. When have you used questions to guide a conversation, and what impact did it have on the group’s dynamics?

    Personal experiences in softening topics

    Personal experiences in softening topics

    One of my most poignant experiences in softening hard topics happened during a curriculum workshop. The presenter shared her struggle with mental illness and how it impacted her teaching. Listening to her personal story made me realize that vulnerability can be a powerful tool in education. It compelled me to think: how often do we shy away from discussing our own challenges, and what if sharing those parts of ourselves could foster understanding?

    Another instance that stands out for me was a panel discussion on grief and loss. Each speaker had a profoundly different experience but they shared one common thread: the need for connection. By recounting their personal journeys, they made the audience feel seen and heard. I was moved by how openly discussing their pain allowed others to reflect on their experiences, creating a space for healing. Have you ever felt comforted just by knowing that others have faced similar struggles?

    I also remember an adult education course where we delved into the topic of bias and privilege. The facilitator encouraged participants to share their own experiences related to these sensitive themes. In this environment, I was surprised to see individuals from different backgrounds find common ground through their stories. It became clear to me that by allowing space for personal narratives, difficult conversations can become transformative, igniting empathy and a greater understanding. What stories could you share to help others engage with hard topics?

    Tips for facilitating difficult conversations

    Tips for facilitating difficult conversations

    When it comes to facilitating difficult conversations, one crucial tip is to create a safe environment. I recall a workshop where the facilitator started by establishing ground rules, emphasizing respect and confidentiality. This approach immediately put everyone at ease, allowing participants to speak freely. Have you ever noticed how a little clarity can remove barriers?

    Practicing active listening is another vital tip. In a recent discussion about educational equity, I found that truly hearing my colleagues’ perspectives not only validated their feelings but also deepened my understanding. It’s amazing how much a simple nod or an empathetic expression can encourage others to share their thoughts. Isn’t it fascinating how listening can turn a tough topic into a rich dialogue?

    Lastly, I believe it’s important to acknowledge emotions during these conversations. I participated in a session focused on trauma-informed teaching, where the leader encouraged participants to express their feelings before diving into the content. This acknowledgment made a world of difference. Why do we often overlook the emotional component when discussing challenging subjects? Recognizing feelings fosters connection, making it easier for everyone to engage.