Version 1.6.2 - August 3, 2022

  • Fixed: all tags including children are now shown in tag selection dropdown.
  • Fixed: rename controls around enable and draft status for non-standalone to clear up confusion.
  • Fixed: make empty submission text translatable on discussion.

GreXXL the entry cannot be deleted within the form's mask

"linked" forms (discussion fields and user profiles) submissions are stored identically to standalone submissions in the database, however they should not be manipulated directly. That's why I have disabled lock/delete actions. I intend to hide the submission page entirely as well, currently it's still visible only because the code is re-used for all form types. Submissions for linked forms should automatically be created and deleted as needed by the extension.

GreXXL If a field is not mandatory and is not used, would it be possible to hide it in the discussion?

I will add an option for this in the next feature release. I think I'll add the option per-field as it will give the most flexibility.

GreXXL there is "Access: CREATE ONLY", - which I don't understand

This was also a side-effect of the same UI being used for both standalone and linked forms. I have published a patch request where I updated the translations to better reflect their purpose. On linked form, it's either in draft or enabled mode. Ability to edit is controlled through the permissions. There isn't really a concept of creation vs edition for linked forms, since its existence it linked to another resource.

GreXXL Could formulaire overwrite the "Start a Discussion" button within a tag

This is not really planned. The intent is to have forms support inside of the discussion composer in a future update.

