Auto Upgrading Umbraco 7.1.4 with /umbraco/AuthorizeUpgrade gives an error
Guys
Running umbraco application in Visual Studio all of the sudden results in an error after redirecting to the following page : /umbraco/AuthorizeUpgrade?redir=%2finstall%2f%3fredir%3dtrue%26url%3dhttp%253a%252f%252flocalhost%253a55105%252fumbraco%252f
The error is in Application line 1: Uncaught ReferenceError: yepnope is not defined
Looks like yepnope is missing. Empty Cache an Hard Reload doesn't solve the issue
Question: Before trying, if I update Umbraco via Nuget will that make the autoupdate message go away?
Problem is sort of 'solved' by adding a reference to yepnope in /umbraco/Views/AuthorizeUpgrade.cshtml
@*And finally we can load in our angular app*@ <!-- inserted this line -->
<script type="text/javascript" src="lib/yepnope/yepnope.min.js"></script> <!--end inserted this line -->
<script type="text/javascript" src="lib/lazyload/lazyload.min.js"></script>
<script type="text/javascript" src="@Url.Action("Application", "BackOffice")"></script>
We don't use yepnope any more. Make sure to update version in ClientDependency.config (just set it to 1 version higher or lower than it was before) and do another browser cache reset, that should help.
Auto Upgrading Umbraco 7.1.4 with /umbraco/AuthorizeUpgrade gives an error
Guys
Running umbraco application in Visual Studio all of the sudden results in an error after redirecting to the following page : /umbraco/AuthorizeUpgrade?redir=%2finstall%2f%3fredir%3dtrue%26url%3dhttp%253a%252f%252flocalhost%253a55105%252fumbraco%252f
The error is in Application line 1: Uncaught ReferenceError: yepnope is not defined
Looks like yepnope is missing. Empty Cache an Hard Reload doesn't solve the issue
Question: Before trying, if I update Umbraco via Nuget will that make the autoupdate message go away?
Tnx
Problem is sort of 'solved' by adding a reference to yepnope in /umbraco/Views/AuthorizeUpgrade.cshtml
We don't use yepnope any more. Make sure to update version in ClientDependency.config (just set it to 1 version higher or lower than it was before) and do another browser cache reset, that should help.
Hi Sebastiaan,
That didn't help either, don't know exacly what the problem was, after an update via nuget all was well again
But nonetheless thanks:)
Greetings,
Garret
is working on a reply...