Full text search on subdomain takes me back to readthedocs.org

[rufuspollock]

Make be related to #62 (Site URLs should be configurable) but is somewhat different AFAICT (apologies if I've missed any other similar issues -- I have searched issues before submitting).

• I'm on a CNAME'd subdomain: http://docs.ckan.org/en/latest/index.html (FWIW this also happens if you start on a subdomain e.g. http://ckan.readthedocs.org/en/latest/index.html)
• Go to full text search in sidebar and search
• End up at: http://readthedocs.org/search/project/?q=theme&selected_facets=project%3Ackan
  • All links on that page to results go to http://readthedocs.org/docs/{project-name}/...

This leads to inconsistent urls for the project (one just wants people to use urls at e.g. docs.ckan.org) and can be rather confusing to users. I'm not sure how easy to fix this is (I imagine it requires us to start setting explicit config for project as to authoritative base url so this can be used in link generation and search url).

[ericholscher]

Well, the main problem is that the CNAMEs and Subdomains have a different URL config, so there is no way to access search from it. the best way I can think of is to implement the search page as an API client, and return the search from the API. This would take a decent bit of work, but there isn't really another way I can see this working.

[rufuspollock]

Understood. I guess a lesser item is that once back on the main RTD site all links don't point to the CNAME site but to RTD -- perhaps that is fixable.

Re search page as an API client I note there is this simple jquery plugin that acts as a frontend to SOLR or ES (disclaimer: I've contributed to this): http://okfnlabs.org/facetview/

[ericholscher]

Going to close this for now. Keeping track of the canonical CNAME for a project is fraught with problems. I guess we could add a field to the project to keep track of this, but I don't think it's really worth it in the end. I like the ability of allowing arbitrary CNAMEs, and linking to non-RTD domains from the site will eventually break plans to move everything to SSL, since I can't serve SSL on non-RTD domains.