And I'm going to test my theory / query
# social
s
And I'm going to test my theory / query / issue myself then create a forum post. Hopefully it will help others. I'm basically dabbling with a v16 upgrade and hitting a few bits and I've no idea if they are new issues, issues that need a fix, things that I can workaround etc etc.
r
I tend to agree with tghis being a forum post, as its possibly knowledge that will be useful to others and therefore more widely availa ble
but the thing i will say, is i liked you asked the question of where is the rght place..
s
Sometimes it's nice to be able to sense check something without it becoming a forum post and looking dumb for the rest of eternity.... 😉
OK so here's a dumb 101 issue I'd rather sense check than forum post up. I've updated my templates - run the Umbraco template for LTS (expecting a fairly latest and greatest 13.x)... Installs but the site doesn't build. Two things 1) It's due to a partial view error - huh - thought views were only compiled at runtime and these wouldn't stop a build (I feel dumb here - you can tell I don't create new solutions very often...) 2) Is there really a bug in the core partial view /Views/Partials/blockgrid/items.cshtml where data-element-key="@item.ContentKey" should be data-element-key="@item.Content.Key" Seems odd this has never been spotted
m
@SiempreSteve 1. You mentioned v16 earlier and a upgrade. Now you are talking about “installing” LTS. What exactly did you do? Upgrade? Fresh install? Or did you have a v13 site and just updated the packages? 2. Most likely left overs from v13 right? Updating the packages references would not update your view files. Here is what I would do: install a clean instance of the target version you are looking to upgrade to in a a new fresh folder. Update package references in your v13 site to v16. Compare file content from the fresh v16 and adjust the upgrades site where needed.
s
No - this was a completely clean install from Visual Studio using the Umbraco Template. Instead of specifying a version I had a drop down with Latest or LTS - LTS created an install with this error.
I was doing this to test the upgrade path from a vanilla v13 -> v16 to see if my other issue was something in my project only and hit this wall first.