• Extensions

  • FriendsOfFlarum Mason, the discussion custom fields builder

  • [deleted]

  • Post #119
  • Edited

Justman10000 did you see the incompatible tag for this extension ? It looks as though this may be abandoned

    The Incompatible tag does not mean this extension is abandoned. It just hasn't been updated yet for v1.

    Looking at GitHub, it looks like it was updated (FriendsOfFlarum/mason9404279) but is going through some additional fixes/refactors.

    1.0.0

    • Update for Flarum 1.0
    Installation
    composer require fof/mason:"*"
php flarum cache:clear

      IanM I get error after using php flarum cache:clear

      Declaration of Flarum\Filesystem\FilesystemManager::resolve($name): Illuminate\Contracts\Filesystem\Filesystem should be compatible with Illuminate\Filesystem\FilesystemManager::resolve($name, $config = NULL) in /home/user/web/domain.com/public_html/vendor/flarum/core/src/Filesystem/FilesystemManager.php on line 38
      • IanM replied to this.
          5 days later

          1.0.1

          • Fix issue where starting a discussion resulted in a js error if Show tags as field was enabled FriendsOfFlarum/mason29
          Installation
          composer require fof/mason:"*"
php flarum cache:clear

          First thanks for this extension!!!
          Today I installed Flarum the first time... It is exciting!

          But... ;-)
          How is it possible to change the Layout from the Mason-Fields?
          I want to add a field with a optional price-Tag....
          and it doesnt look nice 🙁
          So is it possible to change the styling for one single input?
          And to get it as Tag in the Category-Listing?

            6 days later
            21 days later

            GVG while I do agree that screenshots are very useful, there's also a very good reason we don't have any on most extension: it's a lot of work.

            I think all the FoF extension that have screenshots are completely outdated. It's very difficult to keep them up to date. And sometimes outdated screenshots give the wrong idea since they might show features that were changed or removed.

            The discussion first post is also often the same as the GitHub README file and it's not always practical to include screenshots in README since they need to be either hosted inside of the repository, or externally but then not all README viewers will show them the same way.

            I do hope we can standardize this a bit better between extensions in the future!

              • [deleted]

              • Post #137

              GVG Please don't post in uppercase text to get a point across. You can place emphasis on words by using bold or italics, but uppercase text in forums is seen as shouting and impolite.

              This is a community forum where you'll get much more traction if you ask for something rather than simply complain about it's lack of existence.

                2 months later
                5 months later

                I'm starting to consider uses for this extension, I would like to know before I get into a real use case, if it would be possible to use the field answers set in each field (when we have not activated the custom fields) as dropdown filters in the discussion list. I would like to know if this could be developed without complicating the current implementation.

                3 months later