eCampaigning tool bombing during generic setup?
si si
I have (re)installed from the latest svn branch (0.2beta) from the
collective, and when I go to reinstall in the quick installer, I get
an attribute error (pasted below). It's bombing at the generic setup
steps (I think). On our production site we are using plone2.5.2 but I
also tested on our test site which is 2.5.3 and I get the same error.
I could roll back to the older version of eCampaigning but there is
that wee issue of data integrity. We've got a new action alert for
tomorrow so I'd love to use the tool again and not our old php, so if
anyone has any hints before the end of the day, I'd appreciate hearing
them!
Cheers,
sisi
Zope 2.9.8-final with plone 2.5.3 or
Zope 2.9.6-final with plone 2.5.2
using the following branch of the eCampaigning tool:
https://svn.plone.org/svn/collective/eCampaigning/branches/0.2/
Transcript
2007-11-15 12:50:30
failed:
Traceback (most recent call last):
File "/home/foei/members/Products/CMFQuickInstallerTool/QuickInstallerTool.py",
line 322, in installProduct
res=install(portal)
File "/opt/Zope2.9/lib/python/Products/ExternalMethod/ExternalMethod.py",
line 225, in __call__
try: return f(*args, **kw)
File "/home/foei/members/Products/eCampaigning/Extensions/Install.py",
line 248, in install
applyGenericSetupProfile(self, out)
File "/home/foei/members/Products/eCampaigning/Extensions/Install.py",
line 24, in applyGenericSetupProfile
setup_tool.runAllImportSteps(purge_old=False)
File "/home/foei/members/Products/GenericSetup/tool.py", line 251, in
runAllImportSteps
message = self._doRunImportStep(step, context)
File "/home/foei/members/Products/GenericSetup/tool.py", line 725, in
_doRunImportStep
return handler(context)
File "/home/foei/members/Products/eCampaigning/setuphandlers.py", line
7, in config_actionrecord_catalog
catalog = site.actionrecord_catalog
AttributeError: actionrecord_catalog
Duane Raymond (FairSay)
We'll check it out - although your timing is a bit tight for us
:-)
We've got the latest version of the eCampaigning Tool from the
0.2 branch running successfully on both whiteband.org and on
fairsay.com (both of which were upgraded from previous
versions)...so I'll check with Petri what the issues are.
In the next 'release' the 'actionrecord_catalog' in the error
statement allows you to control what data is published (e.g. if
you wish to have a public list of who has completed the
petition) - and at first glance it seems to be an issue with
that.
(there are also a number of other improvements to security, the
portlet and other issues - but that is in the history file and
I'll make a list when it is bundled and released)
Hopefully it is simple to resolve (and we appreciate you trying
it out!)
Cheers,
Duane
===========================================================
Duane Raymond
FairSay - Making Campaigning Count
+44 (0)207 993 4200
IM: fairsay (Skype, Yahoo!, Google, MSN)
Blog: http://fairsay.com/blog?utm_source=dr&utm_medium=ems
Bookmarks: http://del.icio.us/fairsay
Web: http://fairsay.com/
FairSay is a ltd. company registered in England and Wales. Reg.
No. 5244802
si si
Thanks for your reply - please don't sweat it, we're using
ploneFormGen as a temporary measure for this cyberaction (we had a
tight schedule too, how those campaigners like to keep us on our
toes!) and the next one, which is coming up next week.
I worked out (after sending the email) that it had to do with the
actionrecord_catalog but it seemed to me to be looking for a file or
script or object called actionrecord_catalog while installing, not
finding it and therefore bombing. I couldn't work out where this
object was supposed to be, or where it was supposed to be created,
though I assumed it was supposed to be created at the root of the
site:
site = context.getSite()
catalog = site.actionrecord_catalog
So anyway, I couldn't get further than that. I realised that this was
a shiney new feature, so I hope it's something easy to work out, so
that we can continue using the tool. Every time we want to test
though, it's because we have a cyber action coming up. It would be
better to set up a mail server on our test site and test while we are
at leisure! But it will be a while before I can ask our sys admin to
set that up.
When this current rash of cyberactions are over I'd like to assess how
ploneFormGen worked for us to see if we can get the best of both
worlds into your kick ass eCamp tool.
One of the things I was thinking about for the eCamp tool was having a
suite of products (based on the plone4artists model) rather than one
big product. I was hoping to talk to you at the plone conf (I missed
you both!). Anyway if you think that an interesting idea we can
discuss it further here. I thought it might make it easier to get
other developers on board and stream line all the options for the end
users, but I don't know what your master plans are! :-)
Anyway, a discussion for a rainy day. Good luck with whatever it is
you're working on,
sisi
Duane Raymond (FairSay)
> > > I have (re)installed from the latest svn branch
> > > (0.2beta) from the
> > > collective, and when I go to reinstall in the quick
> > > installer, I get
> > > an attribute error (pasted below). It's bombing at the
> > > generic setup
> > > steps (I think). On our production site we are using
> > > plone2.5.2 but I
> > > also tested on our test site which is 2.5.3 and I get
> > > the same error.
> I worked out (after sending the email) that it had to do with the
> actionrecord_catalog
<snip>
Petri and I think we may have a solution for your problem..but we need
you to try it and see if it works for you.
As you will have seen, the actionrecords_catalog is needed by the
latest version of the eCampaigning Tool. What we suspect is that all
the additions to make this work aren't being installed properly
(despite being defined in the installer) when you try and upgrade.
So - what we suggest is to try these things:
1) Add the following properties via the ZMI at
/portal_properties/ecampaigning_properties/:
a) Name: recent_actions_count ; Type: Int ; Value: 100 (flexible -
just determines how many of the latest people who have taken actions
will be displayed)
b) Name: actionrecord_catalog ; Type: string ; Value:
actionrecord_catalog
2) Check via the ZMI if the catalogue named actionrecord_catalog if
exists (it should!) If not, maybe try creating it (a ZCatalog).
Doing #1 might be enough.
Note that we now have the eCampaigning Tool latest SVN version (with a
few css fixes and field validation fixes) running on the fairsay.com
site (the eCampaigning Forum registration - not a campaigning action
but using the same functionality) and it is working fine - so it must
be to do with upgrading it.
The next formal release (soon - really!) will be a release candidate.
Let me know if this works.
Cheers,
Duane