Weird behavior after loginHow to Disable Customer Accounts/Sign In Without Breaking the Shopping Cart in...

Is there really no use for MD5 anymore?

Aligning equation numbers vertically

Pre-plastic human skin alternative

How to have a sharp product image?

How come there are so many candidates for the 2020 Democratic party presidential nomination?

If a planet has 3 moons, is it possible to have triple Full/New Moons at once?

A ​Note ​on ​N!

Implications of cigar-shaped bodies having rings?

Does tea made with boiling water cool faster than tea made with boiled (but still hot) water?

Like totally amazing interchangeable sister outfits II: The Revenge

How did Captain America manage to do this?

Why must Chinese maps be obfuscated?

How do I reattach a shelf to the wall when it ripped out of the wall?

How can I practically buy stocks?

Aliens crash on Earth and go into stasis to wait for technology to fix their ship

A strange hotel

Why does Mind Blank stop the Feeblemind spell?

How to not starve gigantic beasts

Can someone publish a story that happened to you?

Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?

Elements other than carbon that can form many different compounds by bonding to themselves?

What's the name of these pliers?

555 timer FM transmitter

What is the philosophical significance of speech acts/implicature?



Weird behavior after login


How to Disable Customer Accounts/Sign In Without Breaking the Shopping Cart in Magento 2.0.4?Persistent cart = off, adding 1 product and login results in 12 products in cartCheck customer login in external scriptMagento 2 minicart, welcome message, other do not work with page cache disabled after customer loginCheckout remains 80% blank Magento 2.0.7Front-end session timeout causes error on checkout and basket pagesMagento 2 checkout page how to get country_id from selected shipping addresses?Tier price for customer group does not automatically apply after logging inMagento 2 | Mini Cart has items but cart is empty | Session problem? | Double clicking on “Proceed To Checkout” redirects to an empty cartHow to add new custom dynamic link in magento2 top header links?Cart & Checkout blank Magento 2.3 after trying to add product to cart






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







4















I'm using Magento 2.0.2, I have this series of errors:




  1. In the Sign in page when I type in a wrong password I get redirected to the same page BUT I didn't see the expected "Invalid login" error message.

  2. After I log in, the top menu bar didn't update with the name of the customer and if I had items in my cart from previous sessions I didn't see the the amount in the little orange square to the right of the icon cart.

  3. If I add a product to the cart, then I get the message telling "You added xxx to your shopping cart" and ALSO I get the previous "Invalid login" error message. Additionally I get the items from previous sessions. BUT if I click on the cart icon and click on "Go to checkout" button I get the login popup...

  4. Then, if I go back to my dashboard, now the top menu bar shows the name of the customer and also I can go normally to the checkout process.


Any ideas? Thanks!










share|improve this question
















bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • All the error messages are stored in the corresponding var/session/sess_ file, but it seems that Magento is not processing them...

    – hiperboreo
    Feb 29 '16 at 4:31


















4















I'm using Magento 2.0.2, I have this series of errors:




  1. In the Sign in page when I type in a wrong password I get redirected to the same page BUT I didn't see the expected "Invalid login" error message.

  2. After I log in, the top menu bar didn't update with the name of the customer and if I had items in my cart from previous sessions I didn't see the the amount in the little orange square to the right of the icon cart.

  3. If I add a product to the cart, then I get the message telling "You added xxx to your shopping cart" and ALSO I get the previous "Invalid login" error message. Additionally I get the items from previous sessions. BUT if I click on the cart icon and click on "Go to checkout" button I get the login popup...

  4. Then, if I go back to my dashboard, now the top menu bar shows the name of the customer and also I can go normally to the checkout process.


Any ideas? Thanks!










share|improve this question
















bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • All the error messages are stored in the corresponding var/session/sess_ file, but it seems that Magento is not processing them...

    – hiperboreo
    Feb 29 '16 at 4:31














4












4








4


2






I'm using Magento 2.0.2, I have this series of errors:




  1. In the Sign in page when I type in a wrong password I get redirected to the same page BUT I didn't see the expected "Invalid login" error message.

  2. After I log in, the top menu bar didn't update with the name of the customer and if I had items in my cart from previous sessions I didn't see the the amount in the little orange square to the right of the icon cart.

  3. If I add a product to the cart, then I get the message telling "You added xxx to your shopping cart" and ALSO I get the previous "Invalid login" error message. Additionally I get the items from previous sessions. BUT if I click on the cart icon and click on "Go to checkout" button I get the login popup...

  4. Then, if I go back to my dashboard, now the top menu bar shows the name of the customer and also I can go normally to the checkout process.


Any ideas? Thanks!










share|improve this question
















I'm using Magento 2.0.2, I have this series of errors:




  1. In the Sign in page when I type in a wrong password I get redirected to the same page BUT I didn't see the expected "Invalid login" error message.

  2. After I log in, the top menu bar didn't update with the name of the customer and if I had items in my cart from previous sessions I didn't see the the amount in the little orange square to the right of the icon cart.

  3. If I add a product to the cart, then I get the message telling "You added xxx to your shopping cart" and ALSO I get the previous "Invalid login" error message. Additionally I get the items from previous sessions. BUT if I click on the cart icon and click on "Go to checkout" button I get the login popup...

  4. Then, if I go back to my dashboard, now the top menu bar shows the name of the customer and also I can go normally to the checkout process.


Any ideas? Thanks!







magento2 checkout login






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 2 '16 at 11:33









Klettseb

3,06531851




3,06531851










asked Feb 29 '16 at 3:13









hiperboreohiperboreo

154113




154113





bumped to the homepage by Community 2 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 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • All the error messages are stored in the corresponding var/session/sess_ file, but it seems that Magento is not processing them...

    – hiperboreo
    Feb 29 '16 at 4:31



















  • All the error messages are stored in the corresponding var/session/sess_ file, but it seems that Magento is not processing them...

    – hiperboreo
    Feb 29 '16 at 4:31

















All the error messages are stored in the corresponding var/session/sess_ file, but it seems that Magento is not processing them...

– hiperboreo
Feb 29 '16 at 4:31





All the error messages are stored in the corresponding var/session/sess_ file, but it seems that Magento is not processing them...

– hiperboreo
Feb 29 '16 at 4:31










3 Answers
3






active

oldest

votes


















0














We had this same issue on our site. Clearing browser cookies would make it work for a while but obviously we couldn't expect customers to always clear their cookies for us. The problem is that it would make two separate session cookies for everyone who logs in. One for example.com and one for .example.com. (notice the dot in front that makes it apply to itself and all subdomains as well) We would get exactly the problem you would describe when these two cookies ended up pointing to different sessions after a while. It's a bug in magento and the work around was as follows:



Go to system -> configuration -> general -> web -> session cookie management
Make sure the fields cookie path and cookie domain are correct.
In most cases, cookie path should just be / and cookie domain should just be your domain name with a dot in front.






share|improve this answer
























  • I tried without success :( It's true that on system -> configuration -> general -> web -> session cookie management the fields you mentioned were empty. For cookie path I typed / , for cookie domain I wrote mine with the dot and I couldn't log in ether as admin neither as customer, accessing directly the table core_config_data I delete the dot in the front of the domain and I can login again. But the error still persists!

    – hiperboreo
    Mar 2 '16 at 2:56













  • You will probably have to clear your cookies once after changing the cookie settings.

    – Christian
    Mar 2 '16 at 20:22



















0














Check your Magento 2 file permissions on the server, especially var/session/. Can your webserver user write to the folder? Is it in the right usergroup?






share|improve this answer


























  • yes, the webserver can read and write to the folder var/session, yes it's in the right usergroup... I'v been tracking how the server access session files, I also thought it was a permission issue, but when I saw the server was writing and changing the content of session files I discard it. Thanks for your comment

    – hiperboreo
    Mar 2 '16 at 2:39



















0














I had exactly the same problems as you had and the same results with the advices on session cookie management settings. After reverting the setting in the database I decided to try to disable the Magento_Persistent module in Configuration -> Advanced -> Advanced and now the front-end behaves exactly like it should behave.



My guess is that somehow server side sessions are not synced well with client side cookies on opening a session so I just stick with client side cookies as I have no need to chase abandoned shopping carts.






share|improve this answer
























  • Well, I did it, disable Magento_Persistent module, but I still have the same issue with the name in the top bar and with the items in the cart, same way to "solve it": going back to my dashboard to get logged in :(

    – hiperboreo
    Mar 7 '16 at 1:24











  • Yeah, sorry, I found out later, too many bugs in 2.0.2. I'm now using the Dev version but due to another bug you might have to set the theme directly in the database. But as far as I can see the weird behavior and some other bugs are gone.

    – sangatpedas
    Mar 8 '16 at 2:54












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%2f103830%2fweird-behavior-after-login%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














We had this same issue on our site. Clearing browser cookies would make it work for a while but obviously we couldn't expect customers to always clear their cookies for us. The problem is that it would make two separate session cookies for everyone who logs in. One for example.com and one for .example.com. (notice the dot in front that makes it apply to itself and all subdomains as well) We would get exactly the problem you would describe when these two cookies ended up pointing to different sessions after a while. It's a bug in magento and the work around was as follows:



Go to system -> configuration -> general -> web -> session cookie management
Make sure the fields cookie path and cookie domain are correct.
In most cases, cookie path should just be / and cookie domain should just be your domain name with a dot in front.






share|improve this answer
























  • I tried without success :( It's true that on system -> configuration -> general -> web -> session cookie management the fields you mentioned were empty. For cookie path I typed / , for cookie domain I wrote mine with the dot and I couldn't log in ether as admin neither as customer, accessing directly the table core_config_data I delete the dot in the front of the domain and I can login again. But the error still persists!

    – hiperboreo
    Mar 2 '16 at 2:56













  • You will probably have to clear your cookies once after changing the cookie settings.

    – Christian
    Mar 2 '16 at 20:22
















0














We had this same issue on our site. Clearing browser cookies would make it work for a while but obviously we couldn't expect customers to always clear their cookies for us. The problem is that it would make two separate session cookies for everyone who logs in. One for example.com and one for .example.com. (notice the dot in front that makes it apply to itself and all subdomains as well) We would get exactly the problem you would describe when these two cookies ended up pointing to different sessions after a while. It's a bug in magento and the work around was as follows:



Go to system -> configuration -> general -> web -> session cookie management
Make sure the fields cookie path and cookie domain are correct.
In most cases, cookie path should just be / and cookie domain should just be your domain name with a dot in front.






share|improve this answer
























  • I tried without success :( It's true that on system -> configuration -> general -> web -> session cookie management the fields you mentioned were empty. For cookie path I typed / , for cookie domain I wrote mine with the dot and I couldn't log in ether as admin neither as customer, accessing directly the table core_config_data I delete the dot in the front of the domain and I can login again. But the error still persists!

    – hiperboreo
    Mar 2 '16 at 2:56













  • You will probably have to clear your cookies once after changing the cookie settings.

    – Christian
    Mar 2 '16 at 20:22














0












0








0







We had this same issue on our site. Clearing browser cookies would make it work for a while but obviously we couldn't expect customers to always clear their cookies for us. The problem is that it would make two separate session cookies for everyone who logs in. One for example.com and one for .example.com. (notice the dot in front that makes it apply to itself and all subdomains as well) We would get exactly the problem you would describe when these two cookies ended up pointing to different sessions after a while. It's a bug in magento and the work around was as follows:



Go to system -> configuration -> general -> web -> session cookie management
Make sure the fields cookie path and cookie domain are correct.
In most cases, cookie path should just be / and cookie domain should just be your domain name with a dot in front.






share|improve this answer













We had this same issue on our site. Clearing browser cookies would make it work for a while but obviously we couldn't expect customers to always clear their cookies for us. The problem is that it would make two separate session cookies for everyone who logs in. One for example.com and one for .example.com. (notice the dot in front that makes it apply to itself and all subdomains as well) We would get exactly the problem you would describe when these two cookies ended up pointing to different sessions after a while. It's a bug in magento and the work around was as follows:



Go to system -> configuration -> general -> web -> session cookie management
Make sure the fields cookie path and cookie domain are correct.
In most cases, cookie path should just be / and cookie domain should just be your domain name with a dot in front.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 1 '16 at 16:56









ChristianChristian

31129




31129













  • I tried without success :( It's true that on system -> configuration -> general -> web -> session cookie management the fields you mentioned were empty. For cookie path I typed / , for cookie domain I wrote mine with the dot and I couldn't log in ether as admin neither as customer, accessing directly the table core_config_data I delete the dot in the front of the domain and I can login again. But the error still persists!

    – hiperboreo
    Mar 2 '16 at 2:56













  • You will probably have to clear your cookies once after changing the cookie settings.

    – Christian
    Mar 2 '16 at 20:22



















  • I tried without success :( It's true that on system -> configuration -> general -> web -> session cookie management the fields you mentioned were empty. For cookie path I typed / , for cookie domain I wrote mine with the dot and I couldn't log in ether as admin neither as customer, accessing directly the table core_config_data I delete the dot in the front of the domain and I can login again. But the error still persists!

    – hiperboreo
    Mar 2 '16 at 2:56













  • You will probably have to clear your cookies once after changing the cookie settings.

    – Christian
    Mar 2 '16 at 20:22

















I tried without success :( It's true that on system -> configuration -> general -> web -> session cookie management the fields you mentioned were empty. For cookie path I typed / , for cookie domain I wrote mine with the dot and I couldn't log in ether as admin neither as customer, accessing directly the table core_config_data I delete the dot in the front of the domain and I can login again. But the error still persists!

– hiperboreo
Mar 2 '16 at 2:56







I tried without success :( It's true that on system -> configuration -> general -> web -> session cookie management the fields you mentioned were empty. For cookie path I typed / , for cookie domain I wrote mine with the dot and I couldn't log in ether as admin neither as customer, accessing directly the table core_config_data I delete the dot in the front of the domain and I can login again. But the error still persists!

– hiperboreo
Mar 2 '16 at 2:56















You will probably have to clear your cookies once after changing the cookie settings.

– Christian
Mar 2 '16 at 20:22





You will probably have to clear your cookies once after changing the cookie settings.

– Christian
Mar 2 '16 at 20:22













0














Check your Magento 2 file permissions on the server, especially var/session/. Can your webserver user write to the folder? Is it in the right usergroup?






share|improve this answer


























  • yes, the webserver can read and write to the folder var/session, yes it's in the right usergroup... I'v been tracking how the server access session files, I also thought it was a permission issue, but when I saw the server was writing and changing the content of session files I discard it. Thanks for your comment

    – hiperboreo
    Mar 2 '16 at 2:39
















0














Check your Magento 2 file permissions on the server, especially var/session/. Can your webserver user write to the folder? Is it in the right usergroup?






share|improve this answer


























  • yes, the webserver can read and write to the folder var/session, yes it's in the right usergroup... I'v been tracking how the server access session files, I also thought it was a permission issue, but when I saw the server was writing and changing the content of session files I discard it. Thanks for your comment

    – hiperboreo
    Mar 2 '16 at 2:39














0












0








0







Check your Magento 2 file permissions on the server, especially var/session/. Can your webserver user write to the folder? Is it in the right usergroup?






share|improve this answer















Check your Magento 2 file permissions on the server, especially var/session/. Can your webserver user write to the folder? Is it in the right usergroup?







share|improve this answer














share|improve this answer



share|improve this answer








edited Mar 2 '16 at 10:01

























answered Mar 1 '16 at 15:57









AkifAkif

7761134




7761134













  • yes, the webserver can read and write to the folder var/session, yes it's in the right usergroup... I'v been tracking how the server access session files, I also thought it was a permission issue, but when I saw the server was writing and changing the content of session files I discard it. Thanks for your comment

    – hiperboreo
    Mar 2 '16 at 2:39



















  • yes, the webserver can read and write to the folder var/session, yes it's in the right usergroup... I'v been tracking how the server access session files, I also thought it was a permission issue, but when I saw the server was writing and changing the content of session files I discard it. Thanks for your comment

    – hiperboreo
    Mar 2 '16 at 2:39

















yes, the webserver can read and write to the folder var/session, yes it's in the right usergroup... I'v been tracking how the server access session files, I also thought it was a permission issue, but when I saw the server was writing and changing the content of session files I discard it. Thanks for your comment

– hiperboreo
Mar 2 '16 at 2:39





yes, the webserver can read and write to the folder var/session, yes it's in the right usergroup... I'v been tracking how the server access session files, I also thought it was a permission issue, but when I saw the server was writing and changing the content of session files I discard it. Thanks for your comment

– hiperboreo
Mar 2 '16 at 2:39











0














I had exactly the same problems as you had and the same results with the advices on session cookie management settings. After reverting the setting in the database I decided to try to disable the Magento_Persistent module in Configuration -> Advanced -> Advanced and now the front-end behaves exactly like it should behave.



My guess is that somehow server side sessions are not synced well with client side cookies on opening a session so I just stick with client side cookies as I have no need to chase abandoned shopping carts.






share|improve this answer
























  • Well, I did it, disable Magento_Persistent module, but I still have the same issue with the name in the top bar and with the items in the cart, same way to "solve it": going back to my dashboard to get logged in :(

    – hiperboreo
    Mar 7 '16 at 1:24











  • Yeah, sorry, I found out later, too many bugs in 2.0.2. I'm now using the Dev version but due to another bug you might have to set the theme directly in the database. But as far as I can see the weird behavior and some other bugs are gone.

    – sangatpedas
    Mar 8 '16 at 2:54
















0














I had exactly the same problems as you had and the same results with the advices on session cookie management settings. After reverting the setting in the database I decided to try to disable the Magento_Persistent module in Configuration -> Advanced -> Advanced and now the front-end behaves exactly like it should behave.



My guess is that somehow server side sessions are not synced well with client side cookies on opening a session so I just stick with client side cookies as I have no need to chase abandoned shopping carts.






share|improve this answer
























  • Well, I did it, disable Magento_Persistent module, but I still have the same issue with the name in the top bar and with the items in the cart, same way to "solve it": going back to my dashboard to get logged in :(

    – hiperboreo
    Mar 7 '16 at 1:24











  • Yeah, sorry, I found out later, too many bugs in 2.0.2. I'm now using the Dev version but due to another bug you might have to set the theme directly in the database. But as far as I can see the weird behavior and some other bugs are gone.

    – sangatpedas
    Mar 8 '16 at 2:54














0












0








0







I had exactly the same problems as you had and the same results with the advices on session cookie management settings. After reverting the setting in the database I decided to try to disable the Magento_Persistent module in Configuration -> Advanced -> Advanced and now the front-end behaves exactly like it should behave.



My guess is that somehow server side sessions are not synced well with client side cookies on opening a session so I just stick with client side cookies as I have no need to chase abandoned shopping carts.






share|improve this answer













I had exactly the same problems as you had and the same results with the advices on session cookie management settings. After reverting the setting in the database I decided to try to disable the Magento_Persistent module in Configuration -> Advanced -> Advanced and now the front-end behaves exactly like it should behave.



My guess is that somehow server side sessions are not synced well with client side cookies on opening a session so I just stick with client side cookies as I have no need to chase abandoned shopping carts.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 4 '16 at 5:30









sangatpedassangatpedas

1




1













  • Well, I did it, disable Magento_Persistent module, but I still have the same issue with the name in the top bar and with the items in the cart, same way to "solve it": going back to my dashboard to get logged in :(

    – hiperboreo
    Mar 7 '16 at 1:24











  • Yeah, sorry, I found out later, too many bugs in 2.0.2. I'm now using the Dev version but due to another bug you might have to set the theme directly in the database. But as far as I can see the weird behavior and some other bugs are gone.

    – sangatpedas
    Mar 8 '16 at 2:54



















  • Well, I did it, disable Magento_Persistent module, but I still have the same issue with the name in the top bar and with the items in the cart, same way to "solve it": going back to my dashboard to get logged in :(

    – hiperboreo
    Mar 7 '16 at 1:24











  • Yeah, sorry, I found out later, too many bugs in 2.0.2. I'm now using the Dev version but due to another bug you might have to set the theme directly in the database. But as far as I can see the weird behavior and some other bugs are gone.

    – sangatpedas
    Mar 8 '16 at 2:54

















Well, I did it, disable Magento_Persistent module, but I still have the same issue with the name in the top bar and with the items in the cart, same way to "solve it": going back to my dashboard to get logged in :(

– hiperboreo
Mar 7 '16 at 1:24





Well, I did it, disable Magento_Persistent module, but I still have the same issue with the name in the top bar and with the items in the cart, same way to "solve it": going back to my dashboard to get logged in :(

– hiperboreo
Mar 7 '16 at 1:24













Yeah, sorry, I found out later, too many bugs in 2.0.2. I'm now using the Dev version but due to another bug you might have to set the theme directly in the database. But as far as I can see the weird behavior and some other bugs are gone.

– sangatpedas
Mar 8 '16 at 2:54





Yeah, sorry, I found out later, too many bugs in 2.0.2. I'm now using the Dev version but due to another bug you might have to set the theme directly in the database. But as far as I can see the weird behavior and some other bugs are gone.

– sangatpedas
Mar 8 '16 at 2:54


















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%2f103830%2fweird-behavior-after-login%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)...

夢乃愛華...