Magento 2 - disabled module still apears in admin panel
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom: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!
magento2
asked Nov 19 '16 at 18:27
Pete JaworskiPete Jaworski
304217
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
- 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
asked Nov 19 '16 at 18:27
Pete JaworskiPete Jaworski
304217
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
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
add a comment |
- 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
asked Nov 19 '16 at 18:27
Pete JaworskiPete Jaworski
304217
- 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
magento2
asked Nov 19 '16 at 18:27
Pete JaworskiPete Jaworski
304217
asked Nov 19 '16 at 18:27
Pete JaworskiPete Jaworski
304217
asked Nov 19 '16 at 18:27
Pete JaworskiPete Jaworski
304217
asked Nov 19 '16 at 18:27
Pete JaworskiPete Jaworski
304217
asked Nov 19 '16 at 18:27
Pete JaworskiPete Jaworski
304217
304217
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
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
add a comment |
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
add a comment |
1 Answer
1
active
oldest
votes
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.
edited Mar 17 '18 at 11:57
Teja Bhagavan Kollepara
2,99341949
answered Nov 20 '16 at 0:13
MaxMax
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
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
edited Mar 17 '18 at 11:57
Teja Bhagavan Kollepara
2,99341949
answered Nov 20 '16 at 0:13
MaxMax
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
add a comment |
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.
edited Mar 17 '18 at 11:57
Teja Bhagavan Kollepara
2,99341949
answered Nov 20 '16 at 0:13
MaxMax
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
add a comment |
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.
edited Mar 17 '18 at 11:57
Teja Bhagavan Kollepara
2,99341949
answered Nov 20 '16 at 0:13
MaxMax
97822144
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.
edited Mar 17 '18 at 11:57
Teja Bhagavan Kollepara
2,99341949
answered Nov 20 '16 at 0:13
MaxMax
97822144
edited Mar 17 '18 at 11:57
Teja Bhagavan Kollepara
2,99341949
edited Mar 17 '18 at 11:57
Teja Bhagavan Kollepara
2,99341949
edited Mar 17 '18 at 11:57
Teja Bhagavan Kollepara
2,99341949
2,99341949
answered Nov 20 '16 at 0:13
MaxMax
97822144
answered Nov 20 '16 at 0:13
MaxMax
97822144
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
add a comment |
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
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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