I can't figure out why this is happening. Another user posted about it in 2016, and the post was moved to the "epub forum" and was never answered. I have known of the (theoretical) existance of this forum, but seems like something changed on the website and we can't actually search for anything in that "forum" or post anything directly to it—even if we add the epub subject tag. But trying anyway.
The file is currently built in CC2018 and I have not really run into this before. The chapters are in a Book file. There is no overset text, nor extra returns or page breaks at the ends of the file. All text and objects are in a single thread in the documents.
When previewing the epub in iBooks there seems to be anywhere for 5 to 16 or so added blanks. looking at the HTML in the unzipped files these are divs with a uniquely numbered image container and a class, within a Basic Text Fram class. Like so:
<div id="_idContainer287" class="Basic-Text-Frame">
<div id="_idContainer288" class="Basic-Text-Frame">
I don't have any blank boxes in the files that I can find.
Has anyone else figured out why the extra pages and how to avoid that?
I can removed them in the HTML code, but I would surely prefer not to have to. There ARE background colred pages in the document on other hidden layers (used in the print version) but these shoudn't be exporting at all. Seem's like it would be many more pages ifo that were the case.
Two perhaps related questions:
1. What is the corrct choice for exporting a book with images to include "classes" or not to include. The default is to include and I've always done that.
2. Why does an epub exported from a book file with multiple separate ID chapter files create another CSS for each chapter? These are mostly full of idGenObjectAttributes, but why couldn't those be all in one CSS? I believe they are needed for calling out the sizes of objects when they are are all different—I've selected Preserve Appearance and Relative to Text Flow for most images. This is a complex reflowable ebook and writing a single CSS myself would be impossible for me. But all these CSS docs are pretty unwieldly.
I may have found the issue with the extra pages. When the book was reflowed it somehow got out of the Master Text Frames on some pages but was still linked to the master text frames on others. This left a bunch of blank text frames on the pages behind the new frames with text in them. I've seen this happen before, but didn't equate it with adding pages in the epub. Too bad there isn't a script to locate all empty text boxes and delete them! (Or maybe there is?) I located as many as I could find and deleted and that seems to have done the trick.
I struggled with and worked around this identical problem by editing chapter files containing extra pages. I'd unzip my epub, then delete extra page related html; an abbreviated example shown below:
I explain this to say thank you and ask if you've learned anything new related to this problem since your Feb 22, 2020 post.
This is what I've done too. I think it's worthwhile if you notice this is happening to visually search through the InDD before conversion and eliminate all the empty boxes you can find. Saves some time (and possible messed up code in my case) over messing with the html. But yes, almost every book requires a little tweaking in my experience.
Nothing new to report on the extra box problem—if we want the text to actually reflow if we change master pages they need to have the master (primary) text frame, and this seems to cause the issue. I know no way around it.
I'm having the same issue. How did you find these "empty boxes"? Similarly, how do you unzip an epub file to look at the code? The Adobe technical team does not know. Please help!
So I was having a similar problem—when I produced reflowable epubs they were fine in Kindle Previewer but for iBooks all sorts of blank pages were added at the end, which were likely related to original smart reflow preferences or something. I occasionally look at these support forums when I'm stuck at something but generally balk at going into the HDML/CSS code, and when I see an explanation with a screenshot of 15 "div" commands my eyes tend to mist over. No disrespect to those who do this for a living, it should be stressed, but we all draw our lines somewhere. Anyway, I found a script which will eliminate these troublesome hidden text frames that were padding my epub with all sorts of extra pages on the end. It's called Delete Empty Text frames and is freely available here. It worked for me, so hopefully it will be of some use to others.
Thank you so much for your response. I was able to eliminate the problem by exporting the book according to the "articles" as opposed to what was on screen. There must have been hidden text frames somewhere. Thanks again!
That's fantastic - thank you! I never ever would have solved this problem on my own!
Glad it could be of some help.
You state that you are working on a complex reflowable epub in InDesign. Have you ever considered a dedicated epub tool like Jutoh instead? It is catered towards epub creation, while InDesign really is not (resulting in issues like yours). InDesign also hides the underlying content structure, while Jutoh exposes it, granting full control over the epub generation workflow.
I moved away from InDesign for any reflowable epub work. It is just too fragile in my opinion.
That's interesting, what is the workflow if you have an InDesign document that you want to take into Jutoh?
My goal is to produce beautiful functional books cost effectively from the SAME files as the print book. Books have such a low profit margin that I doubt my publishers would support me doing layout twice.
As long as you do fixed layout this can be done fairly simply with some small tweeks.
The easiest solution, may God bless me for it, is to make the page break with a paragraph style that is not used in headings at all, and be a paragraph style only for the page break.