Services Plugins FAQs

Putting a Page Break Between Multiple Elements in PDFCreator

Hi,

I have a use case where I’d like to use the PDFCreator plugin to create a multiple page PDF with one element per page (in this case, it is a repeating group of concert size tickets) and I believe the best way to ensure the tickets print correctly is to put one on each page. Is there any way to currently do this in the plugin (maybe inserting some html page break element between each ID?) or would it be possible to modify the app so that it is possible?

Sincerely,

Quinn

Hi @quinn
Thanks for reaching out!

Yes, it’s possible.

  1. place the plugin element on the page, and make sure “file uploads” = yes
  2. assign an ID to your repeating group;
  3. assign an ID to the group inside this repeating group (that has the content you want display on separate pages after conversion);
  4. use any element to trigger the “on-click” event
  5. attach the “Generate pdf from HTML server-side ConvertertoPDFv2.0 A” action to the event from the previous step, and:
  • choose the “Convert target” = single element;
  • insert the repeating group’s ID into the “ID” field and the group’s ID into the “Pagebreak ID” field - Screenshot by Lightshot

Hope this helps!

Best regards,
Gulce

Thank you very much, I’ll give it a shot!

1 Like

Hi Gulce,

I got an unexpected result. Works when I print one but the custom scaling doesn’t seem to hold when I print the whole repeating group. Any ideas?


Hi @quinn,

Could you please provide more details, specifically screenshots/video recordings of your whole setup? It will help us to understand what might be the issue and provide a solution as soon as possible.

Thank you!

Sure, so it’s a repeating group of tickets with a button in each one to print single tickets. That might be part of the reason why it’s not printing correctly. The single prints work perfectly (when I click any of the print buttons in the repeating group) because I’m just targeting that one reusable element (ticket) but maybe I need to put the button and PDF converter into the ignored elements list and it will work? There’s “Print All Tickets” button lower down the page and a PDF converter element outside of the repeating group for that function.

Hello @quinn
Thanks for the details. :pray:

Let me please suggest you few options that can help:

  • Please assign an ID to the repeating group. (e.g. RG) and specify in the ID field (in Generate pdf from HTML server-side ConvertortoPDFv2.0 action)
  • Assing an ID to the ticket (reusable element) (e.g cell) and specify in the page break ID field
  • Assign an ID to the “print” button (e.g ignore_button) and specify in the ignored elements ID field

Please do not group “ticket” and “print” elements.

Also, please try to use Custom format and indicate your reusable element width height in the Custom Format field to get the PDF file to match perfectly to your group parameters (w/h) as in the example above.

Best regards,
Gulce

It’s closer but not quite there. I think it’s using the width of the repeating group though I’m not sure where the space at the bottom is coming from. I put the button and PDFConverter in its own group within the repeating group so I can ignore them both.

If I make the repeating group the same width as my reusable “ticket” then I just have to figure out where to put my button. Maybe a focus group?

Hello @quinn,
Apologies for the late reply due to the weekend. :pray:

To speed up the investigation process, would it be possible for you to add our support@zeroqode.com email to the list of your app collaborators? Please let me know the page where you are using the plugin and a step-by-step guide on how to create a PDF to see the result. (here or via DM). We will create a separate test page to perform plugin tests on it and copy the page where you have faced the mentioned issue.

You can ignore the warning about the subscription plan, limiting the app collaborators number. Zeroqode is on an Agency plan and can be added to any Bubble app as a collaborator.

Looking forward to your reply.

Best regards,
Gulce

Hi @quinn,
Thank you for your patience,

We have updated the plugin and fixed the issue. Kindly ask you to upgrade your plugin to the latest version (1.85.0.) and give it a try.

In case I can help you with anything else, please let me know.

Best regards,
Gulce

Hi @Gulce,

Seems to be working perfectly now. Thank you for the update and all the work you and your team put into diagnosing this.

Sincerely,

Quinn

2 Likes