Some ideas...Try republishing entire site from root Content node context menu. Also try publishing the entrypoint page, and its descendants from its context menu. Finally, last idea but do it first, the context menu on your entry page, Manage Hostnames. Add your preferred hostname "myname.com" first. Add "www.myname.com" also. Hopefully some combination of these will get the site back on track! Also, after logging in, do a Ctrl+F5 refresh.
I read that this is an issue in 4.5 so hopefully there'll be a fix eventually. Loving the improvements to 4.5, once a few of the glitches get ironed out this will be awesome.
This is NOT an issue with Umbraco or Client Dependency, the problem is that the Client Dependency folder was deployed across environments. This should not be done.
4.5.1 install. Url was changed after install, now no UI images or nodes show up.
We installed 4.5.1 for the first time, then changed the URL after installation (from a .net to a .com).
Now, the admin doesn't load any of the UI images (gradients, backgrounds etc.) and the content nodes are not displayed.
upon looking in the browser developer tools, all the UI images are still trying to load from the old .net domain.
Is this an issue with umbraco 'hard-coding' the urls when it's installed, or likely an issue with something else?
thanks.
Some ideas...Try republishing entire site from root Content node context menu. Also try publishing the entrypoint page, and its descendants from its context menu. Finally, last idea but do it first, the context menu on your entry page, Manage Hostnames. Add your preferred hostname "myname.com" first. Add "www.myname.com" also. Hopefully some combination of these will get the site back on track! Also, after logging in, do a Ctrl+F5 refresh.
Try removing the contents in the App_Data/ClientDependency folder. Umbraco will add it back (hopefully) with the correct url.
Hope this helps,
--
Donald
That did the trick, thanks very much guys.
I read that this is an issue in 4.5 so hopefully there'll be a fix eventually. Loving the improvements to 4.5, once a few of the glitches get ironed out this will be awesome.
This is NOT an issue with Umbraco or Client Dependency, the problem is that the Client Dependency folder was deployed across environments. This should not be done.
Please refer to the final comment I left here: http://our.umbraco.org/forum/using/ui-questions/11802-DependencyHandleraxd-Using-Old-Domain-Instead-Of-New-One
is working on a reply...