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 👍

        18 days later

        clarkwinkelmann found another issue. If you have a profile field set up, it will show in the person's profile sidebar as a menu item. When visiting a profile, this does not work for me. When reloading the page, the menu item appears.

        5 months later

        @clarkwinkelmann Is there a way to add a link to view the uploaded image? Right now I only have a delete option, and I would love my mods to be able to view the image without giving them local file access to the server, this could create a major security issue.

          treyb on the "view" version of the submission (not "edit"), the bullet list should be clickable links that open the files. But while you edit the submission and upload files there's no way to see them. This was mostly intentional, because having clickable links in there creates risk of leaving the form before submitting.

          Currently this is the only layout available for files. I plan to add more options for previews in the future. I could make a quick solution just for images as browsers can render them, but there's a risk of things breaking or getting slow if large images are uploaded. Because of that I wanted to wait and make a proper preview implementation with thumbnails and also support at the very least PDF previews.

          If you want to customize the look for your forum only, the Mithril template for the component is extendable. I can give you sample javascript code via email if you'd like an example of how to implement a custom preview for your site. I've done this for a site where you can upload a logo and a preview shows how it's going to look in context.

            clarkwinkelmann Hi Clark - I may be doing something incorrectly, because when I go to submissions > Show. I only get the delete option. Please see recording below. Ignore the first bit, I hit show on the wrong page first.

            https://crefiles.com/drive/s/8E2BO6wtghfg2OhgyylpY26liFGznA

            I would be interested in the code example as well. Im still very much learning the flarum ropes but would love to give it a try.

              treyb sorry, it's my mistake. I had to verify how things worked because it's been a little while since I used file uploads.

              There are no separate view and edit layouts on the web, I was misremembering. The view-only layout is something only used by the email or for users without edit permission.

              The file links should always be clickable, even in edit mode.

              What you are experiencing is a bug that was already on my private bug tracker. When accessing a submission from the submission list, the information about the files is not properly loaded and you see the file UUID instead of the filename, size and link.

              If you refresh the page after opening the submission, the file information should become visible. If you open a submission from the link in the notification email, you'll land directly on the page without any bug.

              I intended to fix this bug as soon as I worked on other updates, but unfortunately those got a bit delayed and the bugfix as well.

                clarkwinkelmann Refresh worked perfectly! Thank you for the help, this will get me by with no problem for now. Thank you sir!

                21 days later

                @clarkwinkelmann it looks like using this script and another make it where I cannot upgrade other extensions.

                `[2024-05-20 20:13:35] composer.ERROR: update --prefer-dist --no-dev -a --with-all-dependencies
                Loading composer repositories with package information
                Updating dependencies
                Your requirements could not be resolved to an installable set of packages.

                Problem 1
                - Root composer.json requires kilowhat/flarum-ext-custom-paths 1.9, found kilowhat/flarum-ext-custom-paths[1.9.0] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.
                Problem 2
                - Root composer.json requires kilowhat/flarum-ext-formulaire 1.9, found kilowhat/flarum-ext-formulaire[1.9.0] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

                <warning>Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.</warning>`

                  treyb do you still have the Extiverse repository configured and properly authenticated ? Try following the steps at Extiverse to create a new token if you can't get things working.

                  I doubt anything from my side could cause this. I have never deleted any release of my premium extensions.

                    treyb unfortunately I'm not sure. I have yet to try the extension manager for myself. I'm not sure how it works together with Extiverse. But I believed it used the same configuration file and should work fine if it already works from the command line.