Adobe InDesign: Bugs
When filing a new bug, please provide:
- Version of Adobe InDesign, InCopy or InDesign Server
- Steps to reproduce the issues
- Expected result
- Actual result
- Test file, screenshot, video or GIF capturing the issue (optional)
- or
No existing idea results
- ~ No ideas found ~
6985 results found
-
Search option is not working on EPUB fixed Layout
I have found a problematic bug for .epub files exported from InDesign and opened in Adobe Digital Editions. The fixed layout epub file is not searchable.
To note, an epub file exported from InDesign and marked as re-flowable does work.
This is a SIGNIFICANT issue for me and here's why. I have a 700 page interactive book (includes embedded hyperlinks, videos, audio files) that needs to be distributed and opened by the general population and searchable.
1) The design of the book is formatted per page and needs to remain as laid out in InDesign. This means we can NOT use the re-flowable option.
2) For years, we've exported as INTERACTIVE PDF. This allowed users to open with the FREE Adobe Reader and enjoy all the embedded media and search. However, as an exported pdf format, Adobe Acrobat uses flash to play video and audio rather than a different means and as I'm told, due to the removal of flash, Adobe Reader will no longer allow for interactive pdfs to have audio and video controls. So that makes a PDF format not usable for this project. (infuriating!)
3) Next Option: Publish to Online. However, this option does not allow for search and does not include password protection. Again, making this exported format not usable for my client.
4) Next option: .Epub. On my mac, the same mac that creates the Indesign file, within Adobe Editions, the epub file works as expected. However, it does not work on any PC that we've tested. The fixed-format has an error and is not searchable and on some computers, the epub file will NOT even open in Adobe Digital Editions. Again, making this exported .epub file format unusable.
IMPORTANT: Where does this leave me? What format can I use and distribute from InDesign?
This seems LIKE A HUGE ISSUE for ADOBE and is very detrimental to my professional work.
I've been told that Adobe Digital Editions is an end-of-life product and no longer has support. What application is InDesign exporting epub files to work in then? What other viewing options does my client have?
Please help!
I have found a problematic bug for .epub files exported from InDesign and opened in Adobe Digital Editions. The fixed layout epub file is not searchable.
To note, an epub file exported from InDesign and marked as re-flowable does work.
This is a SIGNIFICANT issue for me and here's why. I have a 700 page interactive book (includes embedded hyperlinks, videos, audio files) that needs to be distributed and opened by the general population and searchable.
1) The design of the book is formatted per page and needs to remain as laid out in InDesign. This means we can NOT…
1 vote -
pdf comments panel (minor UI bug)
Mouseover on the "show comments"-button shows some kind of internal localization reference.
See attached imaged...
1 vote -
Images error for Khmer, Lao, Thai
There is an error in InDesign CC 2021 v16.0
Error in image location for Khmer, Lao, Thai icons.
Please refer to the following URL for reference materials.
https://drive.google.com/drive/folders/1OgwMwY8oHB1yOfO6cYgnPabO1ft9RC3R?usp=sharingMyanmar Unicode has similar errors.
Please also check the URL below.
https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/41076298-font-errors-of-southeast-asian-languages-such-as-mhank you very much.
1 vote -
Creative Cloud hijacks my entire computer - slow to the point of unworkable
I see this issue so HUGE in forums everywhere and find it frustrating with the support team coming up with lame answers every time, mostly blaming the user and with micro solutions that are temporary. These issues are known issues and keep coming back. Support close the tickets too readily and we can't re-open those cases to demonstrate how this is unresolved.
I've tried every remedy including:
- Uninstall Creative Cloud and all apps and reinstall
- Many times 'Repaired' - pretty much every restart it needs 'repairing'
- Used the cleaner tool
- Cleaned specific cache as instructed
- Made a second user to ensure it wasn't any preferences or cache issues
- Watch the activity monitor and close everything else to work
- Had support help and even up to engineers with no luck
- Rolling back to 2018 version
Creative Cloud and using InDesign seems to take up to 2-3G of my RAM to operate which seems ridiculous and taxes the computer too much. That's nearly 50% of the computer's RAM which doesn't seem right. At times I see that I only have 39MB left in RAM and that causes the whole thing to go slow.
I don't really keep anything on the computer and run external drives so that the main computer is not taxed. Still is slow because Creative Cloud is hijacking my 'virtual memory' apparently. I clean regularly and now have to optimise as I work to make it speed up using CleanMyMac.
Now there is a new update to InDesign v16.0 and it is not compatible with High Sierra but says I need 10.14 or later. I'm very concerned about updating to Mojave as it seems that it will only increase the amount of RAM being used and make the computer unworkable. I can't upgrade the RAM at the moment, and I do need InDesign to earn my living. I've timed some days that I lose collectively hours of lost time with this slowness and crashing - it is beyond frustrating and been putting up with it for over a year since the 2019/2020 upgrades.
It really isn't OK that this isn't addressed by Adobe. There are bugs in the code and the cloud based system is too taxing on the RAM. Surely the old way of installing some software on the machine was more manageable.
Is there any way to reduce the tax on the RAM please?
Current computer: Mac OS10.13.6, Retina 4K, processor 3GHz Intel Core i5, Memory 8GB 2400 MHz DDR4, Mac HD, Graphics: Radeon Pro 555 2048 MB
Model Name: iMac
Model Identifier: iMac18,2
Processor Name: Intel Core i5
Processor Speed: 3 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 8 GB
Boot ROM Version: 166.0.0.0.0
SMC Version (system): 2.40f0I see this issue so HUGE in forums everywhere and find it frustrating with the support team coming up with lame answers every time, mostly blaming the user and with micro solutions that are temporary. These issues are known issues and keep coming back. Support close the tickets too readily and we can't re-open those cases to demonstrate how this is unresolved.
I've tried every remedy including:
- Uninstall Creative Cloud and all apps and reinstall
- Many times 'Repaired' - pretty much every restart it needs 'repairing'
- Used the cleaner tool
- Cleaned specific cache as instructed
- Made a second user to…
1 vote -
Indd freezes, then crashes, when opening linked (placed) indd files from an indd file
Indd 16.0 x64, and the previous version. Windows 10. Create a document with test and also linked Indesign "sub-documents" in it. Run spell-check or find & replace, set to check all open documents. Indd opens the linked document, then freezes. You cannot save, quit, or anything. I have submitted numerous crash reports. See https://community.adobe.com/t5/indesign/indesign-2020-crashes-while-using-spell-check-with-linked-indesign-files-on-windows-10/m-p/11608010?page=1#M404257 for details.
My documents are typically books with 10-20 indesign files in each book. Some of the indesign files have placed (linked) indesign files, typically standard "boilerplate" that must be the same everywhere. When I run a spell check across all of the open docs in a book, it opens the linked file then freezes. I later discovered that it does this on a single document if it has placed indd files and you tell it to search all documents.
Indd 16.0 x64, and the previous version. Windows 10. Create a document with test and also linked Indesign "sub-documents" in it. Run spell-check or find & replace, set to check all open documents. Indd opens the linked document, then freezes. You cannot save, quit, or anything. I have submitted numerous crash reports. See https://community.adobe.com/t5/indesign/indesign-2020-crashes-while-using-spell-check-with-linked-indesign-files-on-windows-10/m-p/11608010?page=1#M404257 for details.
My documents are typically books with 10-20 indesign files in each book. Some of the indesign files have placed (linked) indesign files, typically standard "boilerplate" that must be the same everywhere. When I run a spell check across all of the open docs in…
1 vote -
Opening idml from CC2021 crashes CC2020 but not CC2019 and earlier
When I save file as an idml from CC2021 I cannot open it in CC2020 as it crashes. CC2019 and earlier can open idml files from CC2021. It seems to be an issue only with CC2020. I've managed to open a 1 page blank document with CC2020 from CC2021, but anything that I've worked properly on crashes when the idml is opened in CC2020. I've attached an example.
1 vote -
Hi Team, InD CS -yes I know it's from the ark but I love it! It still does a great job!!
When placing an item from Library (in this case formatted Text Boxes), what do they actually link to?
I have them marked "lock position" but then I find them scattered all over the document (a quite long one).
Is there any way to link them (position them) relative to a paragraph mark or some other text item on the page.1 vote -
share for review not working
So first, i made my link and everything went fine. Then after a few times updating it, it started saying that there was an error, and now, there's just nothing that appears in the panel.
1 voteTry the following solutions:
SOLUTION 1
-———
1. Close InDesign.
2. Bring up Creative Cloud Desktop (CCD) and Sign out.
3. Launch InDesign and Sign in here (not from the CCD).
4. Create a new document.
5. Open Share for Review panel.SOLUTION 2
-——-
1) Close InDesign.
2) Close Creative Cloud desktop app.
3) Navigate to the OOBE folder located here:
Windows: [System drive]:\Users\[user name]\AppData\Local\Adobe\OOBE
Mac OS: /Users/[user name]/Library/Application Support/Adobe/OOBE
4) Delete the opm.db file.
5) Launch Creative Cloud desktop app.
6) Launch InDesignPlease let us know if the above solutions work for you.
—
Adobe InDesign team -
InDesign and Publish, Document, Online using MacBookPro upgrade
Upgraded MacBook to OS Big Sur v.11.0.1 and now the Adobe InDesign > Publish, Document, Online does NOT work. It does work for a NEW single page doc. MacBook CRASHES when InDesign SPREAD publish online feature is attempted. PLEASE HELP!!! All of my Adobe InDesign docs are SPREADS and I love the online feature.
1 vote -
sort register
The index does not sort alphabetically
example:EPH98002xx ..... 237
EPH99001xx ...... 237
EPH0100121 ...... 223
EPH0100123 223
EPH0100161 223EPH99001xx should be after EPH0100121
Please fixThank you Paul
1 vote -
insert break character
InDesign 16.0
Insert Break Character in paragraph text inserts a Paragraph Break instead.1 vote -
Danish translation in 'EPUB Export Options' is wrong
In the EPUB Export Options window - Metadata - two fields are translated into Danish. But this is not done correctly.
Re: field 3 "Created by" and 7 "Rights".This Text: > should be translated into this
Oprettet af: > Forfatter: Højre: > Copyright:(because 'Forfatter' means 'Author' and this metadata information is requied in EPUBs.. and 'Højre' means the opposite of left ... so this is NOT the case here ;)
1 vote -
bad hyphenations in english
InDesign CC2021 (16.0) is making very bad hyphenations in English: Great Britain. Some examples in the Screenshot. Thanks for solving.
1 vote -
Cross references rendered to big/wrong line break
Text with cross references isn't rendered correctly. The line break is triggered far to early (see IDML and PNG) image. This affects probably all InDesign Version but was reproduced with CC 2020 and CC 2021
The line break works with the Adobe World-Ready Composers but not with the Classic Composers.
I cannot use the World-Ready Composers because of the justified nonbreaking space see https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/41793187-bug-since-cs6-nonbreaking-space-s-issue-wit
Please fix both bugs!
1 vote -
find/change formatted text error
using cc2021
when trying find/change text with sencences with paragraph style (bold), some characters become regular.
if i change 'Apple' with whole bold to Pineapple, it turns like Pin(bold)e(regular)a(bold)p(regular)pl(bold)e(regular)1 vote -
COMMENT BUBBLE WILL NOT DISAPEAR IN INDESIGN DOCUMENT AFTER CORRECTIONS MADE
COMMENT BUBBLE WILL NOT GO AWAY, EVEN AFTER ATTEMPTING TO DELETE AFTER CORRECTIONS HAVE BEEN MADE.
1 vote -
Clipped items lose their clip when printed
InDesign files with clipped images saved as a PDF look fine in Acrobat. Clip is lost when sending file to the rip. This causes items to overlap
1 vote -
Type shortcut key (t) flips back to previous tool after a second
In InDesign 2021 (16.0) when I press t to get my text tool, the cursor changes to the text tool for about 1 second, then flips back to the previous tool it was on.
This seems to be only with the text tool (t); I can change to other tools without a problem1 vote -
IDS on Windows: Extreme slowness in ExtendScript execution via SOAP connection (with weird workaround)
SETUP
IDS Server 14.0.3.433 running on Windows Server 2019 (build 17763.864)
Local connection using "sampleclient.exe"
Two test scripts (attached):
Slow script: "adobe-ids-win-slow.js" (approx 275 KB in size)
Fast script: "adobe-ids-win-fast.js" (approx 275 KB in size)
PROBLEM
There are two scripts to compare. They are both of identical size, does nothing but declare a variable and return a string value. However, while execution of one of the scripts take a fraction of a second, the other script typically runs for > 10 seconds before completing.
TESTS AND OBSERVATIONS
1) This takes excessive time to run (typically 13 seconds on my test machine):
C:\Users\Administrator\Desktop>"c:\Program Files\Adobe\Adobe InDesign CC Server 2019\sampleclient.exe" -host localhost:8190 c:\Users\Administrator\Desktop\adobe-ids-win-slow.js Script result (std__string): Done2) This completes quickly (typically in less than 0.1 seconds):
C:\Users\Administrator\Desktop>"c:\Program Files\Adobe\Adobe InDesign CC Server 2019\sampleclient.exe" -host localhost:8190 c:\Users\Administrator\Desktop\adobe-ids-win-fast.js Script result (std__string): Done3) Adding the "-server" flag to the slow test will make it run fast, since the script isn't passed via SOAP but instead evaluated directly from local disk. This tells me the parsing of the ExtendScript statements isn't slow in itself so the difference seems to lie in the SOAP request handling.
4) Now a really weird part: removing the very first space (before the comment on line 1) in "adobe-ids-win-slow.js" makes it run almost as fast as the fast script when repeating test 1) above. It turns out that "adobe-ids-win-slow.js" MUST start with a /* */-style comment in the very first byte to run fast; adding the space back, or removing the comment completely, makes it evaluate slowly again. I've tried other tokens such as semicolon, //-style comment, curly brackets etc but none had the same effect.
5) In contrast to the change in 4), adding spaces before the comment, or removing the comment entirely, from "adobe-ids-win-fast.js" makes no difference in its evaluation performance.
6) Another strange discrepancy is that even when "adobe-ids-win-slow.js" is modified to run fast using the change described in 4) above, the speed is still slower than the "adobe-ids-win-fast.js" variant. They both declare a string of same length but the data INSIDE the string is different, but while "adobe-ids-win-fast.js" completes in < 0.1 seconds the modified "adobe-ids-win-slow.js" takes closer to a full second.
7) All of the tests above run at good speed (less than a second) when connecting to IDS 14.0.2.324 on macOS (tested with Catalina 10.15.7). The minor difference in speed between the slow and fast scripts seen in 6) is still present though, but is again eliminated if the "-server" option is used.
OTHER COMMENTS
I tried running Microsoft's Windows Performance Analyzer to capture what the slow IDS is doing during the long wait. I found that the overhead is located in calls from AFL (Adobe File Library) to the NT kernel, but without debug symbols I couldn't pinpoint it in more detail. My totally unconfirmed suspicion is that gSOAP/2.7 (as returned in the "Server" HTTP header in IDS connections) is applying some content sniffing to detect encoding, data format or other properties of the inlined script, but why this would only take place on Windows is a mystery, and it's also odd that the initial code comment would short-circuit this and improve performance dramatically.
I've also tried disabling various Windows Security settings (Firewall, Virus & Threat Protection, Exploit Protection etc) in case that was interfering with network I/O but I've not found any improvement in that area.
The slowness is not inherent in "sampleclient.exe" either since the root problem was first observed using our own HTTP client, as was the weird workaround of adding the comment string. I'm just using "sampleclient.exe" here to set up a self-contained test case.
SETUP
IDS Server 14.0.3.433 running on Windows Server 2019 (build 17763.864)
Local connection using "sampleclient.exe"
Two test scripts (attached):
Slow script: "adobe-ids-win-slow.js" (approx 275 KB in size)
Fast script: "adobe-ids-win-fast.js" (approx 275 KB in size)
PROBLEM
There are two scripts to compare. They are both of identical size, does nothing but declare a variable and return a string value. However, while execution of one of the scripts take a fraction of a second, the other script typically runs for > 10 seconds before completing.
TESTS AND OBSERVATIONS
1) This takes excessive time to run (typically 13 seconds on my test…
1 vote -
CMYK images displaying like RGB (despite CMYK display settings) when using GPU
When using GPU - does not display images in CMYK, but always only in RGB (even if you select transparent filling space CMYK)
It only works when switching to CPU usage
It's a bit anoying. Working with CPU is much slower, especially with big CMYK pictures....
My setting:
I Mac 5K / late 2019 / Radeon Pro 580X
Catalina Mac OS 10.15.71 vote
- Don't see your idea?