[nineteeneleven]

Er because they name is entirely special chars.... I'll see what I can do

[nineteeneleven]

you can put this after line 93 in the ipn.php untill i figure out a better way. What kinda of characters are those? i have no idea where to begin with that.

PHP Code:


if (empty($username)) {
    $username=$tools->randomPassword(6);
} 


[nineteeneleven]

never mind, there is not any real easy way (that i could find) to store all those different special charaters in the database. lol update to 2.0.3



changed files:
class_lib.php

ipn.php

index.php

donate.php

everything in /admin/pages

[StayOx]

Originally Posted by nineteeneleven never mind, there is not any real easy way (that i could find) to store all those different special charaters in the database. lol update to 2.0.3 changed files: class_lib.php ipn.php index.php donate.php everything in /admin/pages

are special caracters, if there is a way to set to UTF-8 I think I managed to solve the problem set UTF-8 to be able to make the translations.

http://www.w3schools.com/tags/ref_charactersets.asp
http://en.wikipedia.org/wiki/Character_encoding


just some suggestions

maybe it would be cool to set everything to support UTF-8 with that customizations and translations would be simpler?

Another issue is the time format that are different in each region.


EDIT:

Not solve the problem

PHP Code:

if (empty($username)) {
    $username=$tools->randomPassword(6);
} 


see the problem

[nineteeneleven]

2.0.3 will at least stop the errors and allow the script to put the user in sourcebans . I don't know much about handling special chars. But I will look into it. I am going to be busy this weekend though so it will be a few day.


Also I can't tell what ur trying to show me in the screenshot.

Edit: if you are trying to track the changes, use the github repo.

[StayOx]

Originally Posted by nineteeneleven 2.0.3 will at least stop the errors and allow the script to put the user in sourcebans . I don't know much about handling special chars. But I will look into it. I am going to be busy this weekend though so it will be a few day. Also I can't tell what ur trying to show me in the screenshot. Edit: if you are trying to track the changes, use the github repo.

ok. about the image is that the note of the User name does not appear on the confirmation screen when the name has special characters

[Dr_Knuckles]

Originally Posted by StayOx Your Admin user must have access to a group of type: "Server Admin Group" the same group that you defined in config.php > define('SB_ADMINS', 'Administrators'); In SourceBans go to: Admin Panel> Group Settings> Add to Group > Select group type: "Server Admin Group" > Enter with the name of Group "Administrators" and now choose the flags and immunity that your Donators will have access.

Im so stupid, thanks

[nineteeneleven]

2.0.4

MAKE SURE YOU RUN admin/install/database_utf8.php, this will update your database to use utf8 instead of latin or whatever.

added logging for server commands that were sent

fixed manual deletion not removeing from ccc database

full support for custom characters

made notification in admin panel hide on click.


This should be the last update for a while

[Dr_Knuckles]

Gonna go back old school.

+karma!!!

[StayOx]

Originally Posted by nineteeneleven 2.0.4 MAKE SURE YOU RUN admin/install/database_utf8.php, this will update your database to use utf8 instead of latin or whatever........

Nice Update, Thanks

Now it is only necessary update the "Collation" on file: install.sql and/or table "donors" to "utf8_general_ci"

I do not know if the plugin track.smx also uses utf-8, so it does not update the "username" on database to another charset.... I'll check