FriendsOfFlarum Mason, the discussion custom fields builder

katos

Can this be restricted by tag? I'd like to only show it in certain tags for example ?
clarkwinkelmann

clarkwinkelmann

katos no this feature isn't implemented yet.

I know it's a highly requested feature, it might be available in a premium version of the extension in the future, or you could get a developer (me or someone else) to add the feature to the free/open-source version as paid work ?

katos

clarkwinkelmann How much would we be talking? ?

clarkwinkelmann

katos each premium extensions will be a monthly subscription, it could be part of a $5/month package.

If you're asking about my rates, please contact me here https://clarkwinkelmann.com/flarum Please note I'm not available immediately.

The amount of work will depend on a few options we have. We can for example limit the feature to a single tag and no other, or make it possible to configure which fields need to be filled under each tag.

Pirat

If you use this plugin, you will not be able to scroll to the bottom of the page on a mobile device.
As I understand it, the plugin clogs the entire part of write a post ..

clarkwinkelmann

Pirat yes depending on the number of fields it's know that there are some issues on mobile.

We have an existing issue here https://github.com/flagrow/mason/issues/7 and there's already a PR that partially fixes it by using a modal instead but I still need to merge it.

The instructions to install this fix are above in clarkwinkelmann and please report any positive or negative finding in the PR here https://github.com/flagrow/mason/pull/4 so it helps me confirm if there are still issues with it and whether I can merge it 😉

Pirat

clarkwinkelmann Not convenient, you need to do extra action, it is better to just scroll down to fix 🙂
On the other hand, this is an interesting idea.

Pirat

clarkwinkelmann When you try to change the data again, everything falls and gives an error

clarkwinkelmann

Pirat please report any issue at https://github.com/flagrow/mason/issues with the error message and steps to reproduce if possible. We'll take a look 😉

Pirat it is better to just scroll down to fix

There are some really strange issues with page height and overflow whenever the keyboard is opened or closed on mobile. This affects Flarum core to a lesser extend and it's very hard to fix with CSS. It's complicated because the issues aren't exactly the same between browsers.

That's why the modal seems the most reliable alternative. But I know there are still some strange things happening with the keyboards, that's why it requires testing.

Pirat

clarkwinkelmann Problem with Use a modal in the Composer if the fields can't fit
Pressing it several times causes a kernel error.
To play create 6 sections
Then change them and click again on the editor.

To prevent the error, I propose to make just scroll 🙂

I myself tried to fix the scrolling, but it looks like the core itself determines the height

clarkwinkelmann

Pirat sorry but I don't understand 😬

What's a kernel error ? Can you copy the error message ?

What do you mean by change them ? Edit the value in the composer modal, or create the discussion and edit fields afterwards ?

I don't understand where is the link between an error and scrolling ability.

Please share any relevant screenshots.

We can continue the discussion here but opening an issue on GitHub would probably reduce the noise for other followers of this discussion 😉

Pirat

clarkwinkelmann These are the errors when you click

Uncaught TypeError: answer.field(...).id is not a function
at forum-e00e0f9b.js:36937
at Array.filter (<anonymous>)
at FieldEditText.init (forum-e00e0f9b.js:36931)
at FieldEditText.Component (forum-e00e0f9b.js:19467)
at new FieldEditText (forum-e00e0f9b.js:36917)
at getController (forum-e00e0f9b.js:1490)
at checkView (forum-e00e0f9b.js:1521)
at markViews (forum-e00e0f9b.js:1549)
at buildObject (forum-e00e0f9b.js:1574)
at build (forum-e00e0f9b.js:1720)
at buildArray (forum-e00e0f9b.js:1350)
at build (forum-e00e0f9b.js:1709)
at constructChildren (forum-e00e0f9b.js:1429)
at buildObject (forum-e00e0f9b.js:1606)
at build (forum-e00e0f9b.js:1720)
at buildArray (forum-e00e0f9b.js:1350)

I think it arises from the repetition of data.
I also noticed that the data is not always added and writes an error at the time of publication.

liferent

Hi there! Ask for help. For my project, it is necessary that additional fields participate in the search for the site, can be found through the search for the data specified in the additional field.

clarkwinkelmann

liferent For my project, it is necessary that additional fields participate in the search for the site, can be found through the search for the data specified in the additional field.

liferent how to display additional fields under the name of the discussion in the main list?

Both of these features aren't implemented at this time. If you need them in the near future I suggest you contact an extension developer (including me if you can wait a few weeks) to work on these features for you as paid work 😉

liferent

Still show how to display additional fields under the name of the discussion in the main list? Thank you! I apologize for the translation, I use a translator of the text. Thank you!

kwangure

Are there present plans to support Flarum 0.1.0-beta.8?

luceos

kwangure yes. Soon 🔜

clarkwinkelmann

Better late than never, the extension is now compatible with beta 8!

Please report any issue you might encounter here or on GitHub

Use composer require flagrow/mason to pull version 0.3.0.

Artuu

Yol, clarkwinkelmann!
I don't fully understand what the "Show tags selector as a field" function is all about. Could you send some screenshots?

« Previous Page Next Page »