Proform does not create posts with custom fields

Bug Reports
1

Hello everybody.
I did several tests with proform and when creating a post only the title and thumbnail are sent, but the options sent with (Update post meta) are blank when created, no text or images (file) are being sent, but when updating the custom post the data is sent and changed normally.
I use Jetengine and as it didn’t work I installed ACF and the same problem happened, I’m using bricks 2.0.2 and 2.1-beta, bricksforge I updated today to version 3.1.5, but I already had this problem.
So what I realized is that the problem is in sending the post creation and in the (Update post meta) part, I also activated (Show Legacy Custom Fields) and add custom field for testing and it didn’t work either.

2

Hi! I’m having exactly the same issue.

I also tested it with JetEngine, enabled “Show Legacy Custom Fields,” and tried adding custom fields manually, but nothing changes. Same behavior.

Did you manage to find any solution or workaround for this?

3

Update/Resolution: Renaming the field’s custom ID fixed the issue. Entries are now saving correctly. If you run into the same problem, check for duplicate or conflicting field IDs.

4

It didn’t solve the problem for me. I changed the ID, redid everything with another form, and it’s still the same. I don’t know what the problem could be, but I know it’s not working.

5

Hey Thiago,

This usually happens when something in the Pro Forms setup blocks the meta fields from being saved only during post creation (but works fine when updating an existing post).

To understand what’s going on in your case, it would help a lot if you could share:

  • screenshots of your Pro Forms field settings
    (General, Actions, Create New Ppst and Update Post)
  • the exact versions of Bricks, Bricksforge
  • whether you’re using any custom JS or CSS on this form
    (added on the page, template, or globally)
  • and if possible, any Console or Network errors that appear when you submit the form while creating a new post

With this information, it’ll be much easier to pinpoint whether the issue is in Pro Forms, the create-post hook, or a conflict with JetEngine/ACF.