Skip to content
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

Add a single organiser mode #569

Closed
wants to merge 4 commits into from

Conversation

publicarray
Copy link
Contributor

Useful to prevent the public from creating Events/Organisations without authorisation. (should be enabled by default IMHO; but that would break compatibility)

I would use this where there is only one organisation publishing events and where we don't want to allow the public to create Events/Organisations

(I think this should be enabled by default IMHO; but that would break compatibility)

Useful to prevent the public from creating Events/Oganisations without authorisation. (should be enabled by default INMO; but that would break compatability)
@ChildLearningClub
Copy link

@publicarray I actually can’t figure out how to allow the public to create events :). It appears that the admin can create users and add organizers, but I don’t see a public facing registeration page.

@publicarray
Copy link
Contributor Author

publicarray commented Mar 9, 2019

The public can create new organisation admin accounts and organisers from /signup. from there users within the organisation can create new events.

This PR disables the /signup route after installation

@ChildLearningClub
Copy link

Thank you @publicarray, I must have missed that... I agree the ability to disable that function is a great option to have.

New signups are only allowed through invitations!
publicarray referenced this pull request in publicarray/Attendize Apr 30, 2019
Useful to prevent the public from creating Events/Oganisations without authorisation. (should be enabled by default INMO; but that would break compatability)
@etiennemarais etiennemarais changed the base branch from master to next November 24, 2019 18:43
@etiennemarais
Copy link
Contributor

@publicarray Thank you for contribution. I am loojing to get this merged into our next branch. Please help with the conflicts? 🙏 The next branch has recently undergone a large laravel version upgrade (6.5.1) Please use the new routes file since it has moved

Copy link
Contributor

@etiennemarais etiennemarais left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please deal with the conflicts?

@publicarray
Copy link
Contributor Author

Closing in favour of new pull request on the updated branch next #741 🤩

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants