# amasty/module-mage-248-fix

> Fix several issues on Magento 2.4.8 version by Amasty

`composer require amasty/module-mage-248-fix`

Canonical URL: https://packagento.com/amasty/module-mage-248-fix

## At a glance

- **Vendor**: amasty (https://packagento.com/amasty.md)
- **Latest version**: 1.0.6 — released 2026-01-19
- **Pricing**: Free
- **Package type**: Magento 2 module
- **Status**: active, accepting new buyers

## Installation

Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them.

1. **Sign in or create an account** at https://packagento.com/customer/account/.

2. **Add the package to your account.** Open https://packagento.com/amasty/module-mage-248-fix and complete the free checkout. A licence is minted automatically.

3. **Create or pick a project, then activate the licence on it.**
   - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/.
   - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project.

4. **Add the project credentials to your Magento codebase.**

   Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`:

   ```json
   {
     "http-basic": {
       "packagento.com": {
         "username": "ppk_live_...",
         "password": "psk_live_..."
       }
     }
   }
   ```

   Add the Packagento Composer repository to `composer.json`:

   ```json
   {
     "repositories": [
       { "type": "composer", "url": "https://packagento.com" }
     ]
   }
   ```

5. **Install and apply.**

   ```bash
   composer require amasty/module-mage-248-fix:*
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```

## What it does

Fix several issues on Magento 2.4.8 version by Amasty

## README

<h1>Magento 2.4.8 Issues Fix Module</h1>

<h2>Overview</h2>
<p>This module is required to address several specific issues in Magento 2.4.8:</p>
<ul>
    <li>
        <strong><a target="_blank" href="https://github.com/magento/magento2/issues/39817">#39817</a></strong>: Ignored .less styles with <code>min-width: (@screen__l)</code>.
    </li>
    <li>
        <strong><a target="_blank" href="https://github.com/magento/magento2/issues/39806">#39806</a></strong>: Store switcher not working (page served from cache after store switch).
    </li>    <li>
        <strong><a target="_blank" href="https://github.com/magento/magento2/issues/39831">#39831</a></strong>: Calendar popup opens over display.
    </li>
    <li>
        <strong><a target="_blank" href="https://github.com/magento/magento2/issues/39847">#39847</a></strong>: Table prefix is not taken into account.
    </li>
</ul>
<p>By resolving these issues, the module ensures a smoother and more reliable Magento 2.4.8 experience for both administrators and end-users.</p>

<h2>Issue Details</h2>

<h3>Issue #39817: Ignored .less Styles with <code>min-width: (@screen__l)</code></h3>
<p>
    This issue occurs when Magento 2.4.8 ignores styles defined in <code>.less</code> files with the media query <code>min-width: (@screen__l)</code>. 
    As a result, certain responsive styles are not applied, leading to inconsistent or broken layouts on larger screens.
</p>

<h3>Issue #39806: Store Switcher Not Working (Page Served from Cache)</h3>
<p>
    This issue arises when switching between stores using the store switcher functionality. Instead of loading fresh content for the selected store, Magento serves the page from the cache, displaying outdated or incorrect content.
</p>

<h3>Issue #39831: Calendar popup opens over display</h3>
<p>
    Datepicker calendar popup may open over display or in wrong position after scrolling the page.
</p>

<h3>Issue #39847: Table prefix is not taken into account</h3>
<p>
   If you are using a table prefix, there will be an error on the theme change page because the table prefix is not taken into account. Fixed missing table prefix usage.
</p>

<h2>Installation</h2>
<h3>Option 1: Installation via Composer (Recommended)</h3>
<ol>
    <li>Open your terminal and navigate to the root directory of your Magento 2.4.8 installation.</li>
    <li>Run the following command to install the module:
        <pre><code>composer require amasty/module-mage-248-fix -W</code></pre>
    </li>
    <li>Enable the module by running:
        <pre><code>php bin/magento setup:upgrade</code></pre>
        <pre><code>php bin/magento setup:di:compile</code></pre>
        <pre><code>php bin/magento cache:flush</code></pre>
    </li>
</ol>

<h3>Option 2: Manual Installation</h3>
<ol>
    <li>Download the module files from the repository.</li>
    <li>Place the module files in the <code>app/code/Amasty/Mage248Fix</code> directory of your Magento 2 installation.</li>
    <li>Run the following commands to enable the module:
        <pre><code>composer require wikimedia/less.php:^5.3.1</code></pre>
        <pre><code>php bin/magento setup:upgrade</code></pre>
        <pre><code>php bin/magento setup:di:compile</code></pre>
        <pre><code>php bin/magento cache:flush</code></pre>
    </li>
</ol>
<h4>Cloud environment</h4>
<p>
    In the Magento Cloud environment, the file system is read-only. 
    Therefore, you need to manually replace the file 
    <code>[magento-root-folder]/lib/web/css/source/lib/_responsive.less</code> 
    with the one provided by the module: 
    <code>[Amasty_Mage248Fix]/lib/web/css/source/lib/_responsive.less</code>, 
    before pushing your changes to the branch.
</p>

<h2>Requirenements</h2>
<p>This module require:</p>
<ul>
    <li>Magento 2.4.8 version</li>
    <li>Amasty Base module exists</li>
    <li>wikimedia/less.php:^5.3.1</li>
</ul>

<h2>Configuration</h2>
<p>No additional configuration is required. The module automatically applies the fixes upon installation and activation.</p>

<p>The issues above partially break the functionality of Amasty modules; however, they can be reproduced without our modules being installed and may generate problems on a clean Magento instance. This is why we made this package public.</p>

_(README truncated for .md surface. Full README on https://packagento.com/amasty/module-mage-248-fix.)_

## Recent Versions

| Version | Released |
|---|---|
| 1.0.6 | 2026-01-19 |
| 1.0.5 | 2025-10-15 |
| 1.0.4 | 2025-08-13 |
| 1.0.3 | 2025-06-11 |
| 1.0.2 | 2025-05-06 |
| 1.0.1 | 2025-04-22 |
| 1.0.0 | 2025-04-17 |

## Dependencies

### Require

| Package | Constraint |
|---|---|
| amasty/base | >=1.21.1 |
| magento/framework | ~103.0.8.0 |
| php | >=8.1 |
| wikimedia/less.php | ^5.3.1 |

## Quality

Latest release (1.0.6) passes the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers.


### Compatibility

Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | not tested | not tested | – | – |
| 2.4.8 | – | not tested | not tested | – |
| 2.4.9 | – | – | not tested | not tested |


### Code Quality

Advisory checks against the module's source. Never affect the Compatibility verdict — a phpcs finding can't make a module incompatible.

#### Static Analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Pass | 0 |  |
| PHPMD | Warning | 2 | 2 rule violations (UnusedFormalParameter:2) |
| Cpd | Pass | 0 |  |
| Composer validate | Info | 2 | valid; 2 advisory notes (composer validate --strict) |

#### PHPStan

Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | Error | Error | – | – |
| 2.4.8 | – | Error | Error | – |
| 2.4.9 | – | – | Error | Error |


### Tests

Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately.

#### Unit Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |

#### Integration Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |


### Security

Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| Composer audit | N/A | 0 | no resolvable dependency tree to audit — Your requirements could not be resolved to an installable set of packages. Problem 1 |
| Malware scan | Pass | 0 |  |

## Licence and pricing

Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step.

Refundable within 14 days of first purchase via https://packagento.com/account/refunds/.

## Install via Claude Code or any MCP client

The Packagento MCP server can run the licence + project + Composer steps above in one tool call:

```
purchase_and_install_packages(
  composer_names=["amasty/module-mage-248-fix"],
  project_id="proj_xxx"
)
```

This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup.

## Vendor

amasty is a Magento 2 vendor on Packagento. See https://packagento.com/amasty.md for their full catalogue.