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

Issue 35838: Customer is logged in but showing 404 error in frontend. #36263

Merged
merged 6 commits into from
May 28, 2024

Conversation

rogerdz
Copy link
Contributor

@rogerdz rogerdz commented Oct 10, 2022

Description (*)

Remove referrer in url when current page 404, after customer login will redirect to Customer dashboard

Fixed Issues (if relevant)

  1. Fixes Customer is logged in but showing 404 error in frontend. #35838

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Oct 10, 2022

Hi @rogerdz. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-community-project m2-community-project bot added the Priority: P3 May be fixed according to the position in the backlog. label Oct 10, 2022
@rogerdz
Copy link
Contributor Author

rogerdz commented Oct 10, 2022

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

Copy link
Contributor

@edenduong edenduong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution.
Could you please check my comment.

@@ -256,4 +261,23 @@ private function getRequestReferrer()
}
return null;
}

/**
* Check if Referrer url is no route url
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Redundant 1 Space character after *

private function isNoRouteUrl($url)
{
$defaultNoRouteUrl = $this->scopeConfig->getValue(
'web/default/no_route',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is better if declare private const XML_PATH_WEB_DEFAULT_NO_ROUTE = 'web/default/no_route'

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your advice, I added change to new commit

@rogerdz
Copy link
Contributor Author

rogerdz commented Oct 13, 2022

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

1 similar comment
@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Lima
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.

@engcom-Charlie
Copy link
Contributor

Before merge, sending it to testing again as it got move to merge after testing more than a year ago.

@engcom-Delta
Copy link
Contributor

@magento run all tests

@engcom-Delta
Copy link
Contributor

✔️ QA Passed

Preconditions:

  • Install fresh Magento 2.4-develop

Manual testing scenario:

1.Go to frontend.
2.Add /customer/account/loginPost/ in your magento url.
3.Now click on sign In
4.Give login id and password.

Before: ✖️ 

Screenshot 2024-04-05 at 2 50 50 PM Screenshot 2024-04-05 at 2 51 18 PM Screenshot 2024-04-05 at 2 51 42 PM Screenshot 2024-04-05 at 2 51 56 PM Screenshot 2024-04-05 at 2 52 48 PM

After: ✔️  

Screenshot 2024-04-05 at 3 01 37 PM Screenshot 2024-04-05 at 3 02 07 PM Screenshot 2024-04-05 at 3 02 27 PM Screenshot 2024-04-05 at 3 02 44 PM

Builds are failed. Hence, moving this PR to Extended Testing.

@engcom-Echo
Copy link
Contributor

@magento run Functional Tests EE, Functional Tests CE,Functional Tests B2B

@engcom-Echo
Copy link
Contributor

Functional Tests EE, Functional Tests CE,Functional Tests B2B build failure are different on last two run on same commit also it contain some known failures.

Functional Tests EE
Run1
36263-ee

Run2
36263-ee2

Functional Tests CE
Run1
36263-ce
Run2
36263-ce2

Functional Tests B2B
Run1
36263-b2b
Run2
36263-b2b2

Hence moving it to merge in progress.

@magento-devops-reposync-svc magento-devops-reposync-svc merged commit 0b0f7c8 into magento:2.4-develop May 28, 2024
9 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Customer Priority: P3 May be fixed according to the position in the backlog. Progress: accept
Projects
Status: Recently Merged
Development

Successfully merging this pull request may close these issues.

Customer is logged in but showing 404 error in frontend.
7 participants