Hey, I tried to run the SQL command @JohanReitsma wrote about to change the Element types on the v13 database before migration to v17.
Most of the blocks are OK, but some of them lose the content. It’s strange, because some the blocks that lose content are placed side-by-side to others that don’t lose it so it’s really confusing why this happens. It’s even more strange because the data of the properties that are inherited from a composition remain in the block as if nothing happen.
EDIT:
I found out that properties on those element types can have VaryByCulture too!
So there is the updated script:
BEGIN TRANSACTION;
-- Temporary store the IDs of element types
DECLARE @elementIds TABLE (nodeId INT);
INSERT INTO @elementIds
SELECT nodeId FROM [dbo].[cmsContentType] WHERE isElement = 1 AND variations = 1;
-- Update variations from 1 to 0 for property types
UPDATE [dbo].[cmsPropertyType]
SET variations = 0
where contentTypeId IN (SELECT nodeId FROM @elementIds);
-- Update variations from 1 to 0 for element types
UPDATE [dbo].[cmsContentType]
SET variations = 0
WHERE nodeId IN (SELECT nodeId FROM @elementIds);
COMMIT;
-- If something looks wrong, use:
--ROLLBACK;
But still be carefull, because some element types should not be altered - in our case we have a special configuration folder with some nodes containing global settings, and those should really have variation set to true.