Sonja
My feedback
3 results found
-
28 votes
Hello All,
Thank you for your support. The issue is now fixed in the latest update of InDesign.
Please upgrade to the new InDesign 14.0 from your Creative Cloud Application.If you are unable to see the update yet, click on the menu (three dots) on the top right corner of Creative cloud app and click on “Check for App Updates”.
Let us know your feedback in the comment section.
Thanks,
Abhinav Kaushik
InDesign TeamAn error occurred while saving the comment Sonja
supported this idea
·
An error occurred while saving the comment Sonja
commented
Same issue here.
It began a few ID-versions back, maby 2 years ago, and still remains in the most recent version (13.0) – even after replacing my macbook and a whole new OS (10.12.6 – not installed High Sierra yet to avoid early bugs) after clean install. This so annoying. Especially when I have to launch the programm after the many ID-crashes! I often have to restart the program 3-4 times in a row until I have all menues and functions back working.
Guys – please offer less software updates but therefore fewer and safe versions. We're all not using Adobe for fun but to do our daily business. So please fix the issues soon.
-
2 votes
An error occurred while saving the comment Sonja
commented
Hier übrigens eine "Anleitung".
https://helpx.adobe.com/de/indesign/kb/troubleshoot-damaged-indesign-documents.html
Das hilft bei mir allerdings nicht. Und auch schon in der alten Version.
– Voreinstellungen löschen und ersetzen, bringt nichts.
– Beschädigte Dateien kann ich ausschließen, das der Fehler bei einfachen wie sehr komplexen Dateien entsteht. Und auch unabhängig von Erstellungsdatum oder Inhalt.
– Beschädigte Schriften kann ich deshalb auch ausschließen (zumal ich auch die neueste Suitcase-Version verwende, die mit beschädigte Schriften sofort aussortiert).
– Andere Dateiformate abspeichern (idml) oder exprotieren geht nicht, kann gar nichts mehr speichern bei Fehlercode 0.
– An Zeichen- oder Absazformaten kann es nicht liegen, das der Fehler auch bei Dateien ohne solche passiert.Mein Lieblingsllösungsvorschlag von Adobe:
"
Öffnen Sie das Dokument auf einem anderen Computer. – Durch den Wechsel der Systemumgebung werden die Ursachen des Problems möglicherweise behoben."WUHAHAHAHAHAHAHA! Ja, das funktioniert ganz sicher!
Die neue Version läuft übrigens auf einem nigelnagelneuen MacBook Pro nach einem Clean Install (Mitte November 2017 gekauft). Es kann also auch nicht an "Altlasten" liegen, die sich irgendwo eingefressen haben.
Sonja
supported this idea
·
An error occurred while saving the comment Sonja
commented
Same here (since CC2017 and also now in CC2018) – happens very often but randomly. I cannot say when or why.
On error code 4 ID is already running. If i want to open a file it tells me the file is "damaged". Error code 4 goes hand in hand with error code 0, which doesn't let me save a file that I am currently working on.
Both errors force me to quite ID and open it again. This happens alt least 2-3 times a day. Very annoying!
PS: Wolfgang, I guess, you are from Germany? Me too. Maybe it has something to do with the language version ("Fehlercode 4" und "Fehlercode 0"). I cannot find English comments on that issue.
-
8 votesSonja
supported this idea
·
Dear Abhinav,
I tested the CC2019 for 2 days now. The panel issue in InDesing is gone but I have gotten a few more new issues instead and I am extremely unhappy with the update to CC2019!
The complete Suite works super slow. Launchin programs drives my laptop fans wild and hot (MacBook Pro (15-inch, 2017), 3,1 GHz Intel Core i7, 16 GB... which was the biggest one last year when I bought it!).
Every few "clicks" the lolly pops up (even if I only mark text in ID) and I cannot do anything for minutes.
Don't know how to handly my workload when this is the new superslow "workflow"... I hope you will release a fix soon.