Upgrade to 2.2.2: CMS Homepage 404

[LSERRE]

Preconditions

1. Magento 2.2.2

Steps to reproduce

1. Configure a CMS Page as Default Page in configuration Panel with Magento 2.2.1
2. Upgrade to Magento 2.2.2
3. Go to Homepage

Expected result

1. Display CMS Homepage

Actual result

1. 404 Error

I tried save stores/configurations/general/web/default pages values again.
The CMS page is now displayed as frontpage but it is not considered as real homepage:

• cms_index_index.xml layout is not loaded
• Widgets associated to CMS Homepage are not displayed

Someone has the same issue and posted on stackoverflow:

https://magento.stackexchange.com/questions/206520/404-on-homepage-magento-2-2-2/207789#207789

[magento-engcom-team]

@LSERRE thank you for your report. Unfortunately, we weren't able to reproduce the issue. It works fine for us. The steps we used:

1. Create a CMS page (Content->Pages->Add new Page)
2. Then set up this page as a home page (Stores->Configuration->General->Web->Default Pages ->CMS Home Page->Choose the page that you created earlier)
3. Upgrade your Magento to 2.2.2 (we used composer for that)
4. Run php bin/magento setup:upgrade
5. Open the homepage and you should see the CMS static page.

Please let us know if we missed anything, or if you used another way. Thank you

[LSERRE]

Thanks for your test. Well maybe this is because I created the Homepage with and older version then. But I still have the issue and some others has it too (see my link).

[magento-engcom-team]

@LSERRE We tried to reproduce it on the clean instance of Magento, and we could not reproduce it. We tried updating 2.2.0->2.2.2 and 2.2.1-> 2.2.2 both ways worked fine. Seems like it's a problem with your Magento instance or seems like you might have 3'rd party code, that causes the problem. Please refer to the Community Forums or the Magento Stack Exchange site for technical questions.

[juharintanen]

I had the exact same thing.
And as Vitaliy Novakivskiy wrote in that Stack Exchange link

You can check DB table url_rewrite and found row cotains request_path='' (empty).It helped me in solving the problem.

My url_rewrite table did have an empty request_path row for some reason. I deleted it and everything worked again.

[LSERRE]

Hi,

Yes I ended up as the same way. Thanks for your answer.

[peterjaap]

+1

[loekderooij]

+1, thanks @juharintanen

[adam2211]

I was getting 404 for every new cms page I create. I was able to resolve this issue by deleting the URL redirect from the database using the following:

DELETE FROM url_rewrite WHERE (entity_type = 'cms-page');

[digvijay2017]

I have also noticed this issue while upgraded Magento 2.2.1 to 2.2.2. But there is no any empty request_path row in url_rewrite table. This is a serious issue and how can @magento-engcom-team close this issue?

[sam110386]

i m facing same issue after upgrade to 2.3.1, i checked "url_rewrite" DB table and there is no empty request_path record

[crysix]

We also have that issue after upgrade to 2.3.1. But it's a little more strange. If we have a 404 one the homepage and clear the hole cache (FPC enabled), everything is working. But after some time running (without changing anything) it will change to 404 again. So only cache clearing will fix it currently, and that is no solution.

We now switched to Redis as cache backend, but there we have the same problem. So it looks like the cache backend type doesn't matter.

Our url_rewrite table has no empty rows and we didn't had that error prior 2.3.1

[crysix]

There is alredy a fix for this here #21299

[ghost]

We have same issue on magento 2.3.1 with homepage on clean install with Luma Sample data.

[ghost]

There is alredy a fix for this here #21299

This does not resolve the issue. We can provide a live site to demonstrate the patch fails.

https://luma.awsamistacx.com

A fresh install of 2.3.1 using aMiSTACX on AWS, and then load sample data should not result in 404 on the homepage after X time; certainly tied into FPC as others have stated.

We can fix this by flushing FPC/Redis, but that is not a solution. Again as others have stated.

Really would be fantastic should someone take this bug seriously.

[mikimobile]

We have actually the same issue as yours right now @crysix
Have you been able to solve it ?

[adam2211]

@mikimobile
I was getting 404 for every new cms page I create. I was able to resolve this issue by deleting the URL redirect from the database using the following:

DELETE FROM url_rewrite WHERE (entity_type = 'cms-page');

[crysix]

@mikimobile Yes, I resolved it as described here #21299

[mikimobile]

Thanks Christian.

…

On Sun, 7 Jul 2019, 22:33 Christian Hinz, ***@***.***> wrote: @mikimobile <https://github.com/mikimobile> Yes, I resolved it as described here #21299 <#21299> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#12950?email_source=notifications&email_token=AA3YGCOH6A2F4NINRXHDZFLP6JHKVA5CNFSM4EKDMXP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZLSSTQ#issuecomment-509028686>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3YGCO5HQHFQOKEMSG3JULP6JHKVANCNFSM4EKDMXPQ> .