Viewing 8 replies - 1 through 8 (of 8 total)
  • Hi @titsmaker, may I know did you turned ON Exclude JQuery?

    Also, could you please provide?your Report Number, found in?WP Admin > LiteSpeed Cache > Report.

    Thread Starter titsmaker

    (@titsmaker)

    Thank you for fast reply. Exclude JQUery is set to ON, JQuery is also excluded manually via “JS Excludes” (as far as I remeber above mentioned function didn’t work in my case). Report number is CHAXKAJQ.

    Please try to turn OFF Remove Comments, if the issue still exists, can you check and send us the JS error log on console?

    Thread Starter titsmaker

    (@titsmaker)

    Setting Remove Comments to OFF didn’t help. Here’s the error from Chrome console – https://gyazo.com/b16936b19cc9fb559573b1428d96af62
    And here’s the code from mentioned in error message 15th line of minified JS:

    ;!function(a){var b="-",c="";screen.width&&(width=screen.width?screen.width:"",height=screen.height?screen.height:"",c+=width+" x "+height);var d,e,f,g=navigator.appVersion,h=navigator.userAgent,i=navigator.appName,j=""+parseFloat(navigator.appVersion),k=parseInt(navigator.appVersion,10);-1!=(e=h.indexOf("Opera"))&&(i="Opera",j=h.substring(e+6),-1!=(e=h.indexOf("Version"))&&(j=h.substring(e+8))),-1!=(e=h.indexOf("OPR"))?(i="Opera",j=h.substring(e+4)):-1!=(e=h.indexOf("Edge"))?(i="Edge",j=h.substring(e+5)):-1!=(e=h.indexOf("MSIE"))?(i="Internet",j=h.substring(e+5)):-1!=(e=h.indexOf("Chrome"))?(i="Chrome",j=h.substring(e+7)):-1!=(e=h.indexOf("Safari"))?(i="Safari",j=h.substring(e+7),-1!=(e=h.indexOf("Version"))&&(j=h.substring(e+8))):-1!=(e=h.indexOf("Firefox"))?(i="Firefox",j=h.substring(e+8)):-1!=h.indexOf("Trident/")?(i="Internet",j=h.substring(h.indexOf("rv:")+3)):(d=h.lastIndexOf(" ")+1)<(e=h.lastIndexOf("/"))&&(i=h.substring(d,e),j=h.substring(e+1),i.toLowerCase()==i.toUpperCase()&&(i=navigator.appName)),-1!=(f=j.indexOf(";"))&&(j=j.substring(0,f)),-1!=(f=j.indexOf(" "))&&(j=j.substring(0,f)),-1!=(f=j.indexOf(")"))&&(j=j.substring(0,f)),k=parseInt(""+j,10),isNaN(k)&&(j=""+parseFloat(navigator.appVersion),k=parseInt(navigator.appVersion,10));var l=/Mobile|mini|Fennec|Android|iP(ad|od|hone)/.test(g),m=b,n=[{s:"Windows 10",r:/(Windows 10.0|Windows NT 10.0)/},{s:"Windows 8.1",r:/(Windows 8.1|Windows NT 6.3)/},{s:"Windows 8",r:/(Windows 8|Windows NT 6.2)/},{s:"Windows 7",r:/(Windows 7|Windows NT 6.1)/},{s:"Windows Vista",r:/Windows NT 6.0/},{s:"Windows Server 2003",r:/Windows NT 5.2/},{s:"Windows XP",r:/(Windows NT 5.1|Windows XP)/},{s:"Windows 2000",r:/(Windows NT 5.0|Windows 2000)/},{s:"Windows ME",r:/(Win 9x 4.90|Windows ME)/},{s:"Windows 98",r:/(Windows 98|Win98)/},{s:"Windows 95",r:/(Windows 95|Win95|Windows_95)/},{s:"Windows NT 4.0",r:/(Windows NT 4.0|WinNT4.0|WinNT|Windows NT)/},{s:"Windows CE",r:/Windows CE/},{s:"Windows 3.11",r:/Win16/},{s:"Android",r:/Android/},{s:"Open BSD",r:/OpenBSD/},{s:"Sun OS",r:/SunOS/},{s:"Linux",r:/(Linux|X11)/},{s:"iOS",r:/(iPhone|iPad|iPod)/},{s:"Mac OS X",r:/Mac OS X/},{s:"Mac OS",r:/(MacPPC|MacIntel|Mac_PowerPC|Macintosh)/},{s:"QNX",r:/QNX/},{s:"UNIX",r:/UNIX/},{s:"BeOS",r:/BeOS/},{s:"OS/2",r:/OS\/2/},{s:"Search Bot",r:/(nuhk|Googlebot|Yammybot|Openbot|Slurp|MSNBot|Ask Jeeves\/Teoma|ia_archiver)/}];for(var o in n){var p=n[o];if(p.r.test(h)){m=p.s;break}}var q=b;switch(/Windows/.test(m)&&(q=/Windows (.*)/.exec(m)[1],m="Windows"),m){case"Mac OS X":q=/Mac OS X (10[\.\_\d]+)/.exec(h)[1];break;case"Android":q=/Android ([\.\_\d]+)/.exec(h)[1];break;case"iOS":q=/OS (\d+)_(\d+)_?(\d+)?/.exec(g),q=q[1]+"."+q[2]+"."+(0|q[3])}var r="no check";if("undefined"!=typeof swfobject){var s=swfobject.getFlashPlayerVersion();r=s.major>0?s.major+"."+s.minor+" r"+s.release:b}a.jscd={screen:c,browser:i,browserVersion:j,browserMajorVersion:k,mobile:l,os:m,osVersion:q,flashVersion:r}}(this),function(a){var b=a("html");b.addClass("browser-"+jscd.browser),b.addClass("platform-"+jscd.os)}(jQuery);

    Thread Starter titsmaker

    (@titsmaker)

    Looks like the code causing the error is not from Flying Pages, but excluding Flying Pages from JS combining fixes the issue somehow.

    If it is not from Flying Pages do you mean when you exclude it you still find the error on somewhere?

    If yes you may need to fix that error first otherwise the JS after the error cannot be loaded.

    Thread Starter titsmaker

    (@titsmaker)

    No, when I exclude Flying Pages from combining JS everything works fine, no errors.
    I mean that the code pointed by error message is supposedly not from Flying Pages but from Litespeed itself, but I can’t say exactly.

    Thanks for the explanation, for this situation we suggest you keep the JS excluded. If you want to find out where is the JS issue come from please join our Slack channel and find me(Stanley Cheung at Litespeed) for reproducing the issue.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘JS Combine + Flying pages is causing issues’ is closed to new replies.