Plone 2.0 to Plone 2.1 - Some Issues Plone HTTP Port, HTML AT Documents, MailHost
We have a successful site created in plone 2.0.1,
we are trying to migrate to plone 2.1 for the simple reason to stay
uptodate. However it is becoming more effort than what is worth. Our
site is made up of dtml docs, zsql scripts, page templates etc. I tried
running the migration of CMFDocuments to AT Documents, and this seemed to work
for somethings but not everything.
I run plone on windows. I have installed the
Plone 2.1 windows installer only. No changes, no added products.
Brand new machine, brand new plone windows install.
I will try to list each of the issues I have had
and their resolution so far.
- Cannot view any customisations through the plone
http port, I can view everything successfully through the zodb management
port. For example I have portal_skins/custom folder with changes e.g the
logo and not a single one comes through if I use the plone port, for example if
I put the text HELLO WORLD at the top of the portal_footer, it doesn't
appear. For example the home page is a splash page. Bascially a dumb
dtml document that points to a splashpage in the portal_skins/custom
folder. This only works if I use the zodb management port. I did set
my document as the default page for the site .. but it doesn't work through the
plone http port, I get a strange error message: Traceback (innermost
last): Module ZPublisher.Publish, line 101, in publish
Module ZPublisher.mapply, line 88, in mapply Module
ZPublisher.Publish, line 39, in call_object Module OFS.DTMLDocument,
line 128, in __call__ - <DTMLDocument instance at
0AF44DD0> - URL: http://myserver2:9876/mysite/index_html/manage_main
- Physical Path: /newcorp/index_html Module
DocumentTemplate.DT_String, line 474, in __call__ KeyError:
'my_homepage' Initially I thought that it may be because of the accessrule
pointing me to the stock standard plone site but I can see folders as tabs that
I have added to mysite, so it can't be that.
- mailhost in a script doesn't work. I have a
contact us page, that calls a script that sends an email. Here is what
used to work: mailHost = getattr(context,
context.superValues("MailHost").id) PM OLD mailHost.send(messageText =
mComment, mto = mTo, mfrom = mFrom, subject=mSubject) PM OLD Here are my
changes to get it to work now. mailHost =
- lists do not work the same in a document with
text format = structured text. for example in old plone a list
<ul><li/>abc<li/>bcd</ul> works perfectly fine ... but
in new plone ... all the > after the / are displayed before list item.
Ok you may want to burn my use of HTML but hey the old version of plone worked
with this, the new version is not backwards compatible.
- all CMFDocument types with text format = HTML
that contain forms, after they are converted to ATDocument, do not work when you
navigate to them. YOu basically get a page with all the form elements such
as buttons, input types, radio buttons all missing. Once again plone 2.1
buggered. If I do a diff on the html that is being used by both plone 2.0
and plone 2.1 the html is exactly the same except that the order of the html
attributes is a little different but no matter about this.
Re: Plone 2.0 to Plone 2.1 - Some Issues Plone HTTP Port, HTML AT Documents, MailHost
if your trying 2.1.1 and still have these issues, could you file them
into the plone.org/collector so they don't get lost in the list traffic?
Peter Millar wrote:
> We have a successful site created in plone 2.0.1, we are trying to
> migrate to plone 2.1 for the simple reason to stay uptodate. However it
> is becoming more effort than what is worth. Our site is made up of dtml
> docs, zsql scripts, page templates etc. I tried running the migration
> of CMFDocuments to AT Documents, and this seemed to work for somethings
> but not everything.
> I run plone on windows. I have installed the Plone 2.1 windows
> installer only. No changes, no added products. Brand new machine,
> brand new plone windows install.
> I will try to list each of the issues I have had and their resolution so
> Well these are the issues so far
> Peter Millar