Title: hitkodev's Replies | WordPress.org --- # hitkodev [ ](https://wordpress.org/support/users/hitkodev/) * [Profile](https://wordpress.org/support/users/hitkodev/) * [Topics Started](https://wordpress.org/support/users/hitkodev/topics/) * [Replies Created](https://wordpress.org/support/users/hitkodev/replies/) * [Reviews Written](https://wordpress.org/support/users/hitkodev/reviews/) * [Topics Replied To](https://wordpress.org/support/users/hitkodev/replied-to/) * [Engagements](https://wordpress.org/support/users/hitkodev/engagements/) * [Favorites](https://wordpress.org/support/users/hitkodev/favorites/) Search replies: ## Forum Replies Created Viewing 6 replies - 1 through 6 (of 6 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Breeze Cache] JS and CSS not gzip enabled](https://wordpress.org/support/topic/js-and-css-not-gzip-enabled/) * [hitkodev](https://wordpress.org/support/users/hitkodev/) * (@hitkodev) * [5 years, 5 months ago](https://wordpress.org/support/topic/js-and-css-not-gzip-enabled/#post-14178028) * [@djeah](https://wordpress.org/support/users/djeah/) Content encoding br means your server supports Brotli compression, which is a more recent alternative to gzip compression. * [https://hacks.mozilla.org/2015/11/better-than-gzip-compression-with-brotli/](https://hacks.mozilla.org/2015/11/better-than-gzip-compression-with-brotli/) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Breeze Cache] Improper exclude url merging](https://wordpress.org/support/topic/improper-exclude-url-merging/) * Thread Starter [hitkodev](https://wordpress.org/support/users/hitkodev/) * (@hitkodev) * [5 years, 5 months ago](https://wordpress.org/support/topic/improper-exclude-url-merging/#post-14175333) * I believe it should be plenty obvious from the code. Let’s go step by step through the affected code, shall we? * ``` $storage['exclude_url'] = array_merge( $ecommerce_exclude_urls, ! empty( $config['breeze-exclude-urls'] ) ? $config['breeze-exclude-urls'] : array() ); ``` * This part merges `$ecommerce_exclude_urls` and exclude urls from config and stores them to `$storage['exclude_url']`. So far so good, your code works. Next code: * ``` $saved_pages = get_option( 'breeze_exclude_url_pages', array() ); if ( ! empty( $saved_pages ) ) { $saved_pages_urls = array(); foreach ( $saved_pages as $page_id ) { $saved_pages_urls[] = get_permalink( $page_id ); } $saved_pages_urls = array_unique( $saved_pages_urls ); $storage['exclude_url'] = array_merge( $saved_pages_urls, ! empty( $config['breeze-exclude-urls'] ) ? $config['breeze-exclude-urls'] : array() ); } ``` * Now if you look what this does is if `$saved_pages` option is set, it merges ` $saved_pages_urls` and exclude urls form the config, and stores them to `$storage[' exclude_url']`. Now tell me, what happened to `$ecommerce_exclude_urls` which were added to `$storage['exclude_url']` in the previous step? They just got overridden by `$saved_pages_urls`. But what’s this? More code? * ``` if( class_exists('WC_Facebook_Loader')){ $woocommerce_fb_feed_link = Breeze_Ecommerce_Cache::factory()->wc_facebook_feed(); if(!empty($woocommerce_fb_feed_link)){ $storage['exclude_url'] = array_merge( $woocommerce_fb_feed_link, ! empty( $config['breeze-exclude-urls'] ) ? $config['breeze-exclude-urls'] : array() ); } } ``` * See the pattern? Now if `WC_Facebook_Loader` is active, we again override any saved or ecommerce urls from the previous step. Amazing. - This reply was modified 5 years, 5 months ago by [hitkodev](https://wordpress.org/support/users/hitkodev/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Breeze Cache] Improper exclude url merging](https://wordpress.org/support/topic/improper-exclude-url-merging/) * Thread Starter [hitkodev](https://wordpress.org/support/users/hitkodev/) * (@hitkodev) * [5 years, 7 months ago](https://wordpress.org/support/topic/improper-exclude-url-merging/#post-13878214) * Here’s a fixed version: [https://pastebin.com/5qMrT3KW](https://pastebin.com/5qMrT3KW) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Breeze Cache] Broken caching in 1.1.7](https://wordpress.org/support/topic/broken-caching-in-1-1-7/) * Thread Starter [hitkodev](https://wordpress.org/support/users/hitkodev/) * (@hitkodev) * [5 years, 10 months ago](https://wordpress.org/support/topic/broken-caching-in-1-1-7/#post-13498693) * The first issue seems to be fixed, but it still doesn’t properly cache multisite. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Breeze Cache] Broken caching in 1.1.7](https://wordpress.org/support/topic/broken-caching-in-1-1-7/) * Thread Starter [hitkodev](https://wordpress.org/support/users/hitkodev/) * (@hitkodev) * [6 years, 1 month ago](https://wordpress.org/support/topic/broken-caching-in-1-1-7/#post-13017886) * Another fine bug (this time on multisite): `$blog_id` defaults to 1, and only resolves AFTER Breeze tries to serve cached content. Since Breeze prepends `$ blog_id` to cache path, it tries to read from `cache/breeze/1/...`, but writes to `cache/breeze/[resolved blog id]/...`, which obviously doesn’t match. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Breeze Cache] Broken caching in 1.1.7](https://wordpress.org/support/topic/broken-caching-in-1-1-7/) * Thread Starter [hitkodev](https://wordpress.org/support/users/hitkodev/) * (@hitkodev) * [6 years, 1 month ago](https://wordpress.org/support/topic/broken-caching-in-1-1-7/#post-13008698) * Everywhere, just look at the damn code, like, say, line 214 in `execute-cache. php` which was not updated with the new logic, and appends `guest` without `?` or `&` prefix. Alternatively, here’s the refactored code, so you won’t have to worry about updating copy-pasted code all over the place: [https://pastebin.com/x9dEDKhc](https://pastebin.com/x9dEDKhc) Viewing 6 replies - 1 through 6 (of 6 total)