Tonight I have my forum updated to 2.6.1 Build 1603.

Thread index simply can not build up. Many forums are for me to zero, although contributions and themes are available.

This issue we had:
Topics Notifications can not rebuild.

@ Dandello

In my forum you've got admin rights. Check this out please themselves.

Be careful, the backup is still on 2.6.0
For the topic structure that is still okay.
But not in the notifications. The still functioned without problems in 2.6.0

Here's a fix to be tested.
In Admin/Maintenance.pm find

    if ($save_moved) { save_moved_file(); } 

Add after

## New forum.totals rebuild ##
     my @newtots = ();
     my @myline1 = ();
     while( ($key, $value) = each %board ) {
         $ftotals = 0;
         fopen ( TOTALS, "<$boardsdir/$key.txt" );
         my @ftotals = <TOTALS>;
         fclose(TOTALS);
         chomp @ftotals;
         $ftotals = @ftotals;
         if ( !$ftotals ) {
             $msgtot = 0;
             $myline1[4] = 'N/A';
             $myline1[0] = q{};
             $myline1[5] = q{};
             $myline1[7]= q{};
             $mesg[0] = q{};
             $messby = 'N/A';
             $msgts = 0;
         }
         else {
             @myline1 = split /[|]/xsm, $ftotals[0];
             $msgtot = 0;
             $msgts = $myline1[8];
             for (@ftotals) {
                 @totalsvars = split /[|]/xsm, $_;
                 $msgtot += $totalsvars[5] + 1;
             }
             fopen ( TOTALSN, "<$datadir/$myline1[0].txt" );
             my @ftotalsn = <TOTALSN>;
             fclose(TOTALSN);
             @mesg =  split /[|]/xsm, $ftotalsn[-1];
             $messby = $myline1[6];
             if ( $messby eq 'Guest') {
                 $messby = $myline1[2];
             }
         }
         push @newtots, qq~$key|$ftotals|$msgtot|$myline1[4]|$messby|$myline1[0]|$myline1[5]|$mesg[0]|$myline1[7]|$msgts\n~;
     }
     fopen ( NTOTALS, ">$boardsdir/forum.totals" );
     print {NTOTALS} @newtots;
     fclose(NTOTALS); 

This will rebuild forum.totals from the rebuilt Message Index during Rebuild Message Index. It's been tested on a small data set and hopefully won't have problems on a big one.

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

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.

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.

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.

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 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.

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).