With still plenty of errors, and confusion as to why there is no documentation for the project module, I have gotten the module to a usable state (so long as I don't make projects public, since I'd have to support users when I have no support myself).
The one remaining error which I've just discovered is that the Download link for projects points to:
/?q=assets/releases/<file_item>
Which is completely broken and should be:
/assets/releases/<file_item>
But the only thing that I've been able to find in the 'project.inc' file is:
$links[] = l(t('Download latest release (%version)', array('%version' => $release->version)), $release->path);
The value $release->path gets set in the file 'release.inc', here:
$dir = dirname($path);
and then, transferred to:
$release->path = $path;
And then later, in the same file ('release.inc'), a Drupal function is called, passing that data:
if ($release->path) { $output .= '<small>Download: '. l(basename($release->path), $release->path) .'</small><br />'; }
So...if I go and edit the function l(), then that will screw everything else.
But it appears that it's getting some bad data in two places, as shown here.
What's different about 'project.module' that I would get back this "/?q=" value, and that be wrong?
Where should I look to fix this last item before I try to personally use this wonky module?
-- Gary
Gary (Lists) wrote:
With still plenty of errors, and confusion as to why there is no documentation for the project module, I have gotten the module to a usable state (so long as I don't make projects public, since I'd have to support users when I have no support myself).
Out of curiousity, have you looked at the casetracker module which is a redone, slimmed down project module?
"Earl Miles" wrote:
Gary (Lists) wrote:
With still plenty of errors, and confusion as to why there is no documentation for the project module, I have gotten the module to a usable state (so long as I don't make projects public, since I'd have to support users when I have no support myself).
Out of curiousity, have you looked at the casetracker module which is a redone, slimmed down project module?
Thank you, Earl.
I have no gone and read about this module, and it really (!) looks useful. I was already struggling with ways to 'mask' some of the geek-specific nature of 'project' module (which should be called 'softwarerelease.module' for clarity.)
We have techie-type software projects available (2 currently, because it's too unstable for users) but we also wanted to manage 'book projects', 'meet-up' projects and the like.
And, our second full-paying client wants to track 'art projects', which we've been able to mostly implement for them, with quirks.
'casetracker' will help, but not for awhile, since it's developed for Drupal 4.7 and the form API's present there. We are not moving to 4.7 and the client uses CivicSpace, which is built on 4.6.6 as you know.
So...I have downloaded the 'casetracker' and I really think this will be useful down the road, if we do decide to use 4.7 when that comes out.
Thanks kindly for turning me onto this module. [1] -- Gary
I really dig the "hey, we fixed that, wanna see?" nature of Drupal. I wish the Drupal.org web site was better at providing the latest updates, however.
One of the serious problems with 'project.module' is because over one year ago, 'nedjo' indicated on the project module issues page that some bug fix patches had been applied.
However, the latest download of the project module, dated this year, this month, does _NOT_ include those patches. It's a real hair-puller trying to reverse engineer almost every aspect of Drupal. :)
-
Earl Miles -
Gary (Lists)