Checking mods lead to one more change:
in Menu.lng, in the %img_txt hash add

'no_text' => q~no text - ~, 

(just add it above the ); at the end of that hash.

This is a placeholder for items that should be in the tabtext.txt file but might not be. So this bit of lets you know that the text is missing and what action it's supposed to be related to.

That should work. Or you can use \~. But there's also no reason you can't go ahead and use q{Item ~ here.}  Just keep in mind that YaBB uses {} for marking things to be replaced so you want to be careful using curly brackets.

If you look in Perl coding books, most people use q{ } or q/ / or ' ' as their uninterpolated string brackets. ( qq{ } and " " indicate interpolated strings inside. ) YaBB uses so many curly brackets for other things that YaBB has gone with ~~ for the string brackets - but you can choose what bracket works best for what you're doing.

Dandello wrote on Nov 2^nd, 2016 at 3:47pm:


I thought so, but I did not know.

Will test it this afternoon and finish up tomorrow morning German_Du.

I'll get it into the SVN as soon as I've finished checking the files in the German_Land zip. One big problem - 2.7.00 is UTF-8 only. I have some errands to run this morning but I should be done with the checks today.

One thing I've noticed: if a string is quoted as q~ STRING 'HERE'~ you don't need to use \' on the quote marks (because those aren't the markers for the begining and end of the string). However, you do have to use \~ if ~ is inside the quote.

Edited:

The login with admin password issue fix:
In Error.lng find

'default_password'    => qq~You are still using the YaBB Setup default password. Please login to your <a href="$scripturl?action=myprofile;username=$username">User profile</a> and change your password to something more secure.~, 

make it

'default_password'    => qq~You are still using the YaBB Setup default password. Please login to your <a href="$scripturl?action=myprofile;username=$username;sid=$mysid">User profile</a> and change your password to something more secure.~, 

In Admin.pm find

            fatal_error('default_password'); 

add before:

            our $mysid = cloak( reverse substr $date, 5, 5 ); 

This is one of the reasons Alpha and Beta testers are so valuable. I never checked that link since I automatically go directly to Edit Profile before trying to login to the Admin Center.

I'll check this as soon as I've had my morning's coffee. However, I suspect I'll need a copy of the German Pack you're working on. The one I'm using for testing is the 2.6 version with the blanks filled in from English.

The Error.lng problem may actually indicate a YaBB error so serious that the error reporting section couldn't even load the Error.lng file. The other indicator for that is if 'Other.template' can't load.

Edited:

I had badly circumscribed this. When you go to the admincenter for the first time, you are prompted to change your password to make it safer. Now it works. On the next bug, which I have yet to find.

Dandello wrote on Nov 1^st, 2016 at 1:48pm:

I thought so. no problem


Can not make password more secure.

An Error Has Occurred. Use of uninitialized value $cur_sid in addition (+) at Sources/Profile.pm line 191.