Extension talk:GoogleSiteSearch

Archives

/Archive 1

Discussion

Discuss Extension:GoogleSiteSearch here:

Previous page history was archived for backup purposes at Extension talk:GoogleSiteSearch/LQT Archive 1 on 2015-07-10.

Hello,

I'm using MediaWiki v1.26, is there any way to have the Google search results display below the MediaWiki search results?

Technically it could be done, but is not feasible because the results would not be reliable because there are times when the SpecialSearchResultsAppend hook does not run, while SpecialSearchResultsPrepend is always guaranteed to run before the MediaWiki results. See Manual:Hooks/SpecialSearchResultsAppend for details.

Hi! I just sent a patch-for-review that adds the option to display the Google search results below the MediaWiki search results. I understand that sometimes this may cause the Google search results to not show, but this can always be documented next to the relevant config option and the choice left to the user. Please check it out! PS, if there's no reply, I may request ownership of the repo to merge this and other improvements, cheers!

Fixed in version 3.0+

Installed your extension, and searching for terms in the Google search form work fine. However, my wiki is in Spanish and if I place a term with accents in the wiki search form (in the toolbar or Special:Search), it runs into trouble. This appears to pass coded accents to Google (i.e. "currículum" instead of "currículum"), and then Google returns no results for the search. Thanks for your help.

This post was posted by Vitruvian95, but signed as Felipe95a.

My wiki in Czech language has the same problem. The solution is replacing htmlentities with htmlspecialchars in

GoogleSiteSearch.php:
$outhtml = str_replace( '_GSS_TERM_ESCAPE_', htmlentities( $term, ENT_QUOTES, $wgGoogleSiteSearchCharset ), $outhtml );

Thanks! That worked for the accents. However, the extension still has trouble interpreting the inverted commas in exact searches (e.g. "currículum nacional"). Any suggestions are appreciated.

This post was posted by Vitruvian95, but signed as Felipe95a.

The latest release (3.0) should have i18n/UTF-8 issues sorted out. For an example, see e.g.

From https://programmablesearchengine.google.com/controlpanel/

How to make search results open in same window?

The way the search results display is controlled from https://programmablesearchengine.google.com/controlpanel/

No, since the search is relying on public search indexing.

My company uses a private wiki (not listed on google). I'd love this exntension because our wiki search is really bad because it is case sensitive, etc. Could I use GoogleSiteSearch our private wiki? Or would you recommend another extension for this purpose?

Hi, this would only work for a public wiki, as it relies on Google's indexing. You would be better off installing CirrusSearch.

Yes, it is.

My wiki is intranet only. Current;y running on my desktop until someone frees up a server for me. Is the CSEID an absolute requirement? I'm going to install anyway but just in case I get stuck I'd like to know.

Nevermind! "The ID of the created Google custom search engine. Required." That's crazy.

Yes, it'll still work. You can still create CSEs through https://cse.google.com/ and use the CSE IDs.

Does this extension still work now that Google has retired the CSE API?

https://productforums.google.com/forum/#!topic/customsearch/HQisP6ckZbg

Yes, it'll still work. You can still create CSEs through https://cse.google.com/ and use the CSE IDs. The GoogleSiteSearch extension just embeds a Google iframe-type setup for that CSE, which is still supported normally.

getLang() was deprecated in favor getLanguage(). This is fixed in the latest extension version.

With the latest master branches of MW and this extension, I'm receiving a Fatal error:

Fatal error: Call to undefined method SpecialSearch::getLang() in extensions/GoogleSiteSearch/GoogleSiteSearch.php on line 81

Did something get deprecated?

It seems getLang() is deprecated and getLanguage() should be used.

Version 3.0 added this as the default. In previous versions this can be accomplished by editing a line in GoogleSiteSearch.content.default.html from customSearchControl.setLinkTarget(google.search.Search.FILTERED_CSE_RESULTSET); to customSearchControl.setLinkTarget(google.search.Search.LINK_TARGET_SELF);.

Thank you for the extension. I wanted to know if it is possible to have search results open in same winodow/tab when clicked. As of now it opens in a new window/tab instead of just taking user to the page. Is this something that can be implemented?

Wikimanz (talk) 06:27, 29 March 2014 (UTC)

I'd be interested in this too.

Anyone have any ideas?

OK, I've managed to solve it.

Edit the GoogleSiteSearch.content.default.html

Change the line: customSearchControl.setLinkTarget(google.search.Search.FILTERED_CSE_RESULTSET);

To: customSearchControl.setLinkTarget(google.search.Search.LINK_TARGET_SELF);

The latest release (3.0) changed the CSE API used, and now defaults to same window/tab.

GoogleSiteSearch can work with the Sphinx search engine.

Hi

I currently use the Sphinx Search on my wiki and was wondering if GoogleSiteSearch can work with Sphinx? Love the concept of this seach extension. Thanks

I'll reply to my self. This extension works great with the Sphinx search.

Not sure if this is the right place, but wanted to say thank you for an amazing extension! This has totally transformed my site :)