New blog: FormBuilder v57 released (5 September 2025)

[ryan]

This week in the blog, we’ve got a new version of FormBuilder released, version 57. This new version of FormBuilder adds a lot, including…

https://processwire.com/blog/posts/formbuilder-v57/

[FireWire]

@ryan Fantastic work. I was just doing some heavy development around FormBuilder earlier this year and this is all awesome stuff. Thanks!

[Kiwi Chris]

Really pleased the documentation is included with the main documentation. 

It would be great to have the documentation for all the pro modules that allow API access included in the same way. ListerPro sort of is, as it extends lister.

Although all Pro modules are mentioned on the site, they're not necessarily in the API reference even if they can be accessed via the API.

Also there's not a single page that lists all built in fieldtypes and pro fields that can offer additional functionality. 

I'd really like there to be a page like this: https://docs.umbraco.com/umbraco-cms/fundamentals/data/data-types/default-data-types (In addition to PHP, I also work with .Net and Umbraco is the closest thing to ProcessWire I've found in that space.)

Thinking as a developer, one of the first things I want to know when I'm evaluating a platform is 'What can it do out of the box?'. If I've got to jump around amongst multiple webpages to find out then I immediately start losing interest.

I'm happy to contribute to ProcessWire by helping with documentation if that would be useful.

 

[bernhard]

@ryan still none of my paid modules show up in the modules directory.

Also do you have some feedback on my questions/suggestions from 4 weeks ago here and here? I'd like to know if you plan to add the suggested improvements or if I have to update all my modules manually.

When I look at the RockPageBuilder module it (still) looks like this:

Is that warning really necessary? Why is that warning shown to regular (non-logged-in) users? IMHO it doesn't add any helpful information for them. How would a guest user add or update the readme of my module?

I understand that my module does not have a readme, but it has extensive docs here: https://www.baumrock.com/en/processwire/modules/rockpagebuilder/docs/

I put a lot of effort into these docs so it is frustrating that all that is visible in the modules directory is an ugly red warning. Even worse I think this warning can make the impression that the module is dead or not actively maintained, which is not the case and which would be harmful to my business.

The "Project" button does nothing when I click on it. What is it intended to do? And why does it appear on my modules page?

And all that said, why does that lead to my modules not being shown in the list of paid modules? Or is there another reason for that?

Next, a minor thing: Why does it show "Since 2025/01/10" and does it have to be like this? On my releases page the oldest release is v3.6.0 from January 2023 and it would be nice to make it obvious that this module has a long history and has always been actively maintained, updated and improved. I understand that this is likely the date when I added the module to the directory, but it's imho nothing that adds value to my module's entry. Could that be made configurable so that I can show the real release date or instead only (not additionally) show the last updated date there, which would be more helpful information for anybody I guess?

Thx

[ryan]

@bernhard I'm always interested in making updates to the modules directory, but over time as bandwidth is available to do so. So currently the modules directory does require a populated README.md in your GitHub repo. I'm definitely open to supporting more options, but short term you'd want to make use of what the modules directory currently supports. Any module missing a populated readme shows that message. For paid modules, that's a category called "premium modules", so if you add your module to that category it should show up as a paid module. The "since" date is the date it was added to the direcgtory. 

[bernhard]

16 hours ago, ryan said:

I'm always interested in making updates to the modules directory, but over time as bandwidth is available to do so.

Thx for the heads up. That's perfectly fine, but it would help if you let us know if something is considered to be implemented in a day, a week or a year or not at all. It would be very frustrating if I went through all my modules and then on the next weekly post get informed that the the requested update is ready and all efforts were useless.

16 hours ago, ryan said:

So currently the modules directory does require a populated README.md in your GitHub repo.

I'm confused. My modules are in private git repos. How would I do that? I also tried to add content to the README.md textarea input in the modules directory but it didn't work because I didn't provide a Github url. But providing a Github url to a private repo makes no sense to me.

16 hours ago, ryan said:

Any module missing a populated readme shows that message.

I understand it is like this, we can see that. My question was does it have to be like this. I don't think it adds value to anybody, especially not to guest users, as I tried to point out.

16 hours ago, ryan said:

For paid modules, that's a category called "premium modules", so if you add your module to that category it should show up as a paid module.

RockCalendar has had this category selected but still doesn't show up. At first I thought the issue might be that I used "premium modules" as second category, but still it does not show up even though I flipped both selected categories. I guess it's because I don't fill the Github url field.