Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Uhh... I just tested this locally using the d.o testing profile. Seems to work as designed for me. As the "doc1" user (i.e. someone without 'administer projects' permission), I created a release node for the "Subscribe" project. I said it was from HEAD, and it was 5.x, (5.x-1.x-dev to be exact). Once that existed, I went back to edit the release node. As expected, the api version selector only had 1 option, the existing value of 5.x.
If there's a bug here, can you provide detailed instructions on how to reproduce it? I *knew* I had code to handle this case, and it even seems to be working. ;)
Comments
Comment #1
dwwyup. this is related to (but not duplicate with) http://drupal.org/node/89699
-d
Comment #2
dwwUhh... I just tested this locally using the d.o testing profile. Seems to work as designed for me. As the "doc1" user (i.e. someone without 'administer projects' permission), I created a release node for the "Subscribe" project. I said it was from HEAD, and it was 5.x, (5.x-1.x-dev to be exact). Once that existed, I went back to edit the release node. As expected, the api version selector only had 1 option, the existing value of 5.x.
If there's a bug here, can you provide detailed instructions on how to reproduce it? I *knew* I had code to handle this case, and it even seems to be working. ;)