Geeklog Forums

I'm running Geeklog on two sites, and I'm admin on both of them. All is working well, but I just realized that I'm unable to post a comment on either one of them.

I type the post, hit 'preview,' get to the next page and hit 'submit' - and it kicks me back to the home page without recording my comment.

Any ideas what could be causing this? I'm stumped.

-Don

Version of GL?

If 1.3.10 I think maybe that was the version where if your story ID was to long it would not record the comments.

1.3.9, both sites.

The really weird thing is, there are comments already on the thread. I wanted to reply to the comments and couldn't.

-D

Can other users post comments? Also a URL to a site experiencing this problem might help a bit. Also, you mysql or phpMyAdmin to check to see if the comments are making into the database.

-Vinny

Yes, others can post comments.

the sites are here and here.

-D

Wow, I think the problem might be the title of your article...

http://web.takebackthemedia.com/geeklog/public_html/article.php?story=20050606035651824

I'm not sure which character(s) its chocking on, but I click on the "Reply To This" link it has a fit, but when I change the title I get the standard "Must be logged in" message.

Is that story (or stories with & ' # or ,) the only ones where you see the problem?

-Vinny

Interesting. I hadn't even thought of it, but most of the time, I change the title before I reply. On the message where I was getting kicked, I left it be.

Good eye, Vinny. I'll try changing the title, and I'll get back to you. Thanks!

Vinny, you're a genius.

I tried replying to a post that contained an ellipsis in the title - kicked me back to the home page.

I tried replying to a post without any special punctuation. It got right through.

Does that qualify as a bug? Anyone else ever have this problem?

-D

This is definitely a bug, please submit a bug and someone (probably me) will get around to fixing it (definitely by the next release).

-Vinny

Submitted. Thanks for th help.

-D

For the record, found out that this was already fixed (by me, I think) in 1.3.10, so current Geeklog installs shouldn't have this problem...

-Vinny