Please read this before following any tutorial on wpnotar.com. It is short, and it matters — the guides here tell you to change things on a live website.
Tutorials are written against a specific WordPress version
Every guide on this site states the WordPress version it was checked against and the date it was last verified. WordPress changes constantly: 7.0 arrived in May 2026, 7.0.1 in July 2026, and 7.1 is due on 19 August 2026. Menu paths move, buttons get renamed, and settings get relocated.
If your version does not match the one at the top of the guide, the steps may not match your screen. Check that date before you start. If a guide has drifted out of date, tell us via the Contact page — see our Editorial Policy for how corrections are handled.
Back up your site first
This is not boilerplate. Real damage is possible from the kinds of steps WordPress tutorials routinely describe:
- Editing theme files,
functions.php, orwp-config.phpcan take a site offline instantly. - Deleting or deactivating a plugin can remove data that plugin was storing.
- Database changes are frequently irreversible.
- Rolling WordPress, PHP, or a plugin back to an older version can break other things that depended on the newer one.
- Updating PHP on your host can break plugins or a theme that have not been maintained.
Take a full backup — files and database — before you follow any tutorial on this site, and make sure you know how to restore it. Where a change is significant, test it on a staging copy before you touch the live site. Your host may provide both backups and staging; many do.
Your site is your responsibility
The information here is provided in good faith and for general informational purposes, on an "as is" basis, without warranties of any kind.
WordPress installations are not interchangeable. Your host, theme, plugin combination, PHP version, server configuration and existing customisations all affect what a given step does on your site. A procedure that is safe and correct on a standard install can behave differently on yours.
You follow these guides at your own risk, and you remain responsible for your own website, its data, and its backups. wpnotar.com accepts no liability for any loss, downtime, data loss, or damage arising from the use of, or reliance on, anything published here. Nothing on this site guarantees a particular outcome — technical, commercial, or otherwise.
This is not professional advice
The content here is general information for site owners doing their own WordPress work. It is not professional development, security, legal, or compliance advice, and it does not create any professional or client relationship.
If your site is business-critical — it takes payments, stores customer data, or your income depends on it — get a qualified WordPress developer to make the change. The cost of an hour of professional help is almost always lower than the cost of a broken store. Likewise, anything touching privacy law, terms, or compliance obligations for your own site is a question for a qualified professional in your jurisdiction, not for a tutorial.
Not affiliated with WordPress or any vendor
wpnotar.com is an independent website. It is not affiliated with, endorsed by, sponsored by, or connected to the WordPress Foundation, WordPress.org, WordPress.com, Automattic Inc., or any plugin, theme, or hosting company mentioned on this site.
"WordPress" is a registered trademark of the WordPress Foundation. Other product and company names mentioned here are the trademarks of their respective owners, and are used only to identify the products being discussed.
External links
This site links to third-party websites — official documentation, plugin pages, host support articles and similar. Those sites are not under our control. Linking to a resource is not an endorsement of everything on it, and we are not responsible for the content, accuracy, or practices of any external site. Follow external links at your own discretion.
Commercial relationships
This site currently carries no affiliate links, no sponsored content, and no advertising. If that changes, it will be disclosed clearly and up front. See the Affiliate Disclosure for the full position.
Last reviewed: 17 July 2026. Questions about anything on this page: contact us.
