Hi there.

I've been using the older version of Project with 4.6.x for a while. I finally (don't say it) got around to updating to 4.7.4 today, which works fine in other regards. However I am having some issues with project. I DLed and installed both Project and Project_Issues. This worked OK so far as I could tell. I then ran update.php. It claimed "no newer version" was available but I did not believe it (upon not updating things were not working). So I selected the updates listed. Project_Issue only had one available, so I selected that. Project.module had four available, listed as 1-2-3-4. I'm not sure which was newest/oldest, so I picked "1". I then ran the update script and everything seemed OK. On the projects page, all my old stuff was listed with proper releases, etc.

Now for the problem. I cannot seem to add new releases like I used to. I have tried a couple of things and none have worked. First, the old way, was to just "attach" a file with the same base name and a higher number. For example file-0.3.0.tar.gz was the old release. Attach file-0.3.1.tar.gz, and Project realizes that's the newest release and updates your links, under 4.6.x. Under the new version this does not happen. I tried deleting all the files and just attaching the newest one, but that made it totally forget about releases at all.

I went into the admin section and chose the "files" directory explicitly, and had it "scan." It claimed (correctly) that it found some new files and updated some old ones as no longer existing, but when I went back to the page for the project, although the file was still attached, it was not listed as a new release. I tried using the 'create new release' link on the project page, and that looked good. I gave it a version # and chose a file and so forth. However.... after clicking submit that just brought me to a blank page and gave me a stream of errors in the log.

So I am a bit stumped here. How is one supposed to create releases with this new version?

Thanks,

Steve

Comments

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (won't fix)

i don't know, honestly. the current DRUPAL-4-7 branch's handling of releases is pretty screwed up, as far as i can tell. however, i'm not going to even try to get this working, since in the new glorious world of releases-as-nodes (http://drupal.org/node/83339) which is part of the new release system (http://drupal.org/node/77562), it's all vastly better.

if you want to be an early adopter/beta-tester, you can attempt to play with the code in the DRUPAL-4-7--2 branch of project* and see how you like it. sadly, i haven't had a chance to write any install or upgrade docs, so you should definitely tread lightly and only mess with it on a test site. ;) alternatively, you can see how things work on scratch.drupal.org (http://drupal.org/node/90436).

good luck!
-derek

Steve Viscido’s picture

Steve Viscido commented
Title: Can't get releases to work right » Thanks

Thanks for getting back to me.

I'm a bit confused on that last link, as it seems to want to link every release/node to CVS -- which I do not use on my site -- and to give it a version number having to do with Drupal. Since I am building programs that have absolutely nothing to do with Drupal and just using project to help users find and DL the latest release, I'm not sure this module will continue to be of much use if that becomes a key feature. In the end it may be easier for me to just make page nodes and add attachments and let users figure out from my numbering system what the most updated release is.

But thanks for responding anyway.

Steve

dww’s picture

dww
we/he/they
commented
Title: Thanks » Can't get releases to work right

(as the note next to the title field says: "modifying this value will change the title of the entire issue, not your follow-up comment."... setting this back).

i was *very* careful when developing the new release system to:

  • make it all work and make sense without cvs.module installed
  • keep all the drupal.org-specifc stuff either entirely as settings, or, where necessary, as separate functions/files in the parts of the code, clearly labeled with comments (and the bulk of that is in the cvs.module parts of it, though also the script to convert existing project.module installs to convert things to the new release system, which you may not even need depending on the number of existing releases you've got, if you're using the issue queue, etc).

so, the new release system should continue to allow you to use project.module for all of these sorts of things, even if you're not building releases from CVS and don't use the version number scheme we'll have on drupal.org.

give it a try (again, on a test site). checkout the latest version of contributions/modules/project and contributions/modules/project_issue from the DRUPAL-4-7--2 branch and see what i mean.

sorry if the link was confusing... i was mostly just showing you the a) kinds of stuff you can now do with releases and b) how close it is to being ready for production use.

cheers,
-derek

Steve Viscido’s picture

Steve Viscido commented

Ah, OK. I will try it at some point. Sorry about changing the text field. That's what I get for typing without caffeine.