Michael,
You're actually right. Didn't think about strtolower fixing the camel
casing issue. Have a look at the last test case in EpiTwitterTest.php
for example usage. I'll get around to increasing documentation soon
(I hope).
On Nov 2, 10:18 pm, Michael Steuer <mste...@gmail.com> wrote:
> Hi Jaisen,
>
> Doesn't Nelu's use of strtolower take care of your camel case concern?
>
> I just posted a comment on your blog - it'd be great if you could publish a
> couple lines around usage of your lib with the new lists URL structure etc.
>
> Thanks so much,
>
> Michael.
>
> On 11/2/09 9:51 PM, "jmathai" <jmat...@gmail.com> wrote:
>
>
>
> > Nelu,
>
> > While that works, I suggest using the ID over the username since a
> > username with camel case will break the path regex. This should work
> > with the newest version of the library from Github.
>
> > I'm considering including an option to pass in the url as a string in
> > the 2.0 version of the library.
>
> > Jaisen
>
> > On Nov 2, 7:53 am, Nelu Lazar <cont...@nelulazar.com> wrote:
> >> Figured the answer for the issue above, for @jmathai's EPITwitter
> >> library, here is the call code that works:
>
> >> $twitterOAuthObj->{'get_'.(string)strtolower
> >> ($username).'ListsMemberships'}(array(...));
>
> >> - @NeluLazar
>
> >> On Nov 2, 10:37 am, Nelu Lazar <cont...@nelulazar.com> wrote:
>
> >>> I am experiencing "Incorrect signature" responses while requesting any
> >>> Lists API XMLs.
>
> >>> <hash>
> >>> <request>/tweetvisor/lists/subscriptions.xml</request>
> >>> <error>Incorrect signature</error>
> >>> </hash>
>
> >>> I tried various methods, with no success: POST, GET, HTTPS (default),
> >>> HTTP. It only happens to Lists API calls, all other released API calls
> >>> are working fine.
>
> >>> If anyone know what's going on, please advise. Thanks,
>
> >>> - @NeluLazar
