I'm almost certain this is an error in my configuration, but I'll be darned if I can find it.
I've imported all those entries from my b2evo disaster. I've checked them to make sure that "Allow comments to this entry" is checked in the Edit Entries window. When I click a comment link in the blog, it displays the comment form. When I submit the comment, it tells me "Your comment could not be added, because comments for this entry have been disabled." If I'm still logged in, though, the "(Do not allow comments to this entry)" link is available.
I've tried using that link, and the "(Allow comments to this entry)" link that comes up afterwards. I've reconfigured the spam plugin. I've verified that the author has "allow comments to this entry" enabled. I'm out of ideas. How do I allow users to leave comments?
Can't enable comments. User head space error?
-
Guest
Re: Can't enable comments. User head space error?
You might be using the spamblock plugin - this reports this error message if you entered invalid comments (like duplicate comments). Check your plugin configuration of the spamblock plugin and see which options you have enabled there!
Best regards,
Garvin
Best regards,
Garvin
Thanks for all the help.
I thought the Spam Protector plugin might be the problem, so I modified its configuration: no help. In fact, I eventually deleted it without any effect on the problem.
I took a screenshot of the weird convergence of error messages.
http://judebert.com/wasted_youth/photos ... mment1.gif
That's after I deleted the Spam Protector. Could it be a problem with the b2evo import? I'm gonna go check my database manually...
Edited to provide proper URL
I thought the Spam Protector plugin might be the problem, so I modified its configuration: no help. In fact, I eventually deleted it without any effect on the problem.
I took a screenshot of the weird convergence of error messages.
http://judebert.com/wasted_youth/photos ... mment1.gif
That's after I deleted the Spam Protector. Could it be a problem with the b2evo import? I'm gonna go check my database manually...
Edited to provide proper URL
Last edited by judebert on Mon Oct 17, 2005 10:29 pm, edited 1 time in total.
Well, that was an experience. I tried removing all the old config, including the spamblocking and user permisssions (it helps to know a little SQL); no difference. I deleted *all* users except me; still couldn't post a comment. But wait, here's the entry table itself; it claims Judebert as author of all entries, but authorid id is 22?!?
I reset all the author IDs to 1, rechecked my entry permissions, and sure enough, commenting worked.
Perhaps we should define one of those columns as unique. In fact, I think I'm going to make my authorid, username, and email columns unique.
Then I'm going to go reinstall that spam plugin.
Edited to remove the results of my bungling
I reset all the author IDs to 1, rechecked my entry permissions, and sure enough, commenting worked.
Perhaps we should define one of those columns as unique. In fact, I think I'm going to make my authorid, username, and email columns unique.
Then I'm going to go reinstall that spam plugin.
Edited to remove the results of my bungling
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Hm, this all seems to be caused by a whacky b2 evo import, where the entries of the authors were assigned to the wrong users, apparently...hrm.
Regards,
Garvin
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Yup. I had imported multiple times while trying to get it to run all the way to completion. It had imported the users (same username, same password, same email) multiple times. The entries were all marked as written by a user ("Judebert") with a userID of 22. It was having trouble choosing which of the Judeberts had written the article. When I cleaned up the users, it farked up the entries; then I saw the entries had *no* author.
Cleaning up the database tables, so only one author remained, and all entries were written by him, fixed everything.
Cleaning up the database tables, so only one author remained, and all entries were written by him, fixed everything.