[FileType Plugin] GetFileName

[compurandom]

Originally Posted by Rellwood

It seems that changes in the configuration of
Also, what would cause the modified date to be the same as the current date? I noticed this happening on some of the files.

One of the date columns is updated by calibre every time the metadata is modified. If you want to keep the date, you need to save it to a different (new custom?) column.

[Terisa de morgan]

Originally Posted by compurandom

One of the date columns is updated by calibre every time the metadata is modified. If you want to keep the date, you need to save it to a different (new custom?) column.

I think he's talking about "File modified date" column, not standard calibre column for recording a register update.

[Rellwood]

I'm not sure what is happening, but I cannot get the dates to show up for anything other than the current date for AZW3, or MOBI. This includes my Kindle Content from Amazon, and converted files.

The date column is the same as I have used before, but now only epubs have the "current" date (which is still off since the epub hasn't been modified since it's creation)

All other columns are good.

[Rellwood]

Originally Posted by Terisa de morgan

I think he's talking about "File modified date" column, not standard calibre column for recording a register update.

What you said.

[Terisa de morgan]

Originally Posted by Rellwood

I'm not sure what is happening, but I cannot get the dates to show up for anything other than the current date for AZW3, or MOBI. This includes my Kindle Content from Amazon, and converted files.

The date column is the same as I have used before, but now only epubs have the "current" date (which is still off since the epub hasn't been modified since it's creation)

All other columns are good.

I have a question: Do you store the original path or only the file name?

[Rellwood]

I store both.

I have different columns for both

[Rellwood]

@Terisa de morgan

I looked at the zip files for the plugin, and I think the problem with the mobi and azw3 files might lay somewhere in the following line

dict_fmt = {'azw3':'azw','mobi':'azw','cbz':'zip','cbr':'rar' , 'zip':'htm'}

Also, there is another problem in that some of the book file paths lead back to Calibre app data, suggesting that the path is taken after Calibre does whatever their import books plugin does and indicates that as the file location.

There is really no way of predicting when the filepath comes from the Calibre appdata folder, but I do have a bug report that you can look at.

[Rellwood]

I think that the books that have already been imported through the library previously, and have been collected into the calibre cache are the ones that are showing up from that directory. I am trying to see if I dump the cache and see if it changes anything.

[Rellwood]

Ok, so I figured out that if I import a RAR file as an archive that contains another bookfile inside it, such as a RAR file to hold an EPUB, then when Calibre "opens" the file, it then it shows the book coming from the temp file where the plugin that opens the RAR comes from. So, importing a RAR that Calibre automatically opens won't show the original file location.

[Rellwood]

FYI, These problems are dated as starting on feb 26....

[Terisa de morgan]

Originally Posted by Rellwood

Ok, so I figured out that if I import a RAR file as an archive that contains another bookfile inside it, such as a RAR file to hold an EPUB, then when Calibre "opens" the file, it then it shows the book coming from the temp file where the plugin that opens the RAR comes from. So, importing a RAR that Calibre automatically opens won't show the original file location.

It's showing the right directory but not the right file if I have a rar file with an azw file iside).

[Terisa de morgan]

Originally Posted by Rellwood

@Terisa de morgan

I looked at the zip files for the plugin, and I think the problem with the mobi and azw3 files might lay somewhere in the following line

dict_fmt = {'azw3':'azw','mobi':'azw','cbz':'zip','cbr':'rar' , 'zip':'htm'}

Also, there is another problem in that some of the book file paths lead back to Calibre app data, suggesting that the path is taken after Calibre does whatever their import books plugin does and indicates that as the file location.

There is really no way of predicting when the filepath comes from the Calibre appdata folder, but I do have a bug report that you can look at.

Do you have a debug log when the file comes from an appdata folder (temp one). Because I cannot reproduce it.

NOTE: Not needed, it happens only for rar/zip files, when the content is added.

[Terisa de morgan]

Originally Posted by kovidgoyal

@Terisa: From that traceback you appear to be creating a new db instance. Dont do that, instead use the db instance passed into the postadd method.

kovid, there is a problem with this approach that I'm not able to understand. I'm updating the config in the database but when I add a file, the postadd method doesn't get the updated configuration but the previous one. How can I update the info both in the database and the memory copy?

[Terisa de morgan]

Originally Posted by Rellwood

@Terisa de morgan

I looked at the zip files for the plugin, and I think the problem with the mobi and azw3 files might lay somewhere in the following line

dict_fmt = {'azw3':'azw','mobi':'azw','cbz':'zip','cbr':'rar' , 'zip':'htm'}

Not exactly in this poor dictionary It's necessary as calibre transforms that extensions.

[kovidgoyal]

How are you updating the config. Use the config API rather than executing SQL directly.