Hi.
I am working on upgrading one of our older sites that started as a V8 site, that over the years has gone from 8, 10 to 13 and I am now upgrading to version 17.
I am seeing this when I am clicking between pages.
I am using the Block Grid Preview, I am not seeing this on any other site that we are using the block grid preview.
I dont think it a block grid problem.
Is there a way to do a clean up to stop this.
Thanks
Darren
It could be that a property is being updated due to a change in how property values are being stored, so when you open the page something is updating even though you are not doing it explicitly.
Are you able to narrow this down to a particular document type or property? A quick way to test is to create a blank node of one of the affected types and see if the prompt still fires. If Saving/Publishing the node makes it go away then that may be your culprit but the difficulty maybe tracking down which property.
Justin
It looks like it some thing to do with content, I removed all the text areas / boxes and left the images.
Tried again and I still see the save change.
If I remove all the content and then save the page, I am not seeing the error.
It defo a content problem.
I do some more digging.
Darren
The console error may or may not be related. Have you managed to narrow it down at all?
Justin
No It some thing to do with older content that converted from Nested Content to Block Grid.
I removed every except for the grids, and I am still seeing the same issue.
With just a grid with cols in it.
Darren
I’d recommend building a new page from scratch, add grid items to it that the problematic page has. Test that it works as expected, then go to History > Rollback and see the raw stored data. You should be able to compare the raw json between the problematic node and the new one and see what the differences are.
If I am correctly when I converted the site to 13 from 10, I think I used the deploy tool. with some bespoke code. The sites been on 13 for about 10 months, so rolling it back to 10 and then doing the update again, is out.
I had this happen with browser extensions like LastPass or BitWarden. If you have extension permissions to “auto fill” logins and forms, they’ll recognize a form field property as something it thinks it should prefill. Check form fields on the page and see if that’s the case maybe?
I think it an old content issue, I removed every thing except some block grids, and I still see the same thing. It some sort of content issue.
As if I create a new page and add items, save the page then go back to the page later i dont see the save issue.
I would remove/clear out content one property at a time until the errors goes away to narrow it down. Once you’ve got to that point, you can check to see what was causing the issue and check the raw value in the database (ensure you have a backup to refer back to).
It definitely sounds like a content issue from the migration.
Justin
