Hi, I have Problems with automatically adding Users to the Default Communtiy (guess it was called liferay.com, I renamed it to "skn-liferay").

So basically when i put the Comunity "skn-liferay" to default user associations, my
user wont be added to this community.


When i try the same with a custom made Community it works fine. But currently i want to use the default community to keep it as simple as possble.

Is this a bug or a probelm of me, not understanding the Comnunity system XD?

Hi Felix:
I have just tested this and I everything seem to behave as expected.
Which version are you using? Does this happen to you if you create another community?
The default community should behave like any other community. Are you getting any log messsage after the user's creation?

Hi, sry 4 delay.

I am Currently using V6.0.5 (one of the Nightly Releases).

When i create a new community and make it a default user association it works fine.

gotta check the logfiles agian maybe there is something i didnt saw last time.




I did some more testing. I deleted my own account, restarted the server (user import on startup is enabled). Now my account is reimported, but even now im not member of the default community :/ .

Right now all 189 Members are added manually.

Attachments:

1.JPG (16.1k), 2.JPG (23.9k)

Maybe the guest community is somehow special
Try it with another community, just to be sure

Hi Juan,

I already did, its only the default comunity that doesnt work.
comunties created by me are automatically added to the users default
comunities.

Can I create a new comunity that uses the same pages as the default
comunity? A custom comunity with the same pages like the default would
solve my problems I guess?

I could easyl bind my page permissions to the new community, couldn´t I?

Hi,

I have had the same problem. The solution is simple, but not straightworward: You must add "Guest" to the list of default communities. Here comes the explanation:

Juan is almost right when he says that the default community is a regular community. There is one little exception: You cannot set the name of the default community. In the portal UI, it is always referenced by the name you set under Settings/General/Main Configuration/Name. This name, however, does not get copied to the GROUP_ database table. In the database, the default community's name is (always?) "Group". I guess that the default community mechanism uses the information from the GROUP_ database table. That's why you have to use the name "Guest".

I would have used the numerical ID for the default community mechanism instead of the name, since the name may change, but that's a different story.

Holger

Yes I too agree with Keen. I'm also facing exactly the same problem

Hey Holger!

It worked man. Cheers for you !

We were having the same issue with our deployment, and this was exactly what we needed. Good information knowing the "Guest" community is always referenced as "Guest", and doesn't get renamed. Works as expected when adding "Guest" to the list.