Issue with Send to device actions being disabled

[TCBW]

HI,

I have a Foxit eSlick and have been using Calibre for a couple of weeks. I found in the preference window a way to have my books that are part of a series grouped in 1 directory. I changed the line to read the following:-

{author_sort}/{series}/{series_index:0>3s}-{title} - {authors}

When I then try use send to device all but the default action buttons are disabled.

I have tried the following as well:-

{author_sort}/{series}/{series_index}-{title} - {authors}

If I return the string to the default the items in the send to device menu only re-enable after restarting Calibre.

What am I doing wrong. What I am trying to do is get something like:-
Asimov Isaac/The Foundation/001-Prelude To The Foundation - Isaac Asimov.epub

I am using Calibre 0.6.37

Thanks

[itimpi]

My suspicion is that the problem could be caused by the fact that you are trying to use series for a folder, and Calibre finds that the folder does not exist and is not willing to create it. Have yout tried simply including the series name as the first part of the filename?

[theducks]

Originally Posted by itimpi

My suspicion is that the problem could be caused by the fact that you are trying to use series for a folder, and Calibre finds that the folder does not exist and is not willing to create it. Have yout tried simply including the series name as the first part of the filename?

Series as a folder works here for many Calibre versions (Win, Linux)

I think TCBW needs another folder level:

{author_sort}/{series}/{series_index:0>3s}-{title}/ {title} - {authors}

Reason: the file/folder name is getting really long in character count, specially if you have multiple formats, where the only difference is the extension at the tail end.

[kovidgoyal]

Strange, I don't see why the save template would affect which actions are enabled.

Can you run calibre in a terminal as

calibre-debug -g

and post any output you see when the device is connected.

[TCBW]

Sorry about the delay in getting back to this. I've been traveling.

I upgraded to 0.6.40 and then ran the tests as described in the posts above but the issue no longer occurs.