That was a problem in 3.0.3, but it should have been fixed in 3.0.4, so that’s odd. I tested 3.0.4, and didn’t have that problem, but I’ll do some further testing. There may be an edge case I missed.
Is there any possibility that you’d updated to 3.0.3 prior to 3.0.4, and that the settings were actually reset at that time?
Apparently only the “Basic Settings” were reset, I restored them and the shortener settings came back so they were still there, just hidden because the basic settings said no shortener.
I am not sure, I haven’t updated for a few days and I am sure we would have noticed if the settings had changed and if you released 3.0.4 shortly after 3.0.3 I probably skipped 3.0.3
3.0.3 went out 4 days ago, so that’s still possible; it’s hard to say. It is just a subset of the settings that were reset – literally, it was the settings that get configured on a new install; any other settings were untouched.
I just checked my logs and here’s the timeline:
1. the previous update to the plugin was on April 3 (most probably to 3.0.3)
2. an automated tweet was send on April 6 and was normal (so 3.0.3 did not reset our settings)
3. today I upgraded to 3.0.4
4. shortly after an automated tweet went out using the default settings
it appears that 3.0.4 reset the settings, not 3.0.3
Well, what the hell is up with that…
There was *definitely* a bug in 3.0.3 that reset settings, and that I fixed in 3.0.4. But I’ll definitely need to recheck that. Perhaps, as I said, there may be an edge case I didn’t notice.
Oh, hell. I misspelled a setting. Yes, this is a bug, and I’ll get the update out ASAP.
