Well changing the language string in tickets.ini didn't do anything for me, hence my suspicion it was hardcoded somewhere. I flushed my caches and everything :P
That's because Composr reads in the value of the language string as the default config option... and if you previously saved that page, then the raw value got saved with the option, meaning it was no longer associated with the language string.
Now that I think of it, this is probably not ideal. I might make an issue for v11... for every config option, if its value matches default, then blank the saved value out so it always reads in the default value instead (ideal for dynamically adjusting config options left to their default values when/if the default values change).
"Now that I think of it, this is probably not ideal. I might make an issue for
v11... for every config option, if its value matches default, then blank the
saved value out so it always reads in the default value instead (ideal for
dynamically adjusting config options left to their default values when/if the
default values change)."
It would need doing carefully. IIRC We have a field c_set, so you could set c_set=0 if it is just the same as the default. The actual value would still be copied in to the table as cached. You'd then need a new function that clears out cached values (values where c_set=0). You'd call that when lang files are edited.
Setup > Configuration > Message Options > Support Tickets.
I'll have to look into that.
Now that I think of it, this is probably not ideal. I might make an issue for v11... for every config option, if its value matches default, then blank the saved value out so it always reads in the default value instead (ideal for dynamically adjusting config options left to their default values when/if the default values change).
v11... for every config option, if its value matches default, then blank the
saved value out so it always reads in the default value instead (ideal for
dynamically adjusting config options left to their default values when/if the
default values change)."
It would need doing carefully. IIRC We have a field c_set, so you could set c_set=0 if it is just the same as the default. The actual value would still be copied in to the table as cached. You'd then need a new function that clears out cached values (values where c_set=0). You'd call that when lang files are edited.