google-code-export / django-page-cms

Automatically exported from code.google.com/p/django-page-cms
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Child templates (maybe?) should lose data but don't; non-lost content is no longer editable #184

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.  Using the example site, create a page using basic template
2.  Now change the page template for that page (nice one) and see a warning
about losing data (misspelled "loose")
3.  Hit save anyhow and load the page in the CMS

What is the expected output? What do you see instead?
I would expect to see all my old data gone and the new data replacing it. 
Instead I see both the old data which pertained to the old template, and
the new data which pertains to the new template.  Even though the old data
still shows up when the page is rendered.  Might this be because the
template "nice one" extends the default template?

Are you using the trunk version or a released version of this CMS?
1.0.8 release

If you can write a test that reproduce the problem, there is better chance
it will be resolved quickly.
I'm afraid I can't successfully do that.

Original issue reported on code.google.com by Vade...@gmail.com on 17 Nov 2009 at 4:04

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
It's in fact normal. The field/placeholders that have the same name considered 
the same in this CMS even if the template is different.

You could use the language delete if you realy want to get ride of all the data.

Original comment by batiste....@gmail.com on 17 Nov 2009 at 4:39

GoogleCodeExporter commented 9 years ago
Oh, I wasn't aware.  The reason I posted an issue was because of the Javascript 
warning 
me I was going to lose data.  Sorry!

Original comment by Vade...@gmail.com on 17 Nov 2009 at 5:58