|
|
|
Issue 220 of
NEW Zope.org (the website)
[ZOC]
|
| Title: |
Workflow Unnacceptable
|
| Status: |
Pending
|
Security |
related:
No
|
| Description: |
So now we have to make software release private to edit them? So every time I want to tweak anything, the product in question vanishes off Zope.org's ...
|
| From: |
chrisw
|
on: |
Aug 28, 03 07:36
|
| |
chrisw
|
Last update:
|
May 26, 04 16:19
|
| Topic/class: |
functionality/bug
|
Importance:
|
medium
|
| Version info: |
|
|
Issue 220 Transcript
|
|
5 entries
|
= Comment - Entry #5 by slinkp on May 26, 2004 4:19 pm
I presume this is another symptom of the same issue...
Yesterday I created a new Software Package:
http://zope.org/Members/slinkp/CMFBoringTool/view
... and added a Software Release:
http://zope.org/Members/slinkp/CMFBoringTool/CMFBoringTool-0.1.0
... and a Document:
http://zope.org/Members/slinkp/CMFBoringTool/README.txt
All three of the above were submitted, and the "state" link from all of them shows published & effecive; yet I cannot view any of them without being logged in.
Furthermore, the README.txt does not show up in Members/slinkp/CMFBoringTool/folder_contents ... and yet it is evidently there as I can view it??? what the heck???
________________________________________
= Comment - Entry #4 by simon on Oct 5, 2003 9:03 pm
:)
Yes, having just more-or-less figured out the product publishing process - it is much too complicated. I suggest removing workflow from Software Packages, Software Releases, Software Release Files for a quick improvement.
Until then, here's some fresh, hard-won magic that might save others some pain; see http://zwiki.org/zwikidir/Makefile for more::
zdo-swrelease-publish:
@echo publishing the $(VERSIONNO) Software Release on zope.org
curl -nsS \
-Feffective_date= \
-Fexpiration_date= \
-Fcomment= \
-Fworkflow_action=submit \
-Fworkflow_action_submit=Save \
-Fform_submitted=content_status_history \
$(PRODUCTURL)/$(VERSIONNO)/portal_form/content_status_history
@echo
zdo-swrelease-retract:
@echo retracting the $(VERSIONNO) Software Release on zope.org
curl -nsS \
-Feffective_date= \
-Fexpiration_date= \
-Fcomment= \
-Fworkflow_action=retract \
-Fworkflow_action_submit=Save \
-Fform_submitted=content_status_history \
$(PRODUCTURL)/$(VERSIONNO)/portal_form/content_status_history
@echo
________________________________________
= Comment - Entry #3 by simon on Oct 5, 2003 9:01 pm
:)
Yes, having just more-or-less figured out the product publishing process - it is much too complicated. I suggest removing workflow from Software Packages, Software Releases SoftwareReleaseFiles for a quick improvement.
Until then, here's an excerpt fresh from http://zwiki.org/zwikidir/Makefile , hopefully it will save others some pain::
zdo-swrelease-publish:
@echo publishing the $(VERSIONNO) Software Release on zope.org
curl -nsS \
-Feffective_date= \
-Fexpiration_date= \
-Fcomment= \
-Fworkflow_action=submit \
-Fworkflow_action_submit=Save \
-Fform_submitted=content_status_history \
$(PRODUCTURL)/$(VERSIONNO)/portal_form/content_status_history
@echo
zdo-swrelease-retract:
@echo retracting the $(VERSIONNO) Software Release on zope.org
curl -nsS \
-Feffective_date= \
-Fexpiration_date= \
-Fcomment= \
-Fworkflow_action=retract \
-Fworkflow_action_submit=Save \
-Fform_submitted=content_status_history \
$(PRODUCTURL)/$(VERSIONNO)/portal_form/content_status_history
@echo
________________________________________
= Comment - Entry #2 by chrisw on Aug 28, 2003 7:52 am
Good grief! I see you can't even do anything simple (such as submit documents within a software release) once it's been submitted.
Ow! Ow! Stop hurting me....
________________________________________
= Request - Entry #1 by chrisw on Aug 28, 2003 7:36 am
So now we have to make software release private to edit them? So every time I want to tweak anything, the product in question vanishes off Zope.org's navigation until someone gets a chance to approve it again?
Wow, that's gonna suck :-(
|
|
|
Log in
Forgot your password?
