Issues using Google Co-Op search results in a snippet...

I’m having trouble creating a snippet to contain the search results that come from my Google Co-Op custom search engine.

The problem is that google uses the "?q=Search+Term" varable and it seems that MODx uses the same variable to find pages.

Is there a way around this? I’m not too keen on modifying the MODx core just to make this work, but I can’t seem to figure out a way to pass this variable into a snippet without totally confusing MODx.

Has anyone had this same problem? I couldn’t find anything on it in the forums.

Any input would be appreciated.

Ok, I found a workaround hack.

I changed the file document.parser.class.inc.php

Line 258:
Original:

Changed to:


And I changed the .htaccess file:

Line 45:

Changed to:


I did this so I could use my Google Custom Search Results Snippet.

If anyone’s interested in the Snippet, or has any suggestions on something better to do, please let me know.

If your google snippet uses [tt]?g=Search+Request[/tt] and MODx uses [tt]?q=alias/path[/tt] then why did you have to change it

q is not g...

Quote from: sirlancelot at May 04, 2007, 04:30 PM

q is not g...

Gee, you think?

Thanks for the heads up... I fixed the post. I hope it makes sense now. Let me know if you are still confused.

hehe that makes more sense I thought it would be that ’cause google uses the ’q’ for all queries and so does MODx...

You don’t need to hack the core code, use the furls, see: http://wiki.modxcms.com/index.php/Friendly_URLs_Guide#SEO_.28Google.29_Friendly_URLs

doze, when furls are turned on, MODx uses the ’q’ parameter (look at [tt].htaccess[/tt]), and so does zgambino’s snippet (which apparently can’t be changed).

Yes.. but I didn’t mean that he would use .htaccess.. I meant that he would do what I linked to. Doing that, he can change the q to be what ever he wants. Or did I not understand something..?

I have the same problem as zgambino.
I did what he suggested but I had to change ’q’ to ’alias’ in 4 places in the file ’document.parser.class.inc.php’ to get it working (doing search/replace).

@doze
I don’t see what in the instructions for friendly URLs would solve the problem we have. The only parameter that come close is ’Prefix for friendly URLs:’ put it doesn’t apply. In my case I use alias and alias path.

The use of the parameter ’q’ is hard coded in ’document.parser.class.inc.php’ and does collide with the parameter for the query string in Google Search.

lionel

When furls are on, the entire string (URL) is sent to MODx via the ’q’ parameter regardless of any MODx setting.

For instance, if I have: [tt]http://www.example.com/sub/page.html[/tt] furls are on as well as friendly alias path. Apache will rewrite the url to this: [tt]http://www.example.com/index.php?q=sub/page.html[/tt] and MODx would process it.

if the alias prefix were ’[tt]index.php?page=[/tt]’ and suffix was blank, with "Use friendly aliases" turned off, and you had a request like this: [tt]http://www.example.com/index.php?page=432[/tt], Apache would rewrite the url to this: [tt]http://www.example.com/index.php?q=index.php?alias=432[/tt] and MODx would process it.

Apache doesn’t know MODx’s prefix and suffix.