raminpapo / seostats

Automatically exported from code.google.com/p/seostats
0 stars 0 forks source link

Seomoz_Authority and code contribution #16

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Which method(/function) produce a problem?
1.Seomoz_Authority

Does the method(/function) produce the problem for all given URL's?
(If not, what specific URL produces the problem?)
1. N/A

Please provide any additional information below:

We are totally in love with your PHP classes. We might want to add minor stuff. 
For example, for SEOMOZ, we will want to grab "External Followed Links" so we 
will add the "ueid" field.  

We've noticed that there isn't anything in place to submit new code. In case 
you change your mind, we'd be glad to contribute.

Bye

Original issue reported on code.google.com by i...@sylvainrocheleau.com on 3 Jun 2011 at 8:20

GoogleCodeExporter commented 9 years ago
Thank you. Code improvement is always welcome. :) I think i will provide an 
opportunity to contribute code as soon as i'll have some free time what should 
be by the end of next week. (I was thinking about switching to github anyway). 

Well, but for the moment the moment, there's no other way than sending me code 
via email, posting code directly here in place, posting it to the "feature 
request section" on my blog ( http://bexton.net/php-class-seostats/), or 
throwing your code into a pastebin and share that link using the prior listed 
methods.

Original comment by eyecatchup@gmail.com on 7 Jun 2011 at 11:28

GoogleCodeExporter commented 9 years ago
OK, fine with us. We'll wait for github.

I noticed that you've added <pre> tags to format to JSON. There's probably a 
good reason to do that, but it generates errors when we tried to parse it. So 
we've commented those lines out.

Bye

Original comment by i...@sylvainrocheleau.com on 8 Jun 2011 at 8:30

GoogleCodeExporter commented 9 years ago
Thanks again. The next version will use the PEAR's JSON.php file to encode the 
results, so there shouldn't be any issues with that with the next release.

I'll keep you up to date.

Cheers.

Original comment by eyecatchup@gmail.com on 10 Jun 2011 at 4:35

GoogleCodeExporter commented 9 years ago
Thanks.

Meanwhile we observed something strange: Facebook and Twitter mentions, that 
you get from Google, are no longer returning any values. I thought it might 
have something to do with our server but I tried it on your demo and I got this 
message with Facebook mentions Please read: 
http://www.google.com/support/websearch/bin/answer.py?&answer=86640&hl=en.

This message is regarding "Unusual traffic from your computer network ". I see 
two ways around this. First we use proxies (don't like the idea too much) or we 
tried to get these info from other API such as the Graph API from facebook.

Le t me know your thoughts on this.

Cheers

Original comment by i...@sylvainrocheleau.com on 16 Jun 2011 at 1:05

GoogleCodeExporter commented 9 years ago
Hi,

just to let you know (as i said i will set up github the last weekend).. i was 
just to busy - and still am. (well, so far - at least - i managed to register 
an account at github ;)) Bottom line: i don't think i can set everything up 
before the next 10 days. sorry for that delay.

Regarding the error message..

This is quite interesting. As you may have recognized, all data from Google is 
being fetched from the same URI, what is

http://www.google.'. GOOGLE_TLD .'/custom?'. PARAMS .'q='.$query

All public methods, using the googleTotal method, are still returning results 
as they did before. But when it comes to the googleArray method, there seems to 
be a problem. And not only with the FB and Twitter, but also with the Siteindex 
and Backlink-Array methods. Moreover it is not a problem with the method 
googleArray, but seems to occur, when the results array is too big, or 
correctly - and that's the whole point: The requests are getting fired to fast.

I just did a quick test on my local machine. Using the featured 2.0.7 version, 
produces the same results, like on the demo server. But when increasing the 
delay time for the loop, it is working again.

If you like to send me your Email (i can only see i...@sylvain...com) i can 
send you a quick fix. But i will verify that and kkep you up to date.

That's it for the moment.. And thanks again for your contribution! :)

Original comment by eyecatchup@gmail.com on 16 Jun 2011 at 9:15

GoogleCodeExporter commented 9 years ago
Thanks for the quick reply.  Always interested by quick fixes:-) Don't 
worry for the github, since what you've developped is modular, we might 
add support for Facebook Graph API and later for Google Mentions. We're 
taking a break early july and then we're full time on our project till 
october.

Bye

Original comment by i...@sylvainrocheleau.com on 16 Jun 2011 at 9:21

GoogleCodeExporter commented 9 years ago
Closing that issue, as the initial issue was fixed and meanwhile there's 
another ongioing thread on that issue, what was specifically opened for the 
googleArray issue.

See: http://code.google.com/p/seostats/issues/detail?id=18

--FIXED / DUPLICATED--

Original comment by eyecatchup@gmail.com on 7 Jul 2011 at 9:08

GoogleCodeExporter commented 9 years ago
We decided to use the JSON method named googleTotal2() in order to retrieve 
information about the number of  Twitter or Facebook mentions. We don't use the 
googleArrayMethod.
We still have the problem with Facebook and Twitter Mentions : it happens 
randomly that the function doesn't return any values. I think we find the 
source of the problem. It seems Google blocks our IP address because we use 
automated requests.

We will try with Bing methods posted by another person recently and keep you up 
to date with our problem with Google.

Bye,

Original comment by floren...@gmail.com on 22 Jul 2011 at 2:40

GoogleCodeExporter commented 9 years ago
@florent: the reason is, google made changes to the custom search. i used that 
because you're able to get up to 100 results per request (instead of 10 like 
with the standard web search). Anyway, as i wrote in another ticket, i've found 
a great walkaround. i will implement that asap - and now i've finished my last 
project and have some more free time again, you can be sure, that will be SOON. 
:)

Anyway, using the deprecated ajax api for the mentions requests is a good idea. 
Thanks! ;)

Original comment by eyecatchup@gmail.com on 4 Aug 2011 at 3:15