Magento2: Pages not displayed on frontend 2.1.2

[nmallepally]

Preconditions (*)

Magento 2.4-develop

Steps to reproduce (*)

1. Make sure Cache is enabled
2. Go to Content -> Pages
3. Create new page, with _enabeld_ option
4. View page on FE (you should see page content)
5. Go back to the same page and _disable_ it and save.
6. View page on FE (it is not visible)
7. Go to that page on BE and _enable_ it and save.

Expected result (*)

CMS page is visible on FE.

Actual result (*)

CMS Page is not visible on FE after saving with _Disabled_ option and _Full Page Cache_ enabled.

---

Additional information
After clearing _Full Page Cache_ desired page is visible on FE.

[vasilii-b]

@nmallepally I don't see page url in admin panel neither in Front-End.Maybe you have a typo in url key ?

[nmallepally]

Hi @vasilii-b
No i checked it, url key is right.
please find the clear images.

I had reindexed 5-10 times, no use. flushed static files and deployed static content.
still the page does not appear.

[vasilii-b]

@nmallepally on _2.2.0-develop_ works fine with Magento default theme and custom theme. Did you tried to use default theme ? Try to disable installed modules ( I see you have there _EMTHEMES_).

[nmallepally]

@vasilii-b Yes, I did try with it as well.
I disabled installed modules checked it. No use, the page does not appear.
Do you have any work around for the fix? it is blocking us from going live.

[vasilii-b]

@nmallepally I do not have for now, but I'll go into it deeper today.

[vasilii-b]

I've got this issue after disabling, then re-enabling page.
The problem was that _cache_ was enabled, especially Full Page Cache.
After running command bin/magento cache:flush page is visible in front-end.

This was done on Magento 2.1.1 and 2.1.2 versions.

@nmallepally try to do the same - clear cache.

@veloraven I think label CMS should be deleted and Cache added.

[tkacheva]

@nmallepally, @vasilii-b could you provide more detailed steps to reproduce. @vasilii-b does thew issue exist on 2.2 dev?

[vasilii-b]

@tkacheva, here you go:

Steps to reproduce

1. Make sure Cache is enabled
2. Go to Content -> Pages
3. Create new page, with _enabeld_ option
4. View page on FE (you should see page content)
5. Go back to the same page and _disable_ it and save.
6. View page on FE (it is not visible)
7. Go to that page on BE and _enable_ it and save.

Expected result

CMS page is visible on FE.

Actual result

CMS Page is not visible on FE after saving with _Disabled_ option and _Full Page Cache_ enabled.

Additional information

This was tested on Magento versions: 2.1, 2.1.2 and 2.2.0-dev.
After clearing _Full Page Cache_ desired page is visible on FE.

[mitabs]

Hello, I was experiencing some very similar issues and will share my two cents.

Magento CE 2.1.2, PHP 7, MySQL 5.6, CentOS 7
Started new at CE 2.0, recently upgraded a few times to 2.1.2.
Third party modules disabled.

I created a new page via the backend, and it would not show up on the frontend. 404s every time - even after server reboot, static compilation, upgrade to latest available dependencies (11/22/16), disable caching, manual run indexing. New products were OK, and old CMS pages were OK. No frontend javascript errors. Nothing in exception.log. I was receiving the Magento 404.

The issue ended up being what I believe is a new feature in v2.1 - allowing CMS pages to be linked to multiple storeviews (You can now assign a CMS page to multiple storeviews | v2.1 release notes).

I run a single store, so I had previously enabled Single-Store Mode (Stores->Config->General). Because this was enabled, I wasn't getting the correct options on the Content -> Pages -> Add/Edit. Specifically, I was missing "Pages in Websites". Without that option, the pages were getting saved but without an entry for that field. No insert was performed into table 'url_rewrites'.

I disabled single store mode and was able to see the correct options. I chose the correct store view and everything works fine.

I believe this may be relevant because the OP submission also lacks the 'Store View' column.

[nmallepally]

@vasilii-b @tkacheva @mitabs
Same here, it worked and pages started to appear on the front end. when i chose the option to no for enabling single store mode on. pages on backend started showing as all store views.
so i had to go back on each page and save them again , then my pages started displaying on frontend.

Magento 2.1.1

[CreamyG31337]

nice, disabling single store mode also fixes the bug where you can't edit the default welcome message or the copyright thing in the footer.
this thing is so full of bugs. I can't imagine they do any testing at all.

[mattcoz]

I tried disabling single store mode and it has caused all sorts of problems. My theme is no longer being applied and I can't change it. I edit the design configuration and the edits don't persist.

[CreamyG31337]

I think I had to re apply my theme at each level before it worked. The validation is messed up for sure too. If I put "Welcome to our Canadian store!" for the welcome message it resets to default, but without the '!' it saves fine. Maybe set everything to default and change one thing at a time. Worst case you can probably figure out how to bypass this garbage and edit the database directly. That's the only way I can get my E-mail set up since the domain validation is outdated by a few years.

[mattcoz]

I tried applying it at every level, but the changes wouldn't stick. I reverted to single store mode and my theme is back, but my values for copyright, etc are not being used. This software drives me nuts.

[bluec]

Still a problem in 2.1.3 and as @mitabs pointed out it is caused by enabling single store mode. When single store mode is enabled, the "store view" for a page is not saved, and so the page will never be routed and always results in a 404 on the frontend.

[magento-engcom-team]

Updated issue description

[magento-engcom-team]

@nmallepally, thank you for your report.
We've created internal ticket(s) MAGETWO-75796 to track progress on the issue.

[avdb]

I will look into this one

[avdb]

I couldn't resolve this issue.

Reproduced on 2.2-develop branch.

This issue also occurs if you disable the single store mode.
It's also an issue for products, disable a product, visit the product page on the frontend (see a 404) and enables the product again. The 404 page is still visible on the frontend.

Steps to reproduce

1. Disable product / page in the backend.
2. Visit product/page in frontend (get 404 page)
3. Enable product/page in the backend
4. Visit product/page in frontend (get 404 page)

Refreshing full page cache solves the issue.

[sarah-magentech]

Let's disable Google Analytic in the SALES tab, you will be able to edit page. For more information, please check this blog post :)

[Jeeva-Rathinam]

Is your issue solved?

[sunilit42]

Helllo @avdb

is there any solution?

[Neusta-Hartwig]

We had the same problem and maybe I have a solution.

In our case it was the caching of 404-Pages in our varnish. After adding the following part to the vcl_backend_response of the varnish VCL, everythings works:

if ( beresp.status == 404 ) { set beresp.ttl = 0s; }

This part excludes all 404 from being cached by varnish.

Greetings,
Christoph

[m2-assistant[bot]]

Hi @engcom-Charlie. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-30061 were created

Issue Available: @engcom-Charlie, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[Ronak-Bhatti]

Hello
After Enable page from Admin side open SSH and go to your project directory
Then type the following command
php bin/magento cache:flush