#26 — Plone 3.0 compatibility

by Tom Lazar — last modified Feb 21, 2009 10:28 PM

State	Confirmed
Version:	1.0
Area	Functionality
Issue type	Feature
Severity	Important
Submitted by	Tom Lazar
Submitted on	Oct 19, 2007
Responsible	Reinout van Rees
Target release:	—

Return to tracker

1.0 (and presumeably trunk, as it's 1 year old) don't run on Plone 3.0.

Are there any plans to make this product 3.0 compatible? If not, are there any plans for migration to another solution?

Steps to reproduce:: Unpackt the 1.0rc bundle into the products directory of a 3.0.2 instance and start it up. it will fail with an import statement from Formulator.

Added by Reinout van Rees on Oct 19, 2007 02:22 PM

Issue state: unconfirmed → open

Severity: Medium → Important

Responsible manager: (UNASSIGNED) → reinout

I haven't given much thought to it. I presume it wouldn't be too much work to make it run on 3.0, assuming we can get formulator to work.

Eventually, I think a move to ploneformgen is the logical course of action. For me, it'll probably depend on client work. We've got a fair number of ploneformmailer users, so eventually we'll get paid to do it.

I'd look hard at the amount of existing forms: how many are still in use? The form for 2005's christmas dinner doesn't need moving :-) If there are only a few current ones, moving them by hand might be most effective.

Added by Tom Lazar on Oct 19, 2007 04:06 PM

thanks for the info, reinout. ploneformgen was the crucial info that i lacked. it's only one form here for me, so i'll look into pfg then and probably just migrate that manually and be futureproof from then on ;)

No responses can be added.