Corrupted Elements File on Project Open

Elements
1

Hey @Dan and @Ben,

My Elements file became corrupted upon opening this project and the same issue occurred with a website I built last week. Both times, I had to manually delete all the components. In my last project, it was on every page. In this project, it’s only the homepage. I’ve left the corrupted file visible to demonstrate the issue in hope of identifying the root cause!

I’ve uploaded it here:

elementsapp://downloadDocument/wUKOd9lIYzP6

Thanks

2

Where are you storing the Elements project file?

3

The project was built on my iMac and copied into our cloud storage pCloud. This was then opened by my colleague on his Mac Studio. All the original pictures used in the project are still on the iMac that created the original Elements project. Once a picture is added to a project, I assume it became “embedded” in the project so it no longer needed to available?

I should point out that the first time the project is opened on the other Mac, it opens perfectly fine with nothing out of place just as I designed it. It’s only a few days later when re-opening the project an alert appears revealing a number of missing parent files saying…

Document Repaired
Home:Unknown - missing parent
Home:Unknown - missing parent
Home:Unknown - missing parent
Home:Unknown - missing parent
Home:Unknown - missing parent
Home:Unknown - missing parent
Home:Unknown - missing parent
Home:Unknown - missing parent
Home:Unknown - missing parent
Home:Unknown - missing parent
Plus 24 more issues

Looking at the project, it seems all the offending error files are at the top of the page and deleting them via the Node Browser seems to resolve the issue but as you can see, there are quite a few and on the other project we had a problem with, the error was on every page.

4

Hi @jackesquire,

Sorry to hear you’ve hit this problem. It’s something we’re aware of and we’re trying to narrow down the root cause. We’ve identified that this can happen when using globals. When an item is moved or deleted, the action fails to replicate across all globals leaving nodes without a parent. These are then picked up on the next project load and tagged with <RECOVERED>.

Any recovered nodes can safely be deleted. If you’re able to reproduce it in any way, please do let me know.

Cheers