Joomla Core and Extension Update — Safe and Without Data Loss

After a Joomla update, the site may stop opening — a common problem. Most often, the cause is extension incompatibility. Updating Joomla is routine, but often breaks the site: a flawed patch, a forgotten backup, component incompatibility. We update dozens of sites without downtime. With 8+ years of experience and over 200 successful updates, we guarantee stability. 95% of updates proceed without errors, and if issues arise, recovery takes no more than 15 minutes. Recently, we updated an online store from J3.10 to J4: after the update, the cart component stopped working. We found that a third-party plugin was incompatible with the new version. We selected a compatible alternative, tested it — the site worked without data loss.

Such situations occur regularly. It's important to follow a proven algorithm. As written in the official Joomla documentation, a backup is mandatory before any update. We add compatibility audit and a test environment to that. The result is stable operation without surprises.

How to safely update the Joomla core?

Full backup

Before any update, create a backup. Use Akeeba Backup or CLI:

# Files
tar czf /backups/joomla-$(date +%Y%m%d).tar.gz /var/www/yourdomain.com

# Database
mysqldump -u root joomla_db > /backups/joomla-db-$(date +%Y%m%d).sql

Check extension compatibility

Before updating the core, run php cli/joomla.php core:check-updates --verbose. It shows which extensions are incompatible. If there are many, don't rush the update. In 90% of cases, incompatibility is resolved in 2–3 days. For example, Fabrik or VirtueMart often require updates. Contact us for a compatibility assessment of your site.

Update via CLI (Joomla 4+)

CLI update is faster and more reliable than the web panel. More details in the Joomla documentation.

# Check for updates
php cli/joomla.php core:check-updates

# Update the core
php cli/joomla.php core:update

# Update extensions
php cli/joomla.php extension:update --all

Via web panel

Components → Joomla! Update → Update button. Joomla downloads the package, applies the patch, updates the database. Afterwards, double-check the site's operation.

Eliminating extension incompatibility

A typical problem: after the update, the component throws an error or disappears from the panel. Solution:

1. Roll back the update from the backup.
2. Contact the extension developer — often a patch is released within a week.
3. If you can't wait, look for an alternative. For example, instead of RokSprocket, you can use Custom Modules.

In such cases, we conduct an audit and select compatible alternatives turnkey. Get a consultation — it's free.

Why does migration from J3 to J5 require an intermediate update?

There is no direct update from J3 to J5 — you need a sequential migration through J4. Update scheme:

For Joomla 3 → 4, there is a Joomla Update component with automatic migration: Components → Joomla! Update → install Joomla Pre-Update Check. It will check compatibility of all extensions.

Table: CLI vs web update

Updating commercial extensions

Commercial extensions (RokSprocket, K2 Pro) are not updated through the standard updater. You need to:

1. Log in to the developer's site
2. Download the latest version (authorized access)
3. Install via Extensions → Manage → Upload (update, not a new installation)

What mistakes are most often made when updating Joomla?

The most common — updating without a backup. Recovery after a failure can take hours, and if there is no copy, data loss. The second most common — ignoring compatibility checks. Even popular components are sometimes incompatible. The third — updating on production without a test site. Always update on a copy first. The fourth — incorrect PHP version: Joomla 5 requires PHP 8.0+. Check requirements before starting. We insist on these rules — it's a guarantee that the site won't crash. We fix the cost of work before it starts, and if deadlines are missed, we return the money — that's our practice.

What's included in the Joomla update service

• Audit of current version and extensions — compatibility check, vulnerability assessment.
• Creating a full backup — files + database.
• Updating the core to the target version (LTS or latest stable).
• Updating all extensions, including commercial ones.
• Fixing incompatibilities — selecting alternatives or applying patches.
• Testing — checking all critical functions.
• Documentation — report on the work done.

Timeline: scheduled update — from 1 to 3 hours. Complex migration — up to 2 days. The cost is fixed before work begins, guaranteeing savings in time and budget. Order a Joomla update from us — get a site ready to use without errors. Over 8 years of experience, certified engineers.

Website Technical Support: Updates, Monitoring, SLA

A website on Laravel 8 with PHP 7.4. PHP 7.4 is no longer supported, Laravel 8 also doesn't receive security updates. The hosting provider warned about the mandatory PHP update to 8.1 — after the update, two plugins and one library broke, the site went down. We regularly encounter such scenarios: a project without regular maintenance turns every environment update into an emergency.

This case is not an exception, but a rule. Commercial websites lose conversions due to slow loading, vulnerabilities, and downtime. We take care of monitoring, dependency updates, backups, and SLA — so you can focus on business, not the server.

Without systematic support, every environment update becomes a surprise: dependencies break, performance drops, security holes appear. Website technical support is insurance against such surprises and a guarantee of stable operation.

What Actually Goes into Website Technical Support?

Support is not "answering a call when something breaks." It is systematic prevention of breakdowns.

