Inconsistancy of draft/public relations between pages (titles, and possibly extensions)

[Venelin Stoykov]

There are cases when inconstancy can happen between Page.publisher_public and Page.publisher_draft. One of the pages, for example public is pointing to it's draft but the corresponding draft is not pointing the public version. I already opened an issue in GitHub (https://github.com/divio/django-cms/issues/5667).

In order to prevent this to happen in future django-cms need to ensure this consistency or to change the way how it recognizes draft and public versions of a page (because now the data are stored in database in denormalized form).

I know that this denormalization was done because of speed. Nobody want the CMS to do extra SQL queries or complex SQL queries which will slow down everything. 

We need to ensure a proper way of getting/storring this information and ensuring that it is consistent.

[Daniele Procida]

On Wed, Sep 7, 2016, Venelin Stoykov <v.k.s...@gmail.com> wrote:

>There are cases when inconstancy can happen between Page.publisher_public
>and Page.publisher_draft. One of the pages, for example public is pointing
>to it's draft but the corresponding draft is not pointing the public
>version. I already opened an issue in GitHub
>(https://github.com/divio/django-cms/issues/5667).
>
>In order to prevent this to happen in future django-cms need to ensure this
>consistency or to change the way how it recognizes draft and public
>versions of a page (because now the data are stored in database in
>denormalized form).

Can you confirm which version(s) of django CMS you experienced with this? It should have been fixed in 3.3.

However, Reversion can still trigger them in some cases, which we're working on.

Daniele

[Venelin Stoykov]

Hi Daniel,

Yes it's with 3.3 and revisions are activated. We can't disable them because client want them.

--
Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to django-cms-developers+unsub...@googlegroups.com
---
You received this message because you are subscribed to a topic in the Google Groups "django CMS developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-cms-developers/4_qsHxLTnrc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-cms-developers+unsub...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/20160909121832.482814062%40mail.wservices.ch.
For more options, visit https://groups.google.com/d/optout.