Geeklog Forums

Have the blog plugin installed and configured but the 3rd party software doesn't work. I'm using w.bloggar (which is on the list of working clients) and have it set up for my host (themerediths.org) and path (/blog/). It connects, and sees my category titles. I type a new post and click "publish" and it says:


If I tell it to view the latest entry, it says:
even though there is an entry.

You can see for yourself what the XML output is if you naviate to http://themerediths.org/blog/

If I use Drivel (for Linux) and try to connect to the same RPC, it tells me:

However, if I point Drivel to http://themerediths.org/blog/index.php, it is able to sign on and read my most recents posts (albeit, only the html source). But when I try to post a new entry, it says:


All this is making me wonder if the plugin is having a difficulty with the data it is getting. Any hepl would be much appreciated. Thanks!

Do any of those clients log the actual communication between them and the server? That would be helpful.

The blog plugin itself also has a debug option. To enable it, change the value for "blog.debug" in the gl_vars table in your database to 1 (from 0). Communication with the client is then logged in error.log.

See if any of those provide any insight (and if not, post them here). Looks like the plugin is mostly working, probably only a small detail somewhere ...

bye, Dirk

None of the clients have dubugging options (other than the Drivel console output I pasted above). I enabled the plugin debugging. It outputs successful processes such as retrieveing the most recent entry (which has mysteriously started working in w.bloggar). But when I attempt to post a new story, it gives that "Unable to parse the XML response..." message, but nothing shows up in the error.log.

I'd like to hear your thoughts. I'm trying to find another client that has a debug option. Let me know if you have any suggestions. Thanks!

Sounds like something is throwing an error (HTML formatted, probably) when you try to post a story. Now we only need to find out what that message is ...

I'm not too familiar with Blogger clients for Windows, but ecto (for MacOS X) has a nice debug console. I've registered an account with your site (dhaun). So if you would allow me to post through the blog plugin there (see the plugin's options), I'd give it a try.

bye, Dirk

I've added you to the blog users group. I think that oughta do it. Thanks for your help!

There we go:
My fault. The blog plugin is not compatible with 1.3.11sr2 yet - I forgot about that little change regarding the kses filter ...

In the plugin's index.php, find the line that reads: and change it to read Then, a few lines below that, change the two occurences of to read
That should fix it.

bye, Dirk

That fixed it! Thanks!

Allow me to say... this is great software. Thanks again for this!

I don't have the plugin and had to add that info the lib-common.php on line 3310 in order to edit stories...

---

Shane | www.EyeCraveDVD.com

Then your Geeklog install is messed up.

The name of the kses class changed in kses 0.2.2 which we're shipping with Geeklog 1.3.11sr2 The plugin was trying to use the old name, hence the above problems.

Geeklog itself should not have these problems, unless you forgot to update a few files ...

bye, Dirk