How to Enable and Disable Custom Magento Extension?how to check which Extensions are installed on a Magento...

If the Dominion rule using their Jem'Hadar troops, why is their life expectancy so low?

Can you take a "free object interaction" while incapacitated?

Why does the frost depth increase when the surface temperature warms up?

Is there a distance limit for minecart tracks?

"Oh no!" in Latin

Why can't I get pgrep output right to variable on bash script?

Magnifying glass in hyperbolic space

Why do Radio Buttons not fill the entire outer circle?

Center page as a whole without centering each element individually

Why is implicit conversion not ambiguous for non-primitive types?

Why would five hundred and five same as one?

Is there a POSIX way to shutdown a UNIX machine?

How to preserve electronics (computers, ipads, phones) for hundreds of years?

How do I lift the insulation blower into the attic?

How do I prevent inappropriate ads from appearing in my game?

Writing in a Christian voice

"Marked down as someone wanting to sell shares." What does that mean?

What is it called when someone votes for an option that's not their first choice?

Make a Bowl of Alphabet Soup

Offset in split text content

Connection Between Knot Theory and Number Theory

How do you say "Trust your struggle." in French?

Is this saw blade faulty?

Error in master's thesis, I do not know what to do



How to Enable and Disable Custom Magento Extension?


how to check which Extensions are installed on a Magento site?How to set extension enable and disableCustom Magento Extension Enable and Disable by my custom admin moduleEnable Cache while installing extension?Extension no longer exists. Why am I able to disable it in the Advanced area in Admin?How to disable a magento extension from admin?Cannot Disable Extensionmultistore and filter, enable and disableCustom extension disable functionality is not workingMagento 2 - add Enable / Disable field for custom moduleHow to enable extensions through terminal?













4















How to Enable and Disable Custom Magento Extension ?










