Open GoogleCodeExporter opened 9 years ago
Thanks. We have recognized that problem allready, but not yet had the time to
take care of that.
I'll post an update on that tomorrow. Cheers.
Original comment by eyecatchup@gmail.com
on 20 Jun 2011 at 1:49
Any updates to this?
Original comment by mmei...@gmail.com
on 29 Jun 2011 at 11:19
Hi,
Seeing same problem.
That makes the work useless, that's a pitty.
Any other way to get PageRank ?
Thanks
Original comment by pally...@gmail.com
on 2 Jul 2011 at 8:04
I found a fix / solution that affects all methods using googleArray() - which
doesn't apply to PageRank, this is another issue: See Issue 19.
Originally, the method googleArray() uses a "custom" search query which allows
the retrival of 100 results at once - as opposed to the normal search results
which contain only 10 per page. BUT this custom query is banned more or less
quickly, while the normal result pages are not. (you might call that last
sentence a "theory based on observation".)
So let's change this:
$url = 'http://www.google.'. GOOGLE_TLD .'/custom?q='.$query.'&filter=0'.
'&num=100'.(($start == 0) ? '' : '&start='.$start.'00');
to this:
$url = 'http://www.google.'. GOOGLE_TLD
.'/search?q='.$query.'&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:de:official&client
=firefox-a'.
''.(($start == 0) ? '' : '&start='.$start.'0');
or at least implement a switch (config option) to enable the second version as
a backup or "safe mode".
BTW: Don't just change these lines and expect it to work immediately. There are
other changes neccessary like increasing the number of $pages further up and
replace a "div" by a "li" further down in the same method.
I would really appreciate a way to submit my changes to the code (like GitHub).
Original comment by lwswerb...@gmail.com
on 3 Jul 2011 at 10:56
@#4: Thanks for sharing your thoughts on that and at all: sorry for the lack of
updates.
First of: The new Pagerank Checksum API URL is working again. Apart from
returning the correct checksums again, i also corrected the content-type to
application/json, rather than before returning the response as text/html. Also,
you can now use an optional second query parameter, named 'jsonp', for use with
callback functions and i added a third key to the json array, containing the
final toolbar URL:
http://pagerank.bexton.net/?url=http://www.google.de&jsonp=test
For the googleArray method, i meanwhile found a (so far) great working
replacement. As nowadays Google is doing *A LOT* of stuff on the client-site,
filtering your socket dumps once a day, for a few weeks, by a) hostname(s) and
b) content-type (in the transaction's response headers), then digging through,
and decoding thousands of lines of javascripts, then you will get a quite good
inside view. ;) Google is evil! ^^
So, coming to the last point - github: as the tv commercials campaign for the
project i'm currently working on will start in 10 days (as from today), this
will be the final deadline for a) me finishing that project and b) me, having
the time to setup github and also release an updated SEOstats version.
Thanks for your patience and kind regards!
Original comment by eyecatchup@gmail.com
on 7 Jul 2011 at 8:52
Original comment by eyecatchup@gmail.com
on 7 Jul 2011 at 8:53
Sorry again for being late again, but my work is just too messy at the moment.
But finally i had a few minutes to set up Git and move the repo. So, here you
go: https://bexton.net/2011/08/03/seostats-finally-moved-to-github/
Thanks again, best regards and really looking forward to a great collaboration!
:)
Original comment by eyecatchup@gmail.com
on 3 Aug 2011 at 4:14
Issue 26 has been merged into this issue.
Original comment by eyecatchup@gmail.com
on 12 Oct 2011 at 8:04
Original issue reported on code.google.com by
arpad.le...@gmail.com
on 18 Jun 2011 at 5:55