be very aware of using older plone code with newer versions of code - skimming the plone site it seems they like to change the names of parts of their site structure with different major upgrades. what i have seen is mainly nomenclature related but if they were to use the name in any template code there could be issues translating.
note i'm generally not referring to content here - as long as the SQL database field names don't change the data should be fine, but it would be useful if migration from Plone 2.1.4 to 4.X could be researched before attempting it.
scott
On Wed, Mar 14, 2012 at 1:49 PM, Hans-Christoph Steiner hans@at.or.atwrote:
On Tue, Mar 13, 2012, at 07:14, Nicolas Montgermont wrote:
Le 12/03/12 15:23, Hans-Christoph Steiner a écrit :
I've had problems with doing that in the past, so I've stopped doing it altogether and reverted the pages to FrontPage. Basically, when the page gets edited, then a copy of the page gets created that is called FrontPage, so there will then be a DevelopmentWiki and a FrontPage
page.
Does it only happen with wiki pages? Most of the modifications i've done in the community section are based on using a "webpage" instead of a wiki "Frontpage". And at the moment I think there is no problem. Maybe if there is already a Frontpage it doesn't recreate one?
This is obviously not a good thing.
As long as it is displaying the good element for the folder, I see no problem?
So unless you've specifically addressed that issue, or tested a lot to make sure it does not happen ever, I think its a good idea to keep the pages called FrontPage, annoying as it is. Perhaps upgrading Plone would fix this? .hc
n
A plone upgrade is worth trying. I think that webpages had a similar issue but with the index_html name.
.hc
Pdweb mailing list Pdweb@iem.at http://lists.puredata.info/listinfo/pdweb