Hello! It if I add a release to an owned project, it's just fine. While that is wonderful, every time I edit that release it 'vanishes'... or some-how unattached from the project. I've tried even editing and CHANGING NOTHING, and the same effect happens, every time. *shrugs*

After editing my release, I then return to my /project/test and click "View all releases".

Releases for test

There are no published releases for this project. Recently added releases will not be published until the packaging scripts have run.

What's going on?

Comments

czarphanguye’s picture

czarphanguye commented

Note 01. I've just noticed even the breadcrumb is broken "Home » Projects » » Releases" while viewing my release after an edit... could this be an issue with Release or another module (i.e. pathauto?).

dww’s picture

dww
we/he/they
commented

- are you using category.module on your site?
- the breadcrumb will be screwed up like that if the project taxonomy stuff isn't right.

czarphanguye’s picture

czarphanguye commented

I am not using category.module. Should I?
My categories are as follows:

Projects (Main Vocab name, auto made by installation, assigned to Projects Module)
  -> Tool
  - - > Networking
  - - > Programming
Project Release API (Main Vocab Name, Auto made by installation, assigned to Project-release)
  -> v1.0
  -> v2.0

When Project is made, it's assigned (Tool -> Networking).

When Project-Release is made, it's assigned (v2.0).

In admin -> Project Release Settings, I have;

* @Unmoderate projects with releases, Enabled.
* @Active Anti-Cheat Compatibility terms. both v1.0 and v2.0 checked
* @Browse projects by release versions. Checked.
* @Default release overview: v2.0

dww’s picture

dww
we/he/they
commented

I am not using category.module.

good.

Should I?

not if you want project* to work. ;)
http://drupal.org/node/124846
http://drupal.org/node/90188
...

czarphanguye’s picture

czarphanguye commented

Do you believe this is due to conflicts with another module? I'll start disabling and debugging to find out if that helps at all, in the mean time please review this list of installed module as my entire site is shut-down as project-release is a required component. thanks.

Modules Installed
--------------------
* CCK

* Core Modules

* Private Message/Subscriptions
* Coolfilters
* Diff
* HTML Corrector
* Live Discussion
* LoginToboggan
* NodeAccess
* PathAuto
* Printer pages
* Service Links
* Similar Entries
* Taxo Image
* User Badges

* Projects (Project, Issues, Releases)

* Tagadelic

* External Links

* Views (RSS, Theme Wiz, Views UI)

* Leech

Again, the initial project-release works, yet upon edit 'poof' and it's no longer 'attached' to the master project, nor displayed on /projects.

czarphanguye’s picture

czarphanguye commented

Note, I've gone ahead and disabled just about every module that I could and this problem continues.

Using the breadcrumbs as reference.

First Release
--------------------
Home » Projects » Networking » ModProbe » Releases (Releases sinks to /node/250/release)

After Edit
--------------------
Home » Projects » » Releases (Releases links to /node//release)

Clearly the (250) owning project is gone!?

dww’s picture

dww
we/he/they
commented

are you using book.module, by any chance? http://drupal.org/node/98278

czarphanguye’s picture

czarphanguye commented

are you using book.module, by any chance? http://drupal.org/node/98278

Yes! Book.module is enabled. I'll disable and report back.

czarphanguye’s picture

czarphanguye commented

Yes! Book.module is enabled. I'll disable and report back

Disabled and Uninstalled... Still broken. :-( *sigh*

Thank you for your support on this issue!

czarphanguye’s picture

czarphanguye commented

Alright.. So, What I did was add a release (that works), dumped the project_release database. Next, I edited my release and dumped the project_release database again. Here's the diff output:

--- release.works	2007-05-22 19:57:17.000000000 -0400
+++ release.broken	2007-05-22 19:58:06.000000000 -0400
 
@@ -32,7 +32,7 @@ INSERT INTO `project_release_default_ver
 -- 
 
 INSERT INTO `project_release_nodes` (`nid`, `pid`, `version`, `tag`, `file_path`, `file_date`, `file_hash`, `rebuild`, `version_major`, `version_minor`, `version_patch`, `version_extra`) VALUES 
-(428, 425, '3.10', '', 'files/0r_V3.10.zip', 1179878156, '66ecddcaa47741116f663e10ce6cddfa', 0, 3, 10, NULL, NULL);
+(428, 1023, '3.10', '', 'files/0r_V3.10.zip', 1179878156, '66ecddcaa47741116f663e10ce6cddfa', 0, 3, 10, NULL, NULL);
 
 -- 
 -- Dumping data for table `project_release_projects`
@@ -40,3 +40,4 @@ INSERT INTO `project_release_nodes` (`ni
 
 INSERT INTO `project_release_projects` (`nid`, `releases`, `snapshot_table`, `version_format`) VALUES 
 (425, 1, 1, '');
+

As you can see from the above diff, the PID jumped from the correct value of 425 to what appears to be a random 1023. Next I manually edit the mysql database and edit 1023 BACK TO 425, and now thing work...

Oh, what to do... what to do...

czarphanguye’s picture

czarphanguye commented

Help? How might we restrict the PID to the proper table (if that is even the problem) rather then (what appears to be) grabbing the first one on project-release edit?

czarphanguye’s picture

czarphanguye commented

Am I really the ONLY person with this problem? That's amazing... *shrugs*... anyone else?

czarphanguye’s picture

czarphanguye commented

For a price? How much will it cost to have someone correct this issue I'm having? Dare I say, Bounty offered?

Reach me czarphanguye ['at'] gmail.com

aclight’s picture

aclight commented

I am using the latest version of the project* modules, and I also have Book enabled, and I'm NOT seeing this problem at all.

What exactly are you doing when you edit releases? Just clicking edit on the release and then submit, or are you actually changing something? If you are changing something, let me know and I will check to see if I can reproduce the problem on my setup.

AC

czarphanguye’s picture

czarphanguye commented

I can change something, I can change nothing.. doesn't matter. The moment I submit any type of edit, gone.

Perhaps it's the leech.module + project_release.

dww’s picture

dww
we/he/they
commented

i'll tell you exactly what the problem is: something is clobbering $node->pid. it's lame that project* (and all of drupal, for that matter) blindly populates $node with its own variable names, with no concern for namespaces whatsoever. book does this when you put a release node into a book outline, since $node->pid to the book module means the nid of the parent book page, whereas $node->pid for a release node means the nid of the project the release belongs to. same thing here with the issue's $node->pid, which project_issue thinks is the nid of the project the issue belongs to.

that said, i have no idea what module on your site is clobbering $node->pid like that. you'd have to grep for "pid" in all of the drupal code you have on your site and figure it out.

or, you could roll a patch against project_issue that does everything via $node->pi_xxx or $node->project_issue_xxx instead of just $node->xxx directly. however, if you do that, please post the patch at http://drupal.org/node/98278

good luck,
-derek

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (duplicate)

http://drupal.org/node/98278

p.s. it's probably path.module that's killing you, if not book. anyway, we all know the problem now, let's just fix it at #98278