Saturday, August 30, 2014

Digest for adsense-api@googlegroups.com - 3 updates in 1 topic

Syne Oravivattanakul <choapet@gmail.com>: Aug 15 11:16AM -0700

We keep getting "404 Not Found - Account not found [location: accountId]"
error when trying to pull data from one Adsense account using the API call
adsense.accounts.get. Please see below for detail. The exact same API call
worked fine just 3 days ago on Aug 11, 2014. Interestingly, we are able to
pull data from other accounts associated with the same Adsense using the
same API call and the same credential. Note that the account id we pass as
a parameter does exist since we get the account id from
adsense.accounts.list method.
 
Any insights/suggestions are very much appreciated.
 
Request
=====
GET https://www.googleapis.com/adsense/v1.4/accounts/abc?key={YOUR_API_KEY}
 
Authorization: Bearer xyz
X-JavaScript-User-Agent: Google APIs Explorer
 
Response
======
404 Not Found
 
- Show headers -
 
{
"error": {
"errors": [
{
"domain": "global",
"reason": "notFound",
"message": "Account not found.",
"locationType": "parameter",
"location": "accountId"
}
],
"code": 404,
"message": "Account not found."
}
}
"Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com>: Aug 29 02:03AM -0700

Hi Syne,
 
Is it possible that the account is suspended? Can you log into AdSense with
it and check for messages?
 
Cheers,
Jose
 
On Friday, 15 August 2014 19:16:11 UTC+1, Syne Oravivattanakul wrote:
"Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com>: Aug 29 02:20AM -0700

Hi Syne,
 
The problem is being investigated, it has nothing to do with the account.
 
Cheers,
Jose
 
On Friday, 29 August 2014 10:03:58 UTC+1, Jose Alcérreca (AdSense API Team)
wrote:
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to adsense-api+unsubscribe@googlegroups.com.

Friday, August 29, 2014

[WD&D] Digest for sitedesign@googlegroups.com - 1 update in 1 topic

Artist <SitePro@gmail.com>: Aug 29 12:24AM -0700

Hi all!
 
I started a *Google Plus Community* for our little Web Design and
Development Group:
 
https://plus.google.com/u/0/communities/100994253918987699411
 
...wow, that's a crazy url.
 
 
This new community isn't intended to replace the group, but to augment it.
 
 
Our Google email/list group address for the *WD&D* Group remains:
 
http://groups.google.com/group/SiteDesign
<http://groups.google.com/group/SiteDesign?hl=en>
 
 
We are also on *Facebook*:
 
https://www.facebook.com/groups/wdadg/
 
 
And we have arrived at* LinkedIn*:
 
https://www.linkedin.com/groups?home=&gid=6684977
 
(I could've sworn there was a much easier-to-remember url for the group at
LinkedIn - oh well, that will hurt LinkedIn, not us)
 
 
I'm not very active with Twitter, but we do have a *Twitter account* as
well, so I would appreciate your following it if you haven't:
 
https://twitter.com/wdadg
 
 
And even though I promised to get the CMS up and running, it had so many
security issues that I have to update the software for the website yet
again. There is a home page up at:
 
http://www.wdadg.org/
 

If anyone can assure me that they have fixed the numerous security holes
that were designed into Pinterest, I might consider setting some sort of a
community presence there, but you have to convince Me, first.
 
If there is though, an important social network we should (or even just I)
should be a part of, please let Me know.
 
 
-Doug
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to sitedesign+unsubscribe@googlegroups.com.

Saturday, August 23, 2014

BEVERLY HILLS TOP PSYCHIC~ HONEST & AMUSING

Your first 3 minutes are FREE talking live with me.

Please visit my website at: http://www.keen.com/Ask+Fran

Or, call me right now at: 1-800-275-5336 x0160

--
You received this message because you are subscribed to the Google Groups "WhealtyCrib" group.
To unsubscribe from this group and stop receiving emails from it, send an email to whealtycrib+unsubscribe@googlegroups.com.
To post to this group, send email to whealtycrib@googlegroups.com.
Visit this group at http://groups.google.com/group/whealtycrib.
For more options, visit https://groups.google.com/d/optout.

Tuesday, August 19, 2014

[WD&D] Digest for sitedesign@googlegroups.com - 2 updates in 1 topic

we|rd0 <amirediwan@gmail.com>: Aug 17 08:00PM -0700

I have seen issue this for the first time in my life.
 
My mozilla is not picking up the css file.
 
After having copy pasted the below tutorial from the internet, this does
not work either. Could anyone tell me what is the bug in it?
 
*********************************************************
 
