| /* Delete revisions */ | |
| DELETE FROM wp_posts WHERE post_type = "revision"; | |
| /* Only use this if you no longer care about any of your current revisions! */ | |
| /* Delete trashed posts */ | |
| DELETE FROM wp_posts WHERE post_type = "trash"; | |
| /* Delete Jetpack Feedback Spam */ | |
| SELECT * FROM wp_posts WHERE wp_posts.post_type = "feedback" AND wp_posts.post_status= "spam"; |
These are my notes basically. At first i created this gist just as a reminder for myself. But feel free to use this for your project as a starting point. If you have questions you can find me on twitter @thomasf https://twitter.com/thomasf This is how i used it on a Debian Wheezy testing (https://www.debian.org/releases/testing/)
Discuss, ask questions, etc. here https://news.ycombinator.com/item?id=7445545
| <?php | |
| /* | |
| |-------------------------------------------------------------------------- | |
| | 5 Star Rating | |
| |-------------------------------------------------------------------------- | |
| | | |
| | Lower bound of Wilson score confidence interval for a Bernoulli parameter (0.9604) | |
| | | |
| | See: |
In Fall 2023, Slack introduced an updated client with some unpopular UI changes. The tweaks in this document can be used to revert to the old client or hide the new side bar. These will reset every time you fully close Slack but they are easy to re-apply once you get the hang of it.
To run any of these scripts, you'll need to open the Dev Tools (or Console). You can do this by typing /slackdevtools in a Slack channel or direct message. These are the same Dev Tools you'd get in Chrome if you hit F12. Along the top are tabs for Elements, Console, Sources, Network, etc. You'll want to paste these scripts into the Console tab at the > prompt.
If Slack disables this command, then you can open Dev Tools by setting a system-wide environment variable and using a keyboard shortcut to open the console. If /slackdevtools worked for you then you can skip these next two sections.