You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that whenever this subcategory is used for this extractor, the result is a massive list of random images across the site, rather than the intended target image.
I looked at the call being made for this subcategory, and it looks like the parameter imageId is included. Example with https://civitai.com/images/2478631:
but this parameter is not included in the list of available parameters on the Civitai API reference: GET /api/v1/images
which I suspect may be the reason this issue is occurring.
However, there is a postID parameter that can be utilized. This is just a suggestion, but If it's not feasible to be able to extract the target image through the API, it might be more worthwhile to change this subcategory to CivitaiPostExtractor that would be used for extracting images from a post, from URLs like this: https://civitai.com/posts/592634 .
The text was updated successfully, but these errors were encountered:
austblack88
changed the title
[Civitai] CivitaiImageExtractor not working as inteded.
[Civitai] CivitaiImageExtractor not working as intended.
Oct 5, 2024
The imageId parameter was working previously and it usually (civitai/civitai#1329) downloaded the correct image, but now it seems to get ignored and /api/v1/images downloads everything there is without any filter.
Just use the tRPC API endpoints (-o api=trpc). They are undocumented, but at least they support every site feature since they are what gets used internally by the site itself.
it might be more worthwhile to change this subcategory to CivitaiPostExtractor that would be used for extracting images from a post, from URLs like this: https://civitai.com/posts/592634 .
I noticed that whenever this subcategory is used for this extractor, the result is a massive list of random images across the site, rather than the intended target image.
I looked at the call being made for this subcategory, and it looks like the parameter
imageId
is included. Example with https://civitai.com/images/2478631:but this parameter is not included in the list of available parameters on the Civitai API reference: GET /api/v1/images
which I suspect may be the reason this issue is occurring.
However, there is a
postID
parameter that can be utilized. This is just a suggestion, but If it's not feasible to be able to extract the target image through the API, it might be more worthwhile to change this subcategory to CivitaiPostExtractor that would be used for extracting images from a post, from URLs like this: https://civitai.com/posts/592634 .The text was updated successfully, but these errors were encountered: