I’m Using the Zeroqode Bubble page to PDF converter. Why is text is cut-off across pages? See here:
I am using the “Generate pdf from html server side ConvertortoPDFv2.0” workflow action on a page element (not the entire page). All works well except that the text can get cut-off across pages. How can I solve this please? On a side note, the link to this plugin’s documentation directs to a “content not found” page.
thanks
Also, is it possible to repeat the header of the repeating group on every page if the repeating group spans across multiple pages?
Hi @42.decaen,
Thanks for reaching out.
First of all, I would like to point out that the Page Break feature, in the Generate PDF from HTML server" action, is working on the old responsive engine. Therefore, I have to say that this feature is not fully functional since it was in beta. The way it works now is by calculating the page’s parameters and the element’s height/width (the page’s HTML structure). Unfortunately, the calculation process is not stable in different use cases.
It is quite difficult to provide “an accurate page cut” when the page contains a repeating group with dynamic content. Depending on the repeating group’s number of cells, the page’s height is changed accordingly, which affects the place where the content will be cut.
The only workable solution we can suggest at the moment is to change the design of the page/element that way, to fit its content inside one a4 page. Also, I’d like to recommend using Paddings to add free space between the page breaking points.
As for the header of the repeating group, you can use the “header template” field to show the repeating group header on every page. For example:
Hope it helps.
Best,
Gulce
Thank you @Gulce for your quick response, really appreciate it.
Even if i wanted to design the page to avoid the text being cut off across pages, I cannot do it because it’s the user of my app who inputs the text, i.e. I have no control on how much text they will input. If the text was not being cut off across pages, it would be a perfect plugin for my use case.
When do you plan to update the plugin to make it compatible with the new responsive engine ? Will it ensure then that texts are not cut off across pages?
many thanks!
You’re always welcome. @42.decaen
The bubble has confirmed that a new plugin editor engine is under development and has top priority. We will migrate all of our plugins to the New Responsive Engine as soon as we have a chance to have them work properly on it. Here is the announcement from Bubble: Plugin Editor & New Responsive Engine [beta] 6 (the editor is still in beta)
We hope Bubble releases soon a new responsive engine for plugins so we can re-investigate and improve the page breaker functionality. And, we all know how important it is for a plugin to work properly, and do understand your feelings. So please be patient with us.
Hope for your understanding on this matter. 
Also, I’ve missed your message about the documentation, sorry about it. Here is the correct link: https://docs.zeroqode.com/plugins/bubble-page-to-pdf-converter-plugin
Best,
Gulce
Thank you for your quick response. Really appreciate it
Hi,
Looks like you released a new version of the pdf converter plugin (1.640). Is it now compatible with the new responsive engine?
Were you able to improve the page breaker functionality? As a reminder, my issue was that some text was cut off across pages:
Thanks
Hello @42.decaen,
Thank you for your message.
The latest update is not related to the Pagebreak functionality, unfortunately. Adapting the page breaker functionality is quite difficult, but we are trying to do our best to find the most workable and convenient solution for it.
I can take a look at your app and try to provide a few suggestions/make it work if you want. Just add our support@zeroqode.com account to the list of your app’s Collaborators. But there’s no 100% guarantee that it will be working perfectly on your page as we will have no control over how much text your users will input. But still worth trying.
Regards,
Gulce
Hi @Gulce,
Thank you very much for your quick response and offering to take a look at the app. I still want to make a few changes before sharing the app with you so that you can see multiple use cases.
In the meantime, can you share the things that i can potentially do to try and break pages at the right places? I can imagine the following:
A/ Place multiple page breaks (by inputting the ID of the groups that serve as page breakers in the zeroqode PDF converter workflow) before each group where I assume that the user will input a lot of text.
Pros : text will likely not break across pages
Cons: that means a lot of unnecessary blank space at the bottom of each page
B/ Conditionally place the page breaks depending on the height of the previous elements (using the recently released “height” function in bubble), i.e. if the height of group X is more than Y, then assign ID to element (that ID being referenced in the pagebreak IDs field of the zeroqode PDF converter workflow)
Pros : less unnecessary blank space at the bottom of each page
Cons : quite complex to define the conditions
C/ Repeating group where users can input as much text as they want. I can’t figure out a way to place a page break within a repeating group. Potentially the one thing I can do is prompt the user to not input more than X words but this is not a very user friendly experience.
thank you!
Hi @42.decaen, sorry for the late reply.
These options can work, but I need to point out that since page breaker functionality is not stable, we cannot say for sure what the results will be without testing all the options.
However, let me please suggest you few options that can work for your use case.
Please note that you may need to change the design of your page, unfortunately. 
You can display the overall user input within the same popup. This popup will contain a text element or any convenient one to display the user’s text. You can set up 2 events for converting the page to PDF depending on the page height or the number of characters the user has inserted. Why we suggest it: user’s input can be very dynamic and we can’t predict how many characters/how “tall” a text element with the user’s text will be. Since the Pagebreaker is not the best option here - you can try to do a PDF file (use the plugin’s HTML action) with one scale (A4) when the user’s input is about 2000 characters (for example), and use another convert to PDF action when user’s input is more than 2000 characters (A3).
The users can enter the text without any limitations. But, the element that you display the user’s text will show only a few lines of text. So, you will be able to use “paddings” to achieve a clear page cut. In case, it is mandatory to show the entire text in the pdf, you can redirect to different pages for long texts as I mentioned above.
Also you can try truncating the user’s input and display it in separate text elements - to use these text elements as page breaker identification. But the main trouble here might be the difficulty of truncating text characters the way you want (some Bubble magic skills math are needed).
Hope these ideas will be useful for you 
Best,
Gulce
I’m glad it helped. 
Please let me know if there is anything else I can help you with. Have a great day!
