Hi, I created a local document and wanted to create a public prototype link so I could share it in the browser. I used the “Upload this Document to Lunacy Cloud” option to get this prototype link.
I had to make an update to my document, so I made an update. The update I made didn’t reflect in the live cloud version, and I couldn’t find an option to just un-upload it and re-upload it. This meant I had to save this as a new local file, and then re-upload it. I discovered that I’m limited to 10 cloud documents (including deleted ones), which means each time I want to make an update to an existing document, that would take up 1 of my 10 slots, which seems fairly limited.
Is there a way to just update an existing document, so I don’t have to re-upload it as a new document that would take up one of my 10 documents?
We’ve just checked on our end, and when we make changes to a document in Lunacy cloud, the live prototype link updates automatically to reflect those changes.
Could you please show us what you’re changing and how it’s not updating in your live cloud prototype? A short screencast or step-by-step example would be super helpful for us to understand what’s going wrong.
I opened my document today and went to take the screenshots, but I’m now running into a new issue. Because I had to turn it into a cloud document to share the link, I can no longer edit that document and am stuck in some kind of view only mode even though I’m the owner of the document, so I can’t edit it anymore. Do you know why this happened and how I would return to being able to edit my document?
To help us determine what happened, we’ll need a link to the file and/or the relevant log files.
In Lunacy, go to Help → Open App Data Folder. Inside that folder, you’ll find a Logs folder.
Please locate the log file corresponding to the time and date of the error and send it to us.
We checked the logs and found that you opened a historical version of the file instead of the current one. These versions are read-only, which is why you weren’t able to edit it.
I’ve sent you a link to the correct file in your DMs.
Thank you for finding that in the logs and sending over the file, Evan! Do you know how that historical version was opened, so I can avoid doing that in the future?
For the original issue from this post, I updated one of the frames, and it’s updating as intended without having to re-publish each time, it seems. So I’m not sure if there are any specific settings you changed in the file, but it’s working now.
I mainly worry if I create a new file that it’ll have that historical issue again, so I’m just trying to understand what caused that and how to avoid it in the future.
