Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with login sesion #4842

Closed
Deepthi57 opened this issue Jun 3, 2016 · 7 comments
Closed

Issues with login sesion #4842

Deepthi57 opened this issue Jun 3, 2016 · 7 comments
Labels
bug report Component: Customer Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@Deepthi57
Copy link

Note: Version 2.0.7 EE

Steps to reproduce
1.Login into magento frontend
Expected result
1.Customer name displayed after login
Actual result
1.Default welcome msg is being displayed.

Pre-condition:
Have multiple websites ex. main website and website 1

2.Login into main website
3.Login into website 1
4.Add a product in main website to cart
5.Go to website 1

Expected:
2.Main website displays customer name as main site
3.website 1 displays customer name as website 1
4.Product gets added to main site
5.Cart must be empty in website 1

Actual:
3.After log into website 1, main website displays website 1 as customer name
4.Product gets added in main site
5.Same notification displayed in website 1
Clicking on view cart in website 1 then displays empty cart message

6.Login into magento forntend and add item to cart
7.Go to checkout

Expected:
Flow must continue to checkout

Actual:
Page logs out immediately

NOTE: Lots of inconsistencies in session behavior so kindly do not close the issue as not reproducible

Screenshots attached for clarity
customer_name_not_displayed_even_after_log_in
i_add_a_product_in_main_website_but_the_message_and_cart_icon_displayed_in_website_1
cart_displaying_the_item_added_in_main_website
clicking_on_view_cart_displays_empty_cart_message
clicking_on_view_cart_displays_empty_cart_message
after_login_into_website_1 _main_website_showing_website_1_customer_name
item_that__is_added_in_main_website

@sevos1984
Copy link
Contributor

This should be fixed in latest 2.0 version, have you tried updating your code base?

@tommypyatt
Copy link

I have a similar problem in Enterprise 2.1, and am wondering if it's related. @Deepthi57 is this issue still present for you after update?

@deepthit57
Copy link

@tommypyatt
Hi, Yes issue still persists in current version of 2.1.1 which is a fresh installation

@sevos1984
Copy link
Contributor

Internal ticket created MAGETWO-59135. Thanks for reporting

@sevos1984 sevos1984 added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development and removed Progress: needs update labels Sep 29, 2016
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
magento-team pushed a commit that referenced this issue Jun 29, 2017
Bug fixes:
- MAGETWO-59135 [Github] Customer session is shared for different customers on two websites #4842 #6468
- MAGETWO-67623 [M2EE 2.0.10] - Customer Segment - Multiple Select Attribute: MySQL Query Issue
- MAGETWO-47607 [Github] Sitemap generation in wrong folder when vhost is connected to pub folder
- MAGETWO-63159 Content staging value for fields are not saved in database
- MAGETWO-62975 [FT] Functional test Magento\Customer\Test\TestCase\RegisterCustomerFrontendEntityTest is failed
- MAGETWO-56156 [GITHUB] Using API cannot create Tax Rate with a zero rate #4873
@slavvka
Copy link
Member

slavvka commented Jun 29, 2017

The issue has been fixed for 2.2. Soon it will be ported to previous releases

@slavvka slavvka closed this as completed Jun 29, 2017
@korostii
Copy link
Contributor

Hi @slavvka,
Could you please keep the issue open until the fix appears in a released version?

@gsdsd
Copy link

gsdsd commented Jun 29, 2017

/to @slavvka :
Or propose a link to the commit of the v2.2 that corrects this problem.
Cordially, GsdSd.

magento-team pushed a commit that referenced this issue Sep 20, 2017
magento-team pushed a commit that referenced this issue Sep 20, 2017
…ifferent customers on two websites #4842 #6468 - for 2.1

- Remove test;
magento-engcom-team pushed a commit that referenced this issue Oct 2, 2019
[honey] MC-18403: Pricing :: Product pricing schema
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Customer Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests