Magento Upload Image in system.xml is not display the correct path

Magento Upload Image in system.xml is not display the correct path

October 6, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento Upload Image in system.xml is not display the correct path

Title: Solving Magento Image Upload Issues: Troubleshooting system.xml Configuration

Hello there! I hope this post finds you well and that you’re ready to dive into the world of Magento system configuration files. Today, we’re going to tackle a common issue many developers face when working with image fields in the admin panel.

The Mystery of Missing Upload Directories

You’ve created an image field on your admin panel using system.xml, but something isn’t quite right. When you upload an image, Magento saves it correctly at media/theme/default, but the preview shows a broken image with the path media/default. Somehow, that crucial theme directory is missing.

Let’s roll up our sleeves and get to the bottom of this!

Understanding Your Configuration File

First things first—let me break down your current configuration for you:

<bankicon translate="label comment">
    <label>Bank Icon</label>
    <comment>Allowed file types: jpeg, gif, png.</comment>
    <frontend_type>Image</frontend_type>
    <backend_model>adminhtml/system_config_backend_image</backend_model>
    <upload_dir config="system/filesystem/media" scope_info="1">theme</upload_dir>
    <base_url type="media" scope_info="1">theme</base_url>
    <sort_order>5</sort_order>
    <show_in_default>1</show_in_default>
    <show_in_website>1</show_in_website>
    <show_in_store>0</show_in_store>
</bankicon>

You’ve set up an image field called bankicon with the following key properties:

  • Image upload directory: You’ve specified that images should be uploaded to theme under the media folder.
  • Base URL for image preview: Similarly, you’ve configured the base URL to point at theme.
  • Backend model: You’re using a default Magento backend model for managing this field.

The Root of the Problem

Let’s examine your issue with fresh eyes. The problem lies in how Magento interprets the scope_info attribute in your configuration.

When you set scope_info="1", you’re essentially telling Magento to use the store scope for these settings. However, when it comes to image uploads and base URLs, Magento expects a specific format for the path—something like {{media_url}}theme/default.

Unfortunately, providing just theme alone doesn’t work, as Magento isn’t intelligent enough to understand that you mean media/theme/default in this context.

The Solution: A Workaround That Works

To fix this issue, we need to provide a different configuration for the base_url and upload_dir. Here’s what I recommend:

<bankicon translate="label comment">
    <label>Bank Icon</label>
    <comment>Allowed file types: jpeg, gif, png.</comment>
    <frontend_type>Image</frontend_type>
    <backend_model>adminhtml/system_config_backend_image</backend_model>
    <upload_dir config="system/filesystem/media" scope_info="1">theme/default</upload_dir>
    <base_url type="media" scope_info="1">{{media_url}}theme/default/</base_url>
    <sort_order>5</sort_order>
    <show_in_default>1</show_in_default>
    <show_in_website>1</show_in_website>
    <show_in_store>0</show_in_store>
</bankicon>

Here’s what we’ve changed:

  • Upload directory: We’ve updated theme to theme/default. This tells Magento exactly where to store the uploaded images—under the default theme in your media folder.
  • Base URL for image preview: I’ve added {{media_url}} and / at the beginning of your base URL. This ensures that when an image is displayed, it’s properly prefixed with the correct media URL.

Testing Your Fix

After implementing these changes, save your configuration file and clear any cache in your Magento installation. Now, head back to your admin panel and try uploading an image again.

If everything goes well, you should see the uploaded image correctly previewed at media/theme/default!

Remember, this is just a workaround for Magento’s quirks with system.xml configuration files. It’s always best practice to consider using other methods like custom modules or configuration management tools whenever possible.

Conclusion

We’ve explored an intriguing issue today—one that can leave even seasoned developers scratching their heads! By digging deeper into the inner workings of Magento’s system configuration, we were able to identify a solution that should fix your broken image previews and ensure your images are stored correctly.

If you found this post helpful, be sure to check out Laravel Company for more in-depth guides on Magento development and other web technologies. Happy coding!

Themes Admin Configuration Orders

Our network