First Umbraco upgrade 15.1.1 -> 15.1.2
# help-with-umbraco
r
Quick question, making sure this is correct just have some confusion. I upgraded 15.1.1 to 15.1.2 today. Showed successfully updated messages with the newly installed packages in cmd, but going into umbraco backoffice, I see it still shows 15.1.1 when the csproj shows 15.1.2 and the installed packages are 15.1.2. Is this correct? Or did something error out in terms of upgraded? Photos attached! Thanks 🙂 https://cdn.discordapp.com/attachments/1334210999326081114/1334210999674474627/umbracoVersion.PNG?ex=679bb452&is=679a62d2&hm=4b9abe270925a8c1e4209597d80397323912a335db05f77993b983e02fb5b766& https://cdn.discordapp.com/attachments/1334210999326081114/1334211000035053632/umbracoVersion2.PNG?ex=679bb452&is=679a62d2&hm=66561022a2ac9c1dcd6c35e6e616c10703a3e76f7cea2de766e69a99c9a92a3f&
r
On the navbar where the umbraco logo is, when you press it does it show 15.1.1 or 15.1.2?
Sorry yeah
Have you tried in a private browser window, or clearing your cache and reloading?
r
Hm, I have and I cleared cache within umbraco settings weird. Might try it again, maybe a rebuild of the project
s
Do you have multiple
.csproj
files? They all need updating.
Did you do a `dotnet build`or
dotnet run
after updating the
.csproj
file, a regular build is needed.
A rebuild is never needed, it might work but you're hiding a symptom 🙂
r
I did dotnet run just to make sure functionally the site works still, and i only have a single csproj. Very bare bones project. I'll run it locally and check it agian, I didnt check the navbar till i migrated it to a staging server
s
Aah I see you have the problem on a server, well deploying all the code should have worked but I have no idea what your deployment process looks like, so you might be missing something.
If you're doing a
dotnet publish
to deploy the output, make sure to
dotnet build
first, a publish does not automatically run a build.
r
that would be my error then, I went dotnet run, checked if the project ran and worked and right after dotnet published
s
hmm,
dotnet run
does a
dotnet build
first but do check locally if the version says 15.1.2
r
locally it is 15.1.2. I might just give it a shot with a new build and push that up. Might have just been something weird, an anomoly lol
s
possibly! 🤞
r
Will start off the build and push! Hopefully all good this time 🙂 thank you for your help
s
Just realized, if that doesn't work: I am able to deploy all the files on my Linux/kestrel server but it doesn't restart the site when I do so, so you might just want to force a reboot of the site after deploying.
r
I did force a restart on the server and a cache clearing within umbraco settings! I did skip over one dll that was already on the server that gave me errors, might have contributed to my problems but didnt think much of it considering I saw 15.1.2 on the server where you can check installed plugins and packages.
s
So yeah, do not cache clear, absolutely no need. Do not skip over dlls, that's your possible downfall. Guess you will need to stop the site, deploy the files and start it again.
r
Good to know about the clear cache. Its not beneficial after minor upgrades?
s
It should only ever be necessary in extraordinary cases 🙂
r
One last thing since i have you here lol, on localhost I can check the contents of my page, but when I get onto the server I'm no longer able to view it, it only shows our inherited composition SEO tab. Is there a reason this happens only on the server?
btw 15.1.2 now shows on the server!
s
your database locally is different from your database remotely - investigate uSync to make sure they keep in sync after deploys
r
local & server are both pointing to the same DB, ive added fixes ive seen on github where allowing concurrent logins is true, webrouting etc to mitigate other errors that i encountered. Is looking into usync still necessary if both are pointed at the same DB?
s
Oh, now you've entered the realm of load balancing, which is a whole huge other documentation page. I recommend not doing that, and using something like uSync instead. 🙈 😅
2 sites using the same database automatically lands you into load balancing territory with a lot of problems if you don't set it up properly. Most of all, you can only have 1 backoffice instance that updates the database, so this current setup will have all kinds of problems for you 😅
r
Yeah already seems like im running into a few of these problems currently, and this is just local to staging server lol. Good to know, I'll have to fix this issue then, jumping into this as my first umbraco project, so im still figuring out what the no no's are haha. Thank you for that answer 🙂
s
No worries! It's a learning curve for sure! I'm off now, good luck separating those databases! 🤘
r
Have a good day! Thank you 🙂
2 Views