Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion loginUser

Received: by 10.42.158.4 with SMTP id f4mr13673658icx.4.1328690425137;
        Wed, 08 Feb 2012 00:40:25 -0800 (PST)
X-BeenThere: fotoliaapi@googlegroups.com
Received: by 10.50.89.35 with SMTP id bl3ls628576igb.2.gmail; Wed, 08 Feb 2012
 00:40:23 -0800 (PST)
Received: by 10.50.106.166 with SMTP id gv6mr8232162igb.0.1328690423398;
        Wed, 08 Feb 2012 00:40:23 -0800 (PST)
Received: by 10.50.111.98 with SMTP id ih2msigb;
        Wed, 8 Feb 2012 00:39:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.117.42 with SMTP id kb10mr4744287pbb.9.1328690387926; Wed,
 08 Feb 2012 00:39:47 -0800 (PST)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
 itsmezsa...@gmail.com designates internal as permitted sender)
 smtp.mail=itsmezsa...@gmail.com; dkim=pass
 header...@gmail.com
Received: by qt7g2000pbc.googlegroups.com with HTTP; Wed, 8 Feb 2012 00:39:47
 -0800 (PST)
Date: Wed, 8 Feb 2012 00:39:47 -0800 (PST)
In-Reply-To: <877gzx91us.fsf@gandalf.home.thebuble.org>
References: <91cdce78-4930-49f4-95a9-94b289a8d01e@q8g2000pbb.googlegroups.com> <877gzx91us.fsf@gandalf.home.thebuble.org>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0,gzip(gfe)
Message-ID: <e70d04b8-8992-4646-9f13-d973430bd9ad@qt7g2000pbc.googlegroups.com>
Subject: Re: loginUser
From: toby <itsmezsa...@gmail.com>
To: Fotolia API <fotoliaapi@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Sir Olivier,

I just found your library of codes which is fotolia-api.php and just
opted to use it, so I got no more problems anymore! :)

Thanks anyway in taking time to respond to my query.

On Feb 8, 4:16=A0pm, Olivier Sirven <oliv...@fotolia.com> wrote:
> On 2012-02-08 02:07:03, toby =A0wrote:
>
> > Why do I always get an invalid session id from loginUser when it
> > already returns a session id?
>
> are you using the REST API or the XML-RPC one? XML-RPC is deprecated and
> should not be used anymore. And it requires cookies support to be
> functional
>
> --