Limit publishing to newest #509
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
Checks page 1 of newest for 3 or more recent levels from this account or ip
Deletes a level from newest (used in upload_level.php)
👏 worry 👏 about 👏 important 👏 things
|
👍 |
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.
We've had an issue in the past with level spam. As a fix, Stxtics suggested that there be a limit to the number of levels that a user can publish to page 1 of newest at any given time. This pull adds that limit while still letting the user save their level.
Side note: I noticed that when a level gets unpublished, the level remains in
pr2_new_levels. To make this pull work, I needed to count the number of levels from that table. I've added a function toupload_level.phpandremove_level.phpwhich delete the level frompr2_new_levelsif it exists in that table.