Magento 2 - disabled module still apears in admin panel Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How can I add customer attribute in Magento 2?Magento 2: Override checkout/onepage template of Luma themeMagento 2 - Add tree category selector on backend moduleMagento 2 - Show product options and attributes in categoriesmagento 2 custom product attribute won't saveBase Table or View not found after adding Category EAVModule Template is Loading After Module is disabled in Magento2InstallData Attribute showing only on the frontend and not in customer_entity tableMagento 2 Some configurable products not shown on frontendSupport Multiselect Attribute in Admin Grid Column without UI

old style "caution" boxes

Do jazz musicians improvise on the parent scale in addition to the chord-scales?

Would "destroying" Wurmcoil Engine prevent its tokens from being created?

Why are the trig functions versine, haversine, exsecant, etc, rarely used in modern mathematics?

Using et al. for a last / senior author rather than for a first author

What is the meaning of the new sigil in Game of Thrones Season 8 intro?

If a VARCHAR(MAX) column is included in an index, is the entire value always stored in the index page(s)?

How to react to hostile behavior from a senior developer?

Extracting terms with certain heads in a function

また usage in a dictionary

Is it fair for a professor to grade us on the possession of past papers?

Why are there no cargo aircraft with "flying wing" design?

Generate an RGB colour grid

How to find all the available tools in mac terminal?

2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?

What would be the ideal power source for a cybernetic eye?

Fundamental Solution of the Pell Equation

What does the "x" in "x86" represent?

Closed form of recurrent arithmetic series summation

Is there a kind of relay only consumes power when switching?

An adverb for when you're not exaggerating

Do square wave exist?

Amount of permutations on an NxNxN Rubik's Cube

Did MS DOS itself ever use blinking text?



Magento 2 - disabled module still apears in admin panel



Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?How can I add customer attribute in Magento 2?Magento 2: Override checkout/onepage template of Luma themeMagento 2 - Add tree category selector on backend moduleMagento 2 - Show product options and attributes in categoriesmagento 2 custom product attribute won't saveBase Table or View not found after adding Category EAVModule Template is Loading After Module is disabled in Magento2InstallData Attribute showing only on the frontend and not in customer_entity tableMagento 2 Some configurable products not shown on frontendSupport Multiselect Attribute in Admin Grid Column without UI



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















  • I disabled custom module

  • The disabled module was showing a textarea for custom attribute in Category form

  • However, after disabling the module, the textarea is still there. I can't get rid of it.

What I tried:
- setup:upgrade didn't help
- regenerating admin template didn't help
- module:disable with --clear-static-content didn't help



Please let me know what I'm missing here. Thanks!










share|improve this question






















  • how to disable module to you ?

    – Suresh Chikani
    Nov 19 '16 at 18:42











  • I finally made it work by manually deleting attribute in database. Weird....

    – Pete Jaworski
    Nov 21 '16 at 19:36

















0















  • I disabled custom module

  • The disabled module was showing a textarea for custom attribute in Category form

  • However, after disabling the module, the textarea is still there. I can't get rid of it.

What I tried:
- setup:upgrade didn't help
- regenerating admin template didn't help
- module:disable with --clear-static-content didn't help



Please let me know what I'm missing here. Thanks!










share|improve this question






















  • how to disable module to you ?

    – Suresh Chikani
    Nov 19 '16 at 18:42











  • I finally made it work by manually deleting attribute in database. Weird....

    – Pete Jaworski
    Nov 21 '16 at 19:36













0












0








0


1






  • I disabled custom module

  • The disabled module was showing a textarea for custom attribute in Category form

  • However, after disabling the module, the textarea is still there. I can't get rid of it.

What I tried:
- setup:upgrade didn't help
- regenerating admin template didn't help
- module:disable with --clear-static-content didn't help



Please let me know what I'm missing here. Thanks!










