Thanks, Becky. I set up the column as you described (the main difference from what I had been using is that your custom column is set to permitted values), but I still had no luck. Same error message. If I simply change

Code:

"collections": [ "- ", 1 ]

to

Code:

"series": [ "- ", 1 ]

I get 43 collections created, so I know that things are working okay, just not for custom columns for me.

I'm using 7.43 on a Mac - what about you?

On a separate note, even if I got things working your way, wouldn't I only be able to enter a book into 1 collection this way? I also tried another column with comma separated tags, which is what I think might work better for me, but that still didn't work.

On a separate note, even if I got things working your way, wouldn't I only be able to enter a book into 1 collection this way? I also tried another column with comma separated tags, which is what I think might work better for me, but that still didn't work.

I get 43 collections created, so I know that things are working okay, just not for custom columns for me.

The only thing I can think of is a mismatch between the tweak and the custom column. Have you checked your custom column settings to make sure there's not an errant space in there, or capitalization or something?

I'm sure it is some sort of mismatch, but I can't see it (images snip) I'm sure there are sharper eyes than mine out there - what tiny comma or some-such am I missing?

Quote:

Originally Posted by theducks

reference to User columns usually start with a hash mark (added to your chosen name by Calibre) Hover your mouse over the column header for the name to use

I see what theducks is referring to but I've never needed to add the # for the custom columns to work with the plugin. The only thing I'm doing differently than tlrowley is I used the same name for both lookup name and heading.

One thing just occurred to me - when the device is connected there is a "collections" column on the device page, yes? Could that be causing a conflict? Try changing the lookup name to "incollection" or "mycollection" or something other than "collections", then change your tweak to match and see what happens.

"I eliminated the space as it confused my k3 which would no longer do the go to beginning of "k" or "s" ... trick if some of the files were - title rather than -title when in title mode.
Interesting to know about the go to beginning trick (I've used search, but not jump to the beginning - do you do anything special to do this?)."

If you're in author or title mode, and for example, want to go to andre norton books (if collection is from author_sort, collection will be Norton, Andre), use either the n or o key and the bottom of the page search bar will say in faint print, "click to go to N titles or N authors". Clicking will get you to the first entry in N.

I tend to use it most in title mode (which contains titles & collections) so that I can relatively quickly find a file. When I tried a special character with a space then a collection name, that feature didn't work, eliminating the space made it work again.

I don't know if this bug is fixed or not, but a couple of calibre versions ago, the only custom columns that would work in collection programs had to be type "text, column shown in tag browser" Other column types - no luck.

Good spot on the "collections" title, but I've tried "collections", "sample", and "tracey" - none of them work. I'm pretty sure there's no built-in column heading of "tracey"?

At least I can get series to work, but I'd really like an "I'm currently reading" collection, because that's the one I use the most.

Sorry this isn't working - I'm definitely interesting in figuring out what it is.

It may be as suggested by ElizabethN: the type of column. You have "Text, with defined set of permitted values". Try "Text, column shown in the tag browser"

Try running in debug mode as mentioned in the first post to see if it shows anything obvious. If you use the GUI method you need to exit Calibre to see the log file pop up. On command line use calibre-debug --gui-debug=GUI_DEBUG and your info should go to the screen (it should also go to a file but I haven't looked if this works)