Different outputs from pagedesign with "Print" and "PDF-Export" functions

User Talk Plugins
,
1

I use the page-desgin plugin for printing an extract of my table with adjusted row height. When I export the fine with the “print” function everything works fine (row height is adjusted to the content). When I use the PDF-Export function with the same page design, the row height is set to the fixed height settings from the base.
In my case I have to rely on the PDF-Export function as I use it to create PDFs with a button in my base.
Please help to fix this issue.
(Using SeaTable Enterprise)

2

Could you post screenshots? I cannot reproduce the issue.
Could you also tell me which browser you use?

3

Unbenannt
Unbenannt1767×525 148 KB

Unbenannt2
Unbenannt21773×290 84.3 KB

Here are some screenshots of two different outputs (anonymized).
I am always using Google Chrome as a browser

4

Do you have an update/solution for my problem?
It still doesn’t work.

5

Hallo SeaTable team,
I wanted to use the print funktion today as the PDF-Export funktion still does not work as some weeks before. But now the print funktion also does not work. Please help!

6

Hello Franzi, sorry for the tardy reply.
I still cannot replicate your issue. Please find below a screencapture that shows the behavior on my computer using SeaTable Cloud.
ezgif.com-video-to-webp-converter (2)

Can you please check your browser console for errors?
Also: Could you try to empty your browser cache?

7

If this does not help, could you share your base with us for troubleshooting? Could you send an invite link to support@seatable.io.

8 
ProjektPortfolioPortal%20-%20OpenPointList/?tid=N9kG&vid=aDL4:72 django-pwa: ServiceWorker registration successful with scope:  https://cloud.seatable.io/
timeline/?path=/main.js&t=1718897844000:2 react-intl-universal locales data "null" not exists. More info: https://github.com/alibaba/react-intl-universal/issues/144#issuecomment-1345193138
warningHandler @ timeline/?path=/main.js&t=1718897844000:2
timeline/?path=/main.js&t=1718897844000:2 react-intl-universal locales data "null" not exists. More info: https://github.com/alibaba/react-intl-universal/issues/144#issuecomment-1345193138
warningHandler @ timeline/?path=/main.js&t=1718897844000:2
page-design/?path=/main.js&t=1720058558000:2 react-intl-universal locales data "null" not exists. More info: https://github.com/alibaba/react-intl-universal/issues/144#issuecomment-1345193138
warningHandler @ page-design/?path=/main.js&t=1720058558000:2
Fetch event handler is recognized as no-op. No-op fetch handler may bring overhead during navigation. Consider removing the handler if possible.

This is what I get in the console.