Problem/Motivation
I have frequently wanted to see a node "through Solr's eyes", in order to troubleshoot unexpected search results.
Proposed resolution
Extending the devel tab on node pages seems like a natural way to achieve this. This tab can help a developer quickly answer questions like:
- What text is included in
content? - What does
tags_h4_h5_h6contain? - Which text fields are included in the index?
- What's solr's name for my date field?
Remaining tasks
Patch needs review
User interface changes
An extra tab is added to the devel button on node pages.
API changes
N/A

| Comment | File | Size | Author |
|---|---|---|---|
| #13 | devel_interface-1518108-13.patch | 1.7 KB | killua99 |
| #11 | devel_interface-1518108-10.patch | 3.39 KB | killua99 |
| #10 | devel_interface-1518108-10.patch | 3.41 KB | killua99 |
| #8 | devel_interface-1518108-8.patch | 1.71 KB | killua99 |
| #5 | Nostrud Premo Tincidunt | Smartphone compare.jpg | 74 KB | nick_vh |
Comments
Comment #1
pwolanin commentedgood idea, though this doesn't seem to handle correctly the case of multiple documents created from one node?
Comment #2
grendzy commentedI'm not sure how to test it, but I think each document would show as a separate krumo tree on the same page since they are appended in the for loop. What would be the best way to display multiple documents?
There's also the question of non-node entities. There's probably no way to offer buttons for all entities, though I did just notice there's a user/N/devel.
Comment #3
pwolanin commentedoh, I see:
But the page callback is returning a string instead of a render array?
Comment #4
pwolanin commentedupdated patch?
Comment #5
nick_vhI tried with multiple documents and it looks fine. marking as RTBC. I really dig this one!
Comment #6
nick_vhcommitted to 7.x-1.x and credited you for this! thanks a dozen!
Comment #7
killua99 commentedLooking great! this patch ... I'm gonna try this backporting because I'm right know under i+d with solr, so this is great for me also.
Comment #8
killua99 commentedI test it in my site, and I don't see any "weird" data or behavior. The back-porting wasn't hard at all.
I just notice one think in apachesolr.index.inc
Comment #9
nick_vhbad coding standards, please remove obsolete spaces :-)
Thanks
Comment #10
killua99 commentedOk just learning ...
Comment #11
killua99 commentedComment #12
nick_vhlooks like you have the same patch twice in one file?
Comment #13
killua99 commentedKinda weird yes ... it's look like, But my local file is just one patch ... o.O not twice the same code :/ try it again ...
Comment #14
nick_vhcommitted. Thanks!
Comment #15
nick_vh