WP Reset is a plugin that lets you reset your site both completely and partially where only specific sections of your blog are included in the changes. The full reset is pretty self-explanatory, removing all posts, pages, custom post types, comments, media entries, and users.
The action does leave media files (but doesn’t list them under media), as well as integrations such as plugins and theme uploads, along with all of the core characteristics of the site – site title, WordPress address, site address, site language, and visibility settings.
If you’re opting for a partial reset, these are your choices:
- Transients – all transient data is deleted (includes expired, non-expired transients and orphaned transient timeout entries)
- Upload data – all uploaded files in the C:\folder\htdocs\wp\wp-content\uploads are deleted
- Theme options – delete the options and mods for all themes, active and inactive
- Theme deletion – deletes all themes, leaving only the default WordPress theme available
- Plugins – all plugins except WP reset are deleted
- Custom tables – all custom tables with the wp_ prefix are deleted, but all core tables and those without the wp_ prefix remain
- .htaccess file – deletes the .htaccess file located in C:/folder/htdocs/wp/.htaccess
It’s very important to point out that all actions are final and irreversible, no matter which way you go, so be sure before clicking that button.
In case you’re wondering what is the situation that might require a blog/site reset, don’t worry. We’ve compiled a list of six most common reasons which may incur this action. Without further ado, check if your blog is in danger of having to be reset:
One of the first reasons that come to mind when pondering to reset a blog is when switching from local/private to public. When you’re starting out in the field of web development, or even just blog managing your best bet is to start with something where virtually no damage can occur. Whether it’s a local site or a private one it doesn’t really matter, the important thing is to try everything that you can and see how everything works together – plugins, scripts, themes, etc. Once you’ve gotten your bearings and feel it’s time to do the switch towards the real deal more often than not you’ll want to do so from a clean sheet.
Since starting out and doing extensive testing, in the begging actually learning as you went along, there is bound to be a buildup of conflicting pieces across the board. Chances are, these issues will be so deep-rooted in the foundation that the easiest way to start fresh is to bring it back to the begging. With your new knowledge, you’ll then be able to start clean avoiding all the mistakes that have come beforehand.
Following up with the learning/test blog, there are instances where a lot of similar problems may arise with already live blogs. This can especially be true in cases where the site has been up for a long time and has, in that time, provided large amounts of various content. A rule of thumb is that the more content you provide, the more underlying software you’ll need to support it all.
You host a webshop, you need a plugin to run it, you require registration to view some or all your content, you need a plugin, you have various sections with entirely different content on separate pages, you need multiple custom themes to differentiate between them. The list just goes on and on.
You’ll probably just be adding integrations as you need them, not worrying that much about those that remain and can conflict with the new ones you’re implementing. Stacking various solutions, be it integrated plugins, or outside services on top of each other, over time can and probably will resort into chaos.
First for you on the backend and the ultimate for your visitors on the frontend. If it, in fact, comes to that, it’s already too late for anything but a complete reset. Again, individual solutions can maybe be applied, but it’s even more critical here to do the job quickly because the site is open to the public. Since most sites and blogs nowadays have, at least, some basic forms of backup, after the reset you’ll probably be able to hit the ground running relatively quickly.
Change of content direction
A drastic change in content or format could also be the reason you would want to reset your blog. As you evolve, so does your blog and the content you’re putting out. As long as there is a common thread through it all you can keep moving forward, but once a sharp turn happens that may not be possible.
Maybe you want to shake things up, maybe the content you’re putting out is of the times it’s written in (following a campaign for a new product for example) and simply doesn’t apply now. No matter what the reason for the change is there can come a point where clinging to content you don’t need is futile and a fresh start is needed.
Since resetting your site fully deletes your entire self-published content archive (all posts and pages) along with being final and irreversible you need to think hard before going down this path. The previous two reasons we’ve mentioned are more tech-based than anything else (software to be more precise). This one, however, is much more a matter of choice than necessity and therefore requires a much clearer short term and long term plan for the blog, so again – think hard and think twice before acting.
Shutting down your blog
In line with the content-based reason beforehand, this is one follows a similar train of thought. Shutting down your blog for any reason should be accompanied by certain actions to protect from any misuse. Imagine having something drudged up years after your blog is dead and used in a way you not only didn’t intend but is actually harmful. To avoid situations like this it’s a good idea to wipe the slate clean before going offline for good.
Now, we all know that whatever appears on the web stays there forever in one form or another, but you shouldn’t serve up your content on a silver platter. Resetting your blog means that the complete archive of your original content uploaded through posts and pages is deleted. That means that unless somebody locally saved the content when it was originally published is going to have a hard time getting to it.
Like we’ve said completely removing something from the internet is impossible, but with just a few small actions, resetting being first among them you’re both protecting yourself and your intellectual property. In addition to this, you won’t have to completely delete your blog, instead of putting it on a temporary or permanent hiatus which you can come back to in the future. You won’t be able to just continue from where you left off, but there will be a solid base for you to work with.
Until now all the reasons have been either out of convenience, business decisions, or for peace of mind. There are, unfortunately, less desirable reasons for needing to reset a site. Detect that we’ve used the term “needing” and not “wanting”. If there has been a security breach and your site and the content it contains is vulnerable you really do “need” to take appropriate steps. Changing, updating and upgrading your security settings is certainly the first thing you should address, but it isn’t the only thing.
We’ve already mentioned that most of the time there are forms of backup for even the basic domain providers, so a full reset isn’t something that you should be scared of. By doing it you’re protecting both yourself and your blog and content from the threat that already happened and any future threats that may happen.
It seems like we’re going from bad to worse, but these are all the reasons you can encounter which may prompt you to rest your site. Just like with a security breach, when facing any legal action (which is final by the way, not only in the process) there really isn’t much you can do but comply after all other resources have been exhausted.
No matter what order you’ve given, mainly it’s about shutting down your blog/site, it’s wise to do a full reset before you comply. We’ve already covered why this is important and how it can be used in a way you don’t want if you don’t take every precaution with these kinds of delicate things.
The correct line of action in these situations would be order-reset-go offline. Abiding by this you can at least salvage something from an already bad situation and not make it any worse than it already is.
And there you have it. The top six reasons why you would ever want to reset your site, either fully, or partially. If you’ve found yourself in one of the aforementioned situation maybe it’s time to consider an action like this, even if it may seem drastic. Sometimes measures like these are the only ones left.