Step1 of ImportWizard is broken in v2.6.1 when clicking on Add Column (1 Viewer)

[mts]

Hi there,

I have a problem with the "new" version of tvSeries.
When I hit the import button it shows me a page with series/episodes the tool could not recognize.
How can I manually assign the correct series/episodes now?
With the older version I used it was quite simple but now I don't see how it works. When I simply check an undetected series and press next, I get the message: "Unable to continue. All Enabled results need at least the Series/Season/Episode IDs filled out!"

Any ideas?
THX

mts

 

[mastyman]

Re: import undetected series

you should rename them with the season and episode number? Monk.S0XE0X ?

 

[ltfearme]

Re: import undetected series

mts, use the 'Add Column' link in top right and add the SeriesName, Season and Episode Column.

Then fill them out the best you can, dont worry too much about getting the Season/Episode numbers correct as you can match them up later on.

 

[Moelito]

Re: import undetected series

mts, use the 'Add Column' link in top right and add the SeriesName, Season and Episode Column.

Then fill them out the best you can, dont worry too much about getting the Season/Episode numbers correct as you can match them up later on.

In the latest maintenance release 2.6.1 this is broken for me. When I press "add column" I get a the new column I choose BUT duplicates of all previously columns shown. And the importer will never find what I put in the columns so the importer fails.
Only me with this problem? Maybe something is broken with my install...
//Moe

 

[ltfearme]

Re: import undetected series

If that's the case then it's definitely a bug With this release....I will see if I can reproduce.

You can work around this in the meantime by running the the import wizard with a file that will automatically parse ok, this will Create all the columns you need.

 

[ltfearme]

Re: import undetected series

Ok, sorry about this. I can reproduce issue, I must of introduced this in 2.6.1.

I will make a fix and release 2.6.2 shortly...but the work around I suggested in the meantime should work.