CreativePro Forum

Return to Member Forum

• Author
  Posts
• • April 4, 2012 at 10:49 am #61952
    JoAn Armstrong

    Member

    Hi,

    When I export to idml from CS5 or CS5.5, the designmap.xml has the wrong aid type of “pi_for_SaveBackINX”. It should be “document”. Therefore, I am unable to open up the idmls. If I export to idml from CS4, it has the correct type of “document”. I can workaround the CS5 and CS5.5 idmls by opening up the designmap.xml and change the type, but I don't want to have to do that all of the time.

    I am also having problems when I create an InCopy assignment (ID CS5 or CS5.5) by having nothing selected and Adding All Stories to the new assignment. When I open up the icma file in InCopy CS5.5, all I get is the frames with no text. If I instead export each text frame (story) while using the text tool and right clicking and creating a new assignment with the 1st story then clicking in each of the other stories and add them to the assignment one by one, I can open the icma file and all the text is there and editable. But if I use ID CS4 and create an assignment with nothing selected and adding all stories, I can open the icma in InCopy CS5.5 and have all the text there to edit.

    I have tried everything I can think of to try and fix: rebuilt prefs, deleted all 3rd party plug-ins, uninstalled-reinstalled, had a co-worker install my copy of IDCS5.5 and it works perfectly then but not when I reinstall on my computer.

    Does anyone know what is causing the wrong aid type to be written to the xml files?

    Thanks!

    Janine

    Mac OSX 10.6.8

    InDesign CS5.5 v7.5.2.318

    InDesign CS5 v7.0.4.553

    InDesign CS4 v6.0.5.602

    InCopy CS5.5 v7.5.2.318

  • April 5, 2012 at 12:55 pm #61955
    JoAn Armstrong

    Member

    OK, I finally got it figured out after doing another uninstall and a clean reinstall. It worked fine after the reinstall so I loaded up my backed-up prefs, 3rd party plug-ins and scripts. After that, the idml and icma files were bad again. So I started deleting 3rd party plug-ins, still no joy. Then it was on to the startup scripts. I deleted all of the 3rd party scripts and it started working again. After adding back in the scripts one at a time, it ended up being the script Palettenmenus ins Hauptmenu.jsx.

    I went to Gerald Singlemann's website and looked at his instructions again. I had the script in the wrong folder so I moved it to the correct folder and everything works fine again.

    I wanted to report back on what the fix was in case anyone else should ever run into something like this.

    Thanks,

    Janine

• Author
  Posts