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

Wishlist module turns the whole site to 404 #10876

Closed
harshvardhanmalpani opened this issue Sep 13, 2017 · 2 comments
Closed

Wishlist module turns the whole site to 404 #10876

harshvardhanmalpani opened this issue Sep 13, 2017 · 2 comments
Labels
Issue: Cannot Reproduce Cannot reproduce the issue on the latest `2.4-develop` branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed

Comments

@harshvardhanmalpani
Copy link

harshvardhanmalpani commented Sep 13, 2017

The magento2.1.8 instance is working good except this one issue.
Whenever a user wants to add any product in wishlist, he is redirected to login page (/customer/account/login/).
After he logs in successfully, he is redirected to https://domain.com/wishlist/index/index/wishlist_id/1/
and sees an error
##404 error: Page not found.
The problem doesn't end here, The logged in user sees the same error for whole website (homepage or any other page).

Preconditions

  1. Magento v 2.1.8
  2. PHP 7.0 on apache and nginx.

Steps to reproduce

User wants to add any product in wishlist, he is redirected to login page (/customer/account/login/).
After he logs in successfully, he is redirected to https://domain.com/wishlist/index/index/wishlist_id/1/
and sees an error

Expected result

The wishlist should be working normally

Actual result

capture-20170914-004633

I have removed the social login module from the setup and have used commands: upgrade, compile, cache flush and content deploy. Issue persists.

##EDIT -
The same setup works just fine on other websites I have deployed. This particular project has the issue. I had re-updated the Magento version to 2.1.8 using composer, issue is still there.

@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Sep 13, 2017
@magento-engcom-team magento-engcom-team added Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Progress: needs update and removed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Sep 21, 2017
@orlangur
Copy link
Contributor

The same setup works just fine on other websites I have deployed. This particular project has the issue. I had re-updated the Magento version to 2.1.8 using composer, issue is still there.

Bugs of "this particular project" cannot be fixed in Magento core. You need to find out what's going wrong on your side, ideally reproduce a bug on clean Magento installation.

Of course, there is always probability bug is in the core, just wasn't revealed on your other projects due to a different configuration. But you need to debug a problematic project to locate a problematic code.

@magento-engcom-team
Copy link
Contributor

@harshvardhanmalpani, thank you for your report.
We were not able to reproduce this issue by following the steps you provided. If you'd like to update it, please reopen the issue.

@magento-engcom-team magento-engcom-team added the Issue: Cannot Reproduce Cannot reproduce the issue on the latest `2.4-develop` branch label Sep 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Cannot Reproduce Cannot reproduce the issue on the latest `2.4-develop` branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed
Projects
None yet
Development

No branches or pull requests

3 participants