AKASA not planned. This could be added through paid work if needed 
It's probably not a "quick" addition though, as it needs it whole allowed files, max size, disk adapter, and access restrictions.
Masquerade by FriendsOfFlarum, the user profile builder
8 days later
I'm not sure i understand how Laravel validation works. For an age field, i'm trying to do the following: digits_between|min:1|max:3; however, when I try to input my age, I get "an error has occured". Can someone help me out?
- Edited
taciturasa each | separates a rule. So digits_between|min:1|max:3 is 3 rules, the first being incorrectly formatted.
The docs say digits_between is formatted like digits_between:min,max. The min and max parts must be replaced with a number.
So I think what you were trying to do was digits_between:1,3.
digits_between:1,3|min:1|max:3 would mean "a number with 1 to 3 digits AND from 1 to 3", which basically renders the digits_between part useless (possible values would be 1, 2 and 3 only).
If you're trying to allow ages from 1 to 100 year (for example), the easiest would be to just use min:1|max:100.
Ahh, gotcha. Thanks!
3 months later
3 months later
- Edited
I encountered quite a funny problem. I was trying to debug a problem so I suspected it was being caused by masquerade (which wasn't). I disabled the extension to check and I got an error on any page of the forum. I reenabled and it's gone...
I can't disable the extension otherwise the entire flarum breaks down 
. Not that I want to disable it but I think it is worth a look to see what is going on.
Error screen: 
bertaveira That just means the page /masquerade/configure isn't found (because you disabled the extension). If you only tried retrying, go to your forum's home page.
datitisev Nice did that and a cache clear and it worked. Thanks
20 days later
Hi, are there any plans for a beta 13 update? (as this extension uses the removed ConfigureMiddleware event...)
@clarkwinkelmann ?
iPurpl3x it's on low priority right now... But it should eventually get done.
clarkwinkelmann OK thanks for the info. I'll check with my manager, maybe I can make the update.
14 days later
- Edited
clarkwinkelmann Hi!
I've installed "fof/masquerade": "^0.3.3", with enabled options "Force profile completion" and "Disable user bio field".
Proper rights are set to view and edit (both for the registered users) but no redirect happens when the new user is creating its account or confirming its email.
Can you please suggest how to debug and fix this issue?
Thanks!
I have made an issue about it so we don't forget and someone who didn't read this thread might be able to pick it up FriendsOfFlarum/masquerade50
xHasKx if you just upgraded and noticed this extension is incompatible, you should restore from backup. Otherwise I wouldn't recommend to downgrade. Disable Masquerade until the fix is released.
By the way the "disable bio field" option no longer does anything since bio was removed from Flarum core. We need to remove this checkbox. Just don't install the FoF bio extension if you don't want a bio field.
- Edited
clarkwinkelmann
Thanks!
I've just installed the new version from scratch and noticed this issue, so there is no backup to restore 
10 days later
Version 0.3.4 has been released
- Flarum beta 13 compatibility #50
- Fix ability to sort fields #52
- Fix users without profile being redirected when "force completion" is enabled #2
3 months later
Hello ! This is my first post on Flarum's forum, so first, thanks all for your great work !
Just wanted to report a bug I have with Masquerade extension : when I open a user's profile, there's no problem, the fields of Masquerade are well added; but when I try to preview the profile directly in a discussion hovering a user with the mouse, Masquerade fields are shown only for my own profile, and sometimes for users when I have opened them in the full profile page just before. Most of the time it's not shown. Of course, I already tried to reinstall Masquerade. I also tried to disable other profile related extensions like user bio, share social and likes.
Am I alone with this behaviour or is it a bug ?
Thank you !
sylv38 thanks for the report! There might indeed be an inconsistency here.
I think the idea was to not show the fields in the hover card, but if those were already loaded for some users, like is the case for the currently logged in user, then the already loaded fields would be shown. We might want to hide them completely from the hover card, or adjust the data loading to show them all the time.