Project page is empty

As I understand it there are two possible causes for this:

1. The Projects module doesn't like your naming scheme. Projects wants files put out as "releases". To make a file be a release the short name you choose must be the same as the file, minus the following characters (without quote) "-X.tar.gz" -- where X is a release number. For example, you might have MyProject-1.0.1.tar.gz, or NewProj-0.8.tar.gz. If you do not have your file named in this way, Project doesn't understand that this is a file release, and it doesn't get posted. If you are on a windows system, the easiest way to make .tar.gz files is to get cygwin, which is free and will give you a unix-style shell. I can't go into all the details of how to use it but basically, you use the command "tar -cvf (filename)" to make a .tar file, and then gzip (filename.tar) to make a gzip of the archive (the tar, which stands for "tape archive", from back in the old days when computers stored information on reel tapes). However, before you go to this effort, I would make a simple text file and just name it YourFile-1.0.0.tar.gz, and try uploading it with YourFile as the short name, and see if this fixes it. If so, then you know this is the problem.

2. The other fun little problem is that Project does not seem to be compatible with taxononmic categories. If I enable any word or set of words to be usable with "Projects" or "Issues", it hoses the Projects page (I get a page titled "Projects" and it's empty). If I disable this, then immediately my projects re-appear on that page. This is rather frustrating since projects should be searchable by keyword like this, but it's frankly more important that the projects actually show up on the downloads page than that they have categories. I believe this one is a feature request that is currently pending.

Steve

If you name your file "myfile-1.0.tar.gz" or something, and give it a shortname of "myfile" (without quotes) and attach it, that should make the projects package automatically think of it as a release. So that is how you can upload it without shell access. In fact I didn't know about the "releases" directory. I will have to play around with that some.

Steve

The attached patch addresses the two (I know, not so closely related, but hey, both important) issues identified here.

1. While sometimes desirable (as on drupal.org), showing projects only if they have releases is confusing to new users of the project module and often not wanted.

I've made "Show only projects with releases" a configuration option. If checked, only projects with releases are shown. Otherwise (the default), all projects are available.

2. Projects are limited to one vocabulary.

Basically, project.module has a special use for a single vocabulary--the local tasks on the project overview page (and also references in the issue system). Adding new vocabularies for projects can mess up this special use.

To solve this issue, I've pulled the "Project vocabulary" into a configuration option, and then used this variable whenever the special use is needed. With this change in place, other vocabularies can, it seems, be applied freely without messing things up.

I've done some basic testing and things seem to work.

Fixing prob with previous patch.

1. What is wrong with showing projects with no releases on drupal.org? Less options it better IMO.

2. Using a special project vocabulary sounds like the approach we took in the forum.module? You can use different terms (of different vocabularies) to categorize a forum topic, but only one is used to render the forum view.

Here's a patch to remove the requirement for releases before a project is listed on the /project page. I've moved the taxonomy improvements to a new issue at http://drupal.org/node/32121.

Applied.

Can anyone please post a patched version of the project.module that will work on Drupal 4.6.5?

( I run windows and tried patching my project.module with the patches above using Gnuwin32 Patch 2.5.9, but It didn't work. Maybe I have the wrong version of the project.module or something... )

Thank you!

Hello, I am using Drupal 4.6.3 and I tried applying this patch using

"patch < project-list-without-release.patch" in the modules/project
directory. The patch seems to have failed. This is the error I get:

~~
patching file project.module
Hunk #1 FAILED at 350.
1 out of 1 hunk FAILED -- saving rejects to file project.module.rej
~~

A user already posted a note saying there was an issue applying the
patch in 4.6.5.

I find that my project.module file has 1.195.2.3 version
// $Id: project.module,v 1.195.2.3 2005/09/09 20:15:43 ax Exp $

But the patch file seems to refer to a revision 1.204.

How do I use this patch on my project.module? I'm open to overwriting it
with the 1.204 file and then applying the patch, if that is the way, but
I do not know how to do this. Mine is a regular drupal 4.6.3 installation,
and I am using it to build a new site. I need the project module to track development
and need this patch to keep things simple.

Advice appreciated.

-S

I'm able to see the projects in the 'My projects' page, so I'm able to start adding issues and track. The main project page itself remains empty, and is not terribly hampering work.
-S