Processing 0 of ...

[kmccormi]

I've been pulling my hair out trying to get the Data Manager script to work, but I have to admit defeat. I ony installed ComicRack this week, and using TheOrganizer012015 guide I istalled the appropriate scripts and started working on my collection. Everything works but the Data Manager. I installed the latest version, then imported the sample organizer .dat file and all rules imported without difficulty (after reading through your forum posts regarding the '@' character difficulties. Whenever I attempt to run Data Manager on a scraped file there is no confirmation dialog box, it just immediately goes to a 'runprocess' dialog that says 'processing 0 of x' which then hangs until I manually close it out. I have been through all the relevant forum posts and read through the manual, but nothing works.

I'm running ComicRack on Windows 10 (64) and I've enclosed the dataman.dat file (as txt)
dataman.txt

[kmccormi]

Well, after 12 days without a peep of a response I decided to do some experimenting. Hopefully anyone who gets stuck with same problem can benefit from this: the problem lies in the ruleset syntax parameters. After much trial and error I discovered that if you have a rule that has the "ContainsAllOf" modifier, it causes the entire ruleset to crap out with the "processing 0 of xx" error. Change it to something like "StartsWith" and everything works fine. Sheesh

[NobahdiAtoll]

In case you didn't notice I assigned myself to this issue a few hours after you posted it, that means I'm working on it. If you can do a better or quicker job, I invite you to do so (which is why its open source). Coding isn't instant work and there are thousands of lines of inter-dependant code to deal with (not to mention the debugging trace for iron python is horrendous.

[NobahdiAtoll]

Bug address and slated for fix with release 2.06.0 before the month's end

[duckpuppy]

Since this has gone on for a while without a resolution, I've taken a look at what might be the issue.

In 9b981fe, it looks like the in operator was replaced with Contains() for all Contains* functions, which doesn't look like it will work because the Contains() function is a rule itself that takes in a book object, and the parameter being passed to it is a string value. More to the point, the Contains() method is being called on a string, which doesn't have that method.

[duckpuppy]

@kmccormi My commit should fix the issue, if it gets merged in. I also fixed a small bug with Ranges.

[duckpuppy]

@kmccormi I'm going to see if I can create a plugin from my sources with the bug fixes. Don't know how long that will take, but I'm using my version with no issues (and in fact, some issues fixed).

[kmccormi]

Excellent work! Whenever you're ready, I'd be pleased to help you test the plugin on my system