#wrapper- { width: 450px; margin: 0 auto; }
#header-,
#footer-,
#content-wrapper- { float: left; width: 440px; margin:5px; display: block;
clear: both; }
#sidebar-left-,
#sidebar-right- { float: left; width: 90px; height: 250px; }
#content- { float: left; width: 250px; height: 250px; }
 
**************************************************************
 
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Tutorial.aspx.cs"
Inherits="Tutorial" %>
 
<!DOCTYPE html>
 
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title> Tutorial </title>
<link rel="stylesheet" type="text/css" href="Tutorial.css">
</head>
<body>

<div id="wrapper-">
 
<div id="header-"> header </div>
 
<div id="content-wrapper-">
 
<div id="sidebar-left-"> sidebar left </div>
 
<div id="content-"> content </div>
 
<div id="sidebar-right-"> sidebar right </div>
 
</div>
 
<div id="footer-"> footer </div>
 
</div>

</body>
</html>
Artist <sitepro@gmail.com>: Aug 18 03:24AM -0500

For a time, every browser I used was having trouble loading external CSS.
I still run into this on occassion when I am low on memory, but after
upgrading my FireFox and Chrome a couple versions later, it went away (for
the most part) unless I was low on memory.
 
 
 
Doug Peters
(605) 331-0808 (605) 251-8973
http://www.Doug-Peters.com
https://www.facebook.com/symbioticdesign http://twitter.com/Domainating
<http://www.twitter.com/Domainating>
https://www.facebook.com/groups/wdadg/ http://www.wdadg.org/
http://www.W3DN.com http://www.DomainHostmaster.com
http://www.HDWebHosting.com
http://www.PremiumBrand.Name <http://www.premiumbrand.name/>
http://www.font-journal.com <http://www.fontjournal.com>
http://www.GlossaryIndex.com
http://www.faviconvert.com
<http://www.SymbioticDesign.com>
 
 
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to sitedesign+unsubscribe@googlegroups.com.

Saturday, August 9, 2014

Digest for seo-professionals@googlegroups.com - 1 update in 1 topic

Group: http://groups.google.com/group/seo-professionals/topics

    BR David <seodavid08@gmail.com> Aug 08 12:44PM -0700  

    Dear SEO Professional,
     
    Please don't do any SEO work these website. This client not paid my SEO fee
    around 660 USD. He is cheater webmaster. In below i have given all
    information.
     
    Webmaster Name : Thorsten Wittenbecher
    *Michel Deheer( Thorsten)*
    Website :http://ledlichtpanel.com/
    Website :http://liang-international.com/
    Skype: thw.nwa
    Skype: live:info_85169
     
    If any one doing SEO for these site then take all payment in advance.

     

Digest for adsense-api@googlegroups.com - 2 updates in 1 topic

