Hi @Mfristoff,
Source map are not related to any of these issues. It’s use for debugging so please ignore it, unless you’ll debug it which is you can’t do since it’s limited to our developers only. And I don’t see it on my end either so it could be just your browser configuration. Please check this https://developers.google.com/web/tools/chrome-devtools/javascript/source-maps (Enable Source Maps in settings, from same setting, you can disable it)
I’m able to see the screenshots but it’s not related to the issue. Would you mind cloning your site into staging? And what error you’re getting when updating it? I couldn’t update your site as it may cause more trouble and your site is live, please do this in a staging site.
You can create a staging by cloning your site, please check this https://winningwp.com/best-plugins-to-copy-clone-duplicate-a-wordpress-site/ ( ALL-IN-ONE WP MIGRATION ). Once done, provide the staging URL with FTP credentials.
And the Remove Query Strings From Static Resources
should be deactivated along with switching CF to development. The reason versions are added to the URLs are to tell the browser of the current version, if it matches the cache then browser will use that cache so instead of re-downloading the same copy. But, if the site is updated, the new version will appear in the URL and browser will download that latest file. Removing URL query strings removes those versions, hence, browser see the file as the same file it downloads before so it’s not going to download it anymore unless the browser caches are deleted. And now browser also downloads caches from CF (version less URLs), deleting browser caches isn’t going to work unless both CF and browser caches are cleared. Let’s disable all of these while we’re checking the issue to make sure we’re seeing and testing the updated files, and in staging site.
Thanks!