matchattaxoutlet Posted November 13, 2015 Share Posted November 13, 2015 (edited) Hi guys, I have just been browsing my store and am noticing some strange behaviour.When i click on my basket from the homepage i see nothing but the url shows https://www.matchattaxoutlet.co.uk/# However if i click on register i can then see the basket. I have also, once logged in as a user not been able to access my basket or account options.Also if i click on a product page and see a url which is ok, when i click on the basket icon in top right, it stays on the page but just adds # to the end of the url.UPDATE: Seems to be in Chrome where this is happening, IE up to now looks OK I am sure there may be other problems and would be grateful if anyone could have a real good look around and provide some feedback / solutionsTIA Edited November 13, 2015 by matchattaxoutlet Quote Link to comment Share on other sites More sharing options...
bsmither Posted November 13, 2015 Share Posted November 13, 2015 In your 'MatchAttaxFoundation' skin, the main.php template:Find: <script async src="{$STORE_URL}/skins/{$SKIN_FOLDER}/js/vendor/modernizr.min.js"></script> <script async src="{$STORE_URL}/skins/{$SKIN_FOLDER}/js/vendor/jquery.js"></script> Remove the ASYNC attribute. The ASYNC attribute allows the browser to continue loading/processing other javascript files while these two are still being loaded/processed. The result is that the other javascript routines (rating, validate, cookie, bxslider, foundation, cubecart, and cubecart.validate), all of which depend on jQuery being already loaded and ready, will fail. Quote Link to comment Share on other sites More sharing options...
matchattaxoutlet Posted November 13, 2015 Author Share Posted November 13, 2015 Thank you bsmither, that was added following recommendations from Google's pagespeed insights testing...maybe not such a great thing after all! Quote Link to comment Share on other sites More sharing options...
havenswift-hosting Posted November 14, 2015 Share Posted November 14, 2015 that was added following recommendations from Google's pagespeed insights testing...maybe not such a great thing after all!Good catch Brian ! Google PageSpeed Insights are only ever meant to be recommendations and should never simply be followed. This is an extreme case of problems that can be caused but often there can be good reasons not to simply follow their recommendations Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted November 14, 2015 Share Posted November 14, 2015 I, too, had followed Google's asynch suggestion some time ago and ran into similar problems. Ignorance does not always produce bliss. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.