12 messages in com.googlegroups.bloggerdevRe: [bloggerDev] Re: Ngeblog-0.0.2| From | Sent On | Attachments |
|---|---|---|
| Eris Ristemena | 22 Oct 2006 06:01 | |
| Bill Lazar | 22 Oct 2006 18:32 | |
| Eris Ristemena | 23 Oct 2006 05:31 | |
| Bill Lazar | 23 Oct 2006 10:38 | |
| Ryan Cullen | 23 Oct 2006 10:50 | |
| Bill Lazar | 23 Oct 2006 10:59 | |
| Pete Hopkins ☠ | 23 Oct 2006 14:15 | |
| Bill Lazar | 23 Oct 2006 14:54 | |
| Pete Hopkins ☠ | 23 Oct 2006 15:05 | |
| Bill Lazar | 23 Oct 2006 15:41 | |
| Eris Ristemena | 23 Oct 2006 23:40 | |
| Pete Hopkins ☠ | 24 Oct 2006 09:33 |
| Subject: | Re: [bloggerDev] Re: Ngeblog-0.0.2![]() |
|---|---|
| From: | Ryan Cullen (ryan...@gmail.com) |
| Date: | 10/23/2006 10:50:59 AM |
| List: | com.googlegroups.bloggerdev |
Blogger issue, see http://groups-beta.google.com/group/bloggerDev/browse_thread/thread/6fb0e165dbb3b330/88b91e1b908c4911#88b91e1b908c4911
On 10/23/06, Ryan Cullen <ryan...@artesea.co.uk> wrote:
Blogger issue, see
http://groups-beta.google.com/group/bloggerDev/browse_thread/thread/6fb0e165dbb3b330/88b91e1b908c4911#88b91e1b908c4911
On 10/23/06, Bill Lazar <b....@billsaysthis.com> wrote:
This is with existing content, so far I am only using ngeblog for the getPost method. Using 0.0.3 does not seem to change the situation. As I mentioned, this may be a Blogger issue, since my blog is not using the new beta (can't yet since it is not hosted on Blog*Spot and I have a Pro account).
You can see this at http://billsaysthis.com/misc/ngeblog-tester.php .
Thanks, Bill
On Oct 23, 2006, at 5:31 AM, Eris Ristemena wrote:
Bill, have you tried with newest version 0.0.3? http://blog.ngoprek.web.id/2006/10/23/ngeblog-003/
i suspect that's because i used the wrong format in newPost(), (text/html), apparently Blogger only accept xhtml type. Anyway, did you use Ngeblog when post the content? or Blogger web interface?
Anyway, Neblog-0.0.3 now supports multiple blogs too. Please try it out, and as always any comments are welcome
regards -ers
On 10/23/06, Bill Lazar < b....@billsaysthis.com> wrote: Eris,
Thanks for doing this! I've implemented it and am seeing different results when calling the getPost function with different post IDs. I'm replying to the group because I think the problem might be with the Blogger server side rather than your code.
My blog ID is 2791351. Post ID 114697881232022733 gets back an empty string but post ID 114825135697207954 gives back the text of my blog post in the content element.
Calling http://www.blogger.com/feeds/2791351/posts/full/ 114697881232022733 in my browser (Eris I realize you won't be able to do this since you can't log in as me) gives the expected XML formatted response. Calling http://www.blogger.com/feeds/2791351/ posts/full/114825135697207954 returns a normal string (Firefox shows it as a text rather than XML).
I see the same pattern when looking at other entries. Ones which DO NOT work properly show up in the browser as XML files (i.e., Firefox says "This XML file does not appear to have any style information associated with it. The document tree is shown below." across the top of the window) and the entries which do work show as a normal string, with no XML warning.
Eris, your code does NOT return false from the getPost call in either result. At least not using these lines of PHP:
$myblog = new Ngeblog($username, $password); $ent = $myblog->getPost($idx); if(!$ent) { return "error message" }
Help from you or the Blogger Google folks would be much appreciated.
My implementation can be seen in action at http://billsaysthis.com/ content/entertain/bookreviews.php. To see the working example click the title Learning the World (should be first entry in the list) and for one which does not work click the title The Omega Expedition (4th item).
Bill
On Oct 22, 2006, at 6:02 AM, Eris Ristemena wrote:
I have made some improvements to class Ngeblog, now you can update an entry from your Blogger using GData.
For more info please browse this class in PHPClasses .
thanks, -ers
-- Ryan Cullen
w: blog.artesea.co.uk e: ryan...@artesea.co.uk
-- Ryan Cullen
w: blog.artesea.co.uk e: ryan...@artesea.co.uk




