FriendsOfFlarum Mason, the discussion custom fields builder

moreany

Question for users https://discuss.flarum.org/d/7028-friendsofflarum-mason-the-discussion-custom-fields-builder

Is it possible to make a check somehow, that is: for one tag - one form, for another tag - another form.

Is there any similar software with such functions?

What is used in this forum as autocomplete when creating a discussion?

So...

clarkwinkelmann

Version 1.2.0

Use official Flarum ComposerState fields API to hold answer data. This allows other extensions to interact with Mason in new ways.

The only extension known to take advantage of this feature at this time is Composer Page.

jdoe

Can fields be searchable via the main page search?
So far not really working for me...

clarkwinkelmann

jdoe indeed, I don't think it's implemented in the current version. FoF Masquerade has the answer:<keyword> gambit but FoF Mason has none.

Additionally extension currently cannot extend the regular Flarum plain text search outside of gambits without overriding the whole search component, which would be a nice thing to have here as well.

SZSZ

If I restrict permissions to some tags individually, forms in discussions with those tags cannot be viewed except by the admin group.
For example, if I create a new tag A and set it as only the admin group can start a discussion, then neither members nor guests can view forms in discussions with tag A.
I have already set the permission of See fields on all existing discussions to everyone.

Misticalkai

Im trying to regulate what users post on my forum, basically im tryna make it where people put a title, description and a link to a download link, but when i enable the extension, it works for the users when the make a post but it doesnt show to everyone on the forum.

the view of the user who created the post

the view of guests and other users who did not create the post

i also made sure the permissions where correct and the are.

can some one help??

Litalino

which adds a tag configuration so the user can decide which fields can be associated with the tag.

treyb

clarkwinkelmann Are there any thoughts on this still? Mason works well but would be great to adjust per tag.

Yippy

treyb

Just to let you know that someone has already implement a tag relevant fields, but it only works at top level primary tag. fof-mason-tag by xsoft-ict

I've used this for my project, not sure if it's still being maintained but it worked with the latest flarum.

I don't know if migration would work between the two different forks, I had a fresh flarum instance. If you are have alot of data with Mason you should backup your website just to be safe.

treyb

Yippy thank you!

treyb

I love mason, but did anyone come up with a good css option to fix the size issues? I would love to change the width of the text area to have all three options in a columns but seems like everything i try fails.

dinapolis

anyway, I went ahead and added these styles as Custom CSS on Flarum, at least it solves the issues on mobile.

.Form-group:last-child {
    margin-bottom: 24px !important;
}

@media (max-width: 767.98px) {
    .Composer:not(.minimized) {
        height: auto !important;
        overflow: scroll;
    }
    .TextEditor-editorContainer {
        min-height: 75vh;
    }
    textarea.FormControl.Composer-flexible.TextEditor-editor {
        min-height: 50vh;
    }
}

treyb I'll take a look at the widths of the fields because it's also bothering me but I'm not sure you can have it in a column - I'm planning to at least improve the layout of it above the text area.

dinapolis

treyb this might not solve your problem beautifully but it gives you a good starting point. Add these in your custom CSS and adjust from there:

/* puts fields in a column on the left */
@media (min-width: 768px) {
    .ComposerBody-content {
         display: flex;
        flex-direction: row;
        flex-wrap: wrap;
    }
    .ComposerBody-header {
        width: 35%;
        margin-right: 3%;
    }
.ComposerBody-editor {
     width: 60%;
    }

}

dinapolis

Hey guys, is there also a solution to fix the mobile height issue as well? It seems that at this point it's better to just add some CSS overwriting the whole Composer window and make it static atop the content (instead of a modal).
As it is now it's unusable on mobile.

baicai

FriendsOfFlarum oh no!
“Allowed to skip required fields” not work!

« Previous Page