Skip to content

Debbie Mason

My feedback

5 results found

  1. 53 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)
    CLOSED  ·  Abhinav Kaushik responded

    Hello All,

    Thank you for your patience all this while.
    We had launched our investigation into the matter to get to the root cause of the problem. As the part of our investigation, we had reached out to many of you personally over email.
    We have concluded our investigation and have come up with few findings.

    1. For many of the users the issue got fixed after updating InDesign to a newer version.
    2. For some, the issue got resolved after disabling a third-party application such as Suitecase fusion etc.
    3. For few, the issue was intermittent and is no longer reproducible.
    4. For majority of the users, the underlying cause of the performance issue was identified to be related to span columns, cross-references, third party plugin etc.

    We have created separated threads for these issues and we are now working towards resolving them.

    However, over the time this thread…

    Debbie Mason supported this idea  · 
  2. 103 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)
    CLOSED  ·  Abhinav Kaushik responded

    Hello All,

    Thank you for your patience all this while.
    We had launched our investigation into the matter to get to the root cause of the problem. As the part of our investigation, we had reached out to many of you personally over email.
    We have concluded our investigation and have come up with few findings.

    1. For many of the users the issue got fixed after updating InDesign to a newer version.
    2. For some, the issue got resolved after disabling a third-party application such as Suitecase fusion etc.
    3. For few, the issue was intermittent and is no longer reproducible.
    4. For majority of the users, the underlying cause of the performance issue was identified to be related to span columns, cross-references, third party plugin etc.

    We have created separated threads for these issues and we are now working towards resolving them.

    However, over the time this thread…

    Debbie Mason supported this idea  · 
  3. 111 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)

    Hello All,

    Following up on the comments stating that the issue is yet not fixed, we did our investigation and found that, the issues being called out in the comment section, though maybe relevant but are different than the one for which this thread was originally created.

    This particular thread caters to a very specific case which has been fixed in the last update of InDesign.

    If you continue to face performance related issues with InDesign, we sincerely request you to create a separate thread so that we can categorize the performance related issues and address them completely.
    In addition to track the performance issues effectively, it will also enable us to reach out to you in a organised manner when we investigate into each category of performance issues.

    We are extremely sorry for the troubles you are facing with InDesign and we are determined to resolve them as efficiently…

    Debbie Mason supported this idea  · 
  4. 38 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)

    Hello All,

    We have concluded our investigation into the issue and found that the issue is specific to few versions of MacOS 10.14.×.
    As a part of our investigation we had reached out to many of you, where many of you have confirmed that the issue gets resolved after upgrading to MacOS 10.14.5.

    Note:
    If you are NOT using MacOS 10.14.5 and still facing this issue, please upgrade your MacOs to 10.14.5 version.
    In case you continue to face the same issue after the upgrade, you may reach out to us at sharewithid@adobe.com.

    For any other problem related to packaging workflows please create a new thread.

    We are closing this thread for now.

    Thank you for your patience all this while.

    -InDesign Team

    An error occurred while saving the comment
    Debbie Mason commented  · 

    Also experiencing this issue today. Mac OS 10.14 (18A391), ID v14.0.1, packaging to a windows server (dedicated storage on a windows server).
    2 - Same freeze issue regardless.
    3 - Yes, it froze when the indd and package location were both on the server.

    Debbie Mason supported this idea  · 
  5. 28 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)

    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 Team

    Debbie Mason supported this idea  · 
    An error occurred while saving the comment
    Debbie Mason commented  · 

    I'm having the same issue, only it seems to be persistent with the 2018 version.

Feedback and Knowledge Base