DuckDuckGo Search Suggestions

theme-component

(Michael Howell) #1

Solves Is there a way to suggest DuckDuckGo instead of Google for failed search UI?.

A Discourse theme component to use DuckDuckGo as the suggested search system, instead of Google!

p.s. You’ll probably want to customize some of the text strings to stop mentioning Google, too.


Is there a way to suggest DuckDuckGo instead of Google for failed search UI?
(Wolftune) #5

Here’s what I’ve noted to be the places to alter the text:

  • js.search.or_search_google
  • js.search.search_google
  • js.search.search_google_button
  • page_not_found.search_google
    • is that search also adjusted to DDG in the theme? If not, that should be fixed too
  • js.google_search
    • that looks like it’s editable to put in DDG directly, not sure how that’s related

Is that it?


(Michael Howell) #6

Okay, I’m writing this down, because 404 handling in Discourse is weird. Try this link on for size:

https://meta.discourse.org/nonexistant-page

If you open it in a new tab, you’ll notice that your user menu (the one in the upper-right of the page) doesn’t render. In fact, the Discourse Ember app doesn’t get loaded at all in this case. It’s being rendered by the Rails server following app/views/exceptions/not_found.html.erb

Obviously, if you click the link directly in this page, the Ember app remains resident. Try hitting the link with a .json at the end, and instead of sending the app a full 404 page, it sends an HTML fragment, with the heading and stuff removed, which the Ember app just plops into place.


(Wolftune) #7

Oh weird. But if that’s less trivial to fix, at least it can be documented and the easier parts all fixed. Thanks for working on this!


(Michael Howell) #8

Added a commit to do the form rewriting to make the 404 page work, both within and without the Ember app.


(Wolftune) #9

Great! So the only remaining thing is to document (probably both here and at the repo README) the confirmed list of text items theme-users will need to customize in the admin UI?


(Wolftune) #10

I got this working, but it’s a little strange to have the page-not-found version start with the form using site:xxx… with no search term alongside that. Maybe that’s as good as it gets, but it would be ideal if it were feasible to get the text of the URL after the TLD for the not-found page and use that as the default search before the site: part…