How to Require Users to Pay Per Blog Post With a Fluentforms Plugin or Fluentcart?

Hi. Can we do this with Fluentforms?

Do you want to accept sponsored posts on your site and let people pay per post with a WordPress plugin? With WPForms, monetizing your website with sponsored posts is easy. All you need to do is to create a blog post submission form and require users to pay to submit.

Allow writers, freelancers, and guest bloggers to submit content to your site through a simple WordPress form. Receive, review, and release with a few clicks..

WPForms makes it super easy to accept sponsored posts on your site. You don’t even have to offer login credentials to your WordPress site. Still, you can let users submit articles for review on your WordPress dashboard using our Post Submissions addon.

You can also take payments right from your WordPress form. This makes accepting, reviewing, and publishing sponsored post submissions quick and easy.

source: https://wpforms.com/how-to-require-users-to-pay-to-submit-a-post-in-wordpress/

My client wanted to know why she had to integrate separately with Stripe for Fluent Forms, Fluent Booking, Fluent Cart. I said "why indeed?" It's an excellent question.

I realize they are separate plugins, but maybe Fluent wants to create a shared set of truths for Address, payment integrations, and other common data items they all need?

Hi,

Since doing an update to 6.2.13 for Fluen Forms, the advanced date configuration settings I've had working and enabled for months using flatpickr no longer works.  I use flatpickr to enable specific dates on a calendar and disable all others, and this is not functioning any more.

I can't imagine anything in flatpickr code changed, but my current advanced config is this, where all wednesday's are enabled plus specific Thursdays.  The calendar instead is just enabling every single day and ignoring this config completely and I can't for the life of me figure out why.

Any help would be greatly appreciated

{
enable: [
// Specific extra dates
"08/27/2026", // Special Thursday

// Wednesdays except specific date
function(date) {
const isWednesday = date.getDay() === 3;

const isBlocked =
date.getFullYear() === 2026 &&
date.getMonth() === 4 && // May is 4, because months are 0-based
date.getDate() === 6;

return isWednesday && !isBlocked;
}
],

dateFormat: "m/d/Y",
showMonths: 1,
minDate: "today",
maxDate: new Date().fp_incr(60)
}

Hi everyone,

I’m currently working with the Fluent Forms Image Upload crop feature and would be interested to know how other users have solved the following issues:

1. Re-cropping an existing image

In a Post Update/Edit Form, an already uploaded image cannot be opened in the crop editor again. The user has to select/upload the image again before it can be cropped.

Has anyone found a practical way to allow users to re-crop an existing image without having to select it again?

1. Custom aspect ratio

Ratio mode currently only offers the predefined ratios. I need my own fixed aspect ratio that matches the image container on my website, while still allowing the user to freely position/zoom the image within that ratio.

Has anyone implemented a custom crop ratio with custom code or another workaround?

1. Width & Height mode

I also tried using fixed dimensions, for example 990 × 1400 px. However, if the crop selection becomes smaller than the required dimensions, Fluent Forms rejects it instead of scaling the crop to the required output size.

Has anyone found a solution that combines fixed output proportions/dimensions with flexible positioning and zooming?

I would be very interested to hear how other Fluent Forms users are handling this, especially in frontend Post Update/Edit Forms.

Thanks!

ALex.

FluentForms is an excellent form builder however, currently during or after building a form there's no efficient means of knowing what field will be accessed while a user is filling in a form. I've had the less than fun experience of having to rename and move more than half of my form Fields and Elements around on a 5 page form. I really think this would be a valuable feature that all current and future FluentForm builders and user will benefit from and appreciate.

Fluent Forms 6.2.12 adds an optional MCP server so AI assistants can read and act on your forms, entries, and reports. Off by default. Setup in 5 minutes.

Learn how to set it up.

Fluent Forms 6.2.12 is live, and the headline is an MCP server built into the free plugin. Connect Claude, Claude Code, Cursor, Codex or any MCP client to your own forms, entries, and reports.

20 tools in Free, 23 with Pro (the extra three are advanced reporting: revenue analysis, completion rate, subscription report). Some prompts that work on day one:

• "Which form got the most submissions last month, and what is the peak hour?"
• "Show me the last 10 entries on the Contact Form and summarise the common themes."
• "Add a note to entry 4021 saying the refund was approved."
• "Build me a three-step event registration form: details, session choice, notes."

