Usync Complete - Dashboard is not loading after mi...
# help-with-other
a
@Kevin Jump We’ve recently upgraded one of our websites from Umb 8 to 13.6.0. After successful! upgrade, I installed Usync.Complete 13.1.9 but now in backoffice when I try to open Usync dashboard I am getting "Request Error: The URL returned a 404 (not found) : App_Plugins/uSync/backoffice/usync/dashboard.html " The error is similar to https://github.com/KevinJump/uSync/issues/476 but I am still not able to resolve the problem. Even when I try to publish the site, the published files do not contain /App_Plugins/uSync/ folder. Also, after installing Usync.Complete going to settings section, the section name changed to [sync] instead of Settings. Any helps to identify the problem is appreciated.
k
Hi, It does sound like the client files aren't there or the old v8 ones are and that's causing an issue, in development you shouldn't see any uSync (or uSync.Complete) files in app_plugins, as they are served from the nuget cached (when developing). when you publish a .net core site, (via dotnet publish, or visual studio, or webdeploy) it builds the site files structure and that should contain an app_plugins but it will probibly be in wwwroot (so wwwroot/app_plugins). the square [] bit happens when the localization files havene't been found (which are also in the app_plugins folder) so its a sign the client files are some how missing. you could remove and re-add the usync package(s) to the project (they won't delete any usync files or database stuff when you do that). and they will just confirm you have the latest versions of ewverything isntalled.
a
Thanks @Kevin Jump for instant response. I've already tried removing installed packages from project completely and reinstall them few times. still no changes. Also after publishing the '/App_Plugins/uSync/' is not generating in wwwroot either. Actually that was where I meant in my post, but didn't include the wwwroot bit. Regarding the old V8 files, I don't think so, since no direct upgrade route were available between 8 to 10 and I create a blank Umb10 project and import views etc. So not quite sure how the old umb8 files could end up in my new project. However I have a feeling this might be the case for Umb10 files?
k
Does the site run in development (e.g via visual studio or dotnet run) ok ? if you run a
dotnet publish
in the command line what does the bin/release/net8.0/publish folder look like does it have wwwroot/app_plugins/uSync ?
a
I'm Using VS and No, The problem persists in debug mode as well. When I publish the site, either by publish in VS or dotnet publish, it's not generating usync folder under wwwroot/app_plugins
I have a blank Umb with same version of Usync.Complete and that works fine, both in debug mode or published version.
k
Odd if you have it working... i would maybe start by checking the .csproj files see if they look similar (same .net versions, nothing custom etc)
then i would check program.cs - there shoulnd't be anything you need to change on this but maybe a small diffrence might be there.
(thinking about it there was some subtle diffrences between program.cs files in v8 and v10.)
a
in my migrated Umb13 project I am still having startup.cs and program.cs files (which was for Umb10), however in a fresh install of Umb13 it's completely different.
I'll check what you suggested and get back to you with some updates 🤞
I ended up creating a blank umbraco 13 site, installed Usync.Complete and published it. Copied the generated usync files and folders inside app_plugins ino my migrated site and now it's all working as expected! I don't think that's the right way, but it resolved my problem!
k
yeah - there is something odd there, i think for most people this 'just works' especially at the copy files level (which is core .net). So strange things afoot at the circle k 🤔
20 Views