We have been using an InDesign/InCopy workflow for a little over a year. Until recently, we were using InDesign5 and InCopy 5.5, and we had no problems opening and working in the assignments. In the last month or two, some of our new freelancers purchased InCopy6, and it quickly became apparent that it was not compatible with files created in InDesign5. They were unable to open packages, or if a package could be opened it ultimately crashed and lost the changes.
We have upgraded across the board: designers all have InDesign6, and editors/copy editors have InCopy6. However, this upgrade has not resolved the problems and, in fact, the problems seem to be increasing. Many of the files still cannot be opened (often, InCopy shuts down when trying to open a file and says "a serious error was detected"); this seems to be happening more with larger files. Also, some projects open but have pages missing from story/galley view.
Our designers say that they are continuing to work and create assignment packages as before, and even our veteran editors and copy editors are having issues. Does anyone have insight into what may be happening and how we can resolve it? At this point, it's getting hard to rely on this workflow.
We are having the same problem; we have only been able to open one file since we upgraded to CS6. When we open an InCopy file, it reaches the importing snippets stage and then crashes. We've tried reinstalling the software, which hasn't made any difference. I'm hoping someone has a solution.
The designers are using InDesign CS6 on Windows 7. They then send us the link for the icma file, which is on a local server (not sure about the specifications). We are using InCopy CS6 running on Windows 7 (we don't have InDesign on the editors' computers). We tried packaging as a work around, but we had the same problem.
The editors/copy editors work only with the InCopy file, not InDesign, and they are mostly unable to open the files now. However, some files do open, but they seem to be the ones that are much smaller in size. Could file size have anything to do with the problems? (It didn't seem to before, when we all had the previous versions of CS/InCopy.)
Some of the workflow is server-based, and some of it involves packaging assignments. Here's a summary: Our in-house designers create the files in CS6 on Macs and package them for either our in-house editor (working in InCopy6 on a Mac) or place on the server for me (also InCopy6 on Mac) to send (either as an e-mail attachment or via Dropbox, depending on file size) to our remote copy editors (working in InCopy6 on Macs and PCs). Right now, all groups seem to be having trouble.
I have to admit, I’ve become less of a fan of packaged assignments and much more a proponent of using Dropbox for this.
Save all the files there and everyone has access including being able to open the InDesign file directly in InCopy.
That said, if these were previously saved in an earlier version of InDesign I would be tempted to kill any assignments and InCopy content and create it all again in CS6. As an added measure I’d save the file as IDML first to clear out any corruption.
The designers asked me to add the following information:
export for Incopy by selecting:
Edit-Incopy-add all stories to assignment- new.
This is then saved to a location on the server. This method always worked when we were working in Indesign CS5. We have tried saving the Indesign file as an .idml in case the document is corrupted, but this doesn't seem to be the problem.
This problem is happening between two different design pcs, and two different subbing pcs.
The ICMLs are also there. We've just tried opening an InDesign file on InCopy. It opened, allowed us to edit (raising excitement) and then crashed the designer's computer when she tried checking in the changes.
It does sound as if you're doing everything right. I'm sorry this is happening.
As Bob recommends, see if you can narrow down the variables by disabling any third-party plug-ins that might have something do with the issues.
In your shoes, I would test to see if you can replicate the problem without the server:
1) Get a computer with both ID CS6 and IC CS6 installed. Give yourself a different username (File > User) for each app.
2) In ID, open one of the INDD files that is causing problems. Export All to a New Assignment, making sure it saves everything to your local hard drive.
3) Switch to IC and see if you can open the Assignment, check out stories, edit them, save them, etc.
4) Switch to ID and see if you can update the out of date stories.
You might try replicating the Package for InCopy/Return for InDesign routine too.
One last thing, though I know it's not much of a help at this point ... I caution my clients to hold off on using any "point oh" release for actual production work. Wait for "point oh one" (in other words, InDesign CS5 6.01), where these kinds of issues are most often resolved. If Adobe's patch update schedules are consistent with previous CS releases, I wouldn't be surprised to see a CS6.01 for both InDesign and InCopy sometime this summer.
I don't work for Adobe, so I don't know if what you're suffering with is a known 6.0 issue or not. But anyway, try taking third-party software, and then the server itself, out of the mix. See if anything is different there.
Thanks for the suggestions. Bob, it sounds as if using Dropbox from the get-go may be a good solution. Currently, the designers save the files as .icap. Just to be clear, what terminology should I use to ask them to save the file (you mentioned the InDesign file could be opened directly in InCopy)?
We gave that a try, and the file still won't open. (We tried with a couple different files, of varying sizes, and none was successful.)
It is possible that our problems have anything to do with our having the trial versions of InCopy6 and InDesign6? We wanted to test the trial before paying to upgrade, to make sure the upgrade would fix the problems. I had a frustrating phone conversation with Adobe support this morning, in which I was told that they don't support the trial version. It doesn't seem logical that the trial versions would have errors in simply opening the files, but we are trying to examine any possibility.
I am a designer working for the same company as Claire N (posts above). We are still unable to use Incopy as none of the above fixes or suggestions worked. It's now more than two months later and it's making our jobs very diffcult. Is there a fix or update on the way that may solve this issue?
We are having the same issues here - opening CS6 Indesign files with CS6 InCopy using a Dropbox work flow.
I'm the designer working on a Mac, saving InDesign CS6 documents to a shared Dropbox folder. Editors then open with InCopy CS6. About half the PC users using InCopy CS6 can't see the Galley or Story tab, only the Layout tab and can't edit at all.
The issue seems to be with some PCs and not with others.
I'm at my wits end here. I recomended an InCopy workflow and my reputation is at stake. CS5 InCopy and InDesign seemed to work fine. But the CS6 workflow has been a disaster.
I have a video that goes into detail how to use InCopy/InDesign in a Dropbox workflow (and how to troubleshoot issues) in my lynda.com video tutorial title.
Go down to one of the final chapters where I talk how to do a Remote workflow, you'll see a vid's title with "Dropbox" in it. You don't have to have watched all the previous vids to understand it, but it does help to understand the basics of how the ID/IC workflow works.
InDesign: Collaborative Workflows with InCopy
(it covers CS5 but there's nothing diff in CS5.5 or CS6).
Basil, if your InCopy users can't see the Galley or Story view, that means they can't access the linked story files for the stories (text frames) in the INDD they're opening in InCopy. There could be a few different reasons for this, most common are:
Make sure everyone is working in that same dropbox folder, don't copy/paste or drag it out of the dropbox folder. I often find that individuals think they're supposed to work on a copy outside of Dropbox.
So, work directly in the Dropbox folder, and don't rename or move the files. No "Save As's" either. Basil if you're the ID user makes sure you're exporting stories to a subfolder in your project folder (where the INDD file is located) which of course is in the Dropbox folder.
I wrote this original post in early July, and the situation with InCopy6 only worsened over the last few months. We have lost countless hours of copy editors' work as problem after problem kept cropping up. We tried all the suggestions here (and elsewhere) and had our IT department working on it, but to no avail.
Just last week we abandoned the InCopy workflow and have reverted to Word. It's disappointing, since InCopy 5 and 5.5 worked so well for our situation, but it isn't worth jeopardizing our deadlines and quality -- and, especially, our sanity.
Best of luck as you search for a solution.
I have watch your entire series on InCopy Workflow available on Lynda.com, as well as many others. Your tutorials are excellent, I'm a big fan.
My problems with CS6 InCopy workflow presist however. We are vetran InCopy CS5 workflow users here. But since upgrading to CS6 we're experiencing numerous issues.
Here's the situation:
- I and our creative team use Mac Book Pros running the latest version of Mountain Lion (v 10.8.2) and InDesign CS6
- Our editors work on Dell Laptops running Windows 7 and InCopy CS6
- We all use a Dropbox work flow
- Projects begin by myself opening a template from our compliance department (also InCopy workflow). I then "Save As" the new InDesign layout into a new folder in Dropbox, I delete "unlink" all stories from the new document, Then re-save all stories into a new "stories" folder in the same root as the new document.
- Editors then update the content for the new client
This workflow worked flawlessly under CS5, but now doesn't work on half of the PCs.
Making matters worse (for me), I convinced our management to upgrade all the computers to CS6!
As far a I know, all applications are up to date. We alway work directly out of the Dropbox folder.
I'm continuing to work this issue from my side. I appreciate any advice you may give.
Here's a follow up.
I've isolated the issue to a corrupt .indd file. I can't explain how the file got corrupt, but I'm fairly sure this is the cause of my issues here.
Here's what happened.
We use a Dropbox workflow.
I start by creating templates for what we call "program guides." I believe I originally created the template in question with InDesign CS5, but it may have been created with the pre-updated version of InDesign CS6. I don't remember. I then save the stories to a stories folder in the root folder of the document so a compliance officer can edit the content via InCopy CS6.
When a client needs a Program Guide, I then open that template and re-save it into a client specific folder. I delete/unlink the stories and re-export new stories into a stories folder located next to the specific client's Program Guide. Program Managers then edit the marketing portion of the Program Guide content via InCopy CS6.
The issue in this case - the Program Manager could not edit the document, nor could he see the "Galley" or "Story" tabs indicating that InCopy could not see any linked stories.
- I tried re-saving the document, deleting and re-exporting the stories; same result
- I tried exporting the document in .IDML so as to "clense" it and eliminate any corruption; same result
- I tried eliminating elements from the document, one by one, to asertain if a corrupt element (image or text box) might be the culprit; same result
- I finally created a new document, with new text frames and cut and paste the "text only" into the new document/text frames - this worked. When I exported the stories, InCopy was able to see and edit them.
As I believe my original work flow was correct, I still regard this a "bug" in InDesign as the issue seems to have something to do with the way InDesign saves/re-saves an InDesign document.
I do believe I have a tempory work-a-round that will allow me to continue using an InCopy workflow until Adobe updates the software.
Congratulations on solving the problem! Corrupt InDesign docs do happen, InCopy or not, Dropbox or not. Corrupt *templates* are crazy-making.
One thing with your workflow, as I understand from your desription ... I don't recommend saving an INDD file with linked IC stories as a template. Too much work and too prone to confusion. Instead, save a "regular" INDD file as a template (no stories exported to IC). When you need to use the template for a project, open as usual ... it opens as an Untitled doc ... save it in a project folder ... *then* export the stories to IC or make assignments or whatever.
Same thing with using a regular INDD file as a quasi-template, such as re-using older versions or issues of a pub for a head start on a new version. Don't Save As with linked ICML stories, always embed the stories first (unlink) and then do the Save As.
In fact, I make it a point during training to recommend that as part of the "prep for the printer" stage that the InDesign user unlink all the InCopy stories, which converts them to regular InDesign text frames, and then delete (or, if you must, archive) the old ICML files. Do this before the File > Package step or File > PDF Export > Press Quality step.
Then should you ever need to use that pub as the start for a new version/issue, you'd do a Save As as usual, and then export the stories to InCopy format for the new project.
Good advice AnneMarie.
That may have been the root of the issue all along. I will from now on, un-link all stories before re-saving to see what happens.
Our documents here are all "live," ever changing. For that reason, we use regular .indd files as "templates." Maybe I should consider "freezing" versions as real templates (.indt).
If you're ever in Atlant speaking, let me know. Indesign is my life here as boring as that sounds, so I try to stay "abreast" of the latest info.
Thanks so much.