workflow states cannot be renamed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope CMF buildout |
Fix Committed
|
Low
|
Unassigned | ||
Bug Description
CMFCore 2.2.2 on Zope 2.12.10:
Attempting to rename a workflow state from the "States" tab of a workflow definition in the ZMI results in the following traceback:
2010-08-28 17:33:19 ERROR Zope.SiteErrorLog 1282984399.
Traceback (innermost last):
Module ZPublisher.Publish, line 127, in publish
Module ZPublisher.mapply, line 77, in mapply
Module Products.
Module ZPublisher.Publish, line 47, in call_object
Module Products.
Module OFS.CopySupport, line 359, in manage_renameObject
Module OFS.CopySupport, line 539, in _verifyObjectPaste
CopyError:
<HTML>
<HEAD>
<TITLE>Not Supported</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<FORM ACTION=
<TABLE BORDER="0" WIDTH="100%" CELLPADDING="10">
<TR>
<TD VALIGN="TOP">
<BR>
<CENTER><B><FONT SIZE="+6" COLOR="
</TD>
<TD VALIGN="TOP">
<BR><BR>
<CENTER>
The object <em>private</em> does not support this operation.
</CENTER>
</TD>
</TR>
<TR>
<TD VALIGN="TOP">
</TD>
<TD VALIGN="TOP">
<CENTER>
<INPUT TYPE="SUBMIT" VALUE=" Ok ">
</CENTER>
</TD>
</TR>
</TABLE>
</FORM>
</BODY></HTML>
Changed in zope-cmf: | |
importance: | Undecided → Low |
status: | New → Confirmed |
I think the best thing to do is to remove the option to rename a workflow. Not least because any objects attached to a particular workflow will need updating anyway. It will be less confusing to delete and add rather than rename in this context.