PDF Creator
  • Introduction
    • 👋Welcome
    • Quickstart
    • Key use cases
    • Key features
  • Getting Started
    • Installing the plugin
    • Enabling ID attributes
  • Implementing Key Features
    • Generating PDFs of a single element
    • Generating a PDF of multiple elements
    • Downloading PDFs
    • Saving PDFs to your Bubble database
    • Adding footers
    • Adding headers
    • Customising your PDF
    • Sending PDFs via email
  • Making PDF files private
  • Tips
    • How the plugin scales elements to the PDF page
    • Adding a loading screen
    • Generating PDFs of repeating groups that span multiple pages
  • Troubeshooting
    • 'Can't find element' message when using square brackets
    • Unwanted white spaces when using nested repeating groups
    • Unwanted gap at bottom of table elements
    • Traditional Chinese characters formatting
    • White space at the top of pages
Powered by GitBook
On this page
  • Sorry, we couldn't find this element: "[target-element]"
  • Solution
  • my-repeating-group
  • *my-repeating-group*
  1. Troubeshooting

'Can't find element' message when using square brackets

PreviousGenerating PDFs of repeating groups that span multiple pagesNextUnwanted white spaces when using nested repeating groups

Last updated 10 days ago

If you're adding square brackets [] around your ID attribute to help with spacing, you may encounter this error message when you're running the 'Generate PDF Creator' action:

Sorry, we couldn't find this element: "[target-element]"

This typically occurs if you're also using the . The Classify plugin unfortunately causes an issue with how ID attributes are interpreted by PDF Creator, which means you can’t use the [] around an ID attribute.

Solution

If you add a * before and after the ID attribute of the repeating group you are PDF-ing and you will get the same affect as the 's. For example, if your repeating group has the ID attribute:

my-repeating-group

You can add a * before and after to get:

*my-repeating-group*

There is no conflict with the Classify plugin when you use this command.

Classify plugin