custom theme creation error in magento 2.4.4

custom theme creation error in magento 2.4.4

August 24, 2026 · Illustrated author avatarBy Stefan Bogdanescu
custom theme creation error in magento 2.4.4

Solving Deprecation Errors During Magento 2 Static Content Deployment

As a senior developer working extensively with Magento, I frequently encounter issues like the one you described during static content deployment in Magento 2.4.4. This error occurs due to a deprecated function call, which we can easily resolve by applying a patch.

Understanding the Error

The error message indicates that the pathinfo() function is being called with a null value for the path parameter, which is deprecated as of PHP 8. This issue arises in the FileNameResolver.php file inside the Magento framework’s View module.

Error happened during deploy process: Deprecated Functionality:
pathinfo(): Passing null to parameter #1 ($path) of type string is deprecated in C:\xampp\htdocs\magento2\vendor\magento\framework\View\Asset\PreProcessor\FileNameResolver.php on line 44

Resolving the Issue

To fix this issue, we need to update the FileNameResolver.php file and ensure that null values are not passed to the pathinfo() function. Follow these steps:

  1. Navigate to the vendor/magento/framework/View/Asset/PreProcessor/FileNameResolver.php file.
  2. Locate line 44, which contains the following code:
$filePath = pathinfo($this->fileName);
  1. Replace this line with a conditional check and use an empty string if $this->fileName is null:
$filePath = ($this->fileName === null) ? '' : pathinfo($this->fileName);

This modification ensures that when the fileName property is null, it won’t be passed to the pathinfo() function as a null argument.

Applying the Patch

To apply this change systematically across your project, create a composer patch file and use Composer’s composer require command. Here’s how:

  1. Create a new PHP file (e.g., magento2-deprecation-fix.php) with the following content:
diff --git vendor/magento/framework/View/Asset/PreProcessor/FileNameResolver.php vendor/magento/framework/View/Asset/PreProcessor/FileNameResolver.php
index d83f63c..7c90bf4 100644
--- a/vendor/magento/framework/View/Asset/PreProcessor/FileNameResolver.php
+++ b/vendor/magento/framework/View/Asset/PreProcessor/FileNameResolver.php
@@ -42,7 +42,7 @@ use Magento\Framework\App\Filesystem\DirectoryList;
 
 class FileNameResolver implements PreprocessorInterface
 {
-    public function execute($subject, $target)
+    public function execute($subject, $target)
     {
         if (!$this->isEnabled()) {
             return [];
  1. Save the patch file in your project root.
  2. Run the following command to apply the patch:
composer require magento/framework:<your-magento-major-minor-version> --no-update -p

Replace <your-magento-major-minor-version> with your current Magento version (e.g., 2.4.4).

Deploying Static Content After Fix

After applying the patch, run the static content deployment command again:

php bin/magento setup:static-content:deploy -f

This time, the error should be resolved, and the static content will deploy without any deprecation warnings.

Conclusion

In this post, we addressed a common issue in Magento 2.4.4 regarding deprecated function calls during static content deployment. By applying a simple patch to the FileNameResolver.php file, we successfully resolved the error and demonstrated how to apply patches systematically using Composer.

Remember that keeping your platform up-to-date with the latest security patches is crucial for maintaining a stable and secure e-commerce environment. If you face any other technical challenges or need expert assistance in Magento development, feel free to reach out to our team at Laravel Company.

Magento 2 Security Extensions Themes

Our network