Whenever I hit submit, I get some server error message. It happens when using Explorer and Chrome.

It still posts my message, though.

I'm getting sometimes too.

Figured you were all just tired of me.

Yes.

Y2.013k bug...

Ditto. Glad to know I am not alone. Well maybe I am but ... what were we talking about?

Same, but it still works.

I let Mark know.... Hopefully the problem doesn't persist or it's easily diagnosed & repaired.

It's the Mayan end, ie E Moore. Open and drops the pass every time.

lol . . . and i thought it was just a way to annoy the new members that are Skins fans . . .

Yes. Same issue here.

Never happens to me. My posts get priority delivery.

I am getting it too.

All day long! thought it was just me.

Once I submit this, it will gimme server error.

I was going to mention this but I thought it was just my phone acting up. Lol

white screen after post- but works.

Yes

Yep

Automatic built in feature. It only does it if your posts are deemed to be moronic.







Yes, i'm getting it with every post.

Same. I'm on Safari, and everytime I hit 'submit' it gives me a blank screen.

Not sure who your admin is, but your getting a 500 (internal server) error. It looks like a function that runs after the post (probably related to clicking the submit button) is erroring on a "no post mode specified". Probably a NULL value being passed into the function. My 2 cents.

Happening with multiple browsers to me...handy that it's kept me from double posting though.

Still happening at 2:00 AM Pacific time.

Joey13091 wrote:I was going to mention this but I thought it was just my phone acting up. Lol

Same

I'm just getting a blinding white screen. Still posts though. Just started today.

travlinhawk wrote:white screen after post- but works.

Same for me

dunceface wrote:

Joey13091 wrote:I was going to mention this but I thought it was just my phone acting up. Lol

Same

Thrice.

Redskin hacker probably hacked the site.

Test it now

Interesting to work on code from Mexico, via a secure connection to my PC at work in Oregon so I have tools that I need at my disposal... SLOW!

Test

Looks like it is working fine. Thanks, Neal!

Shock2k wrote:Not sure who your admin is, but your getting a 500 (internal server) error. It looks like a function that runs after the post (probably related to clicking the submit button) is erroring on a "no post mode specified". Probably a NULL value being passed into the function. My 2 cents.

Close, but you're in the right area...

Actually, the air:fuel ratio under medium throttle is too rich causing torque values to be negatively affected, and RPM increase rate to suffer. They need to go ahead and add about 4 degrees of base timing, re-jet the primaries two steps down, and increase plug gap by about .005. Might look at coil energy and charge voltage under high fuel pump draw to insure a minimum of 13.8 volts to the ignition system. I wouldn't change the final drive gear ratio until we are seeing signs of a lean mixture at the plugs. Torque converter stall might be a few hunded RPM low also.

Oh, and turn off that damn bass amp during runs.

HoustonHawk82 wrote:

Shock2k wrote:Not sure who your admin is, but your getting a 500 (internal server) error. It looks like a function that runs after the post (probably related to clicking the submit button) is erroring on a "no post mode specified". Probably a NULL value being passed into the function. My 2 cents.

Close, but you're in the right area...

Actually, the air:fuel ratio under medium throttle is too rich causing torque values to be negatively affected, and RPM increase rate to suffer. They need to go ahead and add about 4 degrees of base timing, re-jet the primaries two steps down, and increase plug gap by about .005. Might look at coil energy and charge voltage under high fuel pump draw to insure a minimum of 13.8 volts to the ignition system. I wouldn't change the final drive gear ratio until we are seeing signs of a lean mixture at the plugs. Torque converter stall might be a few hunded RPM low also.

Oh, and turn off that damn bass amp during runs.

The god-damnit on the framastan gasket was actually incorrectly defined.

Anguish wrote:The god-damnit on the framastan gasket was actually incorrectly defined.

Looks like you jimmied a thing and got it working again. Well done!

Seahawk Sailor wrote:

Anguish wrote:The god-damnit on the framastan gasket was actually incorrectly defined.

Looks like you jimmied a thing and got it working again. Well done!

Well, truth be told; he broke it on purpose just so he could look like the hero when fixing it. It's an illness.

Either way, thanks as always Pendejo.

RockHawk wrote:

Seahawk Sailor wrote:

Anguish wrote:The god-damnit on the framastan gasket was actually incorrectly defined.

Looks like you jimmied a thing and got it working again. Well done!

Well, truth be told; he broke it on purpose just so he could look like the hero when fixing it. It's an illness.

Either way, thanks as always Pendejo.

Sort of a .NET related Munchausen by proxy syndrome?

Aaaaand....

Fixed.

It is a .php problem and seems to have subsided.