V17 notification "This Block is not yet created for this variant"

Questions
1

I just noticed some content is missing since upgrading to v17 and on checking I am getting a message I have not seen before?

This is happening with only some existing content not all.
Creating new content seems to work fine.

I do not have languages set.

image
image512×265 12.4 KB

3

Hey @KevinJump is it possible my usync on first boot removed data whilst upgrading to 17?
It seems odd some content was fine and some was marked as “This Block is not yet created for this variant”
Adding them by clicking the “+“ fixes it.
I can go through the site and bring all the content back in but just in case it happens in a big site.

image
image3818×1151 447 KB

4

Hi @deanleigh which version did you upgrade from?

And then you may share a bit more information regaring the configuration of these Blocks. Especially regarding how they Vary. both regarding the Element Type and the Property holding the Blocks.

5

Hi @nielslyngsoe
I went from 17 beta through RC1,2,3,4

Last few commits attached

image
image268×148 2.53 KB

The blocks and content are the same as they have been since version 13:
Layout blocks with Feature blocks in the areas.
All in a single Web Page doctype in a single Block Grid.

The Element Types are all compositions i.e. A Feature composed of things like Feature Title, Feature Description and the Feature Content e.g. RTE, Image etc…

The odd thing is that some features and pages were fine and others not yet no difference between them.
If you install a current v17 UmBootstrap you will be able to see for yourself.

6

At a glance your source uSync files seem old ? -

as that’s the older format that Umbraco was storing the block values in in v13 (maybe in v14 too, can’t quite remember) but it was updated in v15/16 .

So you might need to re-export everything on the master so the newer versions are used (I would recommend after an upgrade you always do a re-export to ensure things are at latest).

If uSync encounters the old format should actually update the old values to the newer ones. it does have the code in to do that migration (its pretty much the same as the core umbraco stuff , but i will double check see if anything extra has been added to core one since we did that).

But in your case here when you upgraded the master project Umbraco will have done it’s version and a uSync export should put it out to disk, and then the package will have the newer version of the files in it.

7

Thank @KevinJump
That has helped me piece together what I think were I think the sequence of events which may help you too @nielslyngsoe

  1. I have had the same content since v13
  2. I upgraded to v17-beta then v17-rc1
  3. At v17-rc2 I edited some pages
  4. I upgraded to rc3 and rc4 then v17 LTS
  5. Then I upgraded Usync

The pages that had the issue with variants were the pages I had NOT edited at v17-rc2.
This was my rc2 commit

<ItemGroup>
    <PackageReference Include="SixLabors.ImageSharp" Version="3.1.11" />
    <PackageReference Include="Umbraco.Cms" Version="17.0.0-rc2" />
    <PackageReference Include="Umbraco.Community.BlockPreview" Version="5.0.0-rc1" />
    <PackageReference Include="Umbraco.Community.UmbNav" Version="4.0.0-beta0052" />
    <PackageReference Include="uSync" Version="17.0.0-rc1" />
  </ItemGroup>