Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with configuration file and metadata #253

Closed
ReneRanzinger opened this issue May 10, 2019 · 1 comment
Closed

Error with configuration file and metadata #253

ReneRanzinger opened this issue May 10, 2019 · 1 comment

Comments

@ReneRanzinger
Copy link

I am using the following configuration file for pixiv download:

{ "extractor":{ "base-directory":"./gallery-dl/", "pixiv":{ "archive":"E:/Images/gallery-dl/gallery-dl/archive-pixiv.sqlite3", "username":"xxx", "password":"xxx", "metadata":{ "mode":"tags", "extension":"txt" } } } }

When I run the command:
gallery-dl.exe -c gallery-dl.conf <pixivURL>
The images are downloaded but no metadata files are created. I tried moving the "metadata" json property around (into pixiv, extractor level or top level). All the same effect - no files.

If I run the command:
gallery-dl.exe -c gallery-dl.conf --write-tags --write-metadata <pixivURL>
Metadata files are created but the settings (txt file, tags) are ignored - JSon files with *.json extension are created. Again moving the "metadata" json property has no effect.

I am also sure it find the configuration file, since it creates the archive file.

Questions:

  • What do I wrong with the metadata settings or is that something pixiv specific?
  • Are their json properties in the configuration file that I can use to enable metadata and do not have to use the command line options (--write-tags --write-metadata)?
@mikf
Copy link
Owner

mikf commented May 10, 2019

Instead of "metadata": ... you need to specify a list of postprocessor objects:

"postprocessors": [
  {"name": "metadata", "mode": "json"},
  {"name": "metadata", "mode": "tags"}
]

By the way: --write-metadata and --write-tags (actually all post-processor command-line options) are mutually exclusive with the way they are implemented at the moment. Only the last one takes effect. (fixed with e64773f)

mikf added a commit that referenced this issue May 14, 2019
... without overwriting any previous ones
@mikf mikf closed this as completed May 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants