Error 404 on new module installation in magento 1.9 and fixing it by logout
I am working in magento 1.9 . I developed new module , when i install it in new instance , it gave Error 404 .
If i Logout, it fix the issue but i want to fix the issue via code . So i try to write a logout code in setup script , but no luck with it . My code looks like
public function expireAdminSession() {
// loguot code
$adminSession = Mage::getSingleton('admin/session');
$adminSession->unsetAll();
$adminSession->getCookie()->delete($adminSession->getSessionName());
}
I have called that function in construct. .
Any body please help or tell me any other solution to logout via code .
Thank you in advance .
magento-1.9
edited Dec 26 '18 at 8:59
Vivek
1,414525
asked Dec 26 '18 at 7:48
Mohammad HamdanMohammad Hamdan
678
add a comment |
I am working in magento 1.9 . I developed new module , when i install it in new instance , it gave Error 404 .
If i Logout, it fix the issue but i want to fix the issue via code . So i try to write a logout code in setup script , but no luck with it . My code looks like
public function expireAdminSession() {
// loguot code
$adminSession = Mage::getSingleton('admin/session');
$adminSession->unsetAll();
$adminSession->getCookie()->delete($adminSession->getSessionName());
}
I have called that function in construct. .
Any body please help or tell me any other solution to logout via code .
Thank you in advance .
magento-1.9
edited Dec 26 '18 at 8:59
Vivek
1,414525
asked Dec 26 '18 at 7:48
Mohammad HamdanMohammad Hamdan
678
add a comment |
I am working in magento 1.9 . I developed new module , when i install it in new instance , it gave Error 404 .
If i Logout, it fix the issue but i want to fix the issue via code . So i try to write a logout code in setup script , but no luck with it . My code looks like
public function expireAdminSession() {
// loguot code
$adminSession = Mage::getSingleton('admin/session');
$adminSession->unsetAll();
$adminSession->getCookie()->delete($adminSession->getSessionName());
}
I have called that function in construct. .
Any body please help or tell me any other solution to logout via code .
Thank you in advance .
magento-1.9
edited Dec 26 '18 at 8:59
Vivek
1,414525
asked Dec 26 '18 at 7:48
Mohammad HamdanMohammad Hamdan
678
I am working in magento 1.9 . I developed new module , when i install it in new instance , it gave Error 404 .
If i Logout, it fix the issue but i want to fix the issue via code . So i try to write a logout code in setup script , but no luck with it . My code looks like
public function expireAdminSession() {
// loguot code
$adminSession = Mage::getSingleton('admin/session');
$adminSession->unsetAll();
$adminSession->getCookie()->delete($adminSession->getSessionName());
}
I have called that function in construct. .
Any body please help or tell me any other solution to logout via code .
Thank you in advance .
magento-1.9
magento-1.9
edited Dec 26 '18 at 8:59
Vivek
1,414525
asked Dec 26 '18 at 7:48
Mohammad HamdanMohammad Hamdan
678
edited Dec 26 '18 at 8:59
Vivek
1,414525
asked Dec 26 '18 at 7:48
Mohammad HamdanMohammad Hamdan
678
edited Dec 26 '18 at 8:59
Vivek
1,414525
edited Dec 26 '18 at 8:59
Vivek
1,414525
edited Dec 26 '18 at 8:59
Vivek
1,414525
1,414525
asked Dec 26 '18 at 7:48
Mohammad HamdanMohammad Hamdan
678
asked Dec 26 '18 at 7:48
Mohammad HamdanMohammad Hamdan
678
asked Dec 26 '18 at 7:48
Mohammad HamdanMohammad Hamdan
678
678
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I think it's default behaviour of Magento after installing any custom module to instance.
You have to follow proper steps in order to avoid this. (In short its not bug It's feature of Magento).
Copy necessary files to server.
Than after completion uploading go to configuration and refresh cache and flush cache.
- Logout of admin and re-login to admin panel.
Now, You are ready to go with your custom module.
Note : It's not my personal thinking. You will find above instruction in most of the premium Magento Partner's Module Installation Guide.
answered Dec 26 '18 at 8:55
VivekVivek
1,414525
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%2f255790%2ferror-404-on-new-module-installation-in-magento-1-9-and-fixing-it-by-logout%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
I think it's default behaviour of Magento after installing any custom module to instance.
You have to follow proper steps in order to avoid this. (In short its not bug It's feature of Magento).
Copy necessary files to server.
Than after completion uploading go to configuration and refresh cache and flush cache.
- Logout of admin and re-login to admin panel.
Now, You are ready to go with your custom module.
Note : It's not my personal thinking. You will find above instruction in most of the premium Magento Partner's Module Installation Guide.
answered Dec 26 '18 at 8:55
VivekVivek
1,414525
add a comment |
I think it's default behaviour of Magento after installing any custom module to instance.
You have to follow proper steps in order to avoid this. (In short its not bug It's feature of Magento).
Copy necessary files to server.
Than after completion uploading go to configuration and refresh cache and flush cache.
- Logout of admin and re-login to admin panel.
Now, You are ready to go with your custom module.
Note : It's not my personal thinking. You will find above instruction in most of the premium Magento Partner's Module Installation Guide.
answered Dec 26 '18 at 8:55
VivekVivek
1,414525
add a comment |
I think it's default behaviour of Magento after installing any custom module to instance.
You have to follow proper steps in order to avoid this. (In short its not bug It's feature of Magento).
Copy necessary files to server.
Than after completion uploading go to configuration and refresh cache and flush cache.
- Logout of admin and re-login to admin panel.
Now, You are ready to go with your custom module.
Note : It's not my personal thinking. You will find above instruction in most of the premium Magento Partner's Module Installation Guide.
answered Dec 26 '18 at 8:55
VivekVivek
1,414525
I think it's default behaviour of Magento after installing any custom module to instance.
You have to follow proper steps in order to avoid this. (In short its not bug It's feature of Magento).
Copy necessary files to server.
Than after completion uploading go to configuration and refresh cache and flush cache.
- Logout of admin and re-login to admin panel.
Now, You are ready to go with your custom module.
Note : It's not my personal thinking. You will find above instruction in most of the premium Magento Partner's Module Installation Guide.
answered Dec 26 '18 at 8:55
VivekVivek
1,414525
edited Dec 26 '18 at 11:50
answered Dec 26 '18 at 8:55
VivekVivek
1,414525
answered Dec 26 '18 at 8:55
VivekVivek
1,414525
answered Dec 26 '18 at 8:55
VivekVivek
1,414525
1,414525
add a comment |
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%2f255790%2ferror-404-on-new-module-installation-in-magento-1-9-and-fixing-it-by-logout%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
