# Magento Support UK

Source: https://dijitulsupport.co.uk/magento-support/
Updated: 2026-10-10

> dijitul support fixes and maintains Magento 2 (Adobe Commerce and Magento Open Source) stores for UK retailers: security patches, 2.4.x upgrades, indexer and cron problems, checkout errors and extension conflicts. Ad-hoc Magento work is £45 an hour + VAT, monthly plans start at £25 a month + VAT, and version upgrades are quoted.

## Common symptoms

- Products or price changes not showing on the front end
- Admin shows "One or more indexers are invalid"
- Checkout spins forever or shows a blank payment step
- "There has been an error processing your request" with an error log number
- Order emails not sending because cron has stopped
- Search returns nothing after a hosting change

## Key facts

- Magento 2.4.8 was released on 8 April 2025 and is supported to April 2028
- Magento 2.4.6 security support ended 14 March 2026; 2.4.5 and 2.4.6 software support ends 11 August 2026
- Upgrades done with Composer on staging, with extension compatibility checked first
- Indexers, cron, Elasticsearch or OpenSearch and Redis issues diagnosed
- Magento 1 stores (end of life June 2020) migrated or replaced, quoted
- Ad-hoc £45 an hour + VAT; plans from £25 a month + VAT

## Magento versions and support dates

Magento 2 (now Adobe Commerce, with a free Magento Open Source edition) is powerful but demanding. Each 2.4.x release has a fixed support window, and running an unsupported version means missing security patches on a system that handles customer and payment data.

| Version | Released | Support |

| 2.4.6 | March 2023 | Security support ended 14 March 2026; software support ends 11 August 2026 |

| 2.4.7 | April 2024 | Supported to April 2027 |

| 2.4.8 | April 2025 | Supported to April 2028 |

Adobe supports upgrading directly from 2.4.5 or 2.4.6 to 2.4.8. Magento 1 has had no official patches since June 2020; if you are still on it, a replatform is overdue.

## Common Magento problems we fix

- **Invalid indexers:** product, price or stock changes not appearing on the front end because indexers are stuck or set to the wrong mode. We reset and reindex with *bin/magento indexer:reindex* and set "Update by Schedule" with working cron.

- **Cron not running:** order emails, indexing, sitemaps and currency rates all depend on cron. A missing crontab after a server move is common.

- **Search broken:** Magento 2.4 requires Elasticsearch or OpenSearch. If the search engine service is down or the wrong version, catalogue search and sometimes category pages fail.

- **Error report numbers:** "There has been an error processing your request" writes a report to *var/report*. We read it to find the failing module.

- **Static content and cache:** missing CSS after deployment because static content was not deployed for the right locale, or Varnish and Redis caches not cleared.

- **Checkout problems:** JavaScript errors from third-party extensions, payment module incompatibility or a misconfigured Content Security Policy.

## Patching and upgrading Magento

Adobe releases security patches on a regular schedule, sometimes with isolated hotfixes for urgent issues. Applying them is not a one-click job: we apply the patch or upgrade through Composer on a staging copy, run *setup:upgrade*, compile dependency injection, deploy static content, then test catalogue, cart, checkout and admin before repeating on live in maintenance mode.

The biggest upgrade risk is extensions. Marketplace and third-party modules must support the new version and its PHP requirement. We list every module, check vendor compatibility, and update, replace or remove as needed. Upgrades are quoted, because a store with five extensions and one with fifty are very different jobs. See also [PHP version upgrade](https://dijitulsupport.co.uk/php-version-upgrade/).

## Security on Magento stores

Magento stores are attractive targets for card skimming attacks that inject JavaScript into checkout. We keep the store patched, check admin users and integrations, make sure the admin URL is not the default, enforce two-factor authentication for admin, and monitor for unexpected changes in files and the *core_config_data* table where skimmers often hide. If you suspect a compromise, see [hacked website repair](https://dijitulsupport.co.uk/hacked-website-repair/).

## Hosting requirements and performance

Magento 2 needs more from its server than most platforms: a supported PHP version, MySQL or MariaDB, OpenSearch or Elasticsearch, and ideally Redis for cache and sessions and Varnish for full-page cache. Running it on basic shared hosting is a common cause of slow category pages and timeouts during checkout.

When a Magento store is slow we check whether full-page cache is actually being hit, whether the store is in production mode rather than developer or default mode, and whether third-party extensions are adding heavy observers or plugins to every request. See [website speed optimisation](https://dijitulsupport.co.uk/website-speed-optimisation/) for the wider approach.

## Magento support prices

Ad-hoc Magento fixes are **£45 an hour + VAT**, 30-minute minimum then 15-minute blocks. For ongoing care, our plans run from **£25 a month + VAT** (Essential: updates applied and checked, daily backups, uptime and security monitoring), through **£50 a month + VAT** (Business: plus an hour of fixes and priority support) to **£99 a month + VAT** (Complete: three hours a month plus IT and Microsoft 365 helpdesk).

Because Magento upgrades vary so much, they are quoted. Large custom builds may involve our development team at [dijitul developments](https://dijituldevelopments.co.uk/). See [ecommerce support](https://dijitulsupport.co.uk/ecommerce-support/) or [request a quote](https://dijitulsupport.co.uk/quote/).

## FAQs

### Which Magento version should I be on?

A 2.4.x release that is still inside Adobe's support window. Magento 2.4.8, released in April 2025, is supported to April 2028. dijitul can check your version and quote an upgrade.

### Why are my Magento product changes not showing?

Usually invalid indexers or stopped cron. Magento needs cron running to process scheduled indexing. dijitul checks the crontab, reindexes and clears caches, typically as a short ad-hoc fix at £45 an hour + VAT.

### How much does a Magento upgrade cost?

It depends on your current version, PHP version, hosting and how many extensions you run. dijitul quotes Magento upgrades after an audit, because a lightly customised store and a heavily extended one are very different jobs.

### Is Magento 1 still safe?

No. Magento 1 has had no official security patches since June 2020. Stores still on it should move to Magento 2 or another platform. dijitul can advise and quote a migration.

### Can you work on Adobe Commerce Cloud?

Yes, for application-level work such as extensions, configuration, patches and code fixes. Infrastructure on Adobe Commerce Cloud is managed by Adobe, so platform-level incidents such as server outages or environment faults go to Adobe support, and dijitul can help you raise them.

## Pricing and contact

Support plans from £25 a month + VAT, or £45 an hour + VAT for one-off fixes. Plans: Essential £25/month + VAT (Website software updates (core, plugins, themes) applied and checked, Daily backups, Uptime monitoring, Security monitoring); Business £50/month + VAT (Everything in Essential, 1 hour of fixes or changes every month, Priority support); Complete £99/month + VAT (Everything in Business, 3 hours of fixes or changes every month, IT and Microsoft 365 helpdesk for your team). Ad-hoc support is £45 an hour + VAT. The first 30 minutes are the minimum charge, then we bill in 15-minute blocks. Contact: 01623 650333, support@dijitul.uk, https://dijitulsupport.co.uk/contact/