InDesign Corrupt files
InDesign users all have to deal with corrupt files sometime during their career using this program. Usually meaning lost time and, more importantly, money. It would be nice if there was a way to have InDesign or another program scan and fix corrupt files (Adobe FirstAid). Dumping this corrupt file into this program would scan the file, find the cause of the error, and isolate it--almost like a virus scanner. Even if this means a page is lost or margins are messed up. It would be nice to at least get some work saved. For example, I throw in a file that keeps causing InDesign to crash. It scans the file. It finds that their is some markup code in a text box on page 23 out of 122 that is throwing an error. This text box is removed, maybe even a red box is put in its place so I know what has been taken out.
Mark Lalumondier
shared this idea
With the release of InDesign 2020(15.0.1), we have enhanced our recovery workflow which fixes multiple scenarios of document corruption.
If your file is still not getting repaired in InDesign CC2020, can you please share the document with Grp-idfile@adobe.com.
Thanks,
Adobe InDesign team"
-
Anonymous
commented
Seems crazy to me that a file created in in an older version of ID (CC v4.0.5) will not open in v13.1. For the amount of money Adobe is extorting out of it's community with the subscription based service, it would seem something so basic would not be an issue.
-
Sara
commented
I'm on a Late 2015 iMac and on Adobe CC 2019. I upgraded to Mojave this morning and have been having issues opening .indd files. I get the error:
"Cannot open the file '___.indd'. Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file may be open in another application."
It's definitely not open in any other programs. I access these files via dropbox. I also ran the Identify script (https://forums.adobe.com/message/4071567#4071567) and the same file gets a "this is not a valid indd file" message. Not sure what the issue is here because I opened these files with no issues on High Sierra.