Is there a bug-thread already ?
I've got one, I think...
When activating
Save images to server and this option
Auto-save image on character update to 'yes' then I have a SQL error:
UPDATE `roster2_addons_siggen_config` SET trigger = '1' WHERE `config_id` = 'signature'
For figure why, because a
UPDATE `roster2_addons_siggen_config` SET guild_trigger = '1' WHERE `config_id` = 'signature'
is just ok.
SQL table field names are ok (
trigger,
guild_trigger or what ever).
When I do this :
[dirty hack inside - one line inserted]
siggen/inc/functions.inc (line 714)
- Code: Select all
if( $settingName != 'sc_op' && $settingValue != $configData[$settingName] )
{
$settingName ="`$settingName`";
$sqlarray += array($settingName => $settingValue);
}
I just back-tick the $settingName variable here on the fourth line - an SQL shuts its mouth, all is ok.
So, SQL is happy with this:
- Code: Select all
UPDATE `roster2_addons_siggen_config` SET `trigger` = '1' WHERE `config_id` = 'signature'
Why, again,
trigger is NO-GOOD and for example,
guild_trigger is ok ?
Why is this patch needed (for me
)
Isn't it not better to place this patch in the $roster->db->build_query() function ?
Anyway, I don't get it...
I could do a translation on the frFR.php .... I'll post one in the weekend.
PS : why not throwing this post in a bug-thread - because, even when siggen 0.3.0 realy looks great - it works ;-) - many posts will follow here - that's for sure.
PS2 : using MySQL: 5.0.32 - is trigger a reserved SQL word ?
Rename it
character_trigger (because there is a
guild-trigger) !
[
edit] : Ok, got it. The 1.7.3 Siggen uses $wodb->add_value(...).
This function DOES add back-ticks arround the field names, so => no error.
$roster->db->build_query() (roster V2) doesn't.
Sorry for making this post a mess.