Hey guys,
I'm trying your tracking system and i found one bug in the begin of my
way.
I have database named like "something-beta". So when i fire your login
form system query database in User::getUserIDByEmail like:
SELECT usr_id FROM something-beta.eventum_user WHERE
usr_email='admin@stripped'
It cause problem because of "-" in the database name.There're quotes
missing. Query should be like this:
SELECT usr_id FROM `something-beta`.`eventum_user` WHERE `usr_email` =
'admin@stripped'
I have no idea how many times you have this query without quotes in your
system. But this time it throw fuzzy error about wrong combination
email and password.
I guess this problem should be solution for bug i found here:
http://lists.mysql.com/eventum-users/874
http://lists.mysql.com/eventum-users/4830
I found solution from Bryan to quote name of database in config but is
should be feature of installator. Don't you thing?
Best regards
Andy
Bryan Alsdorf napsal(a):
> Hi,
>
> I decided to move this discussion to the eventum-devel list.
>
> Originally our plans were to use gettext and the smarty-gettext plugin
> to localize Eventum. However, we would still need our own code to handle
> longer strings (as discussed here:
> http://lists.mysql.com/eventum-users/2735)
>
> The more I look at gettext, the more complicated it seems. I am now
> leaning towards using a simpler method. Instead of PO files, translated
> strings would be stored in PHP files, similar to this:
>
> == en_US ==
> $_LANG['welcome_string'] = "Hello";
>
> == ru_RU ==
> $_LANG['welcome_string'] = "Privet";
>
> The template files would use something like {translate
> name="welcome_string"}
>
> With gettext, the file (with an extension of PO) would look like this:
>
> msgid "Hello"
> msgstr "Privet"
>
> We would then have to run a program to translate the PO file to a binary
> format that gettext uses (a MO file).
>
> The template file would look like {t}Hello{/t}.
>
> In my mind, the first solution seems much simpler to me. We don't need
> to worry about gettext or having two translation sources (one for normal
> strings, one for longer strings).
>
> Does anyone have any comments or opinions on this?
>
> Best Regards,
