fsm
My feedback
9 results found
-
21 votes
Thanks for reporting the issue. We are reviewing it
-InDesign Team
fsm
supported this idea
·
-
194 votes
Dear All,
This feature is now available in latest InDesign CC version. Please upgrade to the latest release.
Thanks
Abhinav Agarwalfsm
supported this idea
·
-
14 votesfsm
supported this idea
·
-
17 votesfsm
supported this idea
·
-
7 votesfsm
shared this idea
·
-
228 votes
Thank you all for your feedback and votes on the feature request.
We are currently looking into this important feature request. As part of the evaluation, I would be reaching out to some of you to gather deeper insights.
Please help us by providing your valuable inputs and feedback.Regards,
Abhinav Kaushik (AK)
Product Manager, InDesignfsm
supported this idea
·
-
108 votes
The fix for this issue is now available in the latest update of InDesign – that is, InDesign 15.0.2.
Please update your InDesign application to get this fix.
—
Adobe InDesign teamAn error occurred while saving the comment An error occurred while saving the comment fsm
commented
@Bertrand Richer: Interesting. I work on a document with a lot of text frames that are set to resize automatically. No problems up until now: I deactivated auto-resize for one specific text frame and linked it to another one. I then made some more edits, hit Cmd-Z eventually, and boom – got thrown back to right before when I linked the text frame (placing cursor is active, so it reverted right back to the point when I clicked into the little "+"-icon on the text frame). This text frame also reflows around a placed image (which caused some trouble on its own in the .0-version).
This is still far from being reproducible, but a colleague of mine encountered this bug at a very similar situation as well (linking text frames, cmd-z then reverting back to the moment when linking text frames).
An error occurred while saving the comment fsm
commented
This sounds an aweful lot like this (unsolved) problem here: https://community.adobe.com/t5/indesign/indesign-cc-won-t-save-my-files/td-p/5167203
or here:
https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/32243044-i-lost-all-save-save-as-undo-functionality-everUndo/Save either becomes unavailable or (that seems new) reverts back to the last saved version. There do not seem to be specific steps to reproduce this behaviour. A colleague of mine may work a day on a variety of documents without ever running into problems, the next day it will hit eyery other minute. Same docs, same machine (macOS 10.14.6). 2020 docs as well as docs that have originally been created with older versions of InDesign. No third party peripherals. All docs are saved locally, no NAS, no server.
Additional weird behaviour, as reported by Alksei Koren below: Resizing text frames will not show until the document is saved or you hit Alt-Cmd-C (see comment from Thorsten Rösch-Allgeier). No clue if related to the Undo/Redo/Save-problem, however it happens to my colleague a lot, and if it happens, Undo/Redo/Save problem often shows, too.
I myself only ran into problems only once, when Undo was suddenly greyed out for no apparent reason. However, Save was still available and anything I did from there was undo/redoable again.
An error occurred while saving the comment fsm
commented
@ Thorsten Rösch-Allgeier: Regarding „Full disk access“, since at least one user encounters the problem under 10.13.x it seems unlikely to be the culprit (full disk access was introduced in 10.14 iirc).
An error occurred while saving the comment fsm
commented
Happens to a colleague of mine (macOS 10.14.6) in most, but not all documents (and not all the time).
fsm
supported this idea
·
-
96 votesfsm
supported this idea
·
-
46 votesfsm
supported this idea
·
I just successfully finished a 216-pager (with tons of auto-resizing text frames and object styles applied) and was hit by the bug only once (when text wrap around graphic frames was involved - as soon as I avoided the text wrap, everything went fine; might be coincidence, though, did not want to try my luck too hard :)).