Rewrite VirtualPorn (using API as a Source) #1654
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1568
Rewrite of VirtualPorn scraper. Most tag IDs on their new site look code generated, so I have used an API that they have called.
There is no references I can find to the old Scene Ids used by XBVR. I have remapped scenes to new Ids based on the Release Date, this seems to work as they normally only release a scene every 2 weeks. This requires calling the API and the old Scene Id is stored in the legacy_scene_id column.
The migration will update links, but to get updated filenames, the user can refresh the scenes, some may still want the old filenames, their choice.