Hi,
we moved from Atlassian Cloud to On premise server with latest Confluence. We have a department with the need to export documents as PDF regularly. They set up PDF Layout and PDF Stylesheets to make it look better.
After migration they complained that Page header messes up layout. I removed our complany logo as it didn't scale correctly anymore. But still there's a difference in page margins and font size that makes documents differ in page numbers (170 vs. 175 pages) this confuses people.
I already checked the layout and stylesheet in both instances. It's identical (I even copied and pasted it - no difference!)
I there another setting for PDF exports we missed to check?
Thanks for any hint.
Hello there!
Peter, some differences can occur when migrating from Cloud to Server. One thing that would help us understand what is happening and possible fixes is the content of your stylesheets for PDF.
Would it be possible for you to share with us a little more information about this? Just be careful not to disclose any sensitive information here. Community is an open space and as such, everyone can look into it!
Also, if possible, share screenshots comparing both Cloud and Server exports so we can have a look on what is happening with the finished files. Again, take care not to disclose sensitive information. You can use dummy content for this.
Looking forward to your reply!
Hi Diego,
so here's a screenshot comparison of the new server version on the left (wrong) and previous cloud version (correct). The Logo in the header of non title pages has already been remove as this messed up pages completely. But still font size and margin differ.
Here are the layouts file contents:
PAGE
<br>
<div class="fsHeader" style="border: 1px solid ;">
<table border="0" width="100%">
<colgroup>
<col width=1%>
<col width=14%>
<col width=70%>
<col width=15%>
</colgroup>
<tr>
<td></td>
<td> <br> <img
src="/download/attachments/399147308/TUI_3CPM_tilewhite.png"
alt="TUI_Logo" height=80% width=80%></td>
<td>
<h3 text-align=center>TUI EM<br>
MAINTENANCE ORGANISATION EXPOSITION</h3>
</td>
<td>
<span style="font-size:8pt">Issue 2019 </span><br>
<span style="font-size:8pt">Revision 00 </span><br>
<br>
</td>
</tr>
<tfoot>
<tr>
<td></td>
<td></td>
<td></td>
<td><span style="font-size:8pt" id="pageNum" /></span></td>
</tr>
</tfoot>
</table>
</div>
CSS
/*Papiergröße, Seitenränder*/
@pagetTeng {
size: 210mm 297mm;
margin-top: 2cm;
margin-bottom: 2cm;
margin-left: 2cm;
margin-right: 2cm;
}
/*Anpassungen für die Titelseite*/
.fsTitlePage {
margin-left: auto;
margin-top: 1, 5cm;
margin-right: auto;
page-break-after: always
}
.fsTitle {
font-size: 16px;
font-weight: bold;
margin: 72px 0 4px 0;
text-align: center;
}
.fsHeader, .fsHeader table, .fsHeader td, .fsHeader tr {
font-size: 8pt;
line-height: 1.1;
color: #000;
font-weight: normal;
}
.wiki-content p {
word-wrap: normal;
}
/*Seitenumbrüche*/
.pagetitle {
page-break-before: always;
}
/*Seitenanzahl*/
#pageNum:before {
content: "Page " counter(page) " of " counter(pages);
}
/*Inhaltsverzeichniss anpassen*/
div.toc {
display: none;
}
div.titlepage, div.toc {
page: title;
}
/*Erzwungener Zeilenumbruch*/
div.pagebreak {
page-break-before: always;
}
/*Anpassung für Column, Section Macro*/
table.sectionMacro>tbody>tr>td {
display: table-cell;
width: 1%;
}
table.sectionMacroWithBorder>tbody>tr>td {
display: table-cell;
width: 1%;
}
/*Tabellen nach Möglichkeit nicht in der Mitte teilen*/
table.confluenceTable tr {
page-break-inside: avoid;
}
TITLE
<br>
<br>
<br>
<br>
<br>
<div class="fsTitlePage">
<img src="/download/attachments/399147308/TUI_3CPM_tilewhite.png" />
<div class="fsTitle">
<br>
<br>
<h1>TUI Engineering & Maintenance</h1>
<br>
<br>
<br>
<h2>Part-145<br>
Maintenance Organisation Exposition (MOE)</h2>
<br>
<h2>2019<br>
19.03.2019<h2>
<br>
<h3>In compliance with recommended structure of AMC 145.A.70(a)</h3>
<br>
</div>
</div>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.