share|improve this question





























    4















    How to Enable and Disable Custom Magento Extension ?










    share|improve this question



























      4












      4








      4


      1






      How to Enable and Disable Custom Magento Extension ?










      share|improve this question
















      How to Enable and Disable Custom Magento Extension ?







      magento-1.9 extensions






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 17 mins ago









      Teja Bhagavan Kollepara

      3,00641949




      3,00641949










      asked Dec 19 '14 at 7:34









      MagentoMagento

      144129




      144129






















          4 Answers
          4






          active

          oldest

          votes


















          7














          The only way to really disable your module is to change



          <active>true</active>


          to



          <active>false</active>


          in your app/etc/modules/foo.xml



          If you want an admin account to be able to do it in the back-end, you can create a config option (with system.xml) to control your module. Although it's not exactly the same as disabling your module, you can make sure your module doesn't do anything by looking at the store config.






          share|improve this answer
























          • Agreed, this is the only reliable way. You can disable it in the admin through System->Configuration->Advanced, but this makes it inactive, yet not disabled. It may still appear on the admin menu for example, but not fully functional.

            – Niels
            Dec 19 '14 at 8:21






          • 2





            This indeed is the most effective way. But instead of opening the .xml file and change the <active> status you could also rename the .xml file to foo.xml.tmp. This also disables the module and is not only quicker/easier, you can also tell by just looking at the contents of app/etc/modules/ which modules are disabled.

            – ForMat
            Dec 19 '14 at 9:02





















          5














          Below are the three ways to disable the modules.




          1. Disabling modules in the Magento backend :


          Go to Magento backend - System > Configuration > Advanced > Disable modules output you can easily disable certain modules.
          You can even select the scope of the configuration (in the top left of the page) and there for disable specific modules only for specific Store Views. This is actually the preferred way of disabling a module.



          (This only disables the output. This means especially, that all the computation is still done, means: Doesn't improve performance!)



          Modifying XML-files :
          In the directory app/etc/modules you can find a bunch of XML-files. While the Magento core-modules are bundled in just a couple of files, in most cases you will find per third party module also a separate XML-file. When you open up the XML-file of for instance our MageBridge extension, you will find the following:



          <config>
          <modules>
          <Namespace_Module>
          <active>true</active>
          <codePool>community</codePool>
          </Namespace_Module>
          </modules>
          </config>


          Now to disable this module, you would change the active-tag from true to false.



          <active>false</active>


          Remember to flush the Magento cache.



          Disabling local modules :



          But this might not solve your problem. If some module is placed in the app/code/local directory it might be overriding a Magento core-class directly, without the use of XML-files. To bypass this problem, you need to temporarily disable all local modules.



          This can be done by opening up the file app/etc/local.xml in which you should change the disable_local_modules-tag to true.



          <disable_local_modules>false</disable_local_modules>


          This should allow you to troubleshoot the problem. Of course there are many more things to troubleshoot when dealing with serious problems, but at least this is a start.






          share|improve this answer

































            2














            By doing the way is two.




            1. in admin, system->configuration->advanced and then disable the module you want.


            2. making your modulename.xml file this line as <active>true</active> to <active>false</active>.(need to flush the cache)



            Hope this is what you need.






            share|improve this answer

































              2














              I stumbled over another way to disable extension in an answer to my own question (admitedly very similar to this one) in this regards which I wanted to share here.



              This was provided by @nintenic (thanks for that) :





              1. In your FTP go to app/etc/modules. This is where all the extension xml files are located.

              2. Create a new folder here called "disabled".

              3. Move the xml file of the extension you wish to disable to this new folder

                (app/etc/modules/disabled).

              4. Now log into the Magento backend and go to > System > Cache Management.

                Click Flush Magento Cache to have Magento recognize the changes.


              This is not the "correct" way. but it's the fastest and easiest; and it's even recommended by some extension developers and hosting providers.







              share|improve this answer























                Your Answer








                StackExchange.ready(function() {
                var channelOptions = {
                tags: "".split(" "),
                id: "479"
                };
                initTagRenderer("".split(" "), "".split(" "), channelOptions);

                StackExchange.using("externalEditor", function() {
                // Have to fire editor after snippets, if snippets enabled
                if (StackExchange.settings.snippets.snippetsEnabled) {
                StackExchange.using("snippets", function() {
                createEditor();
                });
                }
                else {
                createEditor();
                }
                });

                function createEditor() {
                StackExchange.prepareEditor({
                heartbeatType: 'answer',
                autoActivateHeartbeat: false,
                convertImagesToLinks: false,
                noModals: true,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: null,
                bindNavPrevention: true,
                postfix: "",
                imageUploader: {
                brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
                contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
                allowUrls: true
                },
                onDemand: true,
                discardSelector: ".discard-answer"
                ,immediatelyShowMarkdownHelp:true
                });


                }
                });














                draft saved

                draft discarded


















                StackExchange.ready(
                function () {
                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f48838%2fhow-to-enable-and-disable-custom-magento-extension%23new-answer', 'question_page');
                }
                );

                Post as a guest















                Required, but never shown

























                4 Answers
                4






                active

                oldest

                votes








                4 Answers
                4






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                7














                The only way to really disable your module is to change



                <active>true</active>


                to



                <active>false</active>


                in your app/etc/modules/foo.xml



                If you want an admin account to be able to do it in the back-end, you can create a config option (with system.xml) to control your module. Although it's not exactly the same as disabling your module, you can make sure your module doesn't do anything by looking at the store config.






                share|improve this answer
























                • Agreed, this is the only reliable way. You can disable it in the admin through System->Configuration->Advanced, but this makes it inactive, yet not disabled. It may still appear on the admin menu for example, but not fully functional.

                  – Niels
                  Dec 19 '14 at 8:21






                • 2





                  This indeed is the most effective way. But instead of opening the .xml file and change the <active> status you could also rename the .xml file to foo.xml.tmp. This also disables the module and is not only quicker/easier, you can also tell by just looking at the contents of app/etc/modules/ which modules are disabled.

                  – ForMat
                  Dec 19 '14 at 9:02


















                7














                The only way to really disable your module is to change



                <active>true</active>


                to



                <active>false</active>


                in your app/etc/modules/foo.xml



                If you want an admin account to be able to do it in the back-end, you can create a config option (with system.xml) to control your module. Although it's not exactly the same as disabling your module, you can make sure your module doesn't do anything by looking at the store config.






                share|improve this answer
























                • Agreed, this is the only reliable way. You can disable it in the admin through System->Configuration->Advanced, but this makes it inactive, yet not disabled. It may still appear on the admin menu for example, but not fully functional.

                  – Niels
                  Dec 19 '14 at 8:21






                • 2





                  This indeed is the most effective way. But instead of opening the .xml file and change the <active> status you could also rename the .xml file to foo.xml.tmp. This also disables the module and is not only quicker/easier, you can also tell by just looking at the contents of app/etc/modules/ which modules are disabled.

                  – ForMat
                  Dec 19 '14 at 9:02
















                7












                7








                7







                The only way to really disable your module is to change



                <active>true</active>


                to



                <active>false</active>


                in your app/etc/modules/foo.xml



                If you want an admin account to be able to do it in the back-end, you can create a config option (with system.xml) to control your module. Although it's not exactly the same as disabling your module, you can make sure your module doesn't do anything by looking at the store config.






                share|improve this answer













                The only way to really disable your module is to change



                <active>true</active>


                to



                <active>false</active>


                in your app/etc/modules/foo.xml



                If you want an admin account to be able to do it in the back-end, you can create a config option (with system.xml) to control your module. Although it's not exactly the same as disabling your module, you can make sure your module doesn't do anything by looking at the store config.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 19 '14 at 7:40









                MagentoMagento

                144129




                144129













                • Agreed, this is the only reliable way. You can disable it in the admin through System->Configuration->Advanced, but this makes it inactive, yet not disabled. It may still appear on the admin menu for example, but not fully functional.

                  – Niels
                  Dec 19 '14 at 8:21






                • 2





                  This indeed is the most effective way. But instead of opening the .xml file and change the <active> status you could also rename the .xml file to foo.xml.tmp. This also disables the module and is not only quicker/easier, you can also tell by just looking at the contents of app/etc/modules/ which modules are disabled.

                  – ForMat
                  Dec 19 '14 at 9:02





















                • Agreed, this is the only reliable way. You can disable it in the admin through System->Configuration->Advanced, but this makes it inactive, yet not disabled. It may still appear on the admin menu for example, but not fully functional.

                  – Niels
                  Dec 19 '14 at 8:21






                • 2





                  This indeed is the most effective way. But instead of opening the .xml file and change the <active> status you could also rename the .xml file to foo.xml.tmp. This also disables the module and is not only quicker/easier, you can also tell by just looking at the contents of app/etc/modules/ which modules are disabled.

                  – ForMat
                  Dec 19 '14 at 9:02



















                Agreed, this is the only reliable way. You can disable it in the admin through System->Configuration->Advanced, but this makes it inactive, yet not disabled. It may still appear on the admin menu for example, but not fully functional.

                – Niels
                Dec 19 '14 at 8:21





                Agreed, this is the only reliable way. You can disable it in the admin through System->Configuration->Advanced, but this makes it inactive, yet not disabled. It may still appear on the admin menu for example, but not fully functional.

                – Niels
                Dec 19 '14 at 8:21




                2




                2





                This indeed is the most effective way. But instead of opening the .xml file and change the <active> status you could also rename the .xml file to foo.xml.tmp. This also disables the module and is not only quicker/easier, you can also tell by just looking at the contents of app/etc/modules/ which modules are disabled.

                – ForMat
                Dec 19 '14 at 9:02







                This indeed is the most effective way. But instead of opening the .xml file and change the <active> status you could also rename the .xml file to foo.xml.tmp. This also disables the module and is not only quicker/easier, you can also tell by just looking at the contents of app/etc/modules/ which modules are disabled.

                – ForMat
                Dec 19 '14 at 9:02















                5














                Below are the three ways to disable the modules.




                1. Disabling modules in the Magento backend :


                Go to Magento backend - System > Configuration > Advanced > Disable modules output you can easily disable certain modules.
                You can even select the scope of the configuration (in the top left of the page) and there for disable specific modules only for specific Store Views. This is actually the preferred way of disabling a module.



                (This only disables the output. This means especially, that all the computation is still done, means: Doesn't improve performance!)



                Modifying XML-files :
                In the directory app/etc/modules you can find a bunch of XML-files. While the Magento core-modules are bundled in just a couple of files, in most cases you will find per third party module also a separate XML-file. When you open up the XML-file of for instance our MageBridge extension, you will find the following:



                <config>
                <modules>
                <Namespace_Module>
                <active>true</active>
                <codePool>community</codePool>
                </Namespace_Module>
                </modules>
                </config>


                Now to disable this module, you would change the active-tag from true to false.



                <active>false</active>


                Remember to flush the Magento cache.



                Disabling local modules :



                But this might not solve your problem. If some module is placed in the app/code/local directory it might be overriding a Magento core-class directly, without the use of XML-files. To bypass this problem, you need to temporarily disable all local modules.



                This can be done by opening up the file app/etc/local.xml in which you should change the disable_local_modules-tag to true.



                <disable_local_modules>false</disable_local_modules>


                This should allow you to troubleshoot the problem. Of course there are many more things to troubleshoot when dealing with serious problems, but at least this is a start.






                share|improve this answer






























                  5














                  Below are the three ways to disable the modules.




                  1. Disabling modules in the Magento backend :


                  Go to Magento backend - System > Configuration > Advanced > Disable modules output you can easily disable certain modules.
                  You can even select the scope of the configuration (in the top left of the page) and there for disable specific modules only for specific Store Views. This is actually the preferred way of disabling a module.



                  (This only disables the output. This means especially, that all the computation is still done, means: Doesn't improve performance!)



                  Modifying XML-files :
                  In the directory app/etc/modules you can find a bunch of XML-files. While the Magento core-modules are bundled in just a couple of files, in most cases you will find per third party module also a separate XML-file. When you open up the XML-file of for instance our MageBridge extension, you will find the following:



                  <config>
                  <modules>
                  <Namespace_Module>
                  <active>true</active>
                  <codePool>community</codePool>
                  </Namespace_Module>
                  </modules>
                  </config>


                  Now to disable this module, you would change the active-tag from true to false.



                  <active>false</active>


                  Remember to flush the Magento cache.



                  Disabling local modules :



                  But this might not solve your problem. If some module is placed in the app/code/local directory it might be overriding a Magento core-class directly, without the use of XML-files. To bypass this problem, you need to temporarily disable all local modules.



                  This can be done by opening up the file app/etc/local.xml in which you should change the disable_local_modules-tag to true.



                  <disable_local_modules>false</disable_local_modules>


                  This should allow you to troubleshoot the problem. Of course there are many more things to troubleshoot when dealing with serious problems, but at least this is a start.






                  share|improve this answer




























                    5












                    5








                    5







                    Below are the three ways to disable the modules.




                    1. Disabling modules in the Magento backend :


                    Go to Magento backend - System > Configuration > Advanced > Disable modules output you can easily disable certain modules.
                    You can even select the scope of the configuration (in the top left of the page) and there for disable specific modules only for specific Store Views. This is actually the preferred way of disabling a module.



                    (This only disables the output. This means especially, that all the computation is still done, means: Doesn't improve performance!)



                    Modifying XML-files :
                    In the directory app/etc/modules you can find a bunch of XML-files. While the Magento core-modules are bundled in just a couple of files, in most cases you will find per third party module also a separate XML-file. When you open up the XML-file of for instance our MageBridge extension, you will find the following:



                    <config>
                    <modules>
                    <Namespace_Module>
                    <active>true</active>
                    <codePool>community</codePool>
                    </Namespace_Module>
                    </modules>
                    </config>


                    Now to disable this module, you would change the active-tag from true to false.



                    <active>false</active>


                    Remember to flush the Magento cache.



                    Disabling local modules :



                    But this might not solve your problem. If some module is placed in the app/code/local directory it might be overriding a Magento core-class directly, without the use of XML-files. To bypass this problem, you need to temporarily disable all local modules.



                    This can be done by opening up the file app/etc/local.xml in which you should change the disable_local_modules-tag to true.



                    <disable_local_modules>false</disable_local_modules>


                    This should allow you to troubleshoot the problem. Of course there are many more things to troubleshoot when dealing with serious problems, but at least this is a start.






                    share|improve this answer















                    Below are the three ways to disable the modules.




                    1. Disabling modules in the Magento backend :


                    Go to Magento backend - System > Configuration > Advanced > Disable modules output you can easily disable certain modules.
                    You can even select the scope of the configuration (in the top left of the page) and there for disable specific modules only for specific Store Views. This is actually the preferred way of disabling a module.



                    (This only disables the output. This means especially, that all the computation is still done, means: Doesn't improve performance!)



                    Modifying XML-files :
                    In the directory app/etc/modules you can find a bunch of XML-files. While the Magento core-modules are bundled in just a couple of files, in most cases you will find per third party module also a separate XML-file. When you open up the XML-file of for instance our MageBridge extension, you will find the following:



                    <config>
                    <modules>
                    <Namespace_Module>
                    <active>true</active>
                    <codePool>community</codePool>
                    </Namespace_Module>
                    </modules>
                    </config>


                    Now to disable this module, you would change the active-tag from true to false.



                    <active>false</active>


                    Remember to flush the Magento cache.



                    Disabling local modules :



                    But this might not solve your problem. If some module is placed in the app/code/local directory it might be overriding a Magento core-class directly, without the use of XML-files. To bypass this problem, you need to temporarily disable all local modules.



                    This can be done by opening up the file app/etc/local.xml in which you should change the disable_local_modules-tag to true.



                    <disable_local_modules>false</disable_local_modules>


                    This should allow you to troubleshoot the problem. Of course there are many more things to troubleshoot when dealing with serious problems, but at least this is a start.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Jun 7 '15 at 14:55









                    Fabian Blechschmidt

                    33.5k764173




                    33.5k764173










                    answered Dec 19 '14 at 11:39









                    Abhishek GuptaAbhishek Gupta

                    997716




                    997716























                        2














                        By doing the way is two.




                        1. in admin, system->configuration->advanced and then disable the module you want.


                        2. making your modulename.xml file this line as <active>true</active> to <active>false</active>.(need to flush the cache)



                        Hope this is what you need.






                        share|improve this answer






























                          2














                          By doing the way is two.




                          1. in admin, system->configuration->advanced and then disable the module you want.


                          2. making your modulename.xml file this line as <active>true</active> to <active>false</active>.(need to flush the cache)



                          Hope this is what you need.






                          share|improve this answer




























                            2












                            2








                            2







                            By doing the way is two.




                            1. in admin, system->configuration->advanced and then disable the module you want.


                            2. making your modulename.xml file this line as <active>true</active> to <active>false</active>.(need to flush the cache)



                            Hope this is what you need.






                            share|improve this answer















                            By doing the way is two.




                            1. in admin, system->configuration->advanced and then disable the module you want.


                            2. making your modulename.xml file this line as <active>true</active> to <active>false</active>.(need to flush the cache)



                            Hope this is what you need.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Dec 19 '14 at 11:52

























                            answered Dec 19 '14 at 8:13









                            Manikandan ArunachalamManikandan Arunachalam

                            647723




                            647723























                                2














                                I stumbled over another way to disable extension in an answer to my own question (admitedly very similar to this one) in this regards which I wanted to share here.



                                This was provided by @nintenic (thanks for that) :





                                1. In your FTP go to app/etc/modules. This is where all the extension xml files are located.

                                2. Create a new folder here called "disabled".

                                3. Move the xml file of the extension you wish to disable to this new folder

                                  (app/etc/modules/disabled).

                                4. Now log into the Magento backend and go to > System > Cache Management.

                                  Click Flush Magento Cache to have Magento recognize the changes.


                                This is not the "correct" way. but it's the fastest and easiest; and it's even recommended by some extension developers and hosting providers.







                                share|improve this answer




























                                  2














                                  I stumbled over another way to disable extension in an answer to my own question (admitedly very similar to this one) in this regards which I wanted to share here.



                                  This was provided by @nintenic (thanks for that) :





                                  1. In your FTP go to app/etc/modules. This is where all the extension xml files are located.

                                  2. Create a new folder here called "disabled".

                                  3. Move the xml file of the extension you wish to disable to this new folder

                                    (app/etc/modules/disabled).

                                  4. Now log into the Magento backend and go to > System > Cache Management.

                                    Click Flush Magento Cache to have Magento recognize the changes.


                                  This is not the "correct" way. but it's the fastest and easiest; and it's even recommended by some extension developers and hosting providers.







                                  share|improve this answer


























                                    2












                                    2








                                    2







                                    I stumbled over another way to disable extension in an answer to my own question (admitedly very similar to this one) in this regards which I wanted to share here.



                                    This was provided by @nintenic (thanks for that) :





                                    1. In your FTP go to app/etc/modules. This is where all the extension xml files are located.

                                    2. Create a new folder here called "disabled".

                                    3. Move the xml file of the extension you wish to disable to this new folder

                                      (app/etc/modules/disabled).

                                    4. Now log into the Magento backend and go to > System > Cache Management.

                                      Click Flush Magento Cache to have Magento recognize the changes.


                                    This is not the "correct" way. but it's the fastest and easiest; and it's even recommended by some extension developers and hosting providers.







                                    share|improve this answer













                                    I stumbled over another way to disable extension in an answer to my own question (admitedly very similar to this one) in this regards which I wanted to share here.



                                    This was provided by @nintenic (thanks for that) :





                                    1. In your FTP go to app/etc/modules. This is where all the extension xml files are located.

                                    2. Create a new folder here called "disabled".

                                    3. Move the xml file of the extension you wish to disable to this new folder

                                      (app/etc/modules/disabled).

                                    4. Now log into the Magento backend and go to > System > Cache Management.

                                      Click Flush Magento Cache to have Magento recognize the changes.


                                    This is not the "correct" way. but it's the fastest and easiest; and it's even recommended by some extension developers and hosting providers.








                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Aug 2 '18 at 8:42









                                    magpieninjamagpieninja

                                    256




                                    256






























                                        draft saved

                                        draft discarded




















































                                        Thanks for contributing an answer to Magento Stack Exchange!


                                        • Please be sure to answer the question. Provide details and share your research!

                                        But avoid



                                        • Asking for help, clarification, or responding to other answers.

                                        • Making statements based on opinion; back them up with references or personal experience.


                                        To learn more, see our tips on writing great answers.




                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function () {
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f48838%2fhow-to-enable-and-disable-custom-magento-extension%23new-answer', 'question_page');
                                        }
                                        );

                                        Post as a guest















                                        Required, but never shown





















































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown

































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown







                                        Popular posts from this blog

                                        “%fieldName is a required field.”, in Magento2 REST API Call for GET Method Type The Next...

                                        How to change City field to a dropdown in Checkout step Magento 2Magento 2 : How to change UI field(s)...

                                        變成蝙蝠會怎樣? 參考資料 外部連結 导航菜单Thomas Nagel, "What is it like to be a...