I don't know what it was before the upgrade, but after the upgrade it was a Zero. If it had said "NO" then I would have logically known that the options were Yes/NO. And I wouldn't have asked.
Since it was Zero, I thought it could be a number, with zero being "off" and a number such as 1, 2, or 3 indicating the level of compression.
But not knowing if that was correct I read the description of the option which said "set to on." Naturally, with that wording I figured that you were saying it should be "on" or "off".
So, nothing here prepared me for Yes/NO and hence I suggested in the future you simply clearify this in the wording.
I see these kinds of issues with Photopost products often and I see the official response often seems to do nothing to correct the situation. And, it seems many times that you don't see these kinds of issues as problems that need fixing.
Why the makers of this software wouldn't want this to be clear and logical I have no idea. It seems you would not only celebrate your users pointing these issues out, but respond pro-actively to fix simple little issues like this.
This is the code right from our upgrade script. What I am saying and I think your misunderstanding is on a proper upgrade your compression setting which use to be stored in the config file as a 0 or 1 setting is corrected to be a no yes option on the upgrade so it should have been converted and stored in the settings table properly. Now you placed a no in the setting now and see it has a drop down of yes no etc correct? I was merely saying I have no idea why your site did not properly convert the setting as the upgrade instructs.
Ok, sorry. I surely did not get that from your answer. I'm happy to see this has been fixed. But I wonder why it didn't upgrade properly. The date on that file is the new date from all the files of the latest download.
I ran upgrade.php and upgraded from 2.5 to 2.6 and then 2.6 to 3.0.