• Extensions

  • FriendsOfFlarum Mason, the discussion custom fields builder

8 days later

Hi everybody, I wrote an update to this powerful extension with a feature a lot of people have asked for –

UntrustableRus specific tag ... > Chenzy Gaming tag...

pyxxl I just wish that this extension had the option to limit fields to specific tags.

– the ability to turn fields on/off for specific Tags. It's still very much beta but it works well on my dev installs. Before I do the final polish, though, if anyone needs this feature right away they can grab a copy of my version at Github.

@clarkwinkelmann I forked and renamed it Mason Plus for dev purposes so I could run both versions, but let me know if you want me to submit it as a PR to the original.

At the very least being able to tweak an existing extension has taught me a lot about how Flarum works inside and out. Also, as someone who's asked a lot of questions around here, it's nice to be able to contribute something back to the community. Here's a quick video explaining the new features:

          10 days later

          bgkurt hmm, you should be able to download it via github and install it in your /packages folder right away without Composer. I have to figure out how to make it an official extension so that you can install more easily with Composer. Give me a day or two to release it that way.

              20 days later

              raafirivero I have to figure out how to make it an official extension so that you can install more easily with Composer. Give me a day or two to release it that way.

              Updates on this?

                13 days later
                14 days later

                The little issues have been fixed and the package has finally been migrated over to FriendsOfFlarum.

                Updating from Flagrow

                This extension replaces Flagrow Mason.

                Please backup your data before attempting the update!

                You can upgrade from any of the older versions of the Flagrow extension.

                Then upgrade from the old extension to the new one:

                composer remove flagrow/mason
composer require fof/mason

                When you enable the new extension, the permissions, settings and the data from Flagrow Mason will be moved to FoF Mason.

                raafirivero yes, PRs welcome! You will probably need to rebase your code on the new FriendsOfFlarum version though.

                All the layout-related PRs and issues are still on hold until proper reviews can be conducted.

                  luceos changed the title to FriendsOfFlarum Mason, the discussion custom fields builder .
                  18 days later

                  is it possible to only allow custom fields on discussions of a certain tag?

                  regds

                    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.