allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #7278 Admin search page for projects
Date Mon, 18 Aug 2014 20:51:17 GMT
- **status**: code-review --> in-progress
- **assigned_to**: Igor Bondarenko
- **QA**: Dave Brondsema
- **Comment**:

Layout issue, see attached.

If mongo & solr aren't in sync, can get error:

    File '/home/dbrondsema/dbrondsema-1019/forge/Allura/allura/controllers/',
line 303 in search_projects
      p['project'] = mongo_projects[_id]
    KeyError: '536d00a8d8be354ed703137b'

I even tried re-running Allura/allura/scripts/ but that didn't seem to
help.  Maybe we need a separate ticket to make reindex_projects clear out old entries?  What
do you think?  (In other scenarios I've used a last-indexed field in each doc and then delete
all old docs where the last-indexed value is older than the start time of the script).

On the result links, the main project link is incorrectly going to `http://localhost/p/testit/`
for me instead of using the correct domain.

Should partial matches on full name work?  I would like them to.  I have a project named "Test
it..." and a search for "test" isn't matching.  This might be an issue with the solr config/version
I'm using though?

When EasyWidgets isn't so easy (often!) feel free to not use it.  We have some forms that
don't use it and I think that is fine if it makes things actually easier.  Off the top of
my head perhaps the project import forms are like that.


** [tickets:#7278] Admin search page for projects**

**Status:** in-progress
**Milestone:** forge-backlog
**Labels:** 42cc 
**Created:** Thu Mar 20, 2014 09:22 PM UTC by Dave Brondsema
**Last Updated:** Tue Aug 05, 2014 09:04 AM UTC
**Owner:** Igor Bondarenko

Using the indexing set up in [#7257], provide a site admin page to search for projects and
list the results.  Provide options for which field to search by.  Must include at least project
shortname, project full name, and custom fields that are indexed (i.e. sfx group_id for SourceForge
- could be specified in .ini file).  Simple text box and selector for field should be fine
I think.  Form should be a simple GET so that URL can be easily modified (browser custom searches

Then list the results, including easy pagination.  List columns should include shortname w/
link to project, full name, date registered, deleted flag, and any custom fields.

We'll do something similar for users later, so keep that in mind, developing generic re-usable
functions and templates if appropriate.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message