Group: http://groups.google.com/group/adsense-api/topics

    alex@alexquick.com Aug 07 04:39PM -0700  

    Hi,
     
    I'm running into some authentication/authorization issues. What's
    interesting is that this is with a client that works with many other users,
    and this particular issue can be recreated in a homemade client, the Google
    API Python bindings, and manual HTTP requests. The issue is that a
    seemingly valid refresh_token ends up giving 401s when making requests to
    the AdSense API.
     
    Here's the flow--given a refresh token, we exchange it for an access token:
     
    $ curl -vv -XPOST https://accounts.google.com/o/oauth2/token \
    -d"client_id=869353560953.apps.googleusercontent.com" \
    -d"client_secret=snip" \
    -d"refresh_token=1/snip" \
    -d"grant_type=refresh_token"
    > Accept: */*
    > Content-Length: 173
    > Content-Type: application/x-www-form-urlencoded
     
    < HTTP/1.1 200 OK
    < Content-Type: application/json; charset=utf-8
    < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
    < Pragma: no-cache
    < Expires: Fri, 01 Jan 1990 00:00:00 GMT
    < Date: Thu, 07 Aug 2014 21:24:50 GMT
    < Content-Disposition: attachment; filename="json.txt";
    filename*=UTF-8''json.txt
    < X-Content-Type-Options: nosniff
    < X-Frame-Options: SAMEORIGIN
    < X-XSS-Protection: 1; mode=block
    < Server: GSE
    < Alternate-Protocol: 443:quic
    < Transfer-Encoding: chunked
    <
    {
    "access_token" : "ya29.snip",
    "token_type" : "Bearer",
    "expires_in" : 3600,
    "id_token" : "snip"
    }
     
     
     
    Then see if the token is valid:
    curl -vv
    "https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=ya29.snip"
    > User-Agent: curl/7.37.0
    > Host: www.googleapis.com
    > Accept: */*
     
    < HTTP/1.1 200 OK
    < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
    < Pragma: no-cache
    < Expires: Fri, 01 Jan 1990 00:00:00 GMT
    < Date: Thu, 07 Aug 2014 21:26:09 GMT
    < Content-Type: application/json; charset=UTF-8
    < X-Content-Type-Options: nosniff
    < X-Frame-Options: SAMEORIGIN
    < X-XSS-Protection: 1; mode=block
    < Server: GSE
    < Alternate-Protocol: 443:quic
    < Transfer-Encoding: chunked
    <
    {
    "issued_to": "869353560953.apps.googleusercontent.com",
    "audience": "869353560953.apps.googleusercontent.com",
    "user_id": "snip",
    "scope": "https://www.googleapis.com/auth/adsense.readonly
    https://www.googleapis.com/auth/userinfo.email
    https://www.googleapis.com/auth/plus.me",
    "expires_in": 3521,
    "email": "email@example.com",
    "verified_email": true,
    "access_type": "offline"
    }
     
     
     
    Then try to make a request with it that needs only the adsense.readonly
    scope:
     
     
    $ curl -vv
    "https://www.googleapis.com/adsense/v1.3/accounts?access_token=ya29.snip"
     
     
    > User-Agent: curl/7.37.0
    > Host: www.googleapis.com
    > Accept: */*
     
    < HTTP/1.1 401 Unauthorized
    < WWW-Authenticate: Bearer
    realm="https://accounts.google.com/AuthSubRequest", error=invalid_token
    < Content-Type: application/json; charset=UTF-8
    < Date: Thu, 07 Aug 2014 21:29:41 GMT
    < Expires: Thu, 07 Aug 2014 21:29:41 GMT
    < Cache-Control: private, max-age=0
    < X-Content-Type-Options: nosniff
    < X-Frame-Options: SAMEORIGIN
    < X-XSS-Protection: 1; mode=block
    < Server: GSE
    < Alternate-Protocol: 443:quic
    < Transfer-Encoding: chunked
    <
    {
    "error": {
    "errors": [
    {
    "domain": "global",
    "reason": "authError",
    "message": "Invalid Credentials",
    "locationType": "header",
    "location": "Authorization"
    }
    ],
    "code": 401,
    "message": "Invalid Credentials"
    }
    }
     
     
     
    The same is true when sending the token in the authentication header,
    (Authorization: Bearer ya29.snip).
     
    Renegotiating the refresh_token yields the same results. Changing the
    deprecated scope 'https://www.googleapis.com/auth/userinfo.email' to its
    replacement 'email' also doesn't change the behavior. I have a feeling
    there's something about the users's account that is nonstandard but don't
    see anything in the documentation about this.
     
    Has anyone seen something like this or have any ideas?

     

    "Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com> Aug 08 04:17AM -0700  

    Hey Alex,
     
    Everything looks good indeed. It could be a problem with the user. Are they
    able to access the AdSense web interface? If they can, please send me the
    username privately and we'll investigate.
     
    Cheers,
    Jose
     

     

Thursday, August 7, 2014

BEVERLY HILLS TOP PSYCHIC~ HONEST & AMUSING

Your first 3 minutes are FREE talking live with me.

Please visit my website at: http://www.keen.com/Ask+Fran

Or, call me right now at: 1-800-275-5336 x0160

--
You received this message because you are subscribed to the Google Groups "WhealtyCrib" group.
To unsubscribe from this group and stop receiving emails from it, send an email to whealtycrib+unsubscribe@googlegroups.com.
To post to this group, send email to whealtycrib@googlegroups.com.
Visit this group at http://groups.google.com/group/whealtycrib.
For more options, visit https://groups.google.com/d/optout.

Saturday, August 2, 2014

CPA NETWORK: instant aproval, content locker and incentive

Hi,  Content locking: It is a very effective way of making profits via CPA Networks.

As a publisher you'll be able to create multiple forms of content locking gateways by becoming a member of a incentivized CPA networks.

I would like to share with you for free my favourite CPA networks that allows incentive, has a content locker and instant approval:
- http://goo.gl/dcMJ2o
- http://goo.gl/utnnhy
- http://goo.gl/MM25So
- http://goo.gl/Zumvz8
- http://goo.gl/FTXLTI

Tracking: Voluum: The most technologically advanced tracking solution in the universe. Expand your affiliate marketing campaigns to the next level.: http://goo.gl/5k6JgY

--
You received this message because you are subscribed to the Google Groups "NAIJA INTERNET BILLIONAIRES....WE ARE THE BOMB!!!!" group.
To unsubscribe from this group and stop receiving emails from it, send an email to naija-internet-billionaires+unsubscribe@googlegroups.com.
To post to this group, send email to naija-internet-billionaires@googlegroups.com.
Visit this group at http://groups.google.com/group/naija-internet-billionaires.
For more options, visit https://groups.google.com/d/optout.