Extension talk:Woogle4MediaWiki/archive

Is anybody out there running this extension and could publish the URL? For me woogle (native) even fails with a blank mediawiki installation - it only works in parts.

Ike


 * I'm running it as an experiment. Started with Native now Remote.  After I enabled API access to the wikis (which was my first problem!), there was only one real issue which was that all searches were postfixed with "&ref=mw" which caused all searches to fail.  I fixed this by changing WoogleSpecialDummysearch.php from:

// redirect to Woogle (either "Special:Woogle/$search" or "Woogle:$search") if ($wgUsePathInfo === false) { // if we have index.php?title=... mode $wgOut->redirect(WoogleUtil::getWoogleLinkPrefix . $search . '&ref=mw' . $togo); } else { $wgOut->redirect(WoogleUtil::getWoogleLinkPrefix . $search . '?ref=mw' . $togo); }


 * to

// redirect to Woogle (either "Special:Woogle/$search" or "Woogle:$search") if ($wgUsePathInfo === false) { // if we have index.php?title=... mode $wgOut->redirect(WoogleUtil::getWoogleLinkPrefix . $search . $togo); } else { $wgOut->redirect(WoogleUtil::getWoogleLinkPrefix . $search . $togo); }


 * The other issue was that one of the wikis I was indexing wasn't configured to use the nice URLs (index.php/My_Page_Title). Setting the linkPath in repo_config.xml to be "http://myserver/index.php?title=" didn't work as it insisted on putting a slash in front of the titles, so I ended up with "http://myserver/index.php?title=/My_Page_Title" .  This was fixed by updating my Wiki configuration.


 * My only remaining issue is that with some browsers, if you select "go" rather than "search", the search is postfixed with "&go=go". This is probably the $togo in the above code.


 * Jbattersby 12:16, 7 July 2010 (UTC)