📑 Table of Contents

    Updates are essential for security — an outdated plugin is the most common reason sites get hacked. But updating is also the operation most likely to break your site. The answer isn't to postpone updates; it is to update with a point you can return to .

    Why does it break at exactly that moment?

    • Incompatibility: The new version may clash with another plugin or theme you use.
    • PHP version gap: The new version may need a newer PHP; if your server is older, it errors out.
    • Database migration: Some updates change the database structure, and that process can stop halfway.
    • Customisations overwritten: Changes you made directly in theme files are wiped out by the update.

    🎯 The golden rule

    Take a manual full backup right before the update. If your scheduled backup runs at night and you update in the morning, everything in between is unprotected. A manual backup closes that gap.

    The safe order to update in

    1. Take a full backup. One covering both files and database, from that exact moment.
    2. Update one at a time. If you update everything at once, you won't know which one caused the breakage.
    3. Check after every step. The home page, an inner page, a form submission and, if you have one, the payment flow.
    4. Plugins first, then the core — or the other way round; what matters is that the order is consistent and that you make one change at a time.
    5. If something goes wrong, roll back. Because you have a backup taken moments ago, the loss is limited to a few minutes.

    What is a staging environment?

    A staging environment is a separate copy of your live site. You try the update there first and apply it to production only once you've seen that everything works. Your visitors never see this copy, and even if something breaks there, your live site is unaffected.

    A staging environment is especially valuable in these situations:

    • Large version jumps (two major versions at once, for example).
    • Sites that take payments — a broken payment flow is direct lost revenue.
    • A theme change or a wide-ranging design update.
    • Cases where several plugins have to be updated at the same time.

    🧪 A staging copy in one click

    Yedekalma can clone your live site into a separate staging copy: the files go into a separate directory and the database into tables with a separate prefix. You can try the update there first and then move to production. For the details see the WordPress backup page.

    What to watch out for when using staging

    • Block it from search engines. If the staging copy gets indexed you create a duplicate content problem.
    • Disable payments and outgoing email. Don't let an order email reach a real customer from the staging site.
    • The staging copy goes stale. The live site keeps changing; don't drag your testing out too long.
    • Don't copy the change back to production. Verify in staging, then repeat the same steps on the live site. Writing the staging database over production deletes the orders that came in meanwhile.

    Post-update checklist

    After every update check at least the following: do the home page and a few inner pages load, can you sign in to the dashboard, does the contact form submit and does the email go out, if you take payments does a test order go through, and has the mobile layout broken.

    Make sure your next backup covers this updated state too — so that in a future problem you can return to a current point.

    Frequently Asked Questions

    Do I really have to back up before updating?

    Yes, and preferably a manual backup right before the update. If your scheduled backup runs at night and you update in the morning, everything in between is unprotected. A manual backup closes that gap and, if something goes wrong, limits your loss to a few minutes.

    What is a staging environment?

    It is a separate copy of your live site. You try an update, a theme change or a new plugin on that copy first; your visitors never see it, and even if something breaks your live site is unaffected. It is especially valuable on sites that take payments and for large version jumps.

    Is it a bad idea to update all plugins at once?

    It is. If you update them all together and something breaks, working out which one caused it becomes very hard. Updating one at a time and checking the site after each step lets you catch the problem immediately and in the right place.

    How do I move a change from staging to production?

    Don't write the staging database over production; that deletes the orders and content that arrived while you were testing. The right approach is to repeat on the live site the steps you verified in staging. Staging is not a transfer tool — it is a verification environment.

    The update broke my site — what should I do?

    If you have a backup from before the update, rolling back to it is the fastest fix; the loss is limited to the time that has passed since. If you have no backup, first try disabling the offending plugin or theme; in most cases the site comes back at that step.