Spin.js is not missing. The JetPack plugin is overriding the path, which is causing the issue.

Just letting you know as a follow-up, that this outage had an interesting (but still concerning) temporary stop-gap measure, kindly created by my web hosting provider:

_______________________________

Hello

The issue definitely seems to be around the missing spin.js, the code is linking the file on a path where it does not exist.

As a quick and dirty patch, I created a symlink in public_html/blog/wp-content/plugins/jetpack/_inc , spin.js is a link to build/spin.min.js, I think this fixed the problem, although it's just a patch.

Ideally your application should be linking to the appropriate path of the file.

Could you check now and let me know if the way the sites load is the way you expect them to?

Sergio D.
Core Support Manager

--
| Ticket ID: #703902
| Subject: Site not loading correctly starting recently; is it a cache on your server side?
| Status: Answered

Thanks, this is helpful for me to understanding the distinctions. I'll post back here after I've made concerted efforts to identify and wipe out the Jetpack references. (I've read warnings about how not only deactivating Jetpack as a plug-in but also deleting that directory from plug-ins via FTP is apocalyptic, but I might take the risk anyway. Finding the file in my VYSUAL installation that even references Jetpack -- file/directory -- remains problematic.)

My best suggestion is to completely delete the jetpack plugin and clear all your caches (both browser and hosting - if applicable).

I don't know what file is causing that jetpack reference issue, so I can't provide more details unfortunately.

Regarding incognito, that just means the non-incognito is showing a cached version of your site when it was working, which doesn't surprise me. The issue isn't related to incognito being on/off, it's related to what the current state of your source code is, which appears to be using jetpack still.

As of right now, I'm categorizing this issue as "plugin related" until all reference to jetpack is removed from your source code. This is not me dodging the issue or any other ideas you might have about my approach to support. I'm trying to help. I see an issue and it appears plugin-related, which is where my support stops. If the issue continues AFTER the plugin is no longer referenced, you can be sure my nose will be back in your code trying to figure out the issue. ;-)

Best,

Christopher

You've mentioned the reference appearing in my source code, but from what I understand, source code can be many different things. Do you mean the source code of the Page entry that is also the home page? Sounds like you're saying it's not your theme, but if you can cite an actual filename where I can "remove the Jetpack reference" as you request, that's helpful and more specific than just source code in general.

And generally speaking, I really thought that the fact it works perfectly fine still in browsers where it's been before (even after clearing the cache), versus incognito mode, is the biggest clue -- so far unaddressed. All of this might be deeply relevant to the vitality of your theme, if recent Jetpack or other changes have triggered the problem. Wouldn't have asked otherwise for general errors.

Checked in multiple browsers and the JetPack plugin reference still appears in your source code. I'm certain this is the cause of the issue as it's overriding the proper spin.js file reference, which is causing a script error (preventing the rest of the scripts to load) and causing the page to break.

I really can't investigate/troubleshoot this any further until the jetpack reference is removed as that is the only issue that I see.

Best,

Christopher

Not a red herring. Just trying to help. That's the first issue I noticed (and still see).

Jetpack is completely disabled all the way to the root Network Admin multi-site level. And I've confirmed it's also disabled in the plug-ins for quatuor.xyz (and again, samuelbarberfilm.com).

I hope the Jetpack error isn't necessarily a red herring; that Developer Console error showed up at first, but doesn't anymore after Jetpack was disabled. Something else? It's concerning that (in some or potentially all cases) the spin.js reference could be getting incompatible competition...

...also, spin.js is located in the scripts directory of the VYSUAL theme. It appears JetPack is overriding that reference as there must be a feature in JetPack that is also called "spin.js" (best guess).

Hi there,

Just to clarify, I'm using this URL you provided to troubleshoot the issue you're having:

http://quatuor.xyz/

Can you disable JetPack there? I'll check again.

The fact that jetpack is showing as the source directory for spin.js is the cause of the issue (spin.js doesn't exist in that location).

Best,

Chrisotpher

Whether or not Jetpack is running (currently not), I navigated to the spin.js directory location as suggested in your screen capture, and spin.js is not present, which might or might not be concerning. I did notice that Jetpack got an update very recently, and it hadn't been a while -- seems to correspond with the site outage.

I do NOT experience the issue at your demo site, however, which probably throws a wrench into this diagnosis. I also don't experience it (SO FAR) at scroogeopera.com which I REALLY need to keep working for an event tomorrow.

Okay, took another look and still see this in your source code...

https://imgur.com/a/9icNu

Notice spin.js is loading from the JetPack plugin source, which doesn't exists.

To help me narrow down the issue (and make sure it isn't specific to your setup), can you tell me if you are having the same issues with the demo site? Reference: http://themes.themolitor.com/vysual/

Let me know as this will help me to continue looking into this.

Best,

Christopher

Thanks for checking. I'll look into this more... stay tuned.

I hadn't wanted to mention too much at first, but indeed, I had already tried that with no change in result (but I'm leaving Jetpack off). The central clue, it seems to me (and this might affect all your themes that rely upon spin.js) is that it's loading just fine in browsers where perhaps spin.js was previously accessed; yet at Incognito mode for me (and anywhere for most others), your theme gets totally broken. Any further ideas? They could range from .htaccess, to robots.txt, to other plug-in conflicts (doubtful since I disabled sequentially for testing), to getting hacked.

Hi there,

Noticed you have JetPack installed. Try deactivating that and see if the issue resolves.

Let me know.

Best,

Christopher

Further update: looks like the central issue is that spin.js is missing, with the related "Spinner is not defined" error. If you have any further insight to draw from that, much appreciated.

An update to this desperate issue (site not working): after conferring with my hosting provider, making sure it wasn't an issue on their end regarding such matters as server-side caching, the attached error messages will hopefully make clear what the problem is. Very much hoping to hear from you soon.

http://prntscr.com/hnqcrx

This is quite odd, and came to my attention because users could not access my site using VYSUAL.

On one particular computer installation (mine), samuelbarberfilm.com loads just fine. That's when I logged into my WordPress site/host, or even when I'm not. But as soon as I enter the same Chrome browser's incognito mode, I get this:

http://prntscr.com/hn90vd

Basically, the menu at top-right doesn't work, shows a hamburger instead of the word MENU per settings, and leaves the main screen area blank, exposing the footer credits at all times.

To make it weirder, using the same host and WordPress installation, 95theses.com and quatuor.xyz looks the same in both regular and Incognito Chrome.

Kind of an emergency! Amounts to my site being totally down. Please help!