Another PROD Page Related Products issue - javascript not firing

[Bruce - PhosphorMedia]

Yes, AddThis is probably the worst offender of all. When not completely breaking down, it significantly, as in sometime multiple seconds, adds to the download time.

[d2d2d2]

Thanks, Bruce. I can definitely admit to not updating third party JS. I will look into that. I deleted the AddThis social Media links as I read they really slowed page load speed. I will try to reinstall on the new site and assess but gone for now. Thanks to both you and Matt for taking a look and offering some advice.

[Bruce - PhosphorMedia]

A lot of the times when I see transient javascript errors, it almost always turns out to be some outdated (or just poor) social media / tracking javascript.

[Matt Zimmermann]

That is interesting. I will do a check on any of the javascript calls that I added some years ago. For sure, it is possible that Safari has updated something and 'broken" my website. Can you clarify for me - even though the MivaEvent that is not firing is contained in the Iron and Wool scripts.js file, it is possible that another js file is not being called securely and affecting the loading. I understand that correctly? I am uploading an image with screenshot of the console error I see. No other errors other than the usual "strict-dynamic" problem that I have seen for years.

Screen Shot 2020-12-23 at 10.14.35 AM.png

MivaEvents is included in Iron & Wool. I have never seen the "strict-dynamic" error you mentioned in the test site. I have tested your site and, other than the "strict-dynamic" error you mentioned, I am unable to duplicate the issue.

[d2d2d2]

I would love you to. The header and footer seem to be such a mess to me. So many people (me especially) have added javascript files. For some reason I could never get the added javascript to load from the themes file, even though I see them listed, so I have to add them in the footer. I did confirm that there are no calls for non-https javascript files. I played around with moving the load order of the javascript files but it breaks my easytabs.js and qipt.js. I know these scripts are old. Can't wait to get rid of the old and move onto the new but just need to make it work for a little bit longer. Thanks for taking a peek.

Just to be clear, I mostly see the problem in Safari, although it can occur in Chrome and Firefox if the connection is slow. I have checked on numerous devices, mobile, desktop, old, new. There is erratic loading of the script.js and it just breaks the attributes and related products. I saw the same problem displaying, just yesterday, on the linked page from the website lesliekirk posted at the beginning of this topic. This makes me question if it is an Iron and Wool problem?

Here's a complicated product page. Try navigating around to other recliners or sofas. It really seems to be the pages with tons of attributes and swatches that don't load in time.

https://www.designquest.biz/stressle...ture-base.html

[Bruce - PhosphorMedia]

Do you have a URL we can look at?

[d2d2d2]

That is interesting. I will do a check on any of the javascript calls that I added some years ago. For sure, it is possible that Safari has updated something and 'broken" my website. Can you clarify for me - even though the MivaEvent that is not firing is contained in the Iron and Wool scripts.js file, it is possible that another js file is not being called securely and affecting the loading. I understand that correctly? I am uploading an image with screenshot of the console error I see. No other errors other than the usual "strict-dynamic" problem that I have seen for years.

Screen Shot 2020-12-23 at 10.14.35 AM.png

[Bruce - PhosphorMedia]

When you say no errors, are you talking about console errors when the web's UI fails?

It could very well be browser dependent (even more so based on settings). For example, there's now a setting in Chrome that will fail is ANY part of a resource call is non-https. For example, we saw this where a (laughably so) an SSL cert javascript function didn't set the image call to specifically be https://. That stopped ALL javascript downstream from firing. And only issued a warning...not an error.

[d2d2d2]

I have been scouring all over the forum because I have had an ongoing problem with how our website is functioning. This is an old post I am resurrecting but I can see that the Iron and Wool Themed web url that lesliekirk links to in the original post has a malfunctioning website as well, and it also appears that is is only misbehaving at times.

We currently use the Iron and Wool Theme. The product pages only erratically work. It depends if the supporting javascript actually loads. When it doesn't, the product page attribute menu pricing no longer works and the related products load with the first one missing and all the others in a vertical column. The only error I can see is that a MivaEvent call is not found. I know the Iron and Wool theme is legacy. I am working on a new Shadows site but currently our website pricing functionality is broken. Has anyone else run into this problem and come up with a solution?

I worked with Miva support for over a month on this and I think they just gave up and assigned the problem as a "browser-related problem." There is no doubt that the problem is predominantly in Safari but I have recreated it in other browsers. I tried deferred loading of Javascript, put it back, etc etc. Nothing seems to fix the timely loading of javascript so that the MivaEvent fires reliably. Any ideas from other Iron and Wool users? I need to get this patched for a couple more months!

[lesliekirk]

After much banging of my head against my desk I discovered there was a small typo in a css file name. Somehow I had /css/sliders.css when the file name on the server was /css/slider.css.

It's working now

[lesliekirk]

The scripts.js file you are using is looking for the theme_path variable. You will need to either set it to be relative to the actual location of the JS folder or edit the scripts.js file to update for the fact that there is no theme folder structure.

Okay, I put the original scripts.js file back in place, since that didn't work I'll make edits to the previous scripts.js file and see if that works.

[Matt Zimmermann]

The scripts.js file you are using is looking for the theme_path variable. You will need to either set it to be relative to the actual location of the JS folder or edit the scripts.js file to update for the fact that there is no theme folder structure.

[lesliekirk]

This is an older version of the ReadyTheme which I don't think it used this snippet because there is no separate folder for the theme itself.

[Matt Zimmermann]

Check that you have the theme path set in the theme settings for scripts and the MVT is set in the HEAD tag; without it the JavaScript will throw errors.

<script>
var theme_path = "&mvtj:global:theme_path;";
</script>

[lesliekirk]

It looks like might be missing the ReadyThemes theme settings content item for that page.

Yes, I had intentionally left it "off". I turned it back on and it's still not firing.