Chinmoy Biswas

Hello there,

We hope you are doing well today. Thank you for the detailed RTL report.

We tested the reported behavior in an RTL environment. We were able to reproduce the low-contrast Signature instruction text and found a layout overlap in the Preview & Design screen. However, we could not reproduce the following items from the information currently available:

• Extra spacing between the Signature label and field
• The missing border on Button Style Radio fields
• Required validation messages aligned to the left
• The form-builder scrolling issue after the Advanced Fields section
• The typography popup being partially hidden

The Preview & Design URL is accessible only to logged-in administrators, so we cannot inspect it from your shared link. Please publish the affected form on a regular public page and share that page URL with us.

Please also share screenshots or a short screen recording for the items above, along with your Fluent Forms / Fluent Forms Pro versions, WordPress version, active theme, and browser details. This will help us recreate the exact environment and investigate further.

Let us know if we can assist you further.

Thank you!

Hello there,

Yes, we are aware of this behavior. The Signature is saved as a PNG image of the complete signature-pad canvas rather than an image cropped only to the handwritten ink. Since the canvas is typically wide and short, it can appear like a banner when displayed in the table.

The 240px value in the HTML code is the image’s maximum display width. When it is reduced to 100px, the complete image scales down proportionally; therefore, the handwriting and its pen line also become smaller.

If the Signature field is displayed in a fixed-size desktop container, new signatures will use the same canvas dimensions. However, the visible handwriting can still vary because each user may use a different amount of the available signing area.

For future submissions, you may consider adjusting the Signature field’s Pad Height and increasing the Pen Size to improve readability when the image is displayed at a smaller size. Please note that there is currently no built-in option to automatically crop the blank area around the handwritten signature. Displaying a compact preview while retaining the same apparent ink size would require a custom image-cropping solution.

As an optional display adjustment, you can use the following CSS approaches to the Ninja Table transform value section depending on your preference:

1. Keep the full signature visible within a smaller fixed area (Safer):<img src="{{row.signature}}" alt="Signature" style="width:120px;height:50px;object-fit:contain;">
2. Make the signature look larger (May crop edges):<img src="{{row.signature}}" alt="Signature" style="width:120px;height:50px;object-fit:cover;object-position:center;">

Using object-fit: contain is safer to ensure the complete signature is displayed, whereas object-fit: cover may crop parts of the signature.

Let us know if we can assist you further.

Thank you!

Hello there,

Fluent Forms doesn’t have built in feature to show the entires in front end pages. However, you can display the form submissions on the front end by integrating Fluent Forms with Ninja Tables.

Please create a table in Ninja Tables and use the Fluent Forms integration/data source to select your petition form. You can then choose the submission fields you would like to show, such as the signer’s name, location, or registration date.

After configuring the table, place its Ninja Tables shortcode on the desired page. The table will then be visible on the front end and can be styled or configured with search, sorting, and pagination options as needed.

Please check the details here: Show Fluent Forms Entries in Frontend using Ninja Tables

Thank you!

Hello there,

We apologize for the confusion. By “plain Fluent Forms,” we meant testing the form with only the Fluent Forms plugin active, without WPML or the “Multilingual Forms for Fluent Forms with WPML” add-on.

Based on your test, it appears that the issue occurs when the WPML translation integration is enabled. As your form content has been translated, the “Accepted” response may also be processed through WPML.

Please reset the WPML translation and check again to see which specific language is causing the issue, then review the specific form translations within WPML. You can go to WPML → String Translation, search for the exact strings “Accepted” and “Declined“, and check their translations under the fluentform text domain.

Additionally, please use the lowercase SmartCode {ip} instead of {IP}, as Fluent Forms SmartCodes are case-sensitive.

Thank you!

Hi Craig,

We are really glad to hear it’s held up reliably for you, and we appreciate the kind words after 20 years of experience. We willl keep working on staying ahead of the spammers.

Thank you so much for your kind words.

Best, Chinmoy

Hello There,

Thank you so much for the great review and thoughtful feedback.

We truly appreciate your trust. Feedback like this keeps us highly motivated to make our products even better. Please feel free to reach out to us at any time with anything you would like to share.

Wishing you a wonderful day ahead!

Thank you!

Hello there,

Thank you so much for sharing your feedback and for your kind words! We are absolutely thrilled to hear that you consider Fluent Forms to be one of the best form plugins you have worked with. It is wonderful to know that you are enjoying its excellent features, as well as how easy it is to set up and use.

Your high recommendation means the world to our team, and it motivates us to keep improving our products to deliver the best possible experience for your business.

Thank you!