Loading Heatmap…
Syunka created repository Syunka/test
5 years ago
Syunka commented on issue Oppaitime/Gazelle#49
Fix user limit reached noticeOK, I have pushed a new commit with those changes.
7 years ago
Syunka pushed to fix-user-limit-notice at Syunka/Gazelle
028baca966 Update user limit notice criteria
7 years ago
Syunka pushed to fix-user-limit-notice at Syunka/Gazelle
- d3732302e2 Fix user limit reached notice
When USER_LIMIT == 0 (no limit) $UserCount is always > USER_LIMIT so
the notice is always shown. Actually this commit just implements the
exact opposite of the logic on line 137.
455152131e Update README.md
7 years ago
Syunka deleted branch fix-user-limit-notice from Syunka/Gazelle
7 years ago
Syunka deleted branch fix-schedule-auth-logic from Syunka/Gazelle
7 years ago
Syunka pushed to fix-user-limit-notice at Syunka/Gazelle
- 407184e1f0 Fix user limit reached notice
When USER_LIMIT == 0 (no limit) $UserCount is always > USER_LIMIT so
the notice is always shown. Actually this commit just implements the
exact opposite of the logic on line 137.
7 years ago
Syunka commented on issue Oppaitime/Gazelle#48
Fix schedule.php SCHEDULE_KEY logic use as a parameterFYI to see how this code already works look at peerupdate.php , it uses $argv[1] and this works OK in cron.
7 years ago
Syunka created pull request Oppaitime/Gazelle#48
Fix schedule.php SCHEDULE_KEY logic use as a parameter7 years ago
Syunka pushed to fix-schedule-auth-logic at Syunka/Gazelle
- d3a27b1e85 Fix schedule.php SCHEDULE_KEY logic use as a parameter.
Current logic does not check $argv and only checks $_REQUEST['key'] .
Added in $argv logic whilst retaining the ?key= functionality.
The original WCD instructions state that it should be used as a
parameter but I cannot see how this would ever work. This code
allows SCHEDULE_KEY to be used as a parameter via cron.
7 years ago
Syunka created repository Syunka/Gazelle
7 years ago
Syunka opened issue Oppaitime/Gazelle#47
Bug: Change category for a torrent results in SQL error7 years ago