Skip to content

Anonymous

My feedback

3 results found

  1. 108 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    I had the exact same issue this morning.

    I save automatically using quick keys (Cmnd S) every few changes so didn't realise that after 7.5 hrs of work my InDesign file wasn't actually saving. I was unable to Save, Save As or Save a copy, all options were greyed out and not selectable in the File menu.

    I was working on a pretty basic InDesign file (mostly text and tables) using the latest InDesign CC 2019 version 14.03.3 running from my hard drive on macOS Mojave version 10.14.6 running on an iMac Pro (2017). I understand the software had updated to the latest version automatically that morning.

    I was also unable to package the file (an alert advised the file could not be saved). Luckily I was able to export a PDF, but didn't think to export as an IDML before the program spontaneously Quit itself and I lost 7.5hrs work.

    I have had CC for less than a month after being forced to upgrade to a subscription from my trusty CS6 which worked fine on my previous iMac but is no longer supported on the updated iMac Pro.

    Such a huge 'bug' to have in your software Adobe given how expensive subscriptions are and how sole traders like me rely on the software for our income. This is a massive stuff-up yet I see you have closed the previous thread related to this. This should be being investigated and addressed so others don't lose hours of work.

    Please fix!

    Anonymous supported this idea  · 
  2. 127 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    As part of the investigation into the cause of this issue, we personally reached out to many of you over email. We have so far heard from only some of you.

    Of the responses we have received, the conclusion we’ve come to is:
    This issue was intermittent, happened once during the course of work but somehow got resolved and has not happened again. This issue can’t be reproduced now.

    Over a period of time, this thread has not thrown any fresh clues on why this issue seems to occur randomly for some and then seems to resolve itself. So we’re closing this thread.

    However, even though we’re closing this thread, if you again run into this issue any time on a consistent basis, please report it here on UserVoice (in a new thread) with supporting assets like:
    A) a test file,
    B) detailed steps to replicate the issue
    C) any…

    Anonymous supported this idea  · 
  3. 101 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 

Feedback and Knowledge Base