In my reports, there is an empty page added after the backups module outputs the table of backups, but only when the table reaches the bottom of the page.
The table doesn’t spill onto the next new page, there is one hanging row or something. The table ends, then a blank page, then the next module is after that.
I don’t get the blank page when the backups table ends higher up on the previous page.
Clearly it’s rendering because it “thinks” the backups table is extending to the next page, except it isn’t.
Here is the source of the report that shows the backup, maintenance, and outro sections:
Some points to consider:
-
For both backups and maintenance sections, they don’t output the div.page-break until after the plugin is checked to be active, so there shouldn’t be a new page added for the maintenance section since I don’t have that plugin installed.
-
The outro begins with a new page and there isn’t any logic or tests first, since it always outputs and always needs to be on its own page.
-
I have set the margin to 0 for the table element just in case there could be some hidden space after it or something.
-
I don’t remember the reports acting like this until my most recent updating of the template sources. I mainly just changed them so pages would have a background image, and I changed the page margins a bit wider.
-
A surprising number of reports, like 17 out of 20, have the blank page, and not all sites have the same number of backups recorded, so it really seems strange that so many of them just happen to have a number of rows that ends at the bottom of the page. Perhaps pure coincidence?
Is there some way to ensure no new page is created unless it is actually needed for a new row in the table?
No amount of automation and exporting bulk reports helps if I have to open every report one by one to hunt for and remove a blank page. Hopefully there is some way to avoid this.