Display username when fullname is not available

What needs to be done

For ESS France, a lot of people have created their account but have not filled-up their first and last name. That results in a non-usable interface when some navigation buttons appear blank :

Technical details

I don't know how to use a conditional field in solid-display to display something only when something else is void.

The actual Hubl interface does not allow to create users without a full name. The only way to do so are using Django directly.

A way to handle your case may be to add required-name to your solid-display. It'll hide every users without a name.

Can you point me where this is enforced ? I don't think that Django interface has been used here : every user has created its account on their own (its an open registration instance).

With the introduction of communities, Hubl does not support the open registration anymore, by Django I mean the self-registration or the django's admin.

Two rules apply:

• Only a community administrator can invite someone on its community
• A user must belong to a community

First draft of communities does not include anything else, we may implement community notion on job board, then circles/projects before improving it here with custom permissions sets per communities.

Are you kidding ? You mean that I can't upgrade ESS France to the latest Hubl or open registration will not work anymore ? Why ? Can't I opt-out of communities in that case ?

If you mean bare upgrade it, yes.

I don't think that not taking communities is a solution here, as they'll mandatory for every object within Hubl.

Upgrading anything to its latest version, when it include some breaking changes, does involve some adaptability needs.

Still, even if the actual implementation does not handle what you need, it's something that were on the roadmap - we had only one Hubl instance wanting for it (Startin'blox itself).

Here, I think that we can add a simple script:

• Is there a DEFAULT_COMMUNITY (Containing the urlid of the community)
• Yes: When an user is created, add them to this community
• No: Is there only one local community ?
• Yes: When an user is created, add them to this community
• No: This is sad, your user will not belong to any community.

OK, There is only one local community, so I can put this one as default. The question is : will open registration still work, and if no, what do I need to make it work ?

As is, it will still work. Created users will not belong to any community, that can involve few visual bugs on app while not limiting their user experience.

After #853 (moved) implementation, it'll limit their ability to create job offers.

If we implement the behavior on the comment right above: It'll work.

Ah, thanks. I thought that was blocking for me, but it seams OK. I plan to update at some time in the coming weeks.

I think we are safer with belt and braces here : because in the future, user could come from external servers not implemented by DjangoLDP. So a user could register with only a username, and Hubl should provide a consistent interface to deal with this.

While I do agree with you, I'm not sure that we can afford this for now.

Overall, it join this issue: #694 (closed)

A very simple way to implement this would be to change this on the server side in Django :

    def name(self):
        return self.get_full_name()

Replace this definition with :

    def name(self):
        return self.get_full_name() if self.get_full_name() else self.username

and we are done !

Agree, it'll work as long as we don't have any external not-djangoldp servers. :)

@fabien4vo Do you handle the implementation part?