{"id":22351,"date":"2026-08-27T15:56:41","date_gmt":"2026-08-27T13:56:41","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&#038;p=22351"},"modified":"2026-08-27T15:59:27","modified_gmt":"2026-08-27T13:59:27","password":"","slug":"update-wordpress","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/wordpress\/wordpress-aktualisieren\/","title":{"rendered":"Updating WordPress: Keeping Core, Plugins, and Themes Secure and Up to Date"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Regular updates are among the most important tasks in managing a <strong>WordPress website<\/strong>. It's not just about new features. Updates fix bugs, improve compatibility and, above all, close known security vulnerabilities in WordPress, plugins and themes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress does not only consist of the actual WordPress system, the so-called <strong>WordPress Core<\/strong>. A typical website also uses a theme and several plugins. All of these components can be updated independently of each other and should be checked regularly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we show you how to safely update WordPress, plugins, and themes, when automatic updates make sense, why a backup before major updates is important, and what you can do if problems occur after an update.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Briefly explained:<\/strong> You can find available updates in the WordPress dashboard under <strong>Dashboard \u2192 Updates<\/strong>. Before major updates, you should have a recent backup. Regularly update WordPress, plugins, and themes, and then check whether your website continues to function correctly.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Why are WordPress updates so important?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A WordPress website consists of various software components that are continuously being developed. Updates can include various improvements:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Closing known security vulnerabilities<\/li>\n\n\n\n<li>Debugging<\/li>\n\n\n\n<li>Performance and stability improvements<\/li>\n\n\n\n<li>Adaptations to current PHP versions and web standards<\/li>\n\n\n\n<li>Compatibility improvements between WordPress, plugins, and themes<\/li>\n\n\n\n<li>new or revised features<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Security updates in particular should not be postponed unnecessarily long. As soon as a vulnerability is publicly known, outdated installations can be targeted for attacks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A permanently neglected WordPress installation is therefore an avoidable security risk.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What actually needs to be updated in WordPress?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In everyday language, people often just talk about a \u201eWordPress update.\u201c In fact, however, several different components can be affected.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typically, this includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>WordPress Core:<\/strong> the actual content management system<\/li>\n\n\n\n<li><strong>Plugins:<\/strong> Extensions for additional functions<\/li>\n\n\n\n<li><strong>Themes:<\/strong> Design and partially additional functions of the website<\/li>\n\n\n\n<li><strong>Translations:<\/strong> Language files for WordPress, plugins, and themes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">All of these components can receive their own updates.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Where do I see available WordPress updates?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">First, log in to the WordPress admin area.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is usually accessible during a normal installation at:<\/p>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/deine-domain.ch\/wp-admin\n<\/div><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Then open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Dashboard \u2192 Updates<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On this page, WordPress displays available updates for the WordPress core, plugins, themes, and translations, if applicable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Additionally, available plugin updates appear under <strong>Plugins \u2192 Installed Plugins<\/strong> and theme updates under <strong>Design \u2192 Themes<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Create a backup before an update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In most cases, WordPress updates work without any issues. Nevertheless, an update alters files, program code, or potentially database structures of your website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is why, especially before major updates, you should ensure that a <strong>current and recoverable backup<\/strong> is available.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A complete backup of a WordPress website basically includes at least:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the files of the WordPress installation<\/li>\n\n\n\n<li>the WordPress database<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The database is particularly important because, among other things, posts, pages, users, settings, and numerous plugin data are stored there. The files, on the other hand, contain WordPress itself, plugins, themes, and uploads, for example.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> A backup is only truly helpful if it can also be restored in an emergency. Do not rely on a backup for important websites if you do not know whether and how it can be restored.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Update WordPress Core via the dashboard<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a new WordPress version is available, it is normally displayed in the dashboard.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Update WordPress Core<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Log in to the WordPress admin area.<\/li>\n\n\n\n<li>Open <strong>Dashboard \u2192 Updates<\/strong>.<\/li>\n\n\n\n<li>Check which WordPress version is being offered.<\/li>\n\n\n\n<li>Make sure there is a current backup.<\/li>\n\n\n\n<li>Start the offered WordPress update.<\/li>\n\n\n\n<li>Wait until WordPress has completely finished the process.<\/li>\n\n\n\n<li>Then open the website and the admin area.<\/li>\n\n\n\n<li>Check important functions for errors.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">You should not unnecessarily close the browser window or interrupt the process during the update.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happens during a WordPress core update?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">During a normal update, WordPress replaces the required core files with the files of the new version. Custom content such as posts, pages, and media files is not simply deleted in the process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With certain version changes, an update of the WordPress database may also be required. WordPress will usually notify you and guide you through the necessary process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Making changes directly to WordPress core files is problematic because they can be overwritten during updates. Therefore, WordPress core should fundamentally not be modified directly.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Update plugins in WordPress<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Plugins extend WordPress with additional features and are developed independently of the WordPress core. That is why plugin developers release their own updates.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find available plugin updates, for example, under:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Plugins \u2192 Installed Plugins<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">or collected at:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Dashboard \u2192 Updates<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Update WordPress plugin<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open <strong>Plugins \u2192 Installed Plugins<\/strong>.<\/li>\n\n\n\n<li>Check for which plugins updates are available.<\/li>\n\n\n\n<li>Check the information on the new version for important updates if necessary.<\/li>\n\n\n\n<li>Make sure a current backup is available.<\/li>\n\n\n\n<li>Start the update of the requested plugin.<\/li>\n\n\n\n<li>Wait until WordPress reports successful completion.<\/li>\n\n\n\n<li>Next, check the features of your website that depend on this plugin.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how plugins generally work and how to install them in our guide <a href=\"\/en\/help\/wordpress\/wordpress-plugin-installieren\/\">Installing WordPress plugins: What is a plugin and how does the installation work?<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Update all plugins at once or individually?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress makes it possible to update multiple plugins in a single operation. On a small, simple website, this can work without any problems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, for business-critical or more complex websites, it is often more sensible to perform updates in a controlled manner. For example, if you update ten plugins simultaneously and an error occurs afterward, it is not immediately obvious which update caused it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For particularly important plugins, you can therefore proceed step-by-step:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Update plugin<\/li>\n\n\n\n<li>Check website<\/li>\n\n\n\n<li>test important function<\/li>\n\n\n\n<li>update next plugin<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">That takes a little longer, but makes troubleshooting considerably easier.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Which plugins should you update with special care?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The more a plugin interferes with the core functions of your website, the more carefully you should control an update.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Special attention is deserved, for example, by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>WooCommerce and Shop Extensions<\/li>\n\n\n\n<li>Page Builder<\/li>\n\n\n\n<li>Form plugins<\/li>\n\n\n\n<li>Membership and user management systems<\/li>\n\n\n\n<li>Multilingual plugins<\/li>\n\n\n\n<li>SEO plugins<\/li>\n\n\n\n<li>Caching and performance plugins<\/li>\n\n\n\n<li>Security plugins<\/li>\n\n\n\n<li>Backup plugins<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For a productive online shop, you should particularly check the order process, shopping cart, checkout, and payment functions for relevant updates.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Update WordPress themes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Themes also receive updates. These can include bug fixes, security improvements, new features, or adjustments to current WordPress versions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Available theme updates can be found at:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Design \u2192 Themes<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">or:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Dashboard \u2192 Updates<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before a theme update, however, an important question must be answered: <strong>Were changes made directly to the theme?<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Caution with directly modified theme files<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you have edited PHP, CSS, or other files of a theme directly, these changes can be overwritten during a theme update.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Customizations therefore do not belong directly in the files of an updateable parent theme. For more extensive code customizations, a <strong>Child Theme<\/strong> used.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain what a child theme is and when you need one in our guide <a href=\"\/en\/help\/wordpress\/wordpress-child-theme-erstellen\/\">Creating a WordPress Child Theme: Implementing Custom Modifications Safely Against Updates<\/a>.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Do not blindly update a theme with unknown direct code modifications. First, clarify whether changes were made to the parent theme that could be lost due to the update.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What is the difference between minor and major WordPress versions?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress publishes different types of updates. A frequent distinction is made between <strong>Maintenance or security releases<\/strong> and new major versions are distinguished.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A version number can look like this, for example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>6.x.x<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Smaller maintenance and security versions typically focus on bug fixes and security improvements. Major new versions, on the other hand, may introduce more extensive features and technical changes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Regardless of the version number, you should check before an update whether your important plugins and themes are maintained and compatible with the new WordPress version.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Have WordPress update automatically<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress has mechanisms for automatic updates. Certain core updates can be applied automatically, and automatic updates can also be activated for plugins and themes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For plugins, you will usually find corresponding options under:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Plugins \u2192 Installed Plugins<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There, automatic updates can be enabled or disabled for individual plugins.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the WordPress version and configuration, corresponding options are also available for themes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do automatic WordPress updates make sense?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There is no blanket answer to that. Automatic updates have clear advantages, but also disadvantages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Pros:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Security updates are installed faster.<\/li>\n\n\n\n<li>Updates are less easily forgotten.<\/li>\n\n\n\n<li>Smaller websites require less manual maintenance.<\/li>\n\n\n\n<li>known vulnerabilities do not remain unpatched for an unnecessarily long time.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Possible disadvantages:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An incompatible update can be installed without prior inspection<\/li>\n\n\n\n<li>Problems may not be noticed until later<\/li>\n\n\n\n<li>on complex websites, dependencies can exist between multiple components<\/li>\n\n\n\n<li>Mission-critical functions should be tested after updates.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The correct strategy therefore depends heavily on the website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Automatic updates for small websites<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a simple corporate website or a small blog with few established plugins, automatic updates for many components can make sense.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nevertheless, a prerequisite is that regular backups are available and the website is monitored or occasionally checked.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201eAutomatically updated\u201c does not mean \u201enever needs to be checked again\u201c.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Updates for WooCommerce and business-critical websites<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a live WooCommerce store, a membership platform, or a website with mission-critical functions, you should handle updates in a more controlled manner.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An error on a simple subpage is unpleasant. A non-functioning checkout, on the other hand, can directly prevent orders and revenue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For websites like this, a structured approach is useful:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Check backup<\/li>\n\n\n\n<li>Read update notes or changelogs for relevant components<\/li>\n\n\n\n<li>Consider compatibility of important extensions<\/li>\n\n\n\n<li>Install updates in a controlled manner<\/li>\n\n\n\n<li>test core functions immediately afterward<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For extensive or particularly critical websites, an additional <strong>Staging environment<\/strong> make sense to test larger updates on first.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is a staging website?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A staging website is a separate test copy of your live website. Changes can be tested there without visitors or customers being directly affected.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly practical for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>major WordPress updates<\/li>\n\n\n\n<li>extensive plugin updates<\/li>\n\n\n\n<li>WooCommerce updates<\/li>\n\n\n\n<li>PHP version change<\/li>\n\n\n\n<li>Theme change<\/li>\n\n\n\n<li>major design or code changes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">After a successful test, the planned changes can be implemented in a controlled manner on the production website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Update plugins before the WordPress core or after?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There is no universally correct order for every combination of WordPress, theme, and plugin. The respective release notes and dependencies are what matter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">During a normal maintenance procedure, the following approach is often useful:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Practical update order<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Ensure current backup.<\/li>\n\n\n\n<li>Check for available updates and notices.<\/li>\n\n\n\n<li>Check important plugins and their compatibility.<\/li>\n\n\n\n<li>Perform updates in a controlled manner.<\/li>\n\n\n\n<li>Update WordPress core, if necessary.<\/li>\n\n\n\n<li>Update theme and remaining components.<\/li>\n\n\n\n<li>Clear cache.<\/li>\n\n\n\n<li>Test website and core features.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If a developer explicitly recommends a different order for a specific plugin or theme, you should follow these product-specific instructions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What should be tested after a WordPress update?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Just because WordPress reports \u201eUpdate successful\u201c doesn't mean all of your website's features have been checked.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, open at least the most important areas after updates.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Home<\/li>\n\n\n\n<li>important subpages<\/li>\n\n\n\n<li>Navigation and menus<\/li>\n\n\n\n<li>Display on desktop and smartphone<\/li>\n\n\n\n<li>Contact forms<\/li>\n\n\n\n<li>Login areas<\/li>\n\n\n\n<li>Search function<\/li>\n\n\n\n<li>Links and buttons<\/li>\n\n\n\n<li>multilingual content, if available<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Also in WooCommerce:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Product pages<\/li>\n\n\n\n<li>Cart<\/li>\n\n\n\n<li>Checkout<\/li>\n\n\n\n<li>Shipping options<\/li>\n\n\n\n<li>Tax calculation<\/li>\n\n\n\n<li>Payment methods<\/li>\n\n\n\n<li>Order confirmation emails<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Clear the cache after the update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your website uses a caching system, older CSS, JavaScript, or HTML versions may still be delivered after an update.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can make it appear as though an update has caused a display error, even though only outdated cache data is being displayed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, check for relevant updates if necessary:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the WordPress or plugin cache<\/li>\n\n\n\n<li>an existing server cache<\/li>\n\n\n\n<li>a CDN cache, if used<\/li>\n\n\n\n<li>if necessary, the browser cache<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Afterwards, you should test the affected page again.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What does \u201emaintenance mode\u201c mean during an update?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">During certain updates, WordPress briefly puts the website into maintenance mode. Visitors may temporarily see a notice that the website is briefly unavailable due to maintenance work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Normally, this state lasts only a short time and ends automatically once the update is complete.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress is stuck in maintenance mode after an update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If an update is interrupted, it can happen that WordPress does not properly exit maintenance mode.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typically, a file with the following name then remains in the root directory of the WordPress installation:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>.Maintenance<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">back.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If it is certain that no update is running and WordPress still permanently displays the maintenance message, this file can be removed via the cPanel File Manager or FTP.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Delete <code>.Maintenance<\/code> not during an actual ongoing update. First, check whether the update process has really been aborted or completed.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What to do if the website stops working after an update?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If an error occurs immediately after an update, you should not indiscriminately change other components.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First, try to narrow down which update might have caused the error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What was updated immediately before the error?<\/li>\n\n\n\n<li>Is only a specific function affected?<\/li>\n\n\n\n<li>Is the WordPress dashboard still accessible?<\/li>\n\n\n\n<li>Is a specific error message displayed?<\/li>\n\n\n\n<li>Does the error occur on all pages or only in a specific area?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you updated plugins individually and tested after each update, the cause is much easier to identify.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Plugin causes an error after the update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a specific plugin causes issues immediately after being updated, there may be an incompatibility with WordPress, the theme, PHP, or another plugin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the dashboard is still accessible, you should first check the affected feature and the available information about the plugin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the event of severe problems, it may be necessary to temporarily deactivate the plugin. How this works is explained in our guide <a href=\"\/en\/help\/wordpress\/wordpress-plugin-deaktivieren-loeschen\/\">Deactivate or delete WordPress plugins<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On a production website, you should ensure that a recovery option is available before making any further changes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Can I restore an older plugin version?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Technically, a so-called <strong>Rollback<\/strong> be possible to an older version. However, this should not be done without careful consideration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An older version may contain known security vulnerabilities or no longer match the current database structure. Furthermore, some updates modify stored data, so simply replacing the plugin files does not necessarily restore the previous state completely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In critical problems, a complete backup created before the update is often the cleaner recovery option.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Update WordPress manually<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress can generally also be updated manually. In the process, current WordPress files are downloaded and certain files or directories of the existing installation are replaced in a controlled manner.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, for normal operation, updating via the WordPress dashboard is much more convenient and less prone to errors.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A manual update may be necessary, for example, if:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the automatic update keeps failing<\/li>\n\n\n\n<li>the dashboard cannot be used for the update<\/li>\n\n\n\n<li>a damaged WordPress core installation needs to be repaired<\/li>\n\n\n\n<li>a special technical situation requires manual intervention<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>For beginners:<\/strong> If the normal update via the WordPress dashboard works, there is usually no reason to update WordPress manually via FTP.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Manually update WordPress: Basic principle<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">During a manual update, the current WordPress version is obtained from the official WordPress website and the existing installation is updated with the latest core files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the process, individual content and the existing configuration must not simply be overwritten or deleted.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Of particular importance are, among others:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-content<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-config.php<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the directory <code>wp-content<\/code> include, among other things, plugins, themes, and uploads. The file <code>wp-config.php<\/code> contains central settings of your WordPress installation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Since errors during a manual update can render the website unusable, we recommend this method only if you know exactly which files may be replaced.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Never download WordPress from an unknown source<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you need WordPress for a manual installation or update, use exclusively a trusted official source.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not download supposedly \u201eoptimized,\u201c modified, or otherwise offered WordPress packages from unknown download websites.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same applies to plugins and themes. In particular, so-called \u201enulled\u201c premium plugins or themes from unofficial sources can contain tampered code and pose a significant security risk.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">PHP Version and WordPress Updates<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress, themes, and plugins have specific requirements regarding the server's PHP version. Therefore, with a very old PHP version, it can happen that a current software version is no longer supported.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Conversely, very old plugins or themes can cause problems with a newer PHP version.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If WordPress warns you about an unsupported PHP version before an update, you should take this message seriously and first check the compatibility of your website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not blindly change the PHP version of a live website at the same time as numerous WordPress, plugin, and theme updates. Otherwise, troubleshooting becomes unnecessarily difficult if a problem occurs afterward.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Outdated plugins without updates are a problem<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An installed plugin that has not been maintained for a long time should be critically reviewed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That does not automatically mean that every older plugin is insecure. However, if updates are missing for a long time and the extension is no longer tested with current WordPress or PHP versions, the risk of future compatibility and security issues increases.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, regularly check whether your installed plugins:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>still under active development<\/li>\n\n\n\n<li>are actually needed for the website<\/li>\n\n\n\n<li>are compatible with your WordPress version<\/li>\n\n\n\n<li>durch eine gepflegte Alternative ersetzt werden sollten<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Nicht mehr ben\u00f6tigte Plugins solltest du nicht einfach jahrelang installiert lassen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Updates nicht monatelang sammeln<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Es ist keine gute Wartungsstrategie, eine WordPress-Website monatelang nicht anzusehen und anschliessend WordPress, 25 Plugins, mehrere Themes und gleichzeitig PHP zu aktualisieren.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Je gr\u00f6sser der Versionssprung und je mehr Komponenten gleichzeitig ver\u00e4ndert werden, desto schwieriger wird die Fehlersuche.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Regelm\u00e4ssige, kontrollierte Wartung ist wesentlich einfacher als seltene Grossaktionen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Wie oft sollte ich nach WordPress-Updates schauen?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">F\u00fcr eine aktiv betriebene Website solltest du Updates regelm\u00e4ssig kontrollieren. Sicherheitsrelevante Aktualisierungen sollten zeitnah eingespielt werden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wie h\u00e4ufig eine manuelle Kontrolle notwendig ist, h\u00e4ngt davon ab, welche automatischen Updates und \u00dcberwachungsmechanismen du verwendest und wie kritisch deine Website ist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bei einem Onlineshop oder einer gesch\u00e4ftskritischen Website ist ein strukturierter Wartungsprozess sinnvoller als gelegentliches Aktualisieren \u201ewenn man gerade daran denkt\u201c.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Warum ein gr\u00fcnes Update-Symbol nicht die ganze Wartung ersetzt<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eine Website ist nicht automatisch sicher und technisch gesund, nur weil WordPress keine verf\u00fcgbaren Updates mehr anzeigt.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Zu einer vern\u00fcnftigen WordPress-Wartung geh\u00f6ren zus\u00e4tzlich beispielsweise:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>funktionierende Backups<\/li>\n\n\n\n<li>aktuelle PHP-Version<\/li>\n\n\n\n<li>\u00dcberpr\u00fcfung nicht mehr ben\u00f6tigter Plugins und Themes<\/li>\n\n\n\n<li>sichere Benutzerkonten und Passw\u00f6rter<\/li>\n\n\n\n<li>Kontrolle wichtiger Website-Funktionen<\/li>\n\n\n\n<li>\u00dcberwachung auf technische Fehler<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Updates sind also ein zentraler Bestandteil der Wartung, aber nicht der einzige.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Typische Fehler bei WordPress-Updates<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Updates \u00fcber Monate ignorieren<\/li>\n\n\n\n<li>vor gr\u00f6sseren Updates kein Backup besitzen<\/li>\n\n\n\n<li>viele kritische Komponenten gleichzeitig aktualisieren und nicht testen<\/li>\n\n\n\n<li>nach einem Update nur das Dashboard, aber nicht die Website pr\u00fcfen<\/li>\n\n\n\n<li>WooCommerce aktualisieren, ohne Checkout und Zahlungsablauf zu testen<\/li>\n\n\n\n<li>Theme aktualisieren, obwohl direkte \u00c4nderungen am Parent-Theme vorgenommen wurden<\/li>\n\n\n\n<li>PHP, WordPress, Theme und s\u00e4mtliche Plugins gleichzeitig \u00e4ndern<\/li>\n\n\n\n<li>Updates w\u00e4hrend des Vorgangs abbrechen<\/li>\n\n\n\n<li>veraltete und nicht mehr ben\u00f6tigte Plugins installiert lassen<\/li>\n\n\n\n<li>WordPress, Plugins oder Themes aus unbekannten Quellen beziehen<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Note:<\/strong> Updates sind kein Risiko, das man deshalb vermeiden sollte. <strong>Nicht zu aktualisieren ist langfristig das gr\u00f6ssere Risiko.<\/strong> Entscheidend ist, Aktualisierungen regelm\u00e4ssig, mit vorhandener Sicherung und anschliessender Funktionskontrolle durchzuf\u00fchren.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress, Plugins und Themes sollten regelm\u00e4ssig aktualisiert werden. Updates schliessen Sicherheitsl\u00fccken, beheben Fehler, verbessern die Kompatibilit\u00e4t und bringen neue oder \u00fcberarbeitete Funktionen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verf\u00fcgbare Aktualisierungen findest du zentral unter <strong>Dashboard \u2192 Updates<\/strong>. Vor gr\u00f6sseren \u00c4nderungen solltest du sicherstellen, dass eine aktuelle und wiederherstellbare Sicherung deiner Website vorhanden ist. Bei komplexen Websites und Onlineshops empfiehlt es sich, kritische Updates kontrolliert und gegebenenfalls zuerst in einer Staging-Umgebung zu testen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nach jeder relevanten Aktualisierung solltest du die wichtigsten Bereiche deiner Website kontrollieren. Bei WooCommerce geh\u00f6ren dazu insbesondere Produktseiten, Warenkorb, Checkout, Versand, Steuern und Zahlungsmethoden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn ein Plugin nach einer Aktualisierung Probleme verursacht, hilft dir unsere Anleitung zum <a href=\"\/en\/help\/wordpress\/wordpress-plugin-deaktivieren-loeschen\/\">Deaktivieren und L\u00f6schen von WordPress-Plugins<\/a>. Eigene Theme-Anpassungen solltest du mit einem <a href=\"\/en\/help\/wordpress\/wordpress-child-theme-erstellen\/\">WordPress Child-Theme<\/a> updatesicher umsetzen.<\/p>","protected":false},"excerpt":{"rendered":"<p>Regelm\u00e4ssige Updates geh\u00f6ren zu den wichtigsten Aufgaben bei der Verwaltung einer WordPress-Website. Dabei geht es nicht nur um neue Funktionen. Aktualisierungen beheben Fehler, verbessern die Kompatibilit\u00e4t und schliessen vor allem bekannte Sicherheitsl\u00fccken in WordPress, Plugins und Themes. WordPress besteht dabei nicht nur aus dem eigentlichen WordPress-System, dem sogenannten WordPress Core. Eine typische Website verwendet zus\u00e4tzlich [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[80],"doc_tag":[],"class_list":["post-22351","docs","type-docs","status-publish","hentry","doc_category-wordpress"],"year_month":"2026-09","word_count":3150,"total_views":"9","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"WordPress","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/wordpress\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22351","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22351"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22351\/revisions"}],"predecessor-version":[{"id":22353,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22351\/revisions\/22353"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22351"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22351"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22351"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}