github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

"DEFAULT_ALLOW_CREATE_ORGANIZATION = false" is ignored during new user creation #3155

New Issue
Closed
opened 2025-11-02 05:02:14 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 05:02:14 -06:00
Owner
Copy Link

Originally created by @igsol on GitHub (Apr 8, 2019).

  • Gitea version: 1.8.0-rc2
  • Operating system: Linux
  • Database:
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Not relevant

Description

Precondition:

[service]
DEFAULT_ALLOW_CREATE_ORGANIZATION = false

After a brand new user is created he/she is able to create organization.

Screenshots

  1. image
  2. image
Originally created by @igsol on GitHub (Apr 8, 2019). - Gitea version: 1.8.0-rc2 - Operating system: Linux - Database: - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Not relevant ## Description Precondition: ```ini [service] DEFAULT_ALLOW_CREATE_ORGANIZATION = false ``` After a brand new user is created he/she is able to create organization. ## Screenshots 1. ![image](https://user-images.githubusercontent.com/14091049/55725632-c60c8380-5a16-11e9-8d70-9ca5f55052c0.png) 2. ![image](https://user-images.githubusercontent.com/14091049/55725790-0d930f80-5a17-11e9-95da-6b07cf9fb746.png)
GiteaMirror added the type/bug label 2025-11-02 05:02:14 -06:00
GiteaMirror commented 2025-11-02 05:02:15 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 9, 2019):

There is also another config item

[admin]
DISABLE_REGULAR_ORG_CREATION = false

to control organization creation.

@lunny commented on GitHub (Apr 9, 2019): There is also another config item ```ini [admin] DISABLE_REGULAR_ORG_CREATION = false ``` to control organization creation.
GiteaMirror commented 2025-11-02 05:02:15 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Apr 9, 2019):

Too many options ?

@adelowo commented on GitHub (Apr 9, 2019): Too many options ?
GiteaMirror commented 2025-11-02 05:02:15 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 11, 2019):

Yes, maybe only one is necessary.

@lunny commented on GitHub (Apr 11, 2019): Yes, maybe only one is necessary.
GiteaMirror commented 2025-11-02 05:02:15 -06:00
Author
Owner
Copy Link

@igsol commented on GitHub (Apr 11, 2019):

@lunny , thanks for [admin] DISABLE_REGULAR_ORG_CREATION = false, I wasn't aware about it.
Despite the non obvious name, actually it's what I do really need.

@igsol commented on GitHub (Apr 11, 2019): @lunny , thanks for `[admin] DISABLE_REGULAR_ORG_CREATION = false`, I wasn't aware about it. Despite the non obvious name, actually it's what I do really need.
GiteaMirror commented 2025-11-02 05:02:15 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (May 23, 2019):

DEFAULT_ALLOW_CREATE_ORGANIZATION is used in ldap sync and user creation so this should be kept. Don't know about use case for disabling org creation completely

@lafriks commented on GitHub (May 23, 2019): `DEFAULT_ALLOW_CREATE_ORGANIZATION` is used in ldap sync and user creation so this should be kept. Don't know about use case for disabling org creation completely
GiteaMirror commented 2025-11-02 05:02:16 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 23, 2019):

#7017 will rewire it back in. Restoring it's functionality

@zeripath commented on GitHub (May 23, 2019): #7017 will rewire it back in. Restoring it's functionality
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3155
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?