[Answer]-Django-cms entries giving "page not found" errors


Finally my problem wasn’t about the timezone support. Deep into my code, I had a generator with a get_object_or_404() call. This wasn’t supposed to be triggered, but due to trash data that was actually the case.

So, next time check your data first.


You have different warnings for different issues there.

The first warning DeprecationWarning: django.conf.urls.defaults is deprecated; use django.conf.urls instead is due to a change in the Django framework code itself. As it tells you, the module django.conf.urls.defaults is deprecated and you should use django.conf.urls instead, so substituting that in your code will fix it. That is not causing anyway your Django CMS pages not being shown, BTW.

The second is another deprecation warning raised due to some changes in Django CMS code. You must take a look in the upgrade notes in order to workaround this issue. That is not causing your CMS pages problem neither.

The third warning, DateTimeField received a naive datetime while time zone support is active is raised because you are not using time zones support properly. First of all, ensure that you have installed pytz package by pip install pytz. Then, for example, you should use the timezone module to get now() timestamps, instead of the datetime. Please, take a look on the Django Time Zones documentation to fix that issue, since we can’t see where in your project code time stamps are being used.

Looking at the last warning, it seems that the issue with your missing CMS pages takes place somewhere in the timestamps.


I had a very similar problem.

The problem in my case was that the parent page was not published. Parent pages have to be published in order for the subpages to be found.


Leave a comment