The problem appears in this sandbox project. When creating it, I left "Has project releases" enabled. Upon creation, there was a message which, correctly, pointed out that releases are not available for sandbox projects and that this option has therefore been deactivated.
However, something seems to have gone wrong there because, while the project is still definitely a sandbox project, I was able to add a release and enable automated testing (which fails, though, because it tries to retrieve the repository from the wrong location).
Since I'm not able to do this for other sandbox projects (and testing, as said, doesn't work correctly) I think the policy hasn't changed here but that this is a bug.
Comments
Comment #1
drunken monkeyComment #2
drummComment #3
drummIn
project_release_node_validate
,is being triggered on both node save and update.
form_set_value()
works on node save, but not update.Comment #5
drummI'm sure there is a more correct way to do this, but it works.
Comment #6
drummDeployed to Drupal.org and cleared out our data.
Comment #7
drummMoving to PIFT for the automated testing part of this issue.
Comment #8
jthorson CreditAttribution: jthorson commentedFrom pift_project_visibility():
So as long as the releases piece is taken care of, the 'enable' checkbox should never appear (and thus users will not be able to enable testing).
If testing is still enabled on the sandbox, we'll need to disable it manually within the db:
If not, then there's nothing left to do here, and the issue can be closed. :)
Comment #9
jthorson CreditAttribution: jthorson commentedAutomated testing has been disabled for the sandbox project.