We have moved to GitHub Issues
Created by Matthew 09 Mar 2015, 17:47:07 Updated by Shannon Deminick 22 Jun 2015, 09:44:00
Is duplicated by: U4-6253
Is duplicated by: U4-6330
Relates to: U4-6418
Relates to: U4-6544
I'm running Umbraco 7.2.2 on a node balanced site (NLB) with central file system. The site works fine on localhost but the back office is broken on my staging server.
What did you do?
What did you expect to happen? I expected the backoffice to work.
What actually happened? The front end loads fine, but I get a blank screen when accessing the back office and failed GET attempt from LazyLoad.js when it tries to access DEpendencyHandler.axd
Later on I get this error: Uncaught Error: No module: ngTable
According to [https://our.umbraco.org/projects/backoffice-extensions/spectrum-colour-picker/general/61573-Broken-in-Umbraco-722-with-debug-=-false this page] and several other issues around the net, my problem here was due to some security update in the 7.2.2 version of ClientDependancy that seems to have issues with query strings. By checking the package.manifests in /App_Plugins/, I discovered that one of my packages (MemberListView) was using query strings. I removed this package and everything seems to work again.
And copied that reply here:
When a JS file has a query string in it, CDF treats it as an external/request based resource, not a local file system resources since a local file path doesn't have a query string. CDF will not make external/request based resource calls unless you whitelist your domain, so you can fix this by white-listing your domains in the CDF config:
The actual problem for this however is the way that we parse the values in the manifest. Unfortunately in the Umbraco core we've sort of bypassed how CDF is supposed to work. The fix is to let CDF do it's job and output the dependencies correctly. In these cases, any dependency that declares a query string is treated as an external dependency and will be loaded in separately instead of trying to be part of the CDF bundles.
Fixed in rev: 02b0e4dd6a5a0aabd2e2de14ce565624aa608705
I've had my primary domain white-listed since before the release of 7.2.2 and still ran into this issue. Our site runs on a subdomain and my white-list looks like: bundleDomains="localhost:12345,.mysite.edu"
But I assume the fix in 7.2.3 does not rely on the white-list.
Yes, the querystrings problem is fixed independently of the domains, it will work without whitelisting.
Of course in the meantime you can just remove the query string from the dependency listing in the package.manifest that is causing the issue (there shouldn't ever be query strings for local resources in the package manifest!)
I'm experiencing same issue and I just cannot get it to work.
I'm using Umbraco 7.1.8 and this issue happens on all Umbraco 7.1.8. projects that I've worked on.
I have tried literary everything.
Please, do you have any suggestions?
Kind regards, Nevena
@nevena - you'll need to provide more details. You must be seeing some sort of error, etc... in your browser's console. Can you please describe 'your' issue? When logging bug reports its best to include every bit of detail since your issue is probably actually different to someone elses.
Assignee: Shannon Deminick
Backwards Compatible: True
Affected versions: 7.2.2
Due in version: 7.2.3