An online shop is software in continuous operation: core, extensions, theme, server and database keep evolving, and postponing updates is paid for later in effort. This category describes what plannable maintenance looks like — keeping track of version levels, applying changes in a staging environment first, assessing dependencies between extensions, agreeing maintenance windows with sales and preparing rollback paths. Added to this are topics such as database upkeep, clearing out old orders and media, deliverability of shop emails and documenting responsibilities and access credentials. The goal is operations in which updates are routine rather than an emergency — even when internal IT capacity is limited. We also show how to write down a maintenance plan that a stand-in can work through without asking questions.
On this page you will find all posts on the topic “Maintenance & updates”. The newest posts are at the top.
Below each title there is a short text about it. Click on a post. Then you can read the whole text.
Above the list you also see the other topics. At the bottom, a link takes you back to all posts.
WordPress 7.1.2 closed a critical flaw and the fix was backported to 4.7 as a courtesy. What older branches receive, what they do not, and when to move up.
Resolvers may keep serving stale DNS answers for 1 to 3 days. How a shop moves servers without losing orders, cron jobs or payment notifications.
Where the hosting provider’s responsibility ends and maintenance begins: a matrix across every layer of the shop, questions to ask and clear handover points.
Debian 11, MariaDB 10.6 and MySQL 8.0 dropped out of maintenance in 2026. How to inventory distribution, database and PHP and plan the upgrades with lead time.
TYPO3 v12 ends on 30 April 2026, Joomla 5.x on 13 October 2026, Drupal 10 on 9 December 2026. The end dates and the lead time a version jump needs.
How a change freeze enters the maintenance plan: a calendar per change class, an exception path for security fixes, the October list and on-call windows.
On 25 October 2026 the hour from 2 to 3 occurs twice. What that means for cron jobs, timestamps and daily reports in your shop, and how to prepare for it.
When an extension license expires, the code keeps running - only without updates. How to make expiry dates visible before the update path closes for good.
After updates and imports snippets go missing, the fallback language kicks in and hreflang breaks. How to check and maintain your shop's language states.
Agencies build shops, then care slips. How white-label maintenance works: cooperation models, SLA boundaries, tenant separation and reports in your own brand.
When your current maintenance ends, the handover decides: secure the credentials, review the real state in 30 days and switch provider without shop downtime.
Payment integrations age faster than the shop: integration register, deprecation radar, webhook hygiene and daily payment reconciliation as maintenance tasks.
Insurers scrutinise more closely: which patch reports, restore logs and MFA evidence prove the pledges from the risk questionnaire at the time of loss.
Disaster recovery for online shops: a DR plan, tested restores and defined RTO and RPO targets – going beyond plain backups, explained step by step.
Avoid regressions after shop updates: smoke tests, checkout verification, visual regression, staging and rollback as a test plan for safe updates in your store.
Database maintenance for online shops: index optimization, fixing slow queries, cleanup, backups and growth monitoring for fast and stable online stores.
Manage PHP end-of-life safely: 2026 support roadmap, code audit, compatibility checks, staging tests and rollback for predictable PHP upgrades in your store.
Staging environments for safe updates: production parity, database and media sync, smoke tests, blue-green, canary releases and a reliable rollback plan.
Plan and deploy Shopware updates safely: staging environment, regression testing, rollback plans and plugin compatibility for live operations.
Secure WordPress in 2026: core hardening, plugin security, brute-force protection, Web Application Firewall and security monitoring practical guide.
Backup strategies for online shops: plan RPO and RTO, full and incremental backups, off-site storage and restore testing for disaster recovery.
Set up uptime monitoring: synthetic monitoring, real-user monitoring, alerting chains, status pages and SLA tracking for online shops and company websites.
Manage SSL certificates professionally: automated renewal with Let's Encrypt, certificate monitoring, HSTS, TLS configuration and mixed content.
Conduct a plugin audit: identify unnecessary extensions, analyze performance impact, find alternatives and safely deactivate for faster load times.
Emergency plan for a hacked website: detection, containment, forensics, cleanup, hardening and communication – step by step, with clear responsibilities.
Maintenance contract for online shops and websites: SLA tiers, included services, response times, pricing models and the contract clauses worth reading twice.