Replies: 1 comment
-
I support this for django CMS 4.2. Tricky bit will be backward code compatibility. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Up to version 3, there where 2
Page
objects perNode
object, hence a separation of these models made sense. In version 4 this is not the case anymore. For eachNode
there is one and only onePage
object. For simplicity and performance it therefore would be a good idea to merge these two models into one; this eliminates one INNER JOIN on many queries.2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions