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]

✅ 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

[engcom-Bravo]

Hi @nmallepally,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

CMS page is visible on FE and the issue is no more reproducible.

Hence We are closing this issue.

Thanks.