How to display the Profile Type in the Info block on the profile view page?

Hello,

I would like to deter members from creating a profile for a business/organization using the person profile app. Instead, business should create an Organization profile. They have to meet all my platform requirements for organizations and go through an approval process to create their profile.

I know that from the url, we can tell whether a profile is for a person or an organization but, i would like that information to be clearly visible (mentioned) on the profil page as well.

That's why, in the Info block on the profile page (view person and organization), i would like to display a field that shows the profile type. e.g::

Profile Type: Person

or

Profile Type: Organization

I would like other members to easily identify what type of profile they are dealing with, whether it's a person or an organization. That will also expose scammers (people) who will try to act as a legit company while using a person profile.

So, how to achieve that?

Thanks

  • 557
  • More
Replies (12)
    • Can you just add in the corresponding text fields in the Forms -View Info block?

      • My solution for that was to define a special level for organisations to my needs.

        So imagine, the Membershiplevel for Organisations is called ORGANISATION - then you just have to enable MEMBERSHIP in navigation/organisation/snippetmeta and the membershiplevel 'organisation' is shown on the card...

        Same with Organisation Categories and showing them on the cards...

        • Thanks but if I use a text field and enter the Title: 'Profile Type', how will I get the field value: 'Person' or 'Organization' to display? Please remember that the field should not be edited by the members. It will automatically be displayed by the system.

          • Thanks. I have already done that with my membership levels (standard, premium etc), they display in the person and organization snippet meta. I don't have a membership called 'organization'.

            • Hello Dear @LeonidS Please could you jump in and help. Thanks in advance.

              • Hello @OneEagle !

                As the Persons and Organisations apps have their View page and View Info block you may try to use several variants:

                1) Create the language block with text like Profile Type: [profile type]and place it above the Info block for every app. You may append it to other fields set with the Javascript.

                2) Create the Info field in the View Person and View Org displays.

                • Hi Dear @LeonidS Thanks for your reply. The language block idea sounds good but I'd rather go for an info field in the View Person and View Org displays. So what is the appropriate field to create? A text field? If so, how to get its value to automatically display the word '`Person' or 'Organization' without it being added or edited by the the members? Thanks

                  • No, it will be the field like "caption", we have such type in our Forms App (see the attached screenshot). And you may write there the plain info like Profile Type: Person.

                    • Thank you so much. It works! That's exactly what I was looking for. and I wasn't even aware of that caption field.

                      Now there is a small problem. I have a multilingual site. While creating that 'info' caption field, there is no may the enter the value of the 'Custem text' field in different languages.

                      Both 'System Title' and 'Title' fields have an option to enter their value in languages available in UNA but not the 'Custem text' field'. I have even tried to put a language key in that field but it didn't work. Any idea?

                      • Any idea on this one? @LeonidS

                        • If you have already the existing language key like _my_key you may write it there directly (starting with the _ symbol) and it will be processed.

                          • It works. Thanks a lot. As mentioned in my original post, I once tried to use the language key but it didn't work. I discovered why. For some reason, that 'Custom text' field doesn't support custom language keys (the ones I manually created), only existing keys packed into the system. I have used one of them and it worked. Thanks

                            Login or Join to comment.