Magento: Settings has not been loaded. Used default settings Wrong config file size connect.cfg please save Settings again

Magento: Settings has not been loaded. Used default settings Wrong config file size connect.cfg please save Settings again

August 10, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento: Settings has not been loaded. Used default settings Wrong config file size connect.cfg please save Settings again

Solving the Magento Connect Configuration Error

If you’re encountering the “Settings has not been loaded. Used default settings Wrong config file size connect.cfg please save Settings again” error in Magento Connect, don’t worry—you’re not alone. This issue is quite common and can usually be resolved by following a few simple steps.

Understanding the Problem

The error occurs when there’s an inconsistency between your Magento system configuration and the connect.cfg file used for managing extensions. The system is unable to load your saved settings, so it defaults back to its original configuration.

Step 1: Check Your Connect.cfg File

The first thing you should do is verify that your connect.cfg file exists and is correctly configured. This file is typically located in your Magento installation directory at app/etc/connect.cfg.

cd path/to/your/magento/installation
ls -l app/etc/connect.cfg

If the file doesn’t exist or has incorrect permissions (it should be readable), you can create a new one using the following command:

touch app/etc/connect.cfg
chmod 644 app/etc/connect.cfg

Step 2: Verify Your Magento Configuration

Next, ensure that your Magento configuration is correct. Open the app/code/core/Mage/Core/etc/config.xml file and verify that the module_output setting is not set to 0.

<config>
    <global>
        <install_date>2016-12-31 19:57:49</install_date>
        <theme>
            <default>
                <template>
                    <layout>
                        <package>
                            <name>
                                <area>
                                    <design>
                                        <layout_file></layout_file>
                                    </design>
                                </area>
                            </name>
                        </package>
                    </layout>
                </template>
            </default>
        </theme>
        <modules>
            <Mage_All active="true">
                <codePool>core</codePool>
            </Mage_All>
        </modules>
        <resources>
            <db>
                <table prefix="mage_" name="all_tables_setup" setup="default_setup">
                    <connection>
                        <use_mysqli "1"/>
                        <host><![CDATA[localhost]]></host>
                        <user><![CDATA[root]]></user>
                        <password><![CDATA[your_password_here]]></password>
                        <dbname><![CDATA[magentodb]]></dbname>
                        <active>1</active>
                    </connection>
                </table>
            </db>
        </resources>
    </global>
</config>

If the module_output setting is missing or set to 0, add or update it as follows:

<modules>
    <Mage_Compiler active="false">
        <codePool>core</codePool>
    </Mage_Compiler>
    <Mage_Core active="true">
        <codePool>core</codePool>
        <output><![CDATA[0]]></output>
    </Mage_Core>
    <Mage_All active="true">
        <codePool>core</codePool>
    </Mage_All>
</modules>

Step 3: Remove the var Folder

If steps 1 and 2 don’t resolve the issue, try deleting the contents of your Magento var folder.

rm -rf path/to/your/magento/installation/var/*

This folder contains cache files that might be causing conflicts. Deleting its contents forces the system to regenerate these files from scratch.

Step 4: Flush Your Cache

Finally, flush your Magento cache by running the following command:

php -f path/to/your/magento/installation/shell/index.php -- --flush-all-cache

This command clears all cached data and forces a complete rebuild.

Conclusion

If you’ve followed these steps and are still encountering issues, there might be a more complex problem at play. In this case, I recommend reaching out to the Magento support team or consulting with an experienced developer.

Remember, keeping your Magento installation up-to-date is crucial for avoiding these kinds of errors. Always update to the latest stable version whenever possible. For more information on best practices for managing your Magento system, feel free to explore our comprehensive guides at Laravel Company.

Happy troubleshooting!

Security Extensions Themes Configuration

Our network