• Resolved hoy

    (@whereskarlo)


    Hello,

    Since installing version 1.1.3 grouping of js yields a broken page. Turning grouping off for js restores the page to normal (minification for js and css is on).

    With grouping on for js, the Google Console tells me that:
    Uncaught SyntaxError: Unexpected token '%'

    This is for file /wp-content/cache/breeze-minification/js/breeze_d6e3a9af3b936e04ae1876bd02d82296.js

    • This topic was modified 4 years, 9 months ago by hoy.
Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author adeelkhan

    (@adeelkhan)

    Hi
    could you please verify that is there any page builder or theme recommend plugin conflict with JS ?

    Thread Starter hoy

    (@whereskarlo)

    There are no errors with the grouping of js turned off. However it worked in the previous version of breeze. This error started appearing in version 1.1.3 after grouping was changed.

    Thread Starter hoy

    (@whereskarlo)

    Hi again,

    I don’t know what you mean with theme recommend plugin conflict, but there is wpbakery page builder installed. It was working error free before 1.1.3 on Cloudways

    I am also seeing issues with my site when using group JS. Disabling the option fixes the problem, so something is definitely broken with this feature in the latest version.

    https://www.ads-software.com/support/topic/1-1-3-infinite-redirect-loop/

    Plugin Author adeelkhan

    (@adeelkhan)

    Hi

    Yes, we have worked on grouping and minification and you might see some changes.
    I assume that you updated the plugin directly to the latest version. As such, you can follow the following steps for a possible fix of your problem
    First of all, uncheck all boxes for JS minification and grouping. Next, save the changes. Now purge the server cache and the internal Breeze cache.
    Now open your website in a new tab and verify that the site is being served without JS being minified.
    Now enable JS minification and save changes. Open your website in a new tab and verify that the site is being served with JS minified. You can check this by viewing the page source.

    Now enable JS Grouping and save changes. Open your website in a new tab and verify that the site is being served with JS grouped and minified. You can check this by viewing the page source.
    Let me know if this resolves the issue.

    Thread Starter hoy

    (@whereskarlo)

    Thanks for your reply.

    I already tried this, exactly as described. Turned off all caching, cleared all cache in backend and server side, turned on features one by one, cleared cache in between each and every change and checking the website after every change in a new incognito window.

    We got as far as minification turned on for css and js, and grouping turned on for css without issues.

    When grouping is turned on for js and all caches are flushed, the website breaks in an incognito window as described in the first post.

    • This reply was modified 4 years, 9 months ago by hoy.

    Yes, I am having this same issue since the last plugin update. I also tried to follow the steps and it broke once I clicked group js and css.

    I am also having this same issue. It is not related to theme (tried stock) or other plugins (I am running Elementor but tried with ALL disabled except Breeze) and happens even with ALL js files listed in the exclude list. Rolling back to 1.1.2 solves the problem.

    Thread Starter hoy

    (@whereskarlo)

    Hello @adeelkhan , just checking in if the developers are aware that grouping of js has a bug? The steps you suggested does not remedy the problem. The issue is only with grouped js; not with grouped css, minified js / css.

    Plugin Author adeelkhan

    (@adeelkhan)

    Hi all,

    we are in the process of replicating the scenarios posted in the thread. Can you describe which JS files are causing the issue when grouping is enabled?

    Once we have the findings, we’ll update the thread.

    Thread Starter hoy

    (@whereskarlo)

    With grouping on for js, the Google Console tells me that:
    Uncaught SyntaxError: Unexpected token ‘%’

    This is for file /wp-content/cache/breeze-minification/js/breeze_d6e3a9af3b936e04ae1876bd02d82296.js

    Is there another way to specifically find which file/s are causing the error?

    Plugin Author adeelkhan

    (@adeelkhan)

    In the Advanced Option, tab excludes js file from grouping.

    I run a fairly standard WooCommerce build with not too many plugins. Still, the site loads 37 javascript files. The suggestion to step through each file, toggling it on and off, is a bit unreasonable. It seems very many people have experienced this problem, which suggests the problem is with breeze rather than a third party.

    Same issue here with Grouping JS broke Gravity Form. This makes my web forms not show up on frontend. Was working fine in version 1.1.2

    I had taken the time previously to go through each file assuming it was an issue with files on the first broken site. Nothing worked to resolve the issue with excluding files. I even turned off both minification and group so I could get a complete list of JS files and added EVERY file to the exclude list, and then turned back on minification and grouping. The error still occurred and broke the JS on the site. Even when ALL files are excluded a new JS file is created by Breeze and this file breaks everything.

    This is not an isolated random site. I have MANY (read 20+) sites with all different plugin sets and functionality. Some have WooCommerce, some have Elementor, some have Divi, the list goes on and on. The main plugin in common is Breeze.

    Here are some of the plugins found on my sites, and while not a complete list, this is the most common. I did also try turning off groups of plugins, and still had problems.
    Breeze
    Compress JPEG & PNG images
    Elementor
    Elementor Pro
    Enable Media Replace
    GP Premium
    MainWP Child
    SEOPress
    SEOPress PRO
    UpdraftPlus – Backup/Restore
    Wordfence Security
    WP Mail SMTP

    I have also tried using 2 different MySql versions (MariaDB) and both PHP 5.6 and 7.3. No change in behavior. The problem happens regardless of using Apache or Apache/NGinx. All other plugins are 100% up to date, and WordPress is fully up to date. This also happens on different server types and base setups, with some sites on DO with NO CloudWays connection, others with Vultr on CloudWays. Still others running a simple LAMP setup.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Grouping of js broken in 1.1.3’ is closed to new replies.