Under 4.6.2 at least, when project is installed the module doesn't seem to do anything. You can create a project, but projects require releases to be visible; and there is no way to tell that releases are required.

I think this is really two problems.

1) There was no obvious way to create a release. For my purpose, the project didn't actually have any kind of source code; but even if it did, I couldn't find anything that told me how to set up a relase.

2) Projects shouldn't *require* releases; they should have some kind of fallback so that if a project has no releases, it can still be viewed, and give the project owner instructions on how to proceed.

I ended up hacking the project code a bit so that releases aren't required to see most of the functionality. (I'm using it basically as a todo list for setting up my site, that my testers can interact with and use.
A release is just when code goes from the test site to the main site.)

CommentFileSizeAuthor
#5 project.inc-ShowWithoutRelease.patch5.29 KBmoggy

Comments

gtoddv’s picture

gtoddv commented

I concur. There shouldn't have to be releases, and least not code releases. And until the module doesn't require them, the instructions should reflect that project won't work unless you do have a release.

killes@www.drop.org’s picture

killes@www.drop.org commented

I think I'd consider a patch.

singularo’s picture

singularo
Location Adelaide, AUS
commented

I agree, I want to use projects as an interface for customers to submit support calls. Releases are not required for this, and until I found this post, I didn't know why they weren't showing up.

merlinofchaos’s picture

merlinofchaos commented

I would be happy to try to pull the work I've done out and make a patch. I'm worried that there are some possible gotchas; since I'm not using code releases at all, I could easily have broken the functionality if there actually are releases. I will take a look at what I've done when I have some time (hopefully tonight, Pacific time) and post a diff here, and hopefully people who do use releases can test it for me and make sure things continue to work.

If anyone with module knowledge has any advice about this, I would appreciate it!

moggy’s picture

moggy commented
Status: Active » Needs review
StatusFileSize
new project.inc-ShowWithoutRelease.patch5.29 KB

I'm sure I posted a patch for this a few months ago. Any done it again on the latest cvs version.

moggy’s picture

moggy commented
Version: » 4.6.x-1.x-dev
Status: Needs review » Reviewed & tested by the community

currently applies with an ofset of 4 lines, but still does what it's supposed to.

I know this is being addressed in a diferent way in the cvs version of Project, but I don't think that is going to be backported to 4.6, so could this be the 4.6 solution?

sammos’s picture

sammos commented

I installed this patch, double-checked it, and don't see any change in behavior. Still no projects showing up. I'm not sure what I'm doing wrong.

Thanks! ;)

benwei’s picture

benwei commented

I also have tried both of moggy's patches, and neither of them seems to fix the issue. I still get a blank projects overview page.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Try the patch that was applied to fix this in HEAD, http://drupal.org/node/31264#comment-46694 (comment #7). Not sure if you'll have to manually edit to get it to apply.

dww’s picture

dww
we/he/they
commented
Status: Reviewed & tested by the community » Closed (won't fix)

this has long been fixed in the 4.7.x and 5.x versions.