The MCP server is off by default. You can easily enable in 1-2 minutes.

1. Install FluentHub or WordPress MCP Adapter first.
2. Fluent Forms > Global Settings > MCP for AI Agents, enable the server
3. Create an application password from the link in the card and copy it right away
4. Paste the ready-made snippet for your client, then test with "List my forms."

Also in this release:

1. Security hardening (Free + Pro): we completed a detailed review with an external security expert alongside our in-house team. This ships the resulting fixes across entries, reports, integrations, payments and file uploads, plus safer cookie smartcodes and keyword restriction that now catches non-Latin alphabets. Thanks to Patchstack and Wordfence for reporting for the cookie smartcode issue.

• Clickable step navigation (Free + Pro): the Steps indicator now works like Tabs. Click any completed step to jump back. Unreached steps stay locked, nothing to configure.
• Spam filter on entries (Free): Spam now sits alongside Unread, Read, Favorites and Trashed, so you can review flagged submissions and rescue false positives.
• Captcha key warning (Free): a clear notice when global captcha is on but the keys are missing.
• Fixes: Stripe checkout metadata, coupons behind Cloudflare and similar proxies, stacked coupon usage limits, payment confirmation matching, and the Reports country map on translated sites.

Full release post with screenshots and changelog: https://fluentforms.com/fluent-forms-6-2-12/

We are going to keep adding MCP actions. If there is a Fluent Forms task you wish you could just ask an assistant to do, drop it in the comments. That list shapes what comes next.

Happy form building 💙

I'd like to request the integration of FriendlyCaptcha (https://friendlycaptcha.com/) as an additional captcha option.

It's a privacy-friendly, GDPR-compliant European alternative to reCAPTCHA – particularly popular in the DACH region.

I would be thankful if you could evaluate adding FriendlyCaptcha alongside the existing captcha providers.

Thanks!

Hi Ninjas,

I'd like to request some accessibility improvements to make Fluent Forms more WCAG-compliant. Here are concrete issues I've identified:

1. Missing autocomplete attribute support Form fields currently don't allow setting an autocomplete attribute value. This is required by WCAG 1.3.5 (Identify Input Purpose) and helps users – especially those using assistive technologies or autofill tools – to correctly identify input fields like name, email, address, etc.

Request: Add an option in the field settings to define the autocomplete value (e.g. name, email, street-address, etc.).

2. Non-semantic "button" elements (e.g. File Upload trigger) The file upload trigger button is rendered as a <span> instead of a <button>. This breaks semantic HTML and accessibility – screen readers won't identify it as interactive, and it won't be reachable or activatable via keyboard by default.

Request: Either use a native <button> element or at minimum add role="button", tabindex="0", and the appropriate keyboard event handlers (Enter/Space).

3. File upload "remove" (×) not keyboard-accessible The delete/remove icon in the file upload list is not reachable via the Tab key, because it's not a focusable element (no <button>, no tabindex). Keyboard-only users cannot remove uploaded files.

Request: Wrap the remove control in a <button> element (or add role="button" + tabindex="0") with an accessible label, e.g. aria-label="Remove [filename]".

4. Hidden file <input> is reachable via Tab The visually hidden <input type="file"> is still part of the Tab order, even though it's not visible to the user. This creates a confusing experience for keyboard and screen reader users.

Request: Add tabindex="-1" to the hidden input so it's excluded from the Tab order.

These are relatively focused, low-effort changes that would significantly improve usability for people relying on keyboards or assistive technologies. Happy to provide more details or test cases if helpful.

Thanks for considering this!

(Problems identified by myself, only translated via AI)

Fluent Forms already collects signatures, but there appears to be an opportunity for a complete self-hosted document execution system within the Fluent ecosystem: reusable agreement templates populated from Fluent Forms, multiple signers, sequential signing, signer authentication, immutable audit trails, tamper-evident completed PDFs, certificates of completion, automatic FluentCRM tagging/automation, reminders, expiry, and secure document storage. Existing WordPress solutions such as ApproveMe are relatively expensive and don't integrate naturally with Fluent Forms, while newer competitors are now specifically targeting Fluent integrations. A native Fluent solution could keep the entire agreement workflow inside the WPManageNinja ecosystem. 💡 Shahjahan Jewel