Sorry for bumping this but I really need to know if there’s a way to fix this… Anyone?
Hello,
I’m happy to help. A couple things I’d like to know:
1. Is there a URL that illustrates the problem?
2. Have you tried disabling other plugins to see if the problem persists?
Thanks,
Dan
Hi! Sure, I can give you some URLs where you can see it in action. I do use the plugin on 3 different websites. For all of them it does the same thing. Here are the URLs:
http://es-factory.nl/blog/api/get_posts/?p=9540
http://bmwblog.ro/api/get_posts/?p=73792
http://www.nakko.com/api/get_posts/?p=2052
I don’t actually have access to the plugins these websites use, but they are completely independent blogs, so it would have been so much of a coincidence that all 3 of them have a plugin that messes things up
Cheers,
Mickey
Ah, yeah I think the ?p=123 argument triggers a built-in redirection from WordPress. I should look into disabling that, but in the meantime here are some workarounds:
http://es-factory.nl/blog/api/get_posts/?id=9540&count=1
http://bmwblog.ro/api/get_posts/?id=73792&count=1
http://www.nakko.com/api/get_posts/?id=2052&count=1
Not sure if my last reply will make it through the spam filters, but try converting the p argument to id and adding one extra one: count=1.
Ha! 🙂 Not sure how I’ve missed that 😀 But that seems to do the trick! 😀
Thanks!
Actually… This doesn’t work… If I do that the API returns the latest article only :-s
Here’s an example:
http://es-factory.nl/blog/api/get_posts/?id=4110&count=1
And to proove that the article exits:
http://es-factory.nl/blog/api/get_posts/?p=4110
Ah, I figured it out! The id thing was a mistake, I think it was just ignoring that and giving you back the most recent post.
I found a way to avoid the redirect when the p argument is present. Should be fixed in the next release.
whatever happened with this one? any updates? I’m unable to get any info from my “posts page”