Dependency updates. Composer packages, npm packages, CMS or framework. composer audit and npm audit show known vulnerabilities. Dependabot or Renovate create automatic PRs — the support task is to verify that the update didn't break staging and merge.

Updates types: patch (1.2.3 → 1.2.4, only bugfix, safe), minor (1.2.0 → 1.3.0, new features with backward compatibility, usually safe), major (1.x → 2.x, breaking changes, require testing). Ignoring updates for 6+ months accumulates tech debt: bigger gap, more work.

WordPress is a separate story. The platform's popularity makes it a prime attack target. Outdated plugins are the #1 attack vector. Regular updates of core, plugins, themes + correct file permissions + WAF are the necessary minimum. Our experience shows that automatic WordPress Core updates without a test environment are a risk we do not allow.

How Does Monitoring Prevent Downtime?

Uptime monitoring. Basic HTTP check every minute. Better Uptime, Upptime (self-hosted), Checkly, New Relic Synthetics. Alert to Telegram or Slack on downtime — and notification upon recovery. If a site is unavailable for 10 minutes during business hours — direct loss.

Performance. TTFB, LCP, INP — we track via Google Search Console (real users, CrUX) and synthetic monitoring (Lighthouse CI, SpeedCurve). Degradation is often gradual — without monitoring you notice it a month later when LCP is already 5s.

Application errors. Sentry is the standard for real-time JavaScript and PHP/Python error tracking. Each unhandled exception with stack trace, request context, browser version. Especially important for errors users don't report — they just leave.

Database. Volume growth, slow queries (MySQL slow query log, pg_stat_statements for PostgreSQL), index size. A table without VACUUM in PostgreSQL grows to gigabytes due to dead tuples. Routine database maintenance is part of support.

Disk space and logs. Is logrotate configured? /var/log/nginx growing without limits and filling the disk — classic. Automatic rotation + alert at disk > 80%.

Why Are Backups Without Verification an Illusion?

A backup without restore verification is not a backup, but an illusion of security. We've seen cases where mysqldump created a 0-byte file due to permission error, and no one checked the contents for months. We guarantee all copies are restorable.

Backup scheme:

• Daily incremental backup of database + media files
• Weekly full backup
• Storage: at least 3 copies, 2 different media, 1 offsite (S3, Backblaze B2)
• Automatic integrity check (pg_restore --list, mysqldump verify)
• Test restore once a quarter in an isolated environment

Retention policy: 7 daily, 4 weekly, 3 monthly. S3 Lifecycle rules automate deletion.

SLA: What Does It Mean in Practice?

SLA (Service-Level Agreement) Wikipedia — specific commitments for response and resolution times:

SLA makes sense only with monitoring — otherwise you learn about problems from users, not systems. A broken button in a form can silently kill conversions for weeks.

Content Update Process

A developer should not be in the chain for editing text on a page. CMS with a convenient editor, role separation (editor edits content, not code), change history. For Laravel projects — Nova, Filament, or headless CMS (Strapi, Contentful) depending on complexity.

Preview before publishing, staged rollout for important changes. If editors work directly on prod — that's a risk.

Typical Situations We Resolve

Website hack: attack vector analysis, cleanup, security hardening (WAF, fail2ban, file permission restrictions). Recovery from backup takes hours, not days — if backups are properly configured. Average costs to eliminate consequences of a hack are significant, including audit and vulnerability closure. Regular support is much cheaper and prevents such incidents.

Performance drop after update: feature flag + ability to quickly rollback. Canary deployment — update 5% of traffic, check metrics, then 100%.

What's Included in the Support Package (Deliverables)

Upon signing the contract, you receive:

• Documentation: infrastructure diagram, access, recovery procedures
• Monitoring: uptime, performance, errors, logs — set up from day one
• Backup: daily/weekly copies with verification
• Dependency updates: monthly audit and update with testing
• SLA response: per priorities from the table above
• Reports: weekly dashboards, monthly review, quarterly tech plan
• Content editing support: editor training, permission setup

Contact us to choose a suitable plan and get an initial audit of your project.

How We Work: Stages

1. Onboarding (3–5 days): audit of current state, setup of monitoring and backups, infrastructure documentation.
2. Regular rhythm: weekly metrics report, monthly update review, quarterly technical audit.
3. Response: per SLA, with recording of cause and resolution time.
4. Development: upon your request — new features, optimization, refactoring.

We have been working since 2016, supporting over 50 projects from landing pages to marketplaces. Our clients save a significant amount per month through preventive measures.

Timelines and Cost

Setting up monitoring and backups: 3–5 days. Regular support — ongoing contract with a fixed number of hours per month or a subscription. Cost is calculated individually after audit. Get a consultation — we will evaluate your project in 1–2 days.

Comparison: Monitoring with Automatic Alerting vs Manual Checking

Automatic monitoring with Better Uptime responds to failures 10 times faster than manual checking.