problem with sorting after editing project release - urgent

We need more specific information to troubleshoot this.

1. Please provide the actual paths (URLs) on your site where things work and don't work.
2. When you say "the release is categorized accordingly under:", are you giving the breadcrumb visible when you're viewing the release node, or do you mean that you have a multi-level hierarchy project type vocabulary?
3. Please paste the entire hierarchy of your Project type vocabulary and your API Compatability vocabulary.
4. Please provide a list of all core and contributed modules in use on your site, with their versions. In addition, what version of Drupal core are you using?
5. Are there any errors displayed on the page or in your watchdog log that you think are relevant to this problem?

I see that at, as an example, http://crycity.wonderingfish.com/project/release/project-200-rc the breadcrumb does not look right.

However, you have quite a few modules installed, and my hunch is that there is a conflict between project/project release and one or more of your contributed modules.

The best thing to do is to start from a fresh Drupal install, then enable the project and project release modules, and then try enabling one or two additional contrib modules at a time, and each time check to see if you have this problem. Hopefully you would be able to isolate the problem to one or two modules, and then we can go from there.

This isn't something I've seen on my development or live sites, but I'm not running nearly as many modules as you are.

I would take a look at the {project_release_nodes} table for some of the release nodes that you've had problems with. If the value in the pid column for that node is totally wrong, then my guess is that you're running into a well known problem (see #98278: project* namespace bugs in $node). If this is the case the problem is probably being caused by another module which overwrites $node->pid (project id to the project/project release modules) with another value, thus dissociating the release node from the project itself. You could try using grep to search through your code base for '$node->pid' and try disabling any modules that come up. If you do happen to figure out the module that's interacting to cause the problem, please mark this issue as a duplicate and comment in the issue I mentioned above with the module that was the problem.

If it turns out that the information in the database is all correct, then I'm not quite sure where the problem is coming from. My tendency would be to guess it's a problem with some module that's taxonomy related, but I don't really know.

Yep.

I'm going to go ahead and mark this as a duplicate of #98278: project* namespace bugs in $node. Please follow up there if you figure out what module is interacting.

No, not really. I can tell you that views works fine, but that might be the only module I'm using on my site that you also use. My site, which runs project, as well as d.o, both run very few modules compared to most drupal sites.

As I suggested earlier, I'd suggest you grep your code base for some possible conflicts. From the command line, something like this:
grep -rin -e '$node->pid' .

Run this command from your base drupal installation (eg. /drupal) and then investigate the matches.

If you read through the other issue, you'll find a few modules that people have reported as causing problems. But the are likely more.

You can download all of your files to your local machine and do it that way. If you're using windows you'll probably want to install cygwin for the various unix tools.

Yeah, searching for just $node->pid will only get the really obvious problems, because not all modules call the loaded node object $node in all places. Even the project and project_release modules sometimes use $project instead. So grepping is imperfect.

But, I'm glad you figured it out. I'm going to post an issue in the pathauto issue queue pointing the maintainers to this thread. They may be able to offer some advice. If they ask any follow up information here, please respond to them.

Here's the issue in the pathauto queue: #284300: Pathauto (or just core Path module) conflicts with project*.

Issues that are closed, duplicate, fixed, etc. and which are put into a node in the following format:

[#nid]

are displayed with a strike through line.

I guess this is kind of fixed, right? It's been documented at least.