Bug: Registering Empty Strings
-
I spent a great deal of time trying to debug an issue where a number of strings that I had registered were not appearing on the “Strings translation” page.
I was retrieving a number of strings using get_option() to pass to pll_register_string(). Some of these did not yet have values, so, when get_option() returned FALSE, I passed an empty string (i.e. ”) to pll_register_string(). Since I had given the required parameters and no error was thrown, I assumed that the issue laid outside of the plugin.
However, that was not the case. The strings would not appear on the “Strings translation” page until they had a non-empty value, despite having been registered with a name.
This was a very frustrating bug to identify. May I recommend either allowing an empty string or updating the documentation to state that a non-empty string is required?
Otherwise, I’m really liking this plugin. Keep up the great work!
-Paul
The topic ‘Bug: Registering Empty Strings’ is closed to new replies.