Closed raymondjstone closed 6 years ago
The type field is also affected it is exporting as 0 rather than TVShow for new items.
You should not expect values to be exported as English text for 'type' and 'mode' for new items. Since the plugin was internationalized (a few versions ago) a bug was introduced as internally the plugin was comparing against the English values (hard-coded) whereas the saved values were localized. To fix this I switched to exporting values in a locale-invariant way (0=TVShow, 1=Movie, 2=Other, 3=None / 0=Pass, 1=Fail). However, to migrate people's old configuration support was added to also treat the persisted English values appropriately.
That being said, there is obviously still a bug if imported Pass values are being treated as Fail...
Not sure what the issue is but the 2nd example I had above is never getting triggered, could be that it is not being treated as a TVShow rather than being treated as fail perhaps
Given that the numeric fields are now the correct values btw I will amend the .NET application I use to resort my filters to use them and to update the old settings I have as well. Not sure why the 'deception' filter is not kicking in however
If you figure out it definitely is a bug then it would help if you could give details on how to reproduce it - thanks
Might not be a bug after all just a combination of things
Initially I thought having values of Pass and 0 was a bug but you have indicated that this is now by design, one of the affected items was included above but looking at the history beans it looks like it was triggered in the past by a show of the same name (or some other match in the past)
{
"@id":5887,
"@type":"org.kmallan.azureus.rssfeed.HistoryBean",
"fileData":"E:\\My Music - Incoming\\_being_downloaded\\in\\Deception.S01E10.HDTV.x264-LOL",
"location":"{removed for security reasons}",
"filtType":"TVShow",
"filtName":"Deception",
"histId":1363057596029,
"filtId":1357483585100,
"title":null,
"year":0,
"seasonStart":1,
"seasonEnd":1,
"episodeStart":10,
"episodeEnd":10,
"proper":false
},
so this would in this case explain the item not being triggered now and in fact is not related to the export items encoding.
Thanks!
Since the latest update there is still a problem with the pass/fail field when exporting and importing the JSON file
New items set as pass are exporting with a value of '0' not pass/fail and then import in with no error but are treated as fail despite showing pass on screen
example from an exported file (first item is correct, 2nd if not(