Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Hi,
I am trying to create a release for a project, using the "Add New Release" link on the project page.
However, on the release creation page (node/1#overlay=node/add/project-release/1), I am still asked to provide the project id, which, to my understanding, should be automatically populated giving the context.
Any ideas?
Thanks.
foredoc
Comments
Comment #2
drummYes, you are understanding what should be happening.
This is added as a new menu item in
project_release_menu_alter(). If you haven't already, try clearing Drupal’s caches, it could be a stale menu cache. Otherwise, I'm not sure what could be causing this without more information. That function would be a good place to start debugging.Comment #3
drummThe release node type has a Project field. I see this isn't being prepopulated and hidden on a clean install.
Comment #4
foredoc CreditAttribution: foredoc commentedThanks, drumm.
If this is a bug, do you have any suggestions to fix it.
I assume that the project management on drupal.org is not experiencing the same problem as I did, and I am wondering if the project management capability on drupal.org is built on some specific versions/customization of the project module.
Any suggestions on the fix/walk around of this problem will be very much appreciated!
Regards,
Foredoc
Comment #6
drummThis made me realize there's a dependency on field_extrawidgets, which hides the project field.
Drupal.org runs near the -dev version, 96dcb53 at the moment. https://bitbucket.org/drupalorg-infrastructure/drupal.org/src/HEAD/drupa... is always updated.
Comment #7
foredoc CreditAttribution: foredoc commentedThank you very much, drumm!
With the new dev version, I can see that the project id field has been hidden on the "Add New Releases" page. However, when I try to upload the release file, the problem described in:
https://www.drupal.org/node/2671276
still exists. And I have no idea how to solve it.
I appreciate all your help and effort on this, and it will be great and extremely helpful if I can ask one more favor from you:
1) install a fresh drupal 7.x-42, and
2) install the dev version of project module
see if the release upload functionality works, or suggest how to make it work (e.g., is there any specific tuning/setting that I should be aware of).
Many thanks!
Regards,
foredoc
Comment #8
foredoc CreditAttribution: foredoc commentedComment #9
foredoc CreditAttribution: foredoc commentedHi Drumm,
Is there any other tricks I need to know to make it work? Seems that I am the only one who has the problem, however, it repeats for every combination of drupal core and projects module (7.x versions) that I have tested so far.
Thanks.
Regards,
foredoc
Comment #10
foredoc CreditAttribution: foredoc commentedI think that I have found a walk-around for this problem:
1) first, create a project release without uploading the release file;
2) edit the previously created release by adding release file(s) to it.
Currently, this is the only way that I can make it work.
Any suggestions how to enable the release file uploading during release creation?
Thanks.
Regards,
foredoc
Comment #11
drummThat makes sense. On Drupal.org we don't allow users to upload files, they are attached by packaging shortly after the release is saved. So we hadn't encountered this in testing yet.
Comment #12
drummComment #13
dwwIn recent testing of a clean Project* site, this part seems to be working fine. I can create releases and they're automatically associated with their projects. The project field on release nodes is indeed hidden.
I think #2671276: Error in uploading release files is a separate bug and more limited in scope to dealing with release files.
Let's call this fixed and sort out the file attachment stuff over at #2671276.
Thanks,
-Derek