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

Blog

  • How I assess panel success

    Key takeaways:

    • Panel success is defined by quality interaction, relevance of topics, and active audience engagement.
    • Educational events foster community, networking, and inspire continuous learning through diverse perspectives.
    • Utilizing tools such as post-event surveys and live polling can effectively evaluate panel effectiveness and audience interest.
    • Improving panel outcomes involves engaging storytelling, interactive elements, and conducting feedback sessions to enhance participant experiences.

    Understanding panel success criteria

    Understanding panel success criteria

    Understanding panel success criteria involves recognizing what truly defines the effectiveness of a panel discussion. For me, it’s not just about the number of attendees; it’s about the quality of interaction. Have you ever sat in an audience and felt the energy shift when a panelist shared a personal story? That connection is what makes a panel memorable.

    One crucial criterion I’ve observed is the relevance of the topics discussed. I remember attending a panel where the subject matter didn’t resonate with the audience, leading to disinterest and disengagement. It’s a powerful reminder that for a panel to succeed, it must address the audience’s needs and curiosities directly. What subjects spark your passion?

    Feedback is another vital metric for assessing success. After hosting a panel, I always make it a point to gather insights from participants. One time, an attendee told me how a short Q&A session had sparked new ideas for their own work. This type of insight emphasizes how important it is to foster an environment where questions and discussions flourish. What kind of feedback have you received in similar situations?

    Importance of educational events

    Importance of educational events

    Educational events play a crucial role in fostering knowledge and inspiration. I vividly recall a workshop I attended where experts shared their experiences and insights in an intimate setting. The palpable excitement among attendees sparked conversations that went far beyond the event itself, igniting a sense of community and shared purpose. Have you ever felt that connection in an educational space?

    The value of educational events extends to networking opportunities they provide. In one instance, I met someone at a conference who became a long-term collaborator. Those brief interactions, whether during a breakout session or over coffee, can lead to incredible partnerships. Isn’t it fascinating how a single conversation can change the trajectory of your career?

    Moreover, these events encourage continuous learning and personal growth. I find it inspiring to see diverse perspectives being shared, often challenging my own viewpoints. At a recent seminar, a speaker’s story reshaped how I approached my work, highlighting the transformative power of fresh ideas. Have you ever left an event feeling compelled to act on new insights?

    Key factors in panel assessments

    Key factors in panel assessments

    When assessing panel success, one of the key factors is the diversity of perspectives presented. I recall a panel session I attended where experts from various backgrounds shared their unique insights. The breadth of experiences not only enriched the discussion but also sparked my curiosity about viewpoints I hadn’t considered before. Have you ever left a session wondering how someone else’s background shaped their ideas?

    Another crucial aspect is audience engagement during the session. I’ve seen panels thrive when speakers actively encourage questions and discussions. At one event, a panelist welcomed audience participation with such enthusiasm that it transformed the atmosphere. That open dialogue created an electric environment, making everyone feel invested in the conversation. Doesn’t that kind of interaction elevate the entire experience?

    Lastly, it’s essential to evaluate the practicality of the advice shared during a panel. I remember a workshop where the speakers provided actionable strategies that attendees could implement immediately. The excitement was palpable as people exchanged ideas and planned their next steps. It really makes a difference when panelists offer tangible takeaways, don’t you think?

    Tools for evaluating panel effectiveness

    Tools for evaluating panel effectiveness

    To effectively assess panel effectiveness, I find that tools like post-event surveys are invaluable. After one particularly engaging panel I attended, I filled out a survey that asked specific questions about content relevance and speaker engagement. The feedback I provided not only helped the organizers improve future events but also offered me a chance to reflect on what resonated most with me. Have you ever thought about how your input can influence upcoming sessions?

    Another helpful approach is live polling during the event. I remember participating in a session where the moderator asked real-time questions that gauged our opinions on discussions. It was fascinating to see how the group’s thoughts evolved, and it also gave the speakers immediate insight into our interests. This interactive tool not only enhances engagement but also serves as a real-time measure of effectiveness. Wasn’t it enlightening to see instant feedback?

    Additionally, analyzing follow-up interactions can shed light on a panel’s lasting impact. For example, after a panel focused on educational technology, I noticed several attendees sharing resources and ideas long after the event concluded. This ongoing dialogue is often a sign that the panel successfully inspired actionable steps. How often do we evaluate our experiences based on the conversations they spark afterward?

    Personal experiences with successful panels

    Personal experiences with successful panels

    Reflecting on my experiences with successful panels, I recall a session on innovative teaching methods that truly captivated the audience. I felt the energy shift in the room as the speakers shared personal stories alongside their data. It struck me how genuine narratives create an emotional connection, making the content relatable and memorable. Have you ever noticed how a personal touch can transform a dry topic into something impactful?

    One standout panel I attended featured educators sharing their failures alongside their successes. I vividly remember the vulnerability in their voices as they discussed what didn’t work. It reminded me that authenticity fosters trust and encourages openness, leading to deeper discussions. Isn’t it interesting how our willingness to share setbacks can inspire new ways of thinking?

    After a panel that tackled issues of diversity in education, I joined a small group where attendees dove into passionate conversations. I felt an exhilarating sense of community, as everyone shared their insights and experiences. This not only demonstrated the panel’s effectiveness but also reaffirmed the importance of creating spaces for dialogue. How often do we leave an event feeling not just informed but connected?

    Strategies for improving panel outcomes

    Strategies for improving panel outcomes

    Engaging panelists effectively is crucial for improving outcomes. I’ve found that when panelists are encouraged to prepare engaging visuals or storytelling techniques, the audience is much more captivated. For example, in one panel I experienced, a speaker used a creative infographic that vividly illustrated complex data, leading to an exciting discussion. Have you ever thought about how visuals might change the way we absorb information?

    Another strategy I’ve applied is incorporating interactive elements during panels. By asking the audience questions or facilitating live polls, I’ve witnessed meaningful exchanges occur right in the moment. At a recent event, a simple question sparked such enthusiasm that attendees began sharing their experiences, transforming a monologue into a vibrant conversation. Isn’t it fascinating how a little bit of interaction can suddenly make everyone feel involved?

    Lastly, I believe in the power of feedback sessions post-panel. After one particularly thought-provoking discussion, we dedicated a few minutes for attendees to share their takeaways. I was overwhelmed by the depth of the insights and how they reinforced connections amongst participants. Don’t you think that taking the time to reflect and exchange ideas can elevate the entire experience?

    Conclusion and future goals

    Conclusion and future goals

    As I reflect on the success of recent panels, it’s clear that engaging with our audience is a critical component of growth. I often find myself thinking about the moments of genuine connection that can emerge from an engaged crowd. For instance, I once witnessed a lively exchange between panelists and attendees that deepened the overall experience, reinforcing the idea that every voice matters. What if we prioritized these interactions in every future event?

    Looking ahead, my goal is to leverage technology even more in our panels. I envision incorporating virtual reality or augmented reality to create immersive experiences that captivate audiences in ways traditional formats cannot. Just imagine the power of stepping into a simulated environment that illustrates a complex concept. Wouldn’t that redefine our understanding and retention of information?

    Lastly, I’m committed to fostering a culture of continuous improvement through ongoing feedback. Each panel presents a unique opportunity to learn and adapt. After a recent event, I realized how implementing small changes based on attendee feedback could lead to profound impacts on future discussions. How can we truly innovate without heeding the voices of those we serve? This is a question I’ll carry forward as I work towards an even more impactful learning environment.

  • How I approach collaborative storytelling

    Key takeaways:

    • Collaborative storytelling enhances understanding and connection by allowing diverse voices to merge and share unique perspectives.
    • Key elements for success include open communication, trust among participants, and a shared vision that aligns everyone’s contributions.
    • Creating an effective storytelling environment involves establishing a resonant theme, considering logistics, and allowing time for reflection.
    • Utilizing digital tools like collaborative writing software and interactive elements can significantly enrich the storytelling experience.

    Understanding collaborative storytelling

    Understanding collaborative storytelling

    Collaborative storytelling is a fascinating blend of voices, each contributing their unique perspectives to create a richer narrative. I remember a workshop where participants shared their stories of overcoming adversity, which truly highlighted how diverse experiences can weave together to form a community tale. It made me ponder: how often do we miss out on the depth of understanding by telling our stories in isolation?

    At its core, collaborative storytelling invites individuals to engage deeply with one another. I’ve witnessed moments where a simple idea evolved into something profound simply because different minds brought various elements to the table. Isn’t it eye-opening how one person’s narrative can spark a connection or inspire another’s creativity?

    Creating an environment for collaborative storytelling requires vulnerability and trust among participants. I’ve often felt hesitant to share my thoughts initially, worrying they might not resonate. However, once I opened up, I discovered that sharing allows others to join in with their experiences, fostering a sense of belonging. It’s amazing how storytelling can bridge gaps and build empathy, isn’t it?

    Benefits of collaborative storytelling

    Benefits of collaborative storytelling

    Collaborative storytelling offers a unique opportunity for participants to learn from one another, enhancing their understanding of diverse perspectives. I recall a session where individuals from vastly different backgrounds shared their cultural stories. The simple act of listening transformed my worldview; it struck me how our differences could be celebrated rather than overlooked. Have you ever experienced that moment when someone’s story completely shifts your perception?

    One of the most profound benefits I’ve seen is the sense of community that emerges from shared narratives. In a recent group project, the stories we told not only bonded us but also helped us discover common ground amidst our differences. It felt as if each story laid down a brick, creating a bridge between us. Isn’t it incredible how finding shared experiences can strengthen our connections?

    Moreover, collaborative storytelling fosters creativity by encouraging participants to build upon each other’s ideas. During a recent workshop, I watched as one participant’s tale inspired another to add their twist, transforming a linear narrative into a multifaceted experience. This dynamic interactivity not only sparks imaginative thinking but also makes the final story richer and more engaging. How often do we allow our creativity to flourish through the contributions of others?

    Key elements of successful collaboration

    Key elements of successful collaboration

    One key element of successful collaboration is open communication. In my experience, when team members feel free to express their ideas without judgment, magic happens. I recall a project where I encouraged everyone to share even their wildest thoughts. What came out of that openness was a blend of unique concepts that I could never have imagined on my own. Have you ever noticed how a simple “What do you think?” can open up a floodgate of creativity?

    Trust is another cornerstone of effective collaboration. I remember working with a group where vulnerability was met with support, and that created an atmosphere where everyone felt safe to explore their creativity. I found that when we trust each other to bring our best selves to the table, we build a rich tapestry of ideas. This sense of security leads to deeper connections and a willingness to dive into complex discussions. What do you think happens when trust flourishes in a team?

    Lastly, a shared vision keeps everyone aligned and motivated. In a recent storytelling event, we started by defining our end goal, which helped us channel our individual contributions meaningfully. Without that guiding light, I’ve noticed projects can easily veer off course, becoming disjointed and overwhelming. It’s fascinating how a clear, collective goal can not only streamline the creative process but also strengthen the team’s bond. Have you ever participated in a collaboration that had a clear vision? How did it affect the outcome?

    Planning an effective storytelling event

    Planning an effective storytelling event

    When planning an effective storytelling event, I always start by establishing a strong theme that resonates with the audience. For instance, I once organized a storytelling night focused on overcoming adversity, which connected deeply with participants. The stories that emerged were not just tales; they were shared experiences that ignited empathy and understanding among attendees. Have you ever felt the power of a theme that speaks to a shared struggle?

    Logistics play a critical role too, as they can make or break the experience. I’ve learned that everything from choosing the right venue to setting up the seating arrangement affects how stories are received. One time, I opted for a circle arrangement instead of rows, and I instantly noticed how it transformed the atmosphere. The intimacy of the setting encouraged participants to lean in and engage more fully. What settings have you noticed that helped storytellers feel more connected to their audience?

    Finally, providing adequate time for reflection allows creativity to brew. I now always build in pauses after each storyteller to encourage audience members to digest what they’ve heard. At my last event, this practice led to an unexpected discussion that enriched the experience further. It’s fascinating how giving space to think can deepen connections among participants. Have you ever taken a moment to reflect after a story, only to find new meanings unfolding?

    Engaging participants in storytelling

    Engaging participants in storytelling

    Engaging participants in storytelling hinges on creating an environment where everyone feels comfortable to share. I often encourage contributions by kicking off with a personal story that touches on vulnerability, which provides a model for openness. This approach not only breaks the ice but also invites others to connect through their own experiences. Have you noticed how sharing a little piece of yourself can inspire others to do the same?

    Another effective strategy I’ve employed is incorporating interactive elements, like prompts or themes that participants can choose from. During one session, I handed out cards with different emotions written on them, allowing participants to select one that resonated with their story. The results were amazing; people opened up in ways I never expected, weaving narratives filled with raw emotion and authenticity. How can we create opportunities for deeper expression amongst our storytellers?

    It’s also essential to foster a sense of community during storytelling events. By facilitating small group discussions before the main storytelling begins, I’ve seen participants establish connections that make sharing later feel like an extension of a warm conversation. One time, after these discussions, the room buzzed with excitement and camaraderie, transforming into a supportive space that encouraged vulnerability. Have you ever experienced that moment when you feel completely at ease with strangers, as if you were old friends?

    Tools for collaborative storytelling

    Tools for collaborative storytelling

    When it comes to tools for collaborative storytelling, I have found that digital platforms can really enhance the experience. For instance, I once used an online whiteboard during a workshop, allowing participants to collectively map out their stories visually. It was fascinating to see how their ideas intertwined and transformed into a cohesive narrative, demonstrating the power of collaboration in real-time. Have you ever thought about how much a visual element can add to storytelling?

    Another tool I frequently turn to is collaborative writing software, such as Google Docs. During one event, I set up a shared document where participants could contribute to a story simultaneously. The atmosphere was electric; seeing everyone’s thoughts come together in one place felt like watching a live performance unfold. It made me realize how technology can enhance communication and creativity, allowing voices to blend seamlessly. How does your choice of medium influence storytelling dynamics?

    Lastly, I’ve experimented with storytelling apps that allow for audio or video contributions. I recall a session where participants recorded their stories using their phones, then shared them during our gathering. The vulnerability and authenticity captured in their voices added layers to the narratives that text alone couldn’t convey. This experience reinforced my belief that the right tools can create a safe space for deeper connection—how do you think different formats change the essence of a story?

    My personal storytelling experiences

    My personal storytelling experiences

    I remember my first attempt at collaborative storytelling during a community workshop. The room was filled with diverse participants, each with unique backgrounds and ideas. As we passed a story prompt around, I was struck by how personal experiences began weaving together, creating a tapestry of shared emotions and insights. It was a moment that made me realize how powerful vulnerability can be in storytelling—have you ever felt that connection when stories resonate on a deeper level?

    One experience stands out vividly. During a children’s storytelling session, we invited kids to draw their favorite scenes while sharing their tales. I watched as their imaginations blossomed, their drawings infused with joy and excitement. The energy in the room was tangible; it reminded me how collaboration can breathe life into narratives. Seeing those young storytellers express themselves so freely was heartwarming and made me reflect on how storytelling can foster creativity. Have you witnessed such inspiring moments in your storytelling encounters?

    I’ve also had enriching experiences with intergenerational storytelling events. One time, I paired younger attendees with seniors to share family stories. Watching the exchange was captivating; the blend of youthful curiosity and seasoned wisdom created a unique narrative dynamic. I felt a deep appreciation for the lessons passed down through generations, reinforcing the idea that storytelling is not just about sharing tales, but about preserving legacies. Have you found yourself learning something unexpected from stories shared in such collaborative settings?

  • How I analyze audience reactions

    Key takeaways:

    • Understanding audience reactions involves emotional engagement, body language, and relevance to the content, enhancing educational approaches.
    • Analyzing audience feedback goes beyond numbers, providing deeper insights and fostering a sense of community among participants.
    • Employing various methods, such as surveys and live feedback tools, can reveal valuable audience reactions and improve engagement.
    • Adapting presentations based on feedback, such as adjusting pace and visual aids, significantly enhances understanding and connection with the audience.

    Understanding audience reactions in education

    Understanding audience reactions in education

    Understanding audience reactions in education requires more than just observing classroom behavior; it dives into the emotional responses that students experience. I remember attending a workshop where the facilitator asked us to reflect on a time we felt inspired. The stories shared were often met with laughter and nods of agreement, highlighting a shared yearning for connection and relevance in our learning experiences. Isn’t it fascinating how a simple question can open up such deep emotional engagement?

    When analyzing reactions, I often consider body language and facial expressions as valuable indicators. Once, during a group discussion, I noticed a student’s furrowed brow when a complex topic was introduced. It led me to realize that a change in pace or more accessible explanations could have engaged that student better. This experience reinforced my belief that tuning into these subtle cues can significantly enhance our educational approaches.

    Additionally, I find it crucial to connect reactions to the content’s relevance. During a recent seminar, I observed participants light up when we discussed real-world applications of theoretical concepts. This moment made me think: how often do we bridge that gap in our teaching? Understanding audience reactions is not just about what they say; it’s about recognizing those moments of connection that truly resonate and empower learners.

    Importance of analyzing audience feedback

    Importance of analyzing audience feedback

    Analyzing audience feedback is essential because it reveals the underlying sentiments that numbers and statistics alone cannot capture. I remember leading a focus group after an educational event where I eagerly asked for feedback. The candid stories shared gave me much deeper insights than the survey results. It made me wonder: how often do we discount the power of a personal story in shaping our understanding?

    Furthermore, audience reactions often inform us what truly resonates and what doesn’t in our presentations. One time, I experimented with interactive polling in a workshop. The immediate spike in engagement was exhilarating! Observing real-time responses made me realize that adjusting my approach could significantly enhance learning. This experience underscored the idea that flexibility, based on feedback, is crucial for meeting the needs of diverse learners.

    Lastly, understanding feedback fosters a sense of community and connection among participants. During one particular seminar, a participant felt comfortable enough to share their struggles, leading to a heartfelt discussion. That moment highlighted the importance of creating an environment where voice and emotion matter. Could it be that by valuing feedback, we encourage a richer and more collaborative learning experience?

    Methods for collecting audience reactions

    Methods for collecting audience reactions

    When it comes to collecting audience reactions, surveys are often the go-to method. In my experience, crafting well-thought-out questions can yield valuable insights. I remember designing a post-event survey that included open-ended questions. The responses revealed perspectives I hadn’t considered, transforming my approach for future events. Have you ever been surprised by feedback that changed your entire viewpoint?

    Another effective method I’ve employed is live feedback tools, such as audience response systems. During a recent workshop, I utilized a tool where participants could share their thoughts anonymously in real-time. The immediate reactions helped me understand which concepts sparked interest and which fell flat. It left me thinking about how powerful and revealing immediate feedback can be. Isn’t it fascinating how technology bridges the gap between listeners and speakers?

    Observation plays a crucial role as well. I often find myself watching for non-verbal cues during presentations – nods, smiles, or even the occasional yawn. Once, I noticed a group of participants whispering among themselves. Their animated expressions hinted they were excited about the topic. Recognizing these little moments helps me gauge engagement without needing explicit feedback. How often do we overlook the silent signals our audience sends?

    Tools for tracking audience engagement

    Tools for tracking audience engagement

    When tracking audience engagement, analytics tools can be incredibly revealing. For instance, I once used Google Analytics for an educational event website and was astounded to discover which sessions drew the most traffic. This data allowed me to tailor future content to align better with audience interests. Have you ever considered how a simple analysis could reshape your entire strategy?

    Social media monitoring tools are another great asset. I remember launching a new outreach campaign and using a tool that tracked mentions and interactions across platforms. I was genuinely amazed to see how much people were discussing and sharing our content. The genuine excitement reflected in those conversations provided me with invaluable insights into the audience’s connection with the events. Have you explored how social media could amplify your understanding of audience sentiments?

    Lastly, heatmap tools have been game-changers for me. While optimizing a landing page, I utilized a heatmap to see where users clicked and how far they scrolled. I was surprised to find that key information was being overlooked because it was placed too low on the page. These visual insights enabled me to redesign the layout for better engagement. Isn’t it incredible how minor adjustments can lead to significantly improved audience experiences?

    Techniques for interpreting audience data

    Techniques for interpreting audience data

    Understanding your audience begins with interpreting their reactions, and one effective technique is segmenting data. I’ve found that breaking down audience responses by demographics can reveal fascinating patterns. For example, during an event aimed at both students and professionals, I noticed that students preferred hands-on workshops, whereas professionals gravitated toward networking sessions. Have you considered how breaking your audience into segments could provide better insights for your future events?

    Another technique I’ve employed is comparative analysis. I often compare data from different educational events to see what resonated with audiences. During one analysis, I realized that a particular speaker’s session had a much higher engagement rate than others, not only because of the topic but also due to their interactive presentation style. This made me reflect on how crucial presentation delivery is in capturing attention. What lessons could you learn from comparing different audience reactions?

    Lastly, I leverage audience feedback surveys to directly gauge reactions. I vividly remember a post-event survey where attendees overwhelmingly cited desire for more Q&A sessions. Their enthusiasm in the feedback helped me realize the importance of dialogue over monologue. By focusing on direct feedback, I’ve been able to adapt and improve future events significantly. Have you tapped into the voices of your audience to shape your strategies?

    Adapting presentations based on feedback

    Adapting presentations based on feedback

    When adapting presentations based on audience feedback, I always make it a point to revisit the content after an event. I recall one time when a workshop I led on digital literacy received comments that the pace was too fast. Rather than dismiss it, I took those insights seriously, redesigning the presentation to include pauses for reflection and conversation. Have you ever considered how slowing down can truly enhance understanding?

    Another effective strategy I’ve found is adjusting my visual aids in response to feedback. After a recent session where participants noted they struggled to follow along with the slides, I realized the importance of clarity in visuals. I transformed my slides into more straightforward graphics and fewer text-heavy elements. Isn’t it interesting how a simple change can significantly improve engagement and comprehension?

    Moreover, I always consider the emotional tone of feedback. There was a moment when attendees expressed feeling overwhelmed by the amount of information shared in a session. That stark realization pushed me to distill the core messages of my presentations, focusing on what truly resonated with the audience. How often do you reflect on the emotional signals conveyed in audience feedback to refine your presentation style?

    Personal experiences in audience analysis

    Personal experiences in audience analysis

    One time, I observed a noticeable shift in audience engagement during a live Q&A session. Initially, the room felt stiff, with hands hesitantly raised. But as I encouraged vulnerability by sharing my own struggles with a topic, I saw more people begin to open up. It was a powerful reminder that establishing a personal connection can break down barriers and foster a more interactive environment. How often do we underestimate the impact of our own stories?

    During an educational event, I tried something different: I actively sought out feedback while the session was unfolding. I used quick polls to gauge understanding and sentiments in real-time. It was illuminating to see how responsive the audience became when they knew their input mattered. Have you ever experienced how being attuned to audience reactions can shift the dynamic entirely?

    In another instance, after a presentation that didn’t resonate as well as I’d hoped, I took a step back to analyze the reactions. I realized that I had focused too much on delivering information rather than engaging with the audience’s interests. I reflected on how that disconnect felt for both me and the attendees, leading me to prioritize a more dialogue-driven approach in future events. Aren’t those moments of reflection vital for growth as educators?

  • How I approach partnerships in panels

    Key takeaways:

    • Effective partnerships in events require clear communication, shared goals, and aligned values to foster collaboration and enhance impact.
    • Panels are crucial in education as they provide diverse perspectives and encourage critical thinking among attendees, bridging theory and practice.
    • Building lasting partnerships involves ongoing communication, trust, and celebrating successes together to reinforce relationships and collaborative efforts.
    • Learning from past partnerships emphasizes the importance of clear expectations, role definitions, and acknowledging achievements to strengthen future collaborations.

    Understanding partnerships in events

    Understanding partnerships in events

    When I reflect on partnerships in events, I often think about the synergy that can emerge when likeminded organizations come together. For instance, I once helped coordinate a panel discussion that included educators, tech innovators, and local businesses. Seeing them collaborate was inspiring; they shared resources and ideas that enriched the overall experience for attendees.

    The beauty of partnerships lies in their potential to amplify impact. Can you imagine the difference between hosting an event solo versus with partners who bring their networks? Having additional voices can enhance reach and diversify perspectives, making the event not only more engaging but also more meaningful. I’ve always found that a well-rounded panel can spark conversations that wouldn’t happen if each entity stood alone.

    Trust and clear communication are the cornerstones of successful partnerships in events. I learned this firsthand when a misunderstanding nearly derailed a session I was part of. It reminded me that while excitement builds around collaborations, it’s vital to keep everyone aligned on goals and expectations. After all, what’s a partnership if it doesn’t foster transparency and mutual respect?

    Importance of panels in education

    Importance of panels in education

    Panels play a pivotal role in education by creating platforms for diverse voices to share knowledge and experiences. I remember attending a panel where educators from different backgrounds shared strategies for supporting students with varying needs. The insights shared that day illuminated my understanding of inclusive education and sparked new ideas on how I could implement these strategies in my own teaching.

    The interactive nature of panel discussions fosters critical thinking among attendees. Have you ever found yourself questioning assumptions during a panel? I often engage in lively discussions with peers after a session, and I’ve noticed how these conversations lead to deeper explorations of the topics presented. When experts challenge each other’s viewpoints, it encourages us all to think outside the box and develop a more nuanced understanding of the subject matter.

    Furthermore, panels serve as a bridge between theory and practice. I once witnessed a panel featuring industry leaders discussing real-world applications of educational theories. It was enlightening to see how research can come alive through shared experiences. This connection between academia and practical implementation not only enriches the learning environment but also inspires educators to apply what they’ve learned in their own contexts.

    Steps to identify potential partners

    Steps to identify potential partners

    Identifying potential partners begins with understanding your own objectives. I often take a step back and ask myself what the goals of the panel are. Is it to foster collaboration among educators, or perhaps to introduce innovative teaching methods? This clarity helps me pinpoint organizations or individuals who align with my vision.

    Next, I consider the audience we want to attract. For instance, when planning a recent panel on educational technology, I explored partnerships with tech companies that provide tools suitable for educators. This approach not only enriched the conversation but also attracted participants who were genuinely interested in integrating technology into their teaching. Have you considered what kinds of partners would resonate with your audience? Your partners should ideally share insights that enrich the panel’s topic.

    Finally, I leverage my network to seek recommendations and insights. Reaching out to colleagues often reveals hidden gems—organizations or individuals who may not be on your radar but have valuable perspectives to contribute. I recall asking a friend about potential speakers for a panel, and she mentioned someone whose work I had overlooked but deeply admired. This leads me to realize that sometimes, the best partnerships come from conversations that happen outside formal settings. Have you tapped into your existing connections? You never know where a simple chat might lead you.

    Criteria for selecting effective partners

    Criteria for selecting effective partners

    When it comes to selecting effective partners, I rely heavily on shared values and missions. For example, during a recent panel focused on inclusive education, I ensured that my partners understood and prioritized accessibility. This alignment not only strengthened our message but also created a more cohesive atmosphere during discussions. Have you ever noticed how a shared vision can elevate the conversation?

    Another important criterion is expertise. I remember collaborating with a renowned educational researcher whose insights brought a level of depth that I hadn’t anticipated. Having someone with that kind of knowledge can shift the panel from being informative to transformative. It prompts me to ask: what gaps in knowledge could your partners fill?

    Lastly, I consider the ability of potential partners to engage with the audience. I once partnered with a dynamic speaker who effortlessly made complex ideas relatable. The energy in the room was palpable, and it reminded me of the importance of charisma and connection in presentations. Think about it—are your partners capable of captivating the audience, or will they drone on?

    Building lasting relationships with partners

    Building lasting relationships with partners

    Building lasting relationships with partners hinges on consistent communication. I make it a point to check in regularly, even after the event is over. One time, a simple follow-up call led to a deeper partnership with a tech company, eventually allowing us to create a series of workshops together. It really makes me ponder: how often do we stop and reconnect with our partners after we’ve accomplished our goals?

    Trust is another cornerstone of these relationships. I remember working with a small nonprofit that was hesitant to collaborate at first. By inviting them into our planning process, I could see their confidence grow. We ended up creating an impactful event that not only served our audiences but also strengthened our mutual respect. This experience has taught me: how much transparency do we allow in our partnerships?

    Lastly, I believe in celebrating successes together—no matter how small. I’ll never forget our panel’s success, where I organized a casual dinner with all the partners afterward. Sharing that moment helped us bond, and it reinforced the idea that partnerships are not just transactional; they’re personal too. It leads me to ask: when was the last time you celebrated a win with your collaborators?

    My personal approach to partnerships

    My personal approach to partnerships

    My personal approach to partnerships is rooted in authenticity. For me, it’s crucial to take the time to truly understand the goals and values of my partners. I recall a time when I collaborated with a local community center. We didn’t just jump into planning; we spent hours discussing our missions and aspirations. This investment upfront set the stage for a partnership that felt genuine, which ultimately resonated with our audiences.

    Another key aspect is adaptability. Each partnership is unique, and I’ve learned not to apply a one-size-fits-all method. I remember a project where everything seemed on track until last-minute changes threw us a curveball. Instead of panicking, I convened a brainstorming session to adapt our plans collaboratively. That flexibility not only salvaged the event but also showed my partners that we could pivot together, deepening our relationship. I find myself wondering: how often do we allow space for changes in our joint efforts?

    Finally, I strive to create an environment where feedback flows freely. After hosting a workshop, I make it a point to gather input from my partners. Once, during a debrief, a partner shared an idea that transformed our next event’s format. That moment illuminated the power of collaboration; it made me realize we’re all richer for the insights we bring to the table. So, how can we foster more open dialogues in our partnerships?

    Lessons learned from past partnerships

    Lessons learned from past partnerships

    The most profound lesson I’ve learned from past partnerships is the importance of clear communication. I once worked with a diverse team where everyone had different expectations, and that led to confusion and frustration. It made me realize how crucial it is to establish a shared vision from the outset. Without that clarity, even the most well-intentioned collaboration can falter.

    Another pivotal insight came when I faced a challenge in resource allocation during one of my educational events. My partner and I had assumed we were on the same page about responsibilities, but we quickly discovered a gap that could have derailed our efforts. That experience taught me the value of outlining roles explicitly and checking in regularly. I now ask myself: how can we create a shared accountability framework that ensures we are all aligned from day one?

    Lastly, I’ve found that celebrating small wins together strengthens our partnership. In one memorable event, after overcoming several logistical hurdles, my partner and I took a moment to acknowledge our teamwork. It added a layer of connection that enhanced our collaboration for future projects. This makes me ponder: how often do we take the time to recognize our joint achievements, even the small ones, to nurture our relationships?

  • How I approach balancing depth and brevity

    Key takeaways:

    • Educational events serve as dynamic platforms for knowledge exchange, fostering community and igniting passion for continuous learning.
    • Balancing depth and brevity in communication enhances attendees’ understanding and retention of complex ideas.
    • Adapting content for diverse audiences through clear language and relatable examples increases engagement and connection.
    • Measuring success involves gathering participant feedback, observing engagement levels, and noting post-event connections among attendees.

    Understanding educational events

    Understanding educational events

    When I think about educational events, I often reflect on how they serve as powerful platforms for knowledge exchange. One experience that stands out to me is attending a local workshop where educators shared innovative teaching strategies. It was a vibrant gathering, and the energy in the room reminded me just how impactful face-to-face interactions can be in sparking new ideas.

    These events are not merely lectures; they’re dynamic forums where participants engage actively with experts and each other. I remember a particularly inspiring breakout session where we brainstormed solutions to common classroom challenges. Walking away from that event, I felt not just motivated, but part of a community striving for excellence. Isn’t it fascinating how these connections can ignite a passion for continuous learning?

    Furthermore, understanding educational events involves appreciating their diverse formats, from conferences to webinars. Each format brings its own benefits, allowing accessibility for various audiences. Have you ever thought about how a simple online panel can reach someone on the other side of the world? In my experience, these events cater to different learning preferences, making education more inclusive and enriching for everyone involved.

    Importance of depth and brevity

    Importance of depth and brevity

    Depth and brevity are vital in conveying educational content effectively. I once attended a seminar where the speaker struck a perfect balance between elaborate explanations and succinct summaries. It was refreshing to hear complex ideas broken down into digestible points without losing the essence—true clarity emerges from this harmony.

    When I create content for educational events, I often recall a workshop I facilitated, where I had to summarize intricate theories into a few key takeaways. The participants expressed gratitude for the concise insights; they felt empowered to implement changes immediately. It’s a reminder that while depth offers richness, brevity ensures comprehensibility—a critical combination for fostering understanding.

    Moreover, I often ponder how overwhelming information can deter engagement. Have you ever found yourself zoning out during lengthy presentations? I know I have. Striking the right balance between being thorough and being concise not only keeps the audience’s attention but also enhances retention, ensuring they walk away with meaningful knowledge.

    Strategies for balancing information

    Strategies for balancing information

    When balancing information, one effective strategy is to break content into digestible chunks. I remember a panel discussion I attended where the moderator skillfully guided the conversation, steering complex topics into bite-sized segments. By doing this, the audience remained engaged and could easily absorb the key points without feeling overwhelmed. Have you ever felt lost trying to follow a long-winded lecture? That experience crystallizes the importance of structuring information clearly.

    Another approach is using visuals to complement textual information. I once created a presentation for a workshop that relied heavily on infographics. The graphics didn’t just illustrate my points; they simplified complex ideas into visual narratives. This dual approach not only captured attention but also reinforced learning. It made me realize that a picture is worth a thousand words—especially in education.

    Finally, integrating storytelling can create an emotional connection while keeping information concise. During a recent event, I shared a brief personal story that related to the subject at hand. It elicited laughter and camaraderie among participants. I’ve learned that when you weave narratives into educational content, you not only enhance engagement but also facilitate better retention. Who doesn’t remember a great story long after the facts fade?

    Techniques for concise communication

    Techniques for concise communication

    One effective technique for concise communication is prioritizing clarity in language. I recall taking part in a workshop where the facilitator emphasized using simple words instead of jargon. It was refreshing to hear complex concepts explained in everyday language. When was the last time you struggled to understand a presentation full of technical terms? That struggle can be eliminated by choosing words carefully, making sure that everyone can grasp the essential messages without unnecessary confusion.

    Another method I find valuable is employing bullet points for listing information. I once redesigned the agenda for an educational event I organized, breaking down the schedule into easy-to-read bullet points. This format didn’t just make the agenda clearer; it also allowed attendees to quickly locate what interested them most. Have you noticed how much easier it is to skim through a list than to wade through long paragraphs? That small change in presentation can significantly enhance understanding and retention.

    Lastly, practice active listening during discussions. At a recent seminar, I focused on summarizing key points that others shared rather than jumping in with my own insights right away. This approach allowed me to distill what was most relevant and provide a cohesive takeaway for the group. When I took the time to listen first, it not only streamlined the conversation but also made participants feel valued. Think about the last time you felt truly heard—didn’t that create a more productive dialogue? Balancing brevity with engagement fosters a richer educational experience for everyone involved.

    Personal experiences with educational events

    Personal experiences with educational events

    Participating in a community workshop on public speaking profoundly impacted my understanding of educational events. I remember being anxious about sharing my ideas with others, but the supportive environment encouraged vulnerability. Can you recall a moment when you felt genuinely supported while learning? It was a revelation to discover that embracing imperfections can often lead to the best learning experiences.

    One memorable conference I attended focused on innovative teaching methods. A specific session on experiential learning struck a chord with me; the facilitator used role-playing to illustrate concepts. I left feeling energized and eager to incorporate those techniques into my own practice. Reflecting on that day, I realize how engaging activities can transform passive attendees into active participants. Isn’t it fascinating how a shift in format can spark such enthusiasm?

    I also remember an online seminar that seemed to stretch on endlessly. While the content was intriguing, I found my focus waning during long stretches of lecturing. It served as a critical reminder for me about the importance of pacing and interaction in educational events. Have you ever experienced that disconnect? It made me more aware of how vital it is to balance depth with engagement to maintain participant interest throughout an event.

    Adapting content for diverse audiences

    Adapting content for diverse audiences

    When crafting content for diverse audiences, I often draw from my own experience of attending workshops aimed at varied demographic groups. I remember a panel discussion where the speakers used straightforward language to convey complex ideas to educators and students alike. It made me realize that clarity can bridge gaps. Have you ever felt like you were lost in jargon? Simplifying terminology opens doors for everyone, enriching the learning experience.

    I once witnessed an educational event tailored for international participants where the presenters included cultural references that resonated across borders. By incorporating relatable examples, the facilitators ignited curiosity and connection among attendees. I found it heartwarming to see their eyes light up with understanding. Isn’t it incredible how a few thoughtful adjustments can transform communication?

    In another instance, I attended a seminar geared toward parents and teachers, where breakout sessions allowed tailored discussions based on specific interests. Those smaller groups fostered a more intimate setting for dialogue. It was a revelation to see how focused discussions could lead to meaningful exchanges, making the event resonate more deeply with everyone involved. Have you experienced a moment where focused interaction changed the entire tone of an event? The impact of adaptability, in this scenario, was undeniable.

    Measuring success in educational events

    Measuring success in educational events

    Measuring success in educational events can often feel like navigating a maze. I remember measuring the success of a workshop I hosted by gathering feedback immediately after the sessions. The responses offered invaluable insights, revealing which aspects resonated well with participants and which needed refinement. Have you ever collected feedback and been surprised by the range of responses?

    Another key metric I rely on is participant engagement during sessions. During one particularly interactive seminar, I noticed attendees were not only asking questions but also sharing personal stories related to the topic. This organic exchange indicated to me that the content was hitting home. How often do we overlook the power of storytelling in engagement?

    Lastly, I’ve found that the connection formed between participants after the event can be a crucial measure of success. After a collaborative project event, I saw a group of participants form a study group. This spontaneous connection was a powerful indicator that the event not only educated but also fostered community. It begs the question: Isn’t the real success of an educational event defined by its ability to inspire ongoing learning and collaboration?

  • How I approach diverse panel compositions

    Key takeaways:

    • Diverse panel compositions enhance discussions by incorporating various perspectives, fostering richer dialogues and innovative solutions.
    • Representation should balance diversity with expertise to ensure meaningful contributions in discussions.
    • Inclusive panels create a sense of belonging, particularly for marginalized groups, and prepare participants for a globalized world.
    • Evaluating panel effectiveness through audience feedback and emotional resonance helps improve future events and encourages meaningful connections.

    Understanding diverse panel compositions

    Understanding diverse panel compositions

    Diverse panel compositions are crucial because they bring together a variety of perspectives that enrich discussions and decision-making. I recall attending an educational forum where the panel included voices from different cultural backgrounds and fields of expertise. The energy in the room was electric, and the insights shared were not only enlightening but also challenged preconceived notions I didn’t even realize I had. Hasn’t everyone experienced a moment when a unique viewpoint caused a shift in their understanding?

    When assembling a panel, considerations like gender, ethnicity, age, and professional background play an important role. I once noticed how a younger panelist offered a fresh perspective on digital learning tools, something seasoned educators had overlooked. It made me wonder: how often do we intentionally seek out perspectives that diverge from our own? The reality is that diversity doesn’t just embody visible differences; it encompasses experiences and ideas that resonate deeply with various audiences.

    It’s also about striking a balance between representation and expertise. I’ve seen panels where diversity was prioritized over relevant qualifications, leading to discussions that lacked depth or cohesion. It raises an important question: how do we ensure that the voices we amplify also possess the expertise to contribute meaningfully? In my experience, a well-composed panel is one that carefully considers both the diversity of its members and the richness of their professional journeys.

    Importance of diversity in education

    Importance of diversity in education

    The importance of diversity in education can’t be overstated. I remember attending a workshop where the facilitators came from various educational backgrounds and regions. It struck me how their distinct experiences shaped their teaching methodologies, offering us a wealth of strategies to consider. This made me think: don’t we all benefit when we’re exposed to a broader spectrum of ideas?

    Moreover, diversity fosters a sense of belonging, especially for marginalized groups. I’ve seen firsthand how students light up when they see relatable role models in their educators. It truly resonates when they realize their own stories are valued and reflected in the curriculum. Isn’t it vital for learners to see that their identity contributes to the richness of the educational landscape?

    Lastly, incorporating diverse perspectives prepares us for a globalized world. In my own teaching practice, I’ve found that understanding different cultural viewpoints not only enriches discussions but also cultivates empathy among students. It prompts me to ask: how can we expect our future leaders to navigate an increasingly interconnected world if we don’t expose them to a wide array of voices?

    Benefits of diverse panelists

    Benefits of diverse panelists

    Diverse panelists bring unique insights that can lead to richer discussions and innovative solutions. I recall a conference where a panel composed of educators from different disciplines tackled the same educational challenge. It was enlightening to see how each panelist approached the problem from distinct angles—these varied perspectives not only sparked compelling dialogue but also inspired attendees to think outside the box. Can you imagine the possibilities when we combine so many different lenses?

    One key benefit I’ve observed is that diverse panels create a more inclusive atmosphere for participants. There was an event I attended where a panel included voices from different cultural and socioeconomic backgrounds. The palpable excitement in the room showed me that audience members felt seen and heard. It made me wonder: wouldn’t we all thrive in environments where our experiences are acknowledged and embraced?

    Also, having a range of voices can enhance problem-solving in education. I think back to a roundtable discussion I facilitated, where bringing together educators of varying expertise resulted in creative strategies that I hadn’t considered before. The mix of experiences fostered a collaborative spirit that led to actionable ideas. Isn’t it exciting to realize that working with diverse panelists can open the door to solutions we might not have dreamt of alone?

    Strategies for selecting panelists

    Strategies for selecting panelists

    When selecting panelists, I find that it’s vital to consider not just expertise but also the diversity of experiences. Once, I was tasked with assembling a panel for an educational forum, and I intentionally included individuals from various backgrounds—teachers, administrators, and even parents. The resulting discussions were dynamic, highlighting the nuances in their experiences that I hadn’t anticipated. Have you ever noticed how much richness a panel can bring when different stories intertwine?

    Another strategy I employ is to prioritize the inclusion of emerging voices alongside seasoned professionals. I remember an event where a rookie teacher shared her fresh perspectives alongside a veteran educator. The contrast not only energized the conversation but also made the established ideas more relatable. It’s a reminder that everyone has something valuable to contribute, regardless of their tenure in the field. Isn’t it interesting how blending the old with the new can create a more vibrant dialogue?

    Finally, I believe in actively seeking out panelists who challenge conventional thinking. I once observed a panelist who wasn’t afraid to voice controversial opinions; it led to some of the most engaging questions and debates from the audience. Their boldness sparked a sense of curiosity among attendees, prompting them to think critically instead of passively absorbing information. Isn’t it empowering to know that inviting diverse viewpoints can foster a space where everyone feels inspired to engage?

    Techniques for creating inclusive panels

    Techniques for creating inclusive panels

    Creating inclusive panels requires intentionality in the selection process. One technique I’ve found effective is actively reaching out to underrepresented communities. At one conference, I took the extra step to connect with local organizations that support marginalized voices in education. The result? A panel that not only brought unique perspectives but also resonated deeply with attendees who saw themselves reflected in the discussion. Have you ever felt the impact of hearing someone share your story?

    Another approach involves crafting questions that invite all panelists to share diverse viewpoints. I remember an instance where I posed an open-ended question that encouraged panelists to discuss their personal journeys in education. The conversations that emerged were rich and varied, illuminating challenges and breakthroughs that many in the audience had never considered. Isn’t it fascinating how well-structured questions can unlock hidden insights and spark a more meaningful dialogue?

    Moreover, I emphasize the importance of ongoing training for panelists on inclusivity and equity. I once facilitated a workshop for an upcoming panel that focused on fostering an inclusive environment for discussion. The willingness of the panelists to engage in this preemptive dialogue not only enhanced their understanding but also set a precedent for respectful and thoughtful exchanges during the event. Don’t you think that investing in preparation can significantly elevate the quality of panel interactions?

    Personal experience in panel composition

    Personal experience in panel composition

    Selecting the right individuals for a panel is not just about filling slots; it’s about weaving a tapestry of experiences that can resonate with the audience. I recall a particular event where I meticulously chose panelists from various educational backgrounds, including a teacher from a rural school and an administrator from an urban district. Hearing them share their starkly different experiences created a dynamic atmosphere that sparked passion in the room—something I believe is vital for engaging an audience. Have you ever noticed how contrasting viewpoints can energize conversations in ways that one singular perspective cannot?

    While I sometimes focus on the diversity of lived experiences, I also consider the varied expertise each individual brings to the table. In one memorable panel, I included a seasoned educator, an innovative tech entrepreneur, and a student leader. This mix encouraged a powerful discussion about the future of education that drew in attendees from all levels of interest and engagement. It reminded me how vital it is to create a rich learning environment where everyone—whether an expert or novice—feels they have a stake in the conversation. Doesn’t it energize you to think about the multitude of ideas that can arise from such a diverse group?

    Even the way I facilitate these discussions plays a crucial part in the overall experience. I make it a practice to check in with each panelist before the event, encouraging them to share what they hope to discuss. This dialogue not only prepares them but also allows me to see where their passions align. I must say, there’s something incredibly fulfilling about setting the stage for panelists to shine in their unique ways while fostering an environment where every voice contributes to a richer narrative. Isn’t that what we all strive for in meaningful conversations?

    Evaluating panel effectiveness after events

    Evaluating panel effectiveness after events

    Evaluating the effectiveness of a panel after an event can be a revealing experience. I often look at audience engagement through metrics such as participation and feedback. For instance, after one event, I was pleasantly surprised to find that our post-panel survey indicated that attendees not only appreciated the diversity of perspectives but also felt inspired to engage with the topics discussed. How do we measure inspiration, I wonder? It often shows up in the follow-up conversations and initiatives that arise in the days and weeks after the event.

    Listening to audience reactions in real time gives me instant feedback, but I also review recordings to catch nuances I might have missed during the live event. In one instance, I noticed that a question posed to the panel elicited unexpected enthusiasm, which encouraged me to adjust the format for future panels. I realized how pivotal that moment was; it demonstrated that the audience craved dialogue over monologue. Do we truly create spaces for connection, or do we sometimes let our agendas overshadow the voices in the room?

    Finally, reviewing panel effectiveness entails reflecting on the overall atmosphere created within the event. After a particularly vibrant session, attendees approached me to express how they felt seen and heard. This emotional resonance is a key indicator of success. I always ask myself: Did our panel not just inform but also inspire? If the answer is yes, then I know I’ve achieved my goal in fostering an environment that embraces diverse viewpoints. Isn’t it rewarding to cultivate spaces where every participant feels a sense of belonging?

  • How I amplify unheard voices in discussions

    Key takeaways:

    • Creating inclusive spaces encourages marginalized voices to contribute, enriching discussions through diverse perspectives.
    • Using open-ended questions and interactive elements can engage participants and foster deeper connections.
    • Sharing personal experiences can create empathy, encouraging others to open up and enhancing the overall dialogue.
    • Evaluating participant engagement and feedback is crucial for understanding the impact of discussions and identifying areas for improvement.

    Understanding unheard voices

    Understanding unheard voices

    Unheard voices often come from marginalized groups, individuals whose perspectives are overlooked in discussions. I remember attending a panel where a quiet participant finally spoke up, only to share experiences that resonated deeply with many, yet were invisible in mainstream conversations. This moment made me realize just how crucial it is to create space for those who feel silenced.

    Understanding these voices means recognizing not just the words spoken, but the emotions behind them. I’ve often found that when someone shares a personal story, it carries weight—a blend of vulnerability and strength that can shift the dynamics of any discussion. How often do we pause to consider the feelings that lie beneath the surface of someone’s silence?

    In my experiences, I’ve seen how powerful it can be when we intentionally seek these voices in our discussions. By asking open-ended questions and genuinely listening, we not only amplify their messages but enrich our understanding of a more complex world. It’s fascinating to think about how much we miss when we assume everyone is represented. Don’t you think it’s time we change that narrative?

    Importance of amplifying voices

    Importance of amplifying voices

    Amplifying unheard voices is critical because it fosters inclusivity and understanding. I recall a workshop where an individual from a non-traditional background shared their take on educational reform. Their perspective not only challenged the status quo but opened my eyes to alternative solutions I hadn’t considered before. Isn’t it amazing how a different viewpoint can spark creative ideas and discussions?

    When we give space to the unheard, we validate their experiences, and that validation can empower individuals and communities. In my own journey, I’ve witnessed shy participants blossom when encouraged to contribute. I often wonder, what if we consciously sought out diverse voices in every conversation? The depth of discourse we could achieve would be tremendous.

    Moreover, amplifying these voices helps us address systemic inequalities. I think back to community events where traditionally marginalized individuals shared their stories, shedding light on educational barriers. It made me realize that the narratives we hear shape our policies and practices. If we ignore these voices, how can we hope to create equitable solutions?

    Strategies for inclusive discussions

    Strategies for inclusive discussions

    To foster inclusive discussions, it’s essential to create an environment where everyone feels safe to share their thoughts. I once attended a community forum where the facilitator started with a simple affirmation: “Every voice here matters.” This small gesture encouraged participants who often held back to speak up, transforming the room from a hesitant space to a vibrant tapestry of ideas. Could such a shift really be as simple as ensuring participants feel valued?

    Another effective strategy involves actively inviting quieter members into the conversation. In one meeting, I noticed a colleague who typically stayed silent, so I directed a question specifically to her. The moment she began to speak, the entire group leaned in, eager to hear her insights. This experience taught me that sometimes, all it takes is a little nudge to unlock profound contributions from those who may feel unheard.

    Additionally, considering diverse formats for discussions can amplify underrepresented voices. I recall organizing a workshop that incorporated small group discussions alongside larger group shares. This structure allowed for varying levels of comfort, and I was truly moved when a timid yet brilliant participant shared her story in her small group, later inspiring a powerful dialogue when it was brought to the larger audience. Isn’t it incredible how adapting our approach can reveal hidden perspectives?

    Techniques for engaging participants

    Techniques for engaging participants

    One potent technique for engaging participants is the use of open-ended questions. During a recent seminar, I posed a question designed to spark creativity: “What would you change if you could redesign our approach entirely?” The responses flowed, with participants drawing from their unique experiences. I was amazed at how this simple shift brought forth diverse viewpoints that had previously remained unspoken. Have you ever noticed how such questions can unlock potential?

    Another effective method is to incorporate interactive elements, like polls or live quizzes, that invite immediate participation. In an event I organized, we used real-time polling to gauge opinions on various topics. This not only energized the atmosphere but also gave everyone a chance to contribute anonymously. Watching the responses roll in demonstrated how technology could bridge gaps, making even the quietest attendees feel connected to the discussion. Isn’t it fascinating how technology can enhance engagement?

    Creating opportunities for peer-to-peer sharing can also elevate conversations. I once facilitated a session where participants paired up to share their ideas before bringing them to the group. The moment people exchanged thoughts in a more intimate setting, I saw barriers diminish. It became clear that when individuals feel they can freely share with one or two others, they are more likely to voice their perspectives in a larger group. Have you experienced a similar transformation in group discussions?

    Sharing personal experiences

    Sharing personal experiences

    Sharing personal experiences can truly reshape discussions. I recall a workshop where I invited participants to recount challenges they faced in their careers. As each story unfolded, I noticed a shift in the room—the tension dissolved. It was as if those personal narratives created a bridge, allowing vulnerability to foster connection among everyone present.

    In another instance, I shared my own story of overcoming a fear of public speaking. This revelation encouraged others to open up about their insecurities. Their responses were heartfelt, creating a safe space that encouraged even the most reserved individuals to share. It’s fascinating how a single personal experience can act as a catalyst for others to step into the light. Have you ever watched this phenomenon unfold in your own interactions?

    Furthermore, I’ve found that stories often highlight shared values, enhancing empathy. During a panel discussion on inclusivity, I shared a moment when I felt excluded and how it motivated my passion for ensuring everyone’s voice is heard. The reaction was immediate; people nodded in understanding, and several shared similar experiences. When we connect on a personal level, the dialogue deepens. Isn’t it powerful how vulnerability can spark empathy and create a richer conversation?

    Creating supportive environments

    Creating supportive environments

    Creating supportive environments is essential for amplifying unheard voices. In one of my recent group discussions, I noticed how crucial physical space can be. We arranged the seating in a circle, inviting openness and eye contact. The energy in the room shifted as participants felt a sense of equality; no one was at the head of the table. This simple adjustment sparked more engagement and made everyone feel their contributions mattered. Have you ever felt more comfortable in a circle than facing a traditional setup?

    Moreover, I’ve learned how important it is to establish ground rules that promote respect and active listening. In my experience, when I clearly communicated expectations about valuing each person’s input, the atmosphere transformed. One participant confessed that they had often felt dismissed in previous meetings. With these new norms in place, I witnessed a profound change; they began to share ideas without hesitation. Doesn’t it make you wonder how often unspoken guidelines can stifle innovation?

    At another event, during a pause in the discussion, I encouraged participants to silently reflect on their feelings before speaking. I observed a remarkable quietness, as each individual took a moment to gather their thoughts. This practice not only showed that their voices were valued, but it also fostered deeper connections within the group. Isn’t it incredible how just a few moments of intentional reflection can lead to richer, more meaningful dialogue?

    Evaluating impact of discussions

    Evaluating impact of discussions

    Evaluating the impact of discussions requires a keen awareness of how participants engage with one another. At a recent seminar, I took the time to survey attendees after our discussion. The responses revealed not only what resonated with them but also highlighted voices that still felt unheard. It’s enlightening to see how feedback can illuminate gaps in communication – don’t you think the reflections of participants are the real measure of a discussion’s success?

    I’ve found that analyzing body language can provide invaluable insights into participant engagement. After one discussion, I noticed that certain individuals leaned in during specific topics while others became visibly withdrawn. This non-verbal feedback made me realize the importance of revisiting those subjects in future meetings. How often do we overlook these subtle cues that signal enthusiasm or disengagement?

    Tracking the evolution of discussions over time also sheds light on their impact. I made it a point to revisit key themes from previous sessions in a follow-up workshop. The shifts in participants’ confidence and willingness to share new ideas were striking. Witnessing this growth reinforced my belief that evaluating discussions is not a one-time effort; it’s an ongoing journey. Wouldn’t you agree that understanding progress is essential for fostering an inclusive dialogue?

  • How I amplify the importance of emotional safety during discussions

    Key takeaways:

    • Emotional safety fosters an environment where individuals can express thoughts and feelings without fear, leading to deeper connections and creativity.
    • Establishing ground rules and check-ins encourages openness and respect, enhancing emotional safety in discussions.
    • Active listening and reflective pauses deepen understanding and trust, making participants feel valued in conversations.
    • Using physical tools like “talking pieces” and inclusive language promotes a supportive atmosphere and encourages participation.

    Understanding emotional safety

    Understanding emotional safety

    Emotional safety is about creating an environment where individuals feel secure enough to express their thoughts and feelings without fear of judgment or retaliation. I remember attending a workshop where participants shared their personal stories and vulnerabilities; it was transformative. The openness fostered a deep connection amongst us, proving that emotional safety isn’t just a concept—it’s a powerful catalyst for genuine conversation.

    When discussing sensitive topics, have you ever noticed how a supportive atmosphere can change the entire dynamic? I’ve seen discussions flourish simply by setting clear expectations that respect and empathy are paramount. By allowing individuals to voice their concerns without interruption, we create a space where ideas can flow freely and creativity can thrive.

    Emotional safety also means recognizing the impact of our words and actions. During a recent group discussion, one participant hesitated to share due to previous negative experiences in similar settings. It struck me how vital it is to acknowledge these past encounters; they shape our willingness to engage openly. By actively listening and validating each other’s feelings, we can cultivate a space that not only honors personal experiences but encourages the sharing of diverse perspectives.

    Strategies for fostering emotional safety

    Strategies for fostering emotional safety

    Creating ground rules is one effective strategy for fostering emotional safety. I once participated in a discussion where the facilitator encouraged us to establish our own guidelines. We agreed on principles like “no shaming” and “respectful listening,” which made everyone feel protected. Isn’t it amazing how simply outlining these boundaries can lead to greater openness? It changes the atmosphere entirely, allowing for deeper connections.

    Another approach that I find crucial is check-ins at the beginning of discussions. During a recent seminar, we took a moment to gauge everyone’s feelings, and it transformed our interaction. People shared not just their thoughts but their emotional states. This practice encourages vulnerability and invites participants to connect on a deeper level. How often do we overlook the emotional readiness of our group before diving into discussions?

    Additionally, I’ve learned that using “I” statements can significantly enhance emotional safety. When participants speak from their own experiences rather than making generalized statements, it minimizes defensiveness. For instance, I shared a personal story about my struggles with feedback, and it opened the door for others to share similar experiences. This method humanizes the conversation and fosters trust, creating a richer dialogue where everyone feels valued and heard.

    Techniques for effective discussions

    Techniques for effective discussions

    One effective technique I’ve discovered is the use of active listening. During a workshop about communication styles, I observed how participants who genuinely listened to one another created a more supportive environment. When someone else spoke, many practiced paraphrasing their points. This simple act conveyed that their thoughts mattered, and it helped build trust. Have you had moments where you felt truly heard? They can be transformative.

    In addition, integrating reflection breaks can profoundly enhance discussions. I remember facilitating a group where we paused every 20 minutes to reflect on what had been said. It allowed participants to process emotions and articulate their thoughts better. Did you know that taking these short pauses can encourage deeper insights? When we give ourselves a moment, we often realize our emotions influence our opinions significantly.

    Lastly, storytelling can be a powerful technique. I recall a time when a colleague shared a difficult experience related to a project. As she narrated her journey, the room transformed; everyone became more engaged and willing to share. Stories resonate on an emotional level, breaking barriers and inviting connection. Why do stories have such an impact? They remind us of our shared humanity, fostering a sense of belonging and understanding in the discussion.

    Creating a supportive environment

    Creating a supportive environment

    Creating a supportive environment is essential for any meaningful discussion. I always encourage participants to express their thoughts freely without fear of judgment. I remember leading a workshop where one participant hesitated to share because of past criticism. When I reassured her that the space was safe, she opened up, and the group rallied around her. Doesn’t it feel empowering to voice your feelings in a trusting setting?

    Another important aspect is the physical setup of the space. In one seminar, we rearranged the seating into a circle instead of rows. This subtle change fostered a sense of equality and openness. Everyone was more likely to engage when they could see each other’s faces, creating an environment that felt intimate and connected. Have you noticed how the configuration of a space can impact the energy?

    Moreover, being mindful of language plays a vital role in creating emotional safety. I learned this the hard way during a panel discussion when certain phrases unintentionally dismissed some attendees’ experiences. Afterward, I made it a priority to encourage inclusive language that respects everyone’s feelings. How do you think our choice of words shapes the comfort level in conversations? It’s fascinating to realize that even small adjustments can help nurture a more supportive atmosphere.

    Personal experiences with emotional safety

    Personal experiences with emotional safety

    Reflecting on my experiences with emotional safety during discussions, I recall a time when I facilitated a book club that focused on sensitive topics. One evening, a member shared a deeply personal story about loss, and I could feel the weight of vulnerability in the room. Rather than rushing the conversation, I took a moment to acknowledge the emotional gravity of her words, allowing others to express their support. It struck me how a small act of validation can create an expansive sense of belonging.

    In another instance, I was part of a workshop that included a role-playing exercise. Participants were encouraged to express their thoughts from different perspectives. I remember feeling apprehensive at first, but once I slipped into the shoes of another character, I discovered how powerful it felt to be heard, even when voicing discomfort. Isn’t it incredible how stepping outside ourselves fosters empathy and connection? That experience opened my eyes to how emotional safety isn’t just about avoiding harm, but also about embracing vulnerability.

    I’ve also seen emotional safety manifest through accountability. During a training session, one individual apologized for interrupting others. Instead of criticism, we validated his effort to improve. This candid exchange underscored that emotional safety thrives on feedback that fosters growth. Do you think it’s possible to truly learn without a safe space for mistakes? I believe it’s crucial to see each error as a stepping stone toward deeper understanding.

    Tools for enhancing emotional safety

    Tools for enhancing emotional safety

    One effective tool I’ve seen in action is the use of ‘talking pieces’ during discussions. When I facilitated a discussion where each participant could speak only while holding a specific object, I noticed an immediate shift in the atmosphere. This simple approach granted everyone the chance to share their thoughts without interruption, cultivating a deeper sense of respect and consideration. Don’t you think having a physical reminder of whose turn it is to speak can ease the tension that often arises in discussions?

    In another scenario, I implemented ground rules before starting a sensitive workshop. We collectively agreed on principles such as confidentiality and no interrupting others. I remember participants actively nodding, feeling reassured by our shared commitment to maintain a safe emotional environment. Isn’t it fascinating how clearly defined expectations can empower individuals to express their feelings freely?

    Additionally, I discovered the value of reflective listening as a means to enhance emotional safety. During a personal development session, I encouraged participants to paraphrase what the previous speaker had shared before responding. I was amazed at how this created a ripple effect of understanding and acknowledgment among the group. Could it be that by truly hearing one another, we not only validate opinions but also reinforce emotional bonds? In my experience, those connections are vital for any fruitful discussion.

  • How I amplify stakeholder voices during panels

    Key takeaways:

    • Creating an inclusive atmosphere encourages quieter stakeholders to share valuable insights, fostering innovative solutions.
    • Utilizing techniques like anonymous feedback and breakout sessions enhances participation and engagement among all panelists.
    • Preparing stakeholders with pre-event materials and clear expectations empowers them to contribute meaningfully to discussions.
    • Measuring the impact of stakeholder involvement through feedback and observation highlights the correlation between inclusion and engagement levels.

    Understanding stakeholder voices in panels

    Understanding stakeholder voices in panels

    Understanding stakeholder voices in panels is crucial for fostering inclusive conversations. I remember attending a panel once where a timid participant hesitated to share their thoughts, feeling overshadowed by louder voices. That moment highlighted for me the importance of creating an atmosphere where every stakeholder feels empowered to express their viewpoint.

    It’s fascinating how stakeholder perspectives can vary vastly, yet each voice holds unique value. Have you ever noticed how often crucial insights come from those who don’t always command the room? In my experience, by actively inviting quieter participants to share their ideas, I’ve often uncovered innovative solutions that would have otherwise gone unheard.

    Navigating these discussions requires empathy and awareness. I once found myself in a situation where a stakeholder’s emotional connection to the topic shifted the entire panel’s dynamic. The palpable passion in their words resonated with everyone present, reminding me that stakeholder voices are more than just opinions—they are heartfelt stories that can drive meaningful change when given space to shine.

    Importance of amplifying voices

    Importance of amplifying voices

    Amplifying voices in panels is essential because it creates a richer dialogue that benefits everyone involved. I recall being part of a panel discussion where the silence from certain members was palpable. It struck me how valuable those unspoken thoughts might have been if only we had encouraged everyone to chime in. Have you ever felt a conversation falter because not everyone felt comfortable contributing?

    Considering the emotional weight behind each voice can transform the way we approach these discussions. I once listened to a participant share their perspective on a sensitive issue, and their vulnerability sparked an immediate connection with the audience. It made me realize that these moments, where individuals share their truths, can lead to transformative discussions. Isn’t it amazing how one voice can resonate so deeply that it shifts our understanding?

    When we prioritize amplifying others, we not only invite diverse perspectives but also validate their experiences. I remember a panel where, after highlighting quieter speakers, the energy shifted and engagement soared. It reminded me that when people see their voices valued, they are more likely to engage fully. Isn’t this the kind of environment we want to foster in every educational setting?

    Effective strategies for engaging stakeholders

    Effective strategies for engaging stakeholders

    Engaging stakeholders effectively requires creating an atmosphere where everyone feels safe to share their ideas. I once organized a workshop where we used anonymous digital tools for feedback. This approach not only encouraged the quieter participants to voice their thoughts but also revealed insights that I never would have anticipated. How often do we underestimate the value of anonymity in discussions?

    Another strategy that I’ve found impactful is implementing breakout sessions. During a recent educational event, breaking the larger group into smaller discussions allowed participants to dive deeper and share experiences relevant to them. I’ve noticed that when people converse in smaller groups, they tend to be more open and engaged. Have you ever experienced that magic when a small group forms a tight-knit conversation?

    In addition to these methods, actively prompting stakeholders with tailored questions can be incredibly effective. I remember a panel where I asked targeted, personal questions to the audience based on their backgrounds, and the room transformed. The dialogue became richer, and the energy shifted as people felt encouraged to engage on a level that was meaningful to them. Isn’t it remarkable how just a few well-phrased questions can unlock a treasure trove of ideas?

    Preparing stakeholders for participation

    Preparing stakeholders for participation

    Preparing stakeholders for participation requires thoughtful facilitation to ensure everyone feels comfortable expressing their views. I recall a time when I prepared stakeholders by sharing a pre-event questionnaire that invited them to voice their expectations and concerns. By doing this, not only did I gain valuable insights into their priorities, but I also established a mutual understanding before the event. Isn’t it amazing how a little preemptive communication can set the stage for deeper engagement?

    Another crucial step is to provide stakeholders with relevant background material that resonates with their experiences and interests. I once sent out articles and case studies tailored to each participant’s field, which ignited discussions during the panel. When stakeholders perceive that their expertise is valued and relevant, they are more likely to contribute. Have you ever noticed how informed individuals can bring an entirely new perspective just by feeling connected to the topic?

    Lastly, setting clear expectations about participation can empower stakeholders. I remember discussing the panel format with participants beforehand, outlining how their input would shape the conversation. When they understood that their voices held value, I could see the enthusiasm grow as they prepared to engage. This simple act of clarity often transforms passive attendees into active contributors. How impactful is it when people realize they are instrumental in driving the dialogue?

    Techniques to facilitate panel discussions

    Techniques to facilitate panel discussions

    One effective technique to facilitate panel discussions is to encourage an open dialogue by using icebreakers. I once introduced a simple question at the start of a panel: “What inspired you to pursue your field?” The responses sparked immediate connections between panelists and set a more relaxed atmosphere. It’s interesting how a light-hearted inquiry can break down barriers and elevate the energy in the room. Have you ever seen how quickly a group can transform when they share personal stories?

    Using active listening techniques is another essential approach. During a panel I facilitated, I made it a point to summarize what speakers said before posing the next question. This not only reinforced their contributions but also made them feel heard and acknowledged. I noticed that this practice encouraged panelists to engage more deeply with each other’s ideas. Isn’t it remarkable how validating someone’s input can create a ripple effect of interaction?

    Lastly, strategically utilizing open-ended questions can lead to richer discussions. I recall a session where I asked, “How can we innovate in our respective fields?” The answers illuminated diverse perspectives and ignited a lively exchange. It made me realize how empowering it can be for participants to reflect on broader implications. Have you experienced how a single question can unlock a treasure trove of insights?

    Personal experiences from past events

    Personal experiences from past events

    At a recent educational event, I vividly remember a moment that underscored the importance of amplifying stakeholder voices. I invited a participant from the audience to share their experience, which sparked an unexpectedly profound conversation about barriers in education. It was eye-opening to witness how their story resonated with others and shifted the focus of the panel, bringing new dimensions to our discussion. Have you ever noticed how a single voice can shift the tone and energy of an entire session?

    During another panel, I made it a point to utilize a round-table format, allowing everyone to contribute equally. One attendee shared their innovative approach to community engagement—something I hadn’t considered before. Their insights were both refreshing and motivating, proving that every stakeholder has something valuable to offer. Isn’t it fascinating how these shared experiences can lead to collective learning?

    I also recall a panel where I introduced brief breakout sessions for smaller groups to discuss their thoughts. This method led to richer discussions when we regrouped. Participants felt empowered to share their ideas with the larger audience, often surprising me with the depth of their insights. I believe these types of engagements foster a sense of belonging and collaboration, which is vital in educational settings. How often do we create spaces where everyone feels valued?

    Measuring impact of stakeholder involvement

    Measuring impact of stakeholder involvement

    Measuring the impact of stakeholder involvement can be as simple as asking for feedback after an event. I once implemented a short survey to capture participants’ thoughts on the discussions and their feelings of inclusion. The results were enlightening: many expressed that they felt more valued and included, which directly correlated to their engagement levels during the panel. Have you considered how a few questions can reveal so much about the effectiveness of your approach?

    Another approach I’ve taken is to observe the dynamics of audience participation during the event. I remember a panel where I noticed an attendee who initially seemed hesitant to voice their opinion. However, as the discussions progressed and other stakeholders shared personal stories, they became increasingly involved. What struck me was the unmistakable shift in their confidence, illustrating how inclusion not only encourages voices to be heard but also fosters personal growth.

    Finally, I believe in assessing the long-term effects of stakeholder contributions. After a series of panels, I followed up with participants several months later to see how their insights influenced their practices. To my surprise, many had implemented new strategies in their work based on dialogues we had. This ripple effect solidified my belief in the power of stakeholder voices. Isn’t it rewarding to see that impactful conversations lead to tangible changes?

  • How I advocate for responsible discussion practices

    Key takeaways:

    • Creating an inclusive environment through responsible discussion practices fosters active listening and empathy, enhancing dialogue and preventing conflict.
    • Engaging participants with interactive elements, storytelling, and personal connections transforms discussions into collaborative experiences.
    • Utilizing feedback actively informs improvements in educational events, aligning discussions with participant preferences and enhancing engagement.
    • Fostering respectful dialogue involves active listening, maintaining composure, and encouraging questions to promote open and productive conversations.

    Understanding responsible discussion practices

    Understanding responsible discussion practices

    Responsible discussion practices involve creating an environment where everyone feels valued and heard. I remember attending a seminar where an impassioned participant veered off the topic. Instead of dismissing them, we redirected the conversation while respecting their perspective. This experience taught me how crucial it is to maintain focus while also ensuring that people feel their voices contribute to the dialogue.

    Have you ever felt silenced in a conversation? I certainly have, and it’s uncomfortable. Responsible discussion practices encourage active listening and empathy, allowing participants to engage deeply with varying viewpoints. I find that when we actively listen to others, it opens doors for richer conversations and helps prevent feedback from becoming combative.

    When I participate in discussions, I prioritize clarity and respect. For instance, I make an effort to clarify my points with relatable examples. This not only keeps the dialogue accessible but also fosters understanding among diverse perspectives. It’s fascinating how a simple shift in approach—like asking open-ended questions—can transform a discussion from a debate into a collaborative exploration of ideas.

    Importance of responsible discussions

    Importance of responsible discussions

    Engaging in responsible discussions is vital because it cultivates a community where everyone feels empowered to share. I recall a workshop where a quiet participant finally raised their hand to share a personal story. The room became charged with energy, and suddenly, their vulnerability opened up the floor for others to share similar experiences. It reminded us all how crucial it is to create a safe space for expression.

    Consider this: when participants feel respected and engaged, the quality of the dialogue improves dramatically. In one of my discussions about sensitive topics, someone expressed a controversial opinion that sparked tension. Instead of dismissing it outright, we encouraged further exploration of their perspective. This not only eased the tension but deepened our understanding of the issue at hand. It’s interesting how the presence of thoughtful discourse can turn potential conflicts into opportunities for growth.

    Moreover, fostering responsible discussions can lead to innovative solutions. During a group project debate, we embraced different viewpoints, which initially seemed opposing. As we navigated through respectful dialogue, we found common ground and even developed ideas that none of us would have considered alone. This taught me that responsible discussions can indeed serve as a breeding ground for creativity, transforming diverse perspectives into collaborative breakthroughs.

    Organizing educational events effectively

    Organizing educational events effectively

    When organizing educational events, it’s essential to set clear objectives that align with your audience’s interests. I once planned a seminar focused on digital literacy, not realizing that many attendees were more interested in practical coding skills. Once I adjusted the agenda to include hands-on workshops, participation skyrocketed, and the event buzzed with enthusiasm. It’s fascinating how understanding the needs of your audience can transform an event from mundane to memorable.

    Another crucial aspect is the importance of skilled facilitators. I remember attending a panel discussion led by a moderator who understood how to balance different viewpoints. Their ability to navigate the conversation kept everyone engaged and made even the most complex topics accessible. It struck me then how a good facilitator can create an atmosphere where diverse opinions are not just tolerated but genuinely appreciated. How often do we overlook the power of a skilled guide in our discussions?

    Lastly, logistical details can make or break the event’s effectiveness. At a recent conference I organized, I underestimated the importance of technology setup. When we faced technical difficulties, the flow of the presentation was disrupted, and the energy in the room waned. It was a lesson learned: seamless logistics ensure that the focus remains on learning. After all, how can we expect engaging discussions when the basic framework isn’t supporting them?

    Strategies for engaging participants

    Strategies for engaging participants

    One effective strategy for engaging participants is to incorporate interactive elements like polls and breakout discussions. During a workshop I led, I introduced live polls to gather immediate feedback on participants’ opinions. The atmosphere shifted from passive listening to active involvement, as attendees were eager to see how their views compared with others. It made me wonder—how often do we miss out on these spontaneous conversations that can lead to richer insights?

    Another approach is to integrate storytelling into your presentations. I vividly recall a time when I shared a personal experience related to the topic at hand. The room fell silent, and I could see the audience leaning in, eager to connect with my narrative. Stories have a unique power to humanize information, but why do we shy away from them in formal settings? By making content relatable, we invite participants to invest emotionally in the discussion.

    Lastly, fostering a sense of community is paramount. I once attended an event where attendees were given nametags with personal prompts, like “What’s your favorite book?” This small detail sparked conversations that went beyond the typical networking chatter. It made me think: could simple strategies like these reshape our interactions? When people feel welcomed and valued, they’re more likely to contribute, transforming a single event into a collaborative experience.

    Utilizing feedback for improvement

    Utilizing feedback for improvement

    Utilizing feedback is essential for enhancing the quality of educational events. I always make it a point to gather feedback after each session. One time, I received a comment about the clarity of my explanations. This prompted me to rethink how I presented complex concepts. It was a lightbulb moment for me; I realized that feedback isn’t just criticism but a pathway to growth.

    Incorporating this feedback led me to adjust my teaching methods, making them more participant-centered. During one workshop, I asked participants to rate the effectiveness of various activities on sticky notes. The insight was eye-opening. I discovered that while I valued group discussions, many preferred hands-on activities. Seeing this made me reconsider how I structure events to align with participants’ preferences.

    Engaging with feedback also creates a cycle of improvement. After implementing changes based on past insights, I noticed a palpable shift in participant engagement. I found myself pondering—how often do we genuinely analyze feedback? By actively responding to participant input, I foster an environment where everyone feels like their voice matters, ultimately enriching the learning experience for all involved.

    Personal experiences in advocacy

    Personal experiences in advocacy

    Advocacy can be an incredibly personal journey, often shaped by our own experiences and interactions. I remember my first time speaking up during a community forum about how educational discussions often left quieter voices unheard. My heart raced as I shared my thoughts, but the encouragement from peers reminded me that advocating for beneficial dialogue can spark change. It was a turning point; I realized that my voice could influence others to share theirs, making our discussions richer and more inclusive.

    In another instance, I found myself at a panel discussion where the emphasis was on fostering respectful debate. I passionately engaged with the speakers, sharing my own observations about the importance of empathy in discussions. The moment I saw a shift in audience reactions—nodding heads, engaged expressions—was truly rewarding. It validated my belief that when we share our lived experiences, we can connect on a deeper level. Have you ever felt that rush of connection when your words resonate? For me, it was a reminder that advocacy often begins with personal stories.

    A particularly profound experience occurred when I facilitated a workshop on respectful dialogue techniques. Initially, I struggled to draw in participants who seemed hesitant to engage. However, when I opened up about my own missteps in discussions—like talking over someone during a heated debate—they began to share their experiences. It reinforced the idea that vulnerability can be powerful in advocacy. I left that day with a renewed appreciation for the role personal narratives play in fostering responsible discussion practices. How can our own stories pave the way for more meaningful conversations? In my case, they certainly have.

    Tips for fostering respectful dialogue

    Tips for fostering respectful dialogue

    One effective tip for fostering respectful dialogue is to actively listen. I once attended a workshop where listening exercises were emphasized, and I was amazed at how simply giving my full attention changed the dynamics. Instead of waiting for my turn to speak, I practiced reflecting back what others said, which not only made them feel valued but also ensured that my responses were more thoughtful. Have you experienced how powerful it can be to truly hear someone?

    Another key aspect is maintaining a calm and open demeanor, even when discussions become heated. I recall a disagreement during a group project; rather than raising my voice to assert my point, I took a deep breath and reminded myself to focus on the issue, not the emotions. This approach not only helped de-escalate tension but also encouraged others to express their views respectfully. It’s intriguing how our body language can either invite dialogue or create barriers, don’t you think?

    Encouraging questions is also vital in creating respectful discussions. I learned this during a community meeting when I started asking open-ended questions instead of making statements. For instance, instead of saying, “This is the problem,” I would ask, “What are your thoughts on this situation?” The shift was remarkable; participants became more engaged and felt empowered to share their perspectives. I’ve found that fostering a culture of curiosity can make all the difference in how discussions unfold. Have you tried asking questions to unlock deeper conversations?