Oh yes, of such horror stories I can sing a song.

The gene pool needs more chlorine... 

I think we all have horror stories about users - I have one who couldn't understand why her Android smartphone didn't automatically have her board password and login cookies off her Mac. And one who wanted me to log her into the forum on her computer when she's on the other end of the country (and on a Mac).

It now has left me no peace. Some presenters with me are just too stupid to edit a post properly. I think it is once again a round shock due.

The poster edited the quoted item. And since the UBBC code appears as code in the textbox, they didn't notice they'd put formatting in the wrong place. They also didn't look at their message in Preview.

I figure we could build a check to make sure that messages don't throw errors before being saved. Or remind people to preview their messages before posting.
Preview threw an absolute hissy fit when I copied that message string into a posting box.

Thank you, now I see it. I just wonder how such a thing comes to conditions.
I'll look at that in more detail tomorrow morning. I'm too tired for that.

Found it -

date=1371145474]Remainder  

The quote tag wasn't properly closed - probably because the person doing the quoting added or removed other formatting. Close the quote tag, removed the extra color tag, and the message should render.

The problem isn't with DateTime - the problem is in the message itself: 

date=1371145474[color=#0000ff]Remainder 

The problem is inside a quote. The inner color tag doesn't have a close and is being sent to DateTime as part of the time string.  (Line 6 in 1370176935.txt)  I'm trying to figure out exactly how to fix the problem. You may have to hand edit the line.

Yes, I'll find out. I have a very different problem namely this:

Nicht abgefangene Fehler :
 The 'epoch' parameter ("1371145474[color=#0000ff") to DateTime::from_epoch did not pass regex check at Modules/Params/ValidatePP.pm line 630	Params::Validate::__ANON__('The \'epoch\' parameter ("1371145474[color=#0000ff") to DateT...') called at Modules/Params/ValidatePP.pm line 554 Params::Validate::_validate_one_param('1371145474[color=#0000ff', 'HASH(0x19f0938)', 'HASH(0x12f29c8)', 'The \'epoch\' parameter ("1371145474[color=#0000ff")') called at Modules/Params/ValidatePP.pm line 353	Params::Validate::validate('ARRAY(0x1739cc0)', 'HASH(0x18b6970)') called at Modules/DateTime.pm line 517	DateTime::from_epoch(undef, 'epoch', '1371145474[color=#0000ff') called at Sources/DateTime.pm line 54 main::toffs('1371145474[color=#0000ff', 0) called at Sources/DateTime.pm line 177 main::timeformat('1371145474[color=#0000ff', 0, 0, 0, 1) called at Sources/YaBBC.pm line 131 main::quotemsg('6F666E626D707666030', '1370176935/3#3', '1371145474[color=#0000ff', 'Remainder\x{a}[url=http://anti-scam...') called at Sources/YaBBC.pm line 393	main:oUBBC() called at Sources/Display.pm line 1347	main:isplay() called at YaBB.pl line 226	main::yymain() called at YaBB.pl line 171	eval {...} called at YaBB.pl line 171


 http://anti-scam.de/cgi-bin/yabb2/YaBB.pl?board=Afrika_White_Females&action=&num...1370176935 

The selected thread exists but is not accessible by the mentioned error message. From CPAN (Dave Rolsky) I just get stupid answers. We really should consider whether we need it at all. It was previously without this feature.

I can not open the selected contribution, although it is there. I just get this stupid error message and Google gets this too. It is as if the post did not exist.

The whole DateTime and DateTime::TimeZone would be totally revised. The time I do not take me and go back to local.

Some engines are more sensitive to javascript conflicts that others (although IE is usually the most finicky). 

Upppps. You are right. Even with IE it works. Opera seems to have problems since. I will later time to test a different browser with Google engine. What I find funny though, I'm using the Opera in your forum, as does the spell check.
I think this is a mod trouble (we had the spoiler too).
This is only to find out once my part.
The picture says it out some.


I was able to change my password without problems. Since I will probably be able to do anything.

There's also a problem with changing passwords - I couldn't change mine. (Possibly because of the way the account was set up. You may have to change it by hand editing the vars file.)

And as of Dec 2^nd, 2014 at 2:48pm Spell check works fine on FireFox on anti-scam.de.

No problem, you should only change your password.
But now I have another problem. spell check does not appear, though enabled. I think that makes a mod problems. Maybe I'll find it.

It will be in the next Build. And thanks for reporting it AND letting me dig into your data.

Perfect. Both worked. Please take into SVN, so it will not be forgotten.   

And for the Rebuild Notifications (I'm hoping since I can't test it.)
In Maintenance.pm find

    require Sources::Notify; 

Add above

	my (%members, $sumuser, $sumbo, $sumthr, $sumtotal, $start_time, $exitloop);
  

Find

        my %members = map {/(.*)\t(.*)/xsm} <MEMBNOTIF>; 

replace:

        %members = map {/(.*)\t(.*)/xsm} <MEMBNOTIF>; 

Find:

        my $start_time = <CALCNOTIF>;
         my $sumuser    = <CALCNOTIF>;
         my $sumbo      = <CALCNOTIF>;
         my $sumthr     = <CALCNOTIF>; 

replace

        $start_time = <CALCNOTIF>;
         $sumuser    = <CALCNOTIF>;
         $sumbo      = <CALCNOTIF>;
         $sumthr     = <CALCNOTIF>; 

Find

    my ( $exitloop ); 

replace:

#    my ( $exitloop ); 

I'm fairly certain the problem with Rebuild Notification was a localization issue.