share|improve this question














  • I disabled custom module

  • The disabled module was showing a textarea for custom attribute in Category form

  • However, after disabling the module, the textarea is still there. I can't get rid of it.

What I tried:
- setup:upgrade didn't help
- regenerating admin template didn't help
- module:disable with --clear-static-content didn't help



Please let me know what I'm missing here. Thanks!







magento2






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '16 at 18:27









Pete JaworskiPete Jaworski

304217




304217












  • how to disable module to you ?

    – Suresh Chikani
    Nov 19 '16 at 18:42











  • I finally made it work by manually deleting attribute in database. Weird....

    – Pete Jaworski
    Nov 21 '16 at 19:36

















  • how to disable module to you ?

    – Suresh Chikani
    Nov 19 '16 at 18:42











  • I finally made it work by manually deleting attribute in database. Weird....

    – Pete Jaworski
    Nov 21 '16 at 19:36
















how to disable module to you ?

– Suresh Chikani
Nov 19 '16 at 18:42





how to disable module to you ?

– Suresh Chikani
Nov 19 '16 at 18:42













I finally made it work by manually deleting attribute in database. Weird....

– Pete Jaworski
Nov 21 '16 at 19:36





I finally made it work by manually deleting attribute in database. Weird....

– Pete Jaworski
Nov 21 '16 at 19:36










1 Answer
1






active

oldest

votes


















0














Go to Shops -> Configurations -> Advanced -> Advances Tab. You should see a list of all installed and running add-ons. Search for the Module that gives you bugs: Vendor_Namespace. If its still there, but its deleted on the filesystem, then it might just be a bug with the cache.



Before you start -- check for mistakes made:
Do you have a second folder of M2 running on your webserver?
Which mode are you in? Developer or production? Switch to Developer if you haven't switched after install yet. You can do this via php bin/magento deploy:mode:set developer. Note: if you have switched it before via this command, you might not wanna do it (the mode of the deployment of the files basically changes and a little other dev-stuff gets enabled).



Otherwise, proceed:



utilize bin/Magento via SSH.



php bin/magento setup:upgrade && php setup:static-content:deploy



If you have another, different language as backend user as en_US, add the specific flag to the deploy-paramter. I.e.: setup:static-content:deploy en_US de_DE fr_FR .._::`.



If this still doesn't work, try deleting the content of pub/static/. You can do this with:



rm -rf pub/static/* var/cache/* var/page_cache/* var/view_preprocessed/*, however, never delete pub/static (!!!) directly, always add the /* after it.



If the modules output is still there you should manually check the aboves folders. Also, set your chmod (664 for files, 755 for folders) in order to allow Magento to deploy correctly.






share|improve this answer

























  • None of above worked. The module in not listed in Shops->Config->Adv->Adv. It is also phisically removed from web server. Static content rebuilt, folders cleared and it still there!!! Help!

    – Pete Jaworski
    Nov 21 '16 at 11:26











  • I didn't downvote any answer. No idea why there are -1. It wasn't me.

    – Pete Jaworski
    Nov 21 '16 at 19:36











  • Check updated answer.

    – Max
    Nov 21 '16 at 23:24












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%2f146572%2fmagento-2-disabled-module-still-apears-in-admin-panel%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Go to Shops -> Configurations -> Advanced -> Advances Tab. You should see a list of all installed and running add-ons. Search for the Module that gives you bugs: Vendor_Namespace. If its still there, but its deleted on the filesystem, then it might just be a bug with the cache.



Before you start -- check for mistakes made:
Do you have a second folder of M2 running on your webserver?
Which mode are you in? Developer or production? Switch to Developer if you haven't switched after install yet. You can do this via php bin/magento deploy:mode:set developer. Note: if you have switched it before via this command, you might not wanna do it (the mode of the deployment of the files basically changes and a little other dev-stuff gets enabled).



Otherwise, proceed:



utilize bin/Magento via SSH.



php bin/magento setup:upgrade && php setup:static-content:deploy



If you have another, different language as backend user as en_US, add the specific flag to the deploy-paramter. I.e.: setup:static-content:deploy en_US de_DE fr_FR .._::`.