The "create discussion from standalone form" option was a bit of a hack, it was created as a client request but that's not how I originally intended the extension to be used.

            clarkwinkelmann "linked" forms (discussion fields and user profiles) submissions are stored identically to standalone submissions in the database, however they should not be manipulated directly. That's why I have disabled lock/delete actions. I intend to hide the submission page entirely as well, currently it's still visible only because the code is re-used for all form types. Submissions for linked forms should automatically be created and deleted as needed by the extension.

            Got it, totally makes sense. Will just ignore it for now.

            clarkwinkelmann I will add an option for this in the next feature release. I think I'll add the option per-field as it will give the most flexibility.

            That would be very awesome. Makes the result much cleaner.

            clarkwinkelmann This was also a side-effect of the same UI being used for both standalone and linked forms. I have published a patch request where I updated the translations to better reflect their purpose. On linked form, it's either in draft or enabled mode. Ability to edit is controlled through the permissions. There isn't really a concept of creation vs edition for linked forms, since its existence it linked to another resource.

            Thanks for the clarification!

            clarkwinkelmann This is not really planned. The intent is to have forms support inside of the discussion composer in a future update.

            Sure - that makes more sense of course. Is there any estimate on this? Maybe something that could be (partly) funded/financed to get it in?

                    a month later

                    Version 1.7.0 - September 8, 2022

                    • Added: discussion fields in start discussion composer.
                    • Added: optional horizontal form layout for discussion, profile and standalone.
                    • Added: contextual validation errors in sign up modal
                    • Changed: the REST API validation error pointers for linked models are now prefixed with formulaireForms/<form uid>/ to ensure the messages can be shown under the correct fields in case customized field keys are re-used across forms or conflict with native discussion or user attributes.

                    Discussion fields are now officially out of beta. The feature is best used together with the free Composer Page extension.

                    Premium subscribers of Formulaire also get support for Composer Page. The 2 extensions are designed to be used together. Composer Page was released as open-source since it's also very useful without Formulaire and this will help making it compatible with as many other extensions as possible.

                    The discussion fields and user profile fields are also fully supported for automated REST API interaction. The integration tests for 1.7.0 (not part of the distributed source code) have been expanded to include many required fields and group/tag scopes situations.

                    I have kept the composer layout as simple as possible, but I'm open to add more layout options based on client wishes. The fields could be moved to a modal, to a separate tab, etc. I'll implement those options if there is interest.

                    Without enabling any other setting, the fields will look something like this:

                    The most advanced solution is to use both the Composer Page extension and the "Uniform composer layout" setting to achieve a large uniform form. Visible in the screenshot is also the Flamarkt Taxonomies and FriendsOfFlarum Polls extensions:

                    5 days later

                    Version 1.7.1 - September 13, 2022

                    • Changed: Formulaire fields now have the same layout in SignUp Modal as everywhere else instead of inheriting the larger SignUp fields input style (larger style would only apply to short text inputs and buttons which was inconsistent).
                    • Fixed: missing margins in SignUp modal.
                    • Fixed: discussion fields edit modal layout issue on Flarum 1.5.

                    The extension was confirmed working on Flarum 1.5.

                    🎁 To celebrate the release of Flarum 1.5, all KILOWHAT premium extensions are 15% off until the end of September. Grab the yearly plan for Formulaire at 42,50 USD/year instead of 50 USD/year with the following link:

                    https://extiverse.com/extension/kilowhat/flarum-ext-formulaire?key=stellar-anomaly-astronaut-celestial

                    The yearly plan price is reduced for life until manually cancelled. The monthly plans are not reduced.

                    Great extension,

                    Btw, is it possible to add custom field on comment / reply composer?

                      ikhsan017 only on the discussion composer at this time, but this could potentially be added.

                      Do you have some example use case(s) so I can study how useful it would be for other customers?

                          Are notification currently supported? Is it possible to alert users a survey has been published? For example, if I want to publish a survey that a specific group has permission to - would it be possible for an alert to be generated (web & email) with a link for them to complete it?

                            ctml there's nothing like that at the moment, but I could look into it.

                            The easiest way to achieve that at the moment would be to use the Mailing extension to manually create and send an email to the relevant group.

                            The only email alerts currently implemented are the confirmation for the submitter and the notification to admin for a new submission.

                            Those are only email notifications, there are no web notifications. But I could allow making the existing submission notifications work on the web as well.

                            • ctml replied to this.

                                clarkwinkelmann I am about to build community forum with an auction like feature, where on discussion we can place additional info like opening price, and other members reply with comment and bid

                                At first I found fof/mason and I think it was good start, but then found formulaire to be more complete and almost fit my need

                                  clarkwinkelmann I see, thank you. Maybe consider it as an RFE for down the road. I want to send HTML formatted emails with branding and all with details about the survey that needs to be completed, and the mailing extension is probably not ideal for that. Using pretty mail that other extensions could hook into to provide configurable template for actions supported in the extension would more or less be what I'm after.

                                    a month later

                                    Version 1.8.0 - October 29, 2022

                                    • Added: (manager only) ability to search forms by title.
                                    • Added: (manager only) ability to search forms by title, slug and field names (Scout integration required).
                                    • Added: (manager only) ability to search submissions by field answers (Scout integration required).
                                    • Added: ability to search discussions by field answers (Scout integration required).
                                    • Added: ability to search users by field answers (Scout integration required).
                                    • Added: new PHP events for developers.
                                    • Fixed: updated French translation to consistently use "réponse" as the translation to "submission".

                                    See the documentation for how to configure Scout.

                                    Breaking change for developers: the signature to FormRepository::store() and FormRepository::update() changed to take $data instead of $attributes. I am not aware of any client using the repository classes directly but I'm mentioning this just in case. The 2 existing PHP events have also been deprecated, but I don't plan to remove them anytime soon. See documentation for the new names.

                                    14 days later

                                    Version 1.8.1 - November 12, 2022

                                    • Changed: links in content blocks now open in new tabs and no longer have ugc nofollow rel value.
                                    • Fixed: emails failing to send when the form contains checkbox, radio or select fields.
                                    • Fixed: rich text answers not rendered as HTML in emails.
                                    • Fixed: 500 errors not causing any visible feedback on the form submit and edit pages.
                                    5 months later

                                    Version 1.8.2 - April 6, 2023

                                    • Fixed compatibility with Flarum 1.7+.

                                    This version will only install on Flarum 1.7+. All future updates will require Flarum 1.7+.

                                    iPurpl3x thanks for the heads-up. I had assumed no changes would be required based on the Flarum changelog, and I only run the extension on one of my websites which has not updated to 1.7 yet so had not realized there was a problem. I must have been the only developer to ever use the old javascript frontend extenders that have been refactored in Flarum 1.7. I have updated the code to use the new extenders, and I think that's the only thing that required changes.

                                      3 months later

                                      I have some non-technical questions about Formulaire. We are preparing to deploy Flarum for production use in a private forum. In our test environment on FreeFlarum we have used the FOF/Masquerade extension to create the custom profile the organization requires prior to acceptance of the user into the 'private forum'. In the production installation, I wish to use Formulaire as it offers more flexibility. My first question is with respect to downloading of the user submissions, would this download include all the data the user entered on their profile?

                                      I am also hoping to use Formulaire for the 'create' discussion template within specific tags (at the moment using the Discussion Template available on FreeFlarum). Will Formulaire be able to assist with ensuring consistency in 'topic title'? From reading all of the postings above, I understand I will be able to create templates for the actual content of the initial post in a discussion thread. Is my understanding correct?

                                      Kindest regards,

                                      Deanna

                                        I'm not sure if you have already tried Formulaire or not? I can give you access to the demo forum if you wish to see how some features work before purchasing, or you may subscribe to the extension for 1 month or year on Extiverse and I can refund if it doesn't fit your needs.

                                        DCar with respect to downloading of the user submissions, would this download include all the data the user entered on their profile?

                                        Using the "export" feature that's part of Formulaire, you get the data of all the custom fields, as well as a few attributes that are native to Flarum, like email and username. If you created multiple profile forms to create multiple tabs in the user profile, each of those forms has to be exported separately. But you should be able to merge the data together with external software based on the user ID or email if necessary.

                                        The extension does not offer migration from FoF Masquerade at this time, but it's something I can add if there's demand.

                                        DCar ensuring consistency in 'topic title'?

                                        Unfortunately not, Formulaire only validates the custom fields. The original title and body are still there and left for Flarum or other extensions to customize. I could add an option to completely remove the title and/or body if those don't make sense when used together with custom fields.

                                        I hope that answers your questions! Feel free to reach out via email if you would like access to the demo or want some additional screenshots.

                                            a month later

                                            Version 1.9.0 - August 10, 2023

                                            • Added ability to disable all fields on Byobu discussions so vanilla private discussions can be used alongside global Formulaire fields.

                                            These changes only have an effect if the Byobu extension is installed and the new setting is enabled in the admin panel. If you are only using tag-scoped discussion fields, enabling the new setting makes no difference.

                                            There is currently no way to have fields exclusively for private discussions, but this feature could be implemented if there is interest.

                                            3 months later

                                            Noticed a bug with the extension. There is now a "create user" module in the admin user list. In this dialog Formulaire profile fields are not included (but required - showing the error). So actually you cannot create a user in the admin control when you have required profile fields.

                                              GreXXL good catch, I've actually never used that feature myself so I kind forgot about it. I'm also pretty sure it was introduced after the initial release of Formulaire hence the oversight.

                                              I'm adding this to the list of things to fix for the next update 👍️