Autocomplete on the Project field seems to be missing in places like http://d6.drupal.org/project/user and http://d6.drupal.org/project/issues/user.

All issues assigned to no one on http://d6.drupal.org/project/issues/user shows as "Anonymous (not verified)"

http://d6.drupal.org/project/issues/subscribe-mail hangs forever.

http://d6.drupal.org/project/issues/search?text=&projects=drupal&status[... finds issues in both Drupal, Drupal.org webmasters, etc.

The AJAX update when switching projects on an issue form takes a LONG time to update the component list.

Comments

webernet’s picture

-Edit a comment on an issue, preview/save -- "You must enter a project to navigate to."

webernet’s picture

- Version 'x.y.z' (core) is available again.

hunmonk’s picture

http://d6.drupal.org/project/issues/subscribe-mail hangs forever.

we don't plan of fixing this in the short term, as it's an existing issue w/ the size of the form or PHP memory. we need to redesign the subscription process. so for now, we should just hide the links to that page or something.

dww’s picture

Assigned: Unassigned » dww

1st, thanks for testing and reporting your findings.

A) I'm seeing autocomplete on all those pages -- is this still a problem?

B) anon is a known limitation in views that I said at #76725: Refactor project issue module to use Views and have been asking for someone else to work on. ;)

C) hunmonk already commented on the global issue subscribe woes.

D) the "projects" field there is a text search, not exact match for project names. I think that's a feature, not a bug. If you want to limit to an exact project, you use the project-specific adv search http://d6.drupal.org/project/issues/search/drupal which you get to either from the "Search issues" link on project nodes, by clicking "Advanced search" at the top of regular per-project issue pages, or by clicking on any "Drupal" links in the project column on the page you posted.

E) AJAX update is only slow due to the general performance problems of the tiny VM that this staging site is running on. Changing projects is a fairly rare operation anyway. Plus, the text field massively speeds page loads: #201435: Huge list of projects hard to use, consumes excessive d.o. bandwidth, can hang browser

Lemme know what you think. Thanks!

webchick’s picture

A) I'm now seeing autocomplete too! Must've either gotten fixed since, or I was really tired. :D

B) seems like it'd be easy enough to fix in the theme, no?

C) Cool.

D) Hrm. :( While I know of that project-specific search URL, I'm not sure everyone else does. If that text box is truly meant to be a text search against project, then you should probably remove the autocomplete and add a description, because the autocomplete tricks me into thinking it's going to limit by that project (since everywhere else, it does).

E) Cool.

Thanks, dww!

dww’s picture

B) Perhaps, but I've been trying very hard to avoid site-specific theme tricks to make these views work perfectly. All we really need is an option in the views core username field handler that lets you select "Don't print if anonymous" (more or less). Earl wanted something a little more fancy but is generally open to the feature and will commit it once it exists, my hands have been full, and no one else has stepped up to help on this minor detail. Anyway, this is already known as #76725-43: Refactor project issue module to use Views (E), so if you're interested, meet me over there. ;)

D) Yeah, I know what you mean. I can see why it'd be confusing. I'm reluctant to add description help text, unless it's only 4 words or so. I could label that filter "Search project names" or something, though. Alternatively, I could easily make that filter only do exact match. But, since we have a powerful tool for folks to find what they're looking for, I'd rather make it available instead of hiding it. ;)

F) @webernet: sorry, missed your comment when I was writing my previous reply. Split your first one out to #367419: Editing issue follow-up comments broken so it'll be easier to track (there are already a few sub-points in there). I'll look at "x.y.z" from here -- should be an easy fix.

dww’s picture

Issue tags: +drupal.org upgrade

Oh, and we should generally be using the "drupal.org upgrade" tag for these issues -- thanks. ;)

gábor hojtsy’s picture

Title: [D6 d.o upgrade] Project issue regressions » Project issue regressions

Let's use the tag instead of title hacks.

dww’s picture

C) The global "subscribe-mail" page is disabled on the site now, and the links to subscribe only show up in the per-project views (either from per-project issue queues, or from project nodes. I think this is Good Enough(tm) until we have flag-based issue subscriptions.

F) "x.y.z" is gone again. As expected, it was just a configuration from d.o that wasn't copied over to the d6.d.o settings.php:

$conf['project_issue_invalid_releases'] = array(94702);

The only other thing in still in here (that isn't already to-be-solved in another issue) is the autocomplete for the project search text area (D above). Let's resolve that and we can close this.

dww’s picture

Status: Active » Fixed

D) is kind of a tricky thing that I believe is going to require writing another custom views filter for project*. So, I moved it to #368371: Fix "Project" exposed filters on issue queue views.

Therefore, everything reported here is either resolved, or has a more focused issue about it:

#367419: Editing issue follow-up comments broken
#368234: Add a textfield for the value to print for anonymous users in views_handler_field_user_name
#368371: Fix "Project" exposed filters on issue queue views

So, I'm marking this one fixed.

In general, separate issues per issue is preferable, since these multi-topic issues can get confusing. ;)

Status: Fixed » Closed (fixed)
Issue tags: -drupal.org upgrade

Automatically closed -- issue fixed for 2 weeks with no activity.