Masquerade by FriendsOfFlarum, the user profile builder

Ralkage

You know, importing and exporting "settings" doesn't sound too bad especially in 0E800's situation.

But then it comes down to format, XML or JSON? Or both?

Felli

Sanguine I myself liked the suggestion that both @0E800 & @Ralkage had.

0E800 Thought it would be nifty if there was a way to export/import the settings to a json file that could be done directly from Web browser.

Ralkage But then it comes down to format, XML or JSON? Or both?

Although I think XML would be slightly easier on the database import?

clarkwinkelmann

I actually think it's not a bad idea. Mason could also benefit from this.

A JSON representation of the existing fields (following json:api syntax ?) sounds the most logical export format for me.

Of course if you have access to the database it's currently not very hard to copy existing fields to another install... I think a real benefit could be the ease to share common configurations between users. Some of these presets could even be proposed by Masquerade/Mason themselves with some kind of one-click install.

0E800

clarkwinkelmann
You have an uncanny ability to translate my thoughts so eloquently .

Maybe a separate extension that shows a list of available backup/export options for the various plugins / settings. User can chose what to export to and a json xml whatever is generated.

Have a easy to follow workflow for allowing extensions to be compatible with the backup/import extension.

feyisayo

Thanks a lot for this extension.

I need help with using the validation rules: I have a field called "State of residence" which the user has to enter one of the 37 states in Nigeria. So I have listed out all the states in a validation rule like so (without the quotes): "in:Abia,Adamawa,Akwa Ibom,Anambra,Bauchi,Bayelsa,Benue,Borno,Cross River,Delta,Ebonyi,Edo,Ekiti,Enugu,Gombe,Imo,Jigawa,Kaduna,Kano,Katsina,Kebbi,Kogi,Kwara,Lagos,Nasarawa,Niger,Ogun,Ondo,Osun,Oyo,Plateau,Rivers,Sokoto,Taraba,Yobe,Zamfara,FCT" as described in https://laravel.com/docs/5.2/validation#rule-in

However, I get an HTTP 500 error. Here are the first few lines of the stack trace:
BadMethodCallException: Method [validateAdamawa] does not exist. in /var/www/html/vendor/illuminate/validation/Validator.php:2694
Stack trace:
#0 /var/www/html/vendor/illuminate/validation/Validator.php(363): Illuminate\Validation\Validator->__call('validateAdamawa', Array)
#1 /var/www/html/vendor/illuminate/validation/Validator.php(315): Illuminate\Validation\Validator->validate('State of Reside...', 'Adamawa')
#2 /var/www/html/vendor/illuminate/validation/Validator.php(336): Illuminate\Validation\Validator->passes()
#3 /var/www/html/vendor/flarum/core/src/Core/Validator/AbstractValidator.php(63): Illuminate\Validation\Validator->fails()

So it appears that I am not entering the validation rule properly. Can you help me out?

clarkwinkelmann

feyisayo it's actually a limitation of how it was implemented. Because we're using , to separate rules (as you can see in the example below the field), it's impossible to use the in: rule.

We actually already have a fix ready along with new features but it's never been released, I will take a look at that to see if we can publish it ?

feyisayo

clarkwinkelmann Thanks for the feedback. I look forward to the new release.

Thanks again for the work on this extension.

Do you perhaps know if it is possible to add a dropdown field to the user profile?

clarkwinkelmann

feyisayo Do you perhaps know if it is possible to add a dropdown field to the user profile?

that's exactly what the new feature of that future version is ?

Looking at it now. I'm doing a last check for bugs and if everything's okay I'll publish it right away.

feyisayo

clarkwinkelmann Yippeee!!!!!! Can't wait

clarkwinkelmann

Just released version 0.2.0 of Masquerade. ?

You will probably be able to update without any issue, but there is one possible breaking change for you:

Validation rules are now separated by | instead of ,. Existing fields will be automatically updated when you run the migrate command. If you used | as an actual character in your validation rules, this can break validation. Access your admin panel and change your rule so | isn't used for any other purpose than separating the validation rules ! (you can do that before or after upgrading)

To update:

composer require flagrow/masquerade:^0.2.0
php flarum migrate
php flarum cache:clear
rm assets/rev-manifest.json

Or use Bazaar ?

What's in the update ?

Introducing field types. Setting simple fields is now very easy. Out of the box, you get:

Url
Email
Checkbox
Dropdown
Advanced

Url and checkbox fields use HTML5 field validation so users can type values more easily on mobile devices and the browser gives immediate feedback on invalid values. Links are clickable.

Checkbox offers a choice between yes and no.

Dropdown offers a list of choices in the form of a dropdown.

Checkbox and Dropdown both offer a "no option" option if you don't make them required.

Advanced is a simple text field validated with Laravel rules. If you had existing fields in version 0.1, they are now shown as advanced fields. You can switch their type to one of the new types to get the advantages listed above.

Having issues ?

Something could have slipped under our fingers while testing this (there were a lot of changes to get it working !). Please let us know here or in the GitHub issues if you have any question or issue.

feyisayo

clarkwinkelmann Thanks for this.

Most appreciated.

clarkwinkelmann

Version 0.2.1 has just been released and fixes a security issue present in all previous version of the extension. If you're already on version 0.2.0 you can run composer update flagrow/masquerade. If you're still on 0.1.* you should upgrade by following the instructions in clarkwinkelmann You can also update via Bazaar.

The issue only affects you if you have set "View masquerade profile" permission to something else than "everyone". The issue was that even though the fields were no longer shown on the bio, all fields that are "visible on the bio" were still returned via the API to everybody even if they didn't have permission to view them, possibly exposing private data publicly via the API. The latest version fixes that issue.

Let me know if you have any question.

antalyanakliye

clarkwinkelmann What's in the update ?

Introducing field types. Setting simple fields is now very easy. Out of the box, you get:

Url
Email
Checkbox
Dropdown
Advanced

İs it Also Possible to add Phone Number Here

Hifihedgehog

I just reported an issue.
flagrow/masquerade26

clarkwinkelmann

KazeroG (and also Hifihedgehog ) we automatically get notifications for new GitHub issues, so it's not required to tell us about it here.

We really appreciate the reports though, thanks for helping ?

KazeroG

I just reported an issue to !
flagrow/masquerade29

010101

I just masqueraded it. Very cool. Ability to soup up profiles is very appreciated.

Jenxi

What's the use case for this extension? Is it to just add more information to a user profile? What if I want to have multiple profiles per user? Would that be possible? This has a potential for certain forums where users need a few profiles. For example, in role-playing boards, they would be able to generate a profile for each character they play and then choose which profile they are posting from.

I understand this might be very niche, but in theory it can be done if users get to create more than one profile. Just throwing in some ideas for brainstorming. Maybe someone has a better way to use this in a non-RPG setting.

In any case, I'll be installing and testing this out to see what if offers. Still, I'm curious how you guys are utilising this extension on your forums. Do share!

luceos

Jenxi What if I want to have multiple profiles per user?

Nope.

I love role playing as a target audience, but an extension like that would be pretty much completely custom made.

Jenxi

luceos could it be built off this extension though?

luceos

Jenxi that would be highly unlikely.

lensco

Small niggle with this extension: the order of the fields determined in the admin is only maintained on the profile page, not in the profile header and the users list page. They're displayed in the order created there, it seems.

(Also, what is the point of the Masquerade profile page, as all the information is already displayed in the header right above it?)

« Previous Page Next Page »