Closed (fixed)
Project:
Apache Solr Search
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 May 2009 at 23:59 UTC
Updated:
11 May 2010 at 20:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
mikejoconnor commentedComment #2
mikejoconnor commentedComment #3
pwolanin commentedSure, or perhaps we should leave the trailing '/' off the base path?
Comment #4
mikejoconnor commentedThat's how I approached it the first time. I ran into an issue but I don't recall what it was. I'll see if I can find it again.
Comment #5
pwolanin commentedyou could possibly use rtrim($path, '/') when it's set, or for this function.
Comment #6
pwolanin commentedComment #7
mikejoconnor commentedUnfortunately the patch in #6 will not work. If $basepath is empty, and your call back is your front page you end up with http://example.com//?filters=tid%3A522
Comment #8
pwolanin commentedstill an issue?
Comment #9
JacobSingh commentedI'm not sure how to replicate this exactly.
Mike, can you post more detail or close this out?
Thanks,
j
Comment #10
jpmckinney commentedThe only way to achieve '//' is to pass a base_path with a trailing slash ("search/apachesolr_search/") or to pass an empty base_path. I've committed a PHPDoc update to note that base_path should not have a trailing slash. I prefer to force developers to follow an API, than to have a permissive API that does all sorts of clean-up (in this case, trimming trailing slashes). As for an empty base_path, you should just set <front> to "search/apachesolr_search" to achieve the same result. http://drupal.org/cvs?commit=360074
Finally, I don't see how this has anything to do with having no keywords. Nothing is ever appended to the result of Solr_Base_Query::get_path, so the trailing slash in the absence of keywords is not a problem.