Closed (fixed)
Project:
Drupal Commons
Version:
7.x-3.x-dev
Component:
Theme
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
27 Aug 2013 at 22:03 UTC
Updated:
13 Sep 2013 at 22:51 UTC
Jump to comment: Most recent file
Before searching:

After searching:

| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 2075523-solrusercheck-9.patch | 3.74 KB | japerry |
| #5 | issue-2075523-solr-user-formatting.patch | 910 bytes | Zarabadoo |
Comments
Comment #1
ezra-g commentedThis may be related to http://drupalcode.org/project/commons_origins.git/commit/c0f861c80980a9a....
Comment #2
ezra-g commentedIt looks like the results, when filtered, are being served with a different view mode.
Comment #3
japerrygrr, after hacking on this for a bit, putting the template back in doesn't show results in the original format. Need to extend the grid view into whatever display mode the search results are returning.
Comment #4
Zarabadoo commentedLooking at this makes me think Ezra's theory about the view mode is correct. Even if a template was missing, it should only be putting out the fields declared in the view mode. For some reason it is getting the entire profile.
Comment #5
Zarabadoo commentedThere was a typo in commons_search commit 044ec32380b404628c8c6d33f62a82d96e600c64. I have it committed and ready to push as soon as maintenance is finished. For now, the attached patch should also work.
Comment #6
japerryLooks good. Took a while to see that typo!
Comment #7
ezra-g commentedOn the people page, I'm seeing:
Comment #8
japerryHmm this is a different problem.
its within this function of commons_search_Solr_user, and I don't think related.
foreach ($build['#account']->og_user_node[LANGUAGE_NONE] AS $og_node) {
$gnode = node_load($og_node['target_id']);
$groups['group-item group-' . $gnode->nid] = array(
'title' => $gnode->title,
'href' => 'node/' . $gnode->nid,
'attributes' => array(
'class' => array('group-link'),
),
);
}
Comment #9
japerryThis patch adds some conditionals around edge cases where the search index might not be totally in sync with the site. While some content might look odd if its data is deleted, at least it shouldn't throw notices anymore.
Comment #10
japerryI've been able to eliminate a few notices and errors caused with this commit and I can't find any other issues in testing. Marking as fixed, although who knows what other edge cases people will find. I think either way this is a step in the right direction. :-)
http://drupalcode.org/project/commons.git/commit/6dd7b6f
Comment #11
ezra-g commentedThanks, japerry! Marking as fixed.