-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Join common from a space #2076
Comments
@elatif2020 |
@elatif2020 Again about redirecting to the back page if we are not a member of current space.
Otherwise, if we are either member of root common, or there is autojoin in both root space and space, then we show public content, correct? |
yes sounds good |
@elatif2020 At the moment after log in user is redirected to the inbox page. Should we stay on the front or back page if the user logged in from them? |
@andreymikhadyuk |
@elatif2020 should we remove text |
@elatif2020 do we need to display |
it should be with the relevant name as you wrote |
…om-space Join common from a space #2076
Maybe issue https://github.com/daostack/common-backend/issues/2172 is related here, not sure, need to check |
Guests in a space (with autojoin both for the rootCommon and for space, otherwise show backpage):
Show (public parts of) front page
In the front page: “Join $RootCommonName” in the bottom of selected chat*
Add "Join via common page" button with a link to the root-common in the backpage.
->Stay at (or jump to) that space front page (but now with writing option in chat)
BE: Follow only common Home and that space Home upon joining
In the backpage make the $parentCommonName a link to it.
For unauthenticated user ask to user first to login\signup and after it check membership again and do the relevant action.
** If the user is a member in the root common and not in the parent we should show a message instead of the join button:
"To join this space you should first join $ParentCommonName" (with a link)
The text was updated successfully, but these errors were encountered: