Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

»Comment Submission Error« #32

Open
daxim opened this Issue · 12 comments

9 participants

@daxim

See screenshot http://www2.pic-upload.de/11.12.09/gg7ag4614xk5.png.

No matter what I do, I can't preview or submit a commit. The error message is »Your comment submission failed for the following reasons: Invalid request«, which is rubbish because it does not tell me what exactly it thinks is invalid.

@davorg
Owner

This appears to be working fine for many people. Can you give us a bit more information so we can try to recreate your issue - which OS and browser are you using (and which versions).

And if you could give us a couple of timestamps for your failures, we can investigate the error log.

@daxim

This is Opera 10.10 on openSUSE 11.2/KDE 4.3.4. Timestamp: 2009-12-14 15:11:00+0100

  1. Navigate to http://blogs.perl.org/users/dave_cross/2009/12/what-can-we-improve.html.
  2. Fill in »Name« daxim, »Email Address« daxim@cpan.org, leave »URL« empty, leave »Remember personal info?« unchecked, fill in »Comments« test test does it work now?
  3. Push button »Preview«.

Expected:
Text preview.

Actual:
See description & screenshot above.

@mpeters

Same thing happens to me on Firefox 3.5.6 on Linux (Fedora 10). Several times this morning including today at 11:11am (EST). Happens when I try to submit a comment or register for the site. I've cleared all my blogs.perl.org cookies in case that was causing a problem and it didn't seem to help.

@yanick

Ubuntu, Firefox 3.5, 2010-02-25, 8:00am EST

the comment appears in the preview, but refuses to submit, giving the infamous "text entered was wrong" message

@parv

With or without supplying name & email address, I could not comment anonymously on http://blogs.perl.org/users/ovid/2010/05/threaded-forums-made-easy.html.

I got the error as noted above, on May 13 2010, 1325 UTC, on CentOS 5 with Firefox 3.5.3.

@cdh

This error is still happening with FF 3.5 on Windows when trying to post comment without signing in.

@yanick

Still happen for me with FF4.0. Tried to change my name, email, url, just to see, but alas no dice.

Funnily enough, logged in, and this time I get a "Can't call method "remove" on an undefined value ". I don't know if that's a second issue or a different symptom of the same problem.

@barbie

Just happened to me, Ubuntu 10.04 FF3.6.17. Posted roughly at 2011/05/06 08:00:00 to acme's post (http://blogs.perl.org/users/acme/2011/05/how-cpan-testers-helped-me-improve-my-module.html). I can preview the comment, but cannot submit it.

Comment text was "Excellent, you've saved me having to think of something to say :) acme++". Tried with and without

tags around it. Makes no difference still the same error as Daxim. :(

@davorg
Owner

Sorry about this. I'm trying to find someone who knows more about MT than I do to investigate.

@StommePoes

Okay, at Ovid's suggestion I'll add to this one (there are a lot of submission bugs, but so far only this one is exactly mine).

Firefox on Ubuntu 10 (have NoScript plugin which I thought first might have been the issue). Went to comment with name/url and got the "text entered was wrong". Logged into my blogs.perl account and could post fine, though got some error upon logging out (but going to another page did show I was truly logged out, so ignored error).

The not being able to comment is bad enough, but I was actually more irked by the incredibly horrible error text. "Text entered was wrong" tells nobody anything. Not the users, not the devs. : )

@doomvox

I had this exactly problem, and to solve it I had to tell NoScript to "allow perl.org", at which point it made it clear I needed to "sign in". The system is doing a really bad job of degrading for folks who don't run js indiscriminantly. It acts like it's going to let you post, and then responds with a cryptic error message. Why not kick you to a log-in screen, if that's what the problem really is?

@davorg
Owner

@doomvox

Ah. That's very interesting. I'll see if I can get someone to investigate that solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.