fix(brasiltracker): update column offsets for size, grabs and stats#913
Merged
augustuen merged 1 commit intoJun 15, 2026
Merged
Conversation
|
ilike2burnthing
approved these changes
Jun 15, 2026
ilike2burnthing
left a comment
ilike2burnthing
left a comment
Contributor
There was a problem hiding this comment.
Apologies, I missed this PR. LGTM
@augustuen this definition is specific to Prowlarr, so this can be merged.
augustuen
approved these changes
Jun 15, 2026
This file contains hidden or 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
3 participants
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.
Summary of Changes
Adjusted the
td:nth-childindexes forsize,grabs,seeders, andleechersindefinitions/v11/brasiltracker.ymlto match the current HTML layout of the tracker's search page.Description
The torrent results table (
#torrent_table > tbody > tr.torrent) currently includes an Uploader column as the 4th<td>element. This caused a 1-column offset for all subsequent fields starting from the 5th column (Time/Tempo).Because of this offset, Prowlarr was attempting to parse:
Column Mapping Comparison:
td:nth-child(1)td:nth-child(2)td.big_infotd.big_infotd:nth-child(3)td:nth-child(3)td:nth-child(3)td:nth-child(4)td:nth-child(5)span.time(insidetd(5))span.timetd:nth-child(6)td:nth-child(5)(Wrong)td:nth-child(6)td:nth-child(7)td:nth-child(6)(Wrong)td:nth-child(7)td:nth-child(8)td:nth-child(7)(Wrong)td:nth-child(8)td:nth-child(9)td:nth-child(8)(Wrong)td:nth-child(9)