If this still doesn't work, try deleting the content of pub/static/. You can do this with:



rm -rf pub/static/* var/cache/* var/page_cache/* var/view_preprocessed/*, however, never delete pub/static (!!!) directly, always add the /* after it.



If the modules output is still there you should manually check the aboves folders. Also, set your chmod (664 for files, 755 for folders) in order to allow Magento to deploy correctly.






share|improve this answer

























  • None of above worked. The module in not listed in Shops->Config->Adv->Adv. It is also phisically removed from web server. Static content rebuilt, folders cleared and it still there!!! Help!

    – Pete Jaworski
    Nov 21 '16 at 11:26











  • I didn't downvote any answer. No idea why there are -1. It wasn't me.

    – Pete Jaworski
    Nov 21 '16 at 19:36











  • Check updated answer.

    – Max
    Nov 21 '16 at 23:24
















0














Go to Shops -> Configurations -> Advanced -> Advances Tab. You should see a list of all installed and running add-ons. Search for the Module that gives you bugs: Vendor_Namespace. If its still there, but its deleted on the filesystem, then it might just be a bug with the cache.



Before you start -- check for mistakes made:
Do you have a second folder of M2 running on your webserver?
Which mode are you in? Developer or production? Switch to Developer if you haven't switched after install yet. You can do this via php bin/magento deploy:mode:set developer. Note: if you have switched it before via this command, you might not wanna do it (the mode of the deployment of the files basically changes and a little other dev-stuff gets enabled).



Otherwise, proceed:



utilize bin/Magento via SSH.



php bin/magento setup:upgrade && php setup:static-content:deploy



If you have another, different language as backend user as en_US, add the specific flag to the deploy-paramter. I.e.: setup:static-content:deploy en_US de_DE fr_FR .._::`.



If this still doesn't work, try deleting the content of pub/static/. You can do this with:



rm -rf pub/static/* var/cache/* var/page_cache/* var/view_preprocessed/*, however, never delete pub/static (!!!) directly, always add the /* after it.



If the modules output is still there you should manually check the aboves folders. Also, set your chmod (664 for files, 755 for folders) in order to allow Magento to deploy correctly.






share|improve this answer

























  • None of above worked. The module in not listed in Shops->Config->Adv->Adv. It is also phisically removed from web server. Static content rebuilt, folders cleared and it still there!!! Help!

    – Pete Jaworski
    Nov 21 '16 at 11:26











  • I didn't downvote any answer. No idea why there are -1. It wasn't me.

    – Pete Jaworski
    Nov 21 '16 at 19:36











  • Check updated answer.

    – Max
    Nov 21 '16 at 23:24














0












0








0







Go to Shops -> Configurations -> Advanced -> Advances Tab. You should see a list of all installed and running add-ons. Search for the Module that gives you bugs: Vendor_Namespace. If its still there, but its deleted on the filesystem, then it might just be a bug with the cache.



Before you start -- check for mistakes made:
Do you have a second folder of M2 running on your webserver?
Which mode are you in? Developer or production? Switch to Developer if you haven't switched after install yet. You can do this via php bin/magento deploy:mode:set developer. Note: if you have switched it before via this command, you might not wanna do it (the mode of the deployment of the files basically changes and a little other dev-stuff gets enabled).



Otherwise, proceed:



utilize bin/Magento via SSH.



php bin/magento setup:upgrade && php setup:static-content:deploy



If you have another, different language as backend user as en_US, add the specific flag to the deploy-paramter. I.e.: setup:static-content:deploy en_US de_DE fr_FR .._::`.



If this still doesn't work, try deleting the content of pub/static/. You can do this with:



rm -rf pub/static/* var/cache/* var/page_cache/* var/view_preprocessed/*, however, never delete pub/static (!!!) directly, always add the /* after it.



If the modules output is still there you should manually check the aboves folders. Also, set your chmod (664 for files, 755 for folders) in order to allow Magento to deploy correctly.






share|improve this answer















Go to Shops -> Configurations -> Advanced -> Advances Tab. You should see a list of all installed and running add-ons. Search for the Module that gives you bugs: Vendor_Namespace. If its still there, but its deleted on the filesystem, then it might just be a bug with the cache.



Before you start -- check for mistakes made:
Do you have a second folder of M2 running on your webserver?
Which mode are you in? Developer or production? Switch to Developer if you haven't switched after install yet. You can do this via php bin/magento deploy:mode:set developer. Note: if you have switched it before via this command, you might not wanna do it (the mode of the deployment of the files basically changes and a little other dev-stuff gets enabled).



Otherwise, proceed:



utilize bin/Magento via SSH.



php bin/magento setup:upgrade && php setup:static-content:deploy



If you have another, different language as backend user as en_US, add the specific flag to the deploy-paramter. I.e.: setup:static-content:deploy en_US de_DE fr_FR .._::`.



If this still doesn't work, try deleting the content of pub/static/. You can do this with:



rm -rf pub/static/* var/cache/* var/page_cache/* var/view_preprocessed/*, however, never delete pub/static (!!!) directly, always add the /* after it.



If the modules output is still there you should manually check the aboves folders. Also, set your chmod (664 for files, 755 for folders) in order to allow Magento to deploy correctly.







share|improve this answer














share|improve this answer



share|improve this answer








edited Mar 17 '18 at 11:57









Teja Bhagavan Kollepara

2,98241949




2,98241949










answered Nov 20 '16 at 0:13









MaxMax

97822144




97822144












  • None of above worked. The module in not listed in Shops->Config->Adv->Adv. It is also phisically removed from web server. Static content rebuilt, folders cleared and it still there!!! Help!

    – Pete Jaworski
    Nov 21 '16 at 11:26











  • I didn't downvote any answer. No idea why there are -1. It wasn't me.

    – Pete Jaworski
    Nov 21 '16 at 19:36











  • Check updated answer.

    – Max
    Nov 21 '16 at 23:24


















  • None of above worked. The module in not listed in Shops->Config->Adv->Adv. It is also phisically removed from web server. Static content rebuilt, folders cleared and it still there!!! Help!

    – Pete Jaworski
    Nov 21 '16 at 11:26











  • I didn't downvote any answer. No idea why there are -1. It wasn't me.

    – Pete Jaworski
    Nov 21 '16 at 19:36











  • Check updated answer.

    – Max
    Nov 21 '16 at 23:24

















None of above worked. The module in not listed in Shops->Config->Adv->Adv. It is also phisically removed from web server. Static content rebuilt, folders cleared and it still there!!! Help!

– Pete Jaworski
Nov 21 '16 at 11:26





None of above worked. The module in not listed in Shops->Config->Adv->Adv. It is also phisically removed from web server. Static content rebuilt, folders cleared and it still there!!! Help!

– Pete Jaworski
Nov 21 '16 at 11:26













I didn't downvote any answer. No idea why there are -1. It wasn't me.

– Pete Jaworski
Nov 21 '16 at 19:36





I didn't downvote any answer. No idea why there are -1. It wasn't me.

– Pete Jaworski
Nov 21 '16 at 19:36













Check updated answer.

– Max
Nov 21 '16 at 23:24






Check updated answer.

– Max
Nov 21 '16 at 23:24


















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%2f146572%2fmagento-2-disabled-module-still-apears-in-admin-panel%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

Sum ergo cogito? 1 nng

419 nièngy_Soadمي 19bal1.5o_g

Queiggey Chernihivv 9NnOo i Zw X QqKk LpB