Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I create the new module and add the release tag. But, I have found that the "Add new release" link become available only after several hours. If the link can be unavailable during several hours, I suggest to write about that in the following docs:
1. https://www.drupal.org/node/1068944
2. https://www.drupal.org/node/1015226
| Comment | File | Size | Author |
|---|
Issue fork drupalorg-3189882
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
wombatbuddy commentedThe link appeared a few hours later.
Comment #3
wombatbuddy commentedComment #4
wombatbuddy commentedComment #5
drummI quickly fixed this yesterday, but didn’t update the issue yet. When editing a project, there is a “Has project releases” option to enable releases in the Releases vertical tab. This defaults to being checked for full projects, with an option to disable it when promoting a sandbox project. I edited the project to re-check that option.
Comment #6
wombatbuddy commentedThanks, but I don't see the "Releases" vertical tab and the "Has project releases" option. Also, I didn't promote this project from the sandbox. See the screenshots:
Comment #7
wombatbuddy commentedComment #8
wombatbuddy commentedComment #9
drummThe option to toggle whether releases are enabled for a project is removed once a project has a release. It is permanently enabled once there is a release.
I’ll double check what this looks like for new projects.
Comment #10
wombatbuddy commentedTake a look at this project, that hasn't a release yet:
https://www.drupal.org/project/gc
I don't see the “Has project releases” option, and you?
Comment #11
drummI missed that we have “Has project releases” locked down to admin-only, which explains why you can not see that vertical tab and checkbox.
What probably happened is some combination of the full/sandbox project type, previewing, etc, got the field set incorrectly. For example, one of the places that the field value is set to disable releases is when previewing and the project type is currently sandbox. Changing it to full project before saving doesn’t have a corresponding way to reset releases to enabled.
Regardless of how it happened, for Drupal.org, we always want full projects to have releases enabled, and sandbox projects to have releases disabled.
Comment #14
drummThis is now deployed, along with a couple other small cleanups, like fixing PHP notices in project_release module I found along the way.