• Extensions

  • FriendsOfFlarum Mason, the discussion custom fields builder

CSDA1 that feature does not exist at this time. You can read above in the thread to learn about the many challenges and questions about that. That's however a feature I've been working on for my premium forms extension.

    18 days later

    Aleram and @Mark73 Hey sorry, I've had a pretty dramatic change in my work situation since June and basically haven't been able to work on my Flarum project at all since then. You're welcome to fork it on GitHub and run it on your own install (it was working great on mine before I had to leave). Trying to find time to get back to working on it but it won't be until November at the earliest.

        raafirivero if/when able, please create a new Extension discussion (or maybe under Dev if it's still under development) for your own extension so that users have a place to comment about the fork.

        This discussion is about the official FoF Mason extension and I'd like to avoid as much confusion as possible. Maybe we should have a GitHub issue somewhere if we want to discuss merging your features back to the main extension. Feel free to create an issue on our GitHub repo 😉

          a month later

          Here's an example of a fairly tasteful way to use this extension as it currently is. Due to space in the post box, I opted to just have 1 custom field. A mood field so members can let everyone know how they're feeling. I styled it minimally and made it so that it takes up the least amount of space as possible.

          CSS:

          /* Mason fields */

.Mason-Fields {
    border: 0px !important;
    border-radius: 0px !important;
    padding: 0 0 0 0px !important;
    zoom: 85%;
}

.Form-group>label {
    font-size: 14px;
    font-weight: bold;
    margin-bottom: 10px;
    color: #111;
    display: inline;
    margin-right: 10px;
}

.FormControl {
    padding-left: 5px;
    font-size: 0.8rem;
    line-height: 1.3;
    color: #669996;
    background-color: transparent;
    border: 2px solid transparent;
    border-radius: 4px;
    -webkit-transition: border-color .15s, background .15s;
    -o-transition: border-color .15s, background .15s;
    transition: border-color .15s, background .15s;
    -webkit-appearance: none;
}
          15 days later
          19 days later

          Release 0.4.2

          I just released version 0.4.2 with beta 14 support.

          This new version will automatically be installed when you updated Flarum to beta 14.

          Add custom settings to the tags?
          Additional;
          Option to not have custom fields in set tags. I just wish I could set up custom fields to appear and be selected in my support discussions.

            DursunCan as said many times before, this requires too much work to add. Unless someone is interested in sponsoring the full development of this feature, this won't happen.

            However I'm working on this feature for my premium Formulaire extension. It's already partially implemented, it's just not yet available from the new discussion composer.

              a month later

              raafirivero

              I really like what you've done there, I think those features really help to enhance the already powerful extension. I am afraid it would not be useable unless it could be configured per tag, with a smaller display on screen like you've added. I would love to see a PR to bring these features into the official extension. 😀

                2 months later

                Release 0.5.0

                • Flarum beta 15 compatibility
                • Fix visual glitch where a refresh was required to see edited field
                • Fix visual glitch where selecting a value in dropdown would still show old value

                This version should automatically get installed when you update Flarum. If it blocks, try setting the required version to * in composer.json

                Release 0.5.1

                • Fix error when viewing posts with number 1 from a user profile
                a month later
                3 months later
                5 days later

                serdo because this is not compatible with beta 15. Your flarum's version is beta 15

                    serdo you are requiring a specific version of this plugin. You need to change it from a specific version to "*" in your composer.json.