Thanks for your help. I don’t really have any regex experience but maybe this is a good chance to learn more!

Would you mind looking at my issue a bit more if I PM’d you some information?

Sure thing Jon, I’ll have a look if you like.

Hey D-Rock,
This is a great plugin and I love the idea… however, I am having some issues with the paging, inparticularly when I jump from the first page of results straight to the last… the number of total results seems to totally adjust and the paging its self gets out of sync.

This only started occuring when I used the Google CSE parameter.

Any ideas?

Cheers
Gary

Gary — I’ve noticed this behavior as well, and unfortunately it’s just how the API works. It seems that they don’t give an accurate result count until you fetch the final page of results.

Thanks D-Rock,
What I dont understand is why this only occurs when I use the CSE parameter… if I leave that out the paging never breaks.

I have done a bit more digging and I think I have fixed the problem… Google filters out some results (usually duplicates), so when you hit the last results page it would all of a sudden decide to reduce the number of results (filter) hence the change in “results found” and the paging messing up…  I am now using the filter=0 parameter and it seems to be working fine…

Hi Derek,

Just installed and tried this plugin and it works great, thanks!

Are you still planning on doing an EE2 version of this? Would love to use this for both EE1 and EE2 and get it as part of my standard builds for both.

Thanks.

HI Derek,

I love the plugin. The only part that’s giving me trouble is when you hit the search button with the field empty, it seems to go to the results page but kicks out to an EE error message (one of the specialty templates).

Is there a way to keep the user on the results page with the {no_results} feedback instead?

Hi Derek,

This is almost working but having problems with the pagination…

Can anyone suggest what I need to do to get the paging to work properly. The links to subsequent pages append q and p paremeters to the query string but due to how I have the URL set up this gives me an ‘Invalid URI’ error. The resulting URL looks something like this:

http://www.myurl.co.uk/ee/index.php?/search/search_results/?q=paper&p=2

I’ve tried adding the ‘remove_query_indicator’ parameter in the form but that doesn’t do anything to help this issue. Any ideas?

Sorry for the delay here all, once again I did not get these notifications.

The only part that’s giving me trouble is when you hit the search button with the field empty, it seems to go to the results page but kicks out to an EE error message (one of the specialty templates). Is there a way to keep the user on the results page with the {no_results} feedback instead?

I hesitate to change this, as it’s not really that they’re getting “no results” ... they’re submitting an empty form, so no results aren’t even possible, hence the error screen.  I’ll think about this though.

Can anyone suggest what I need to do to get the paging to work properly. The links to subsequent pages append q and p paremeters to the query string but due to how I have the URL set up this gives me an ‘Invalid URI’ error.

Does manually changing the URL to something like http://www.myurl.co.uk/ee/index.php?/search/search_results/&q%

OK, manually changing the URL creates 2 issue:

I get a php notice at the top of the page -

Notice: Undefined index: HTTP_REFERER in /homepages/23/d7268723468/htdocs/ee/system/plugins/pi.google_search_results.php on line 94

Secondly if I try to load, say, page 3 by changing the p variable in the querystring to 3, the amount of results gets recalculated to something much smaller. So instead of 64 results, I now only have 34 - weird and random!

Any ideas?