silverstripe-archive/silverstripe-cmsworkflow

Workflow module for SilverStripe CMS

silverstripe-cmsworkflow's Issues

Batch "Request Publication"

Have "Request Publication" as a Batch Job

Support automatic review dates

From: http://open.silverstripe.org/ticket/3318

Add a notion of review dates for pages in the CMS, noting that there ought to be useful common functionality (which this ticket would provide), and that many organisations will want the functionality customised in many random ways.

There is a list of common CMS pitfalls of automated review dates here, which should be respected: http://www.steptwo.com.au/columntwo/do-automated-review-dates-work/

Notes:

Add a 'review date' field to a tab. It would automatically set to a certain interval, e.g.
3 months.

Allow the user to choose easily understood intervals (e.g. 3 months, 6 months, 12 months) as it is easier to set than a calendar picker. But do allow for special situations a calendar picker; it is still useful for when content might align with some business event (new financial year, for instance.)
Provide soft reports to indicate old content. E.g. colouring tree items? Report at bottom left of page? If you view a page should it have a soft dialog to say that "This page needs review. If is is okay then review again in 6 months"
Realise that if 1000 pages all have the same review date, then it will be ignored and redundant. Provide some way to help scatter dates, or efficiently push out review dates. The bulk action box might, for instance, be enhanced to say "Push all review dates out to 1 month from now". This allows people to quickly select major parts of a sitemap and defer review.
Email notifications, RSS-feed style notifications, and setting a person as the reviewer are topics for discussion... but it does relate to workflow so have placed it there. It is also related to embargoexpiry module, in a way.

Missing Documentation

The PDF doesn't say about having to run the "ScheduledPublishing" task every minute to have the Embargo/Expiry functionality to work.

Possibly good to have a config setting that enables/disables this so that if they are unable to have Cron Jobs

Compatible with SilverStripe v3.0.5?

Does this module work with v3.0.5? I am trying to get it to work but get loads of errors after I do the DB flush - it kills SilverStripe and I have to reinstall it? Is this the way to install it? Seems a very odd way to install modules to a CMS? I am used to MODx and WordPress where you just click to install and bang... all done...

I am new to SilverStripe but very impressed by the CMS workflow module - could someone advise if this will work with the latest version of SilverStripe (e.g. v3.0.5) and how to install the module please?

Cheers,

Batch Actions - Publish - not useable in workflow

From http://open.silverstripe.org/ticket/3109

If you are a user with rights to save but not publish, you can not use the Bulk Action "Publish Selected Pages" button.

When you click save it says "Error", presumeably because you don't have rights.

This prevents people from being time effective, as they have to select each page manually...

It should, in some way, just 'request publish'.

Note: Imagine if you have selected 5 pages, some might have publish rights, and some might not have publish rights. So perhaps we need a "Request Publish" and a "Publish" button. When you use the "Publish" button on pages where you don't have access, it just says "Some pages were requested to be published because you don't have direct access to do this".

Javascript Parse Error, Batch "Reset expiry date" on deleted page.

Presumably this action should be not allowed? Or at least, should warn gracefully

Workflow mail uses language of triggering user, not that of the receiving one

The Workflow mails sent by the system don't use the correct/expected language. When a user with cms locale set to German triggers an event (request publication, approve it,...), the mail is sent in German, no matter whether the receiving users have the cms locale set to French or English.

Ensure full translatable support.

From http://open.silverstripe.org/ticket/6524.

The outputs of the cmsworkflow module are only very sparsely translated. This is because most messages i.e. in the templates are hard-coded and do not make use of _t(...). Therefore, the module is more or less inusable within non-English environments. For example, when using de_DE it is very chaotic. Moreover, not only the templates like SiteTreeCMSWorkflow_workflowtab.ss are affected, but also:

error/status messages (-> user_error() )
workflow reports including their titles
the relevant entries in the "Access" tab
the titles of the workflow tabs as well es other outputs from updateCMSFields() of i.e. SiteTreeCMSWorkflow.php
the "Created" column of the "Workflow Archive" tab
I regard these missing translations as critical, especially within the templates, since they do not really allow the use of another UI language.

Error on save and piblish of draft page

When I hit Save and Publish on a draft page, I get an error in the CMS workflow plugin - looking on Firebug the error is:

"NetworkError: 403 Forbidden - http://example.com/index.php/admin/EditForm"
403//Action "cms_publishwithcomment" not allowed on controller (Class: CMSMain)

Any ideas?

Running SS v 2.4.7 and CMS workflow v1.0-rc4

Thanks

Batch Embargo Date

If you set the Embargo Date via the Batch Action this just marks for Awaiting Approval, there is no way to do the Embargo Date & "Save & Publish" via Batch Actions

If the user doing this action is a Publisher then should just be Scheduled as opposed to 'Awaiting Approval'.

Other option would be to add batch Action of 'Awaiting Approval' or via the Reports section (Preferably both)

Workflow issues

Start with an Unpublished Page

• Request Publication
• Set Embargo Date
• Save & Publish
• (WorkflowRequest Status field is "Scheduled")
• Edit the Page (Save)
• WorkflowRequest Status field reverts to "Awaiting Approval"

Shouldn't this revision stay as "Scheduled" and there should be a new WorkflowRequest that would be "Awaiting Approval"

Future State from CMS Admin

This isn't producing a link that works

You end up with a link like "/food-drink/main-space-bars/?futureDate=NaN-NaN-NaN NaN:NaN:00"

SS3 - not compatible

The module is incompatible with Silverstripe 3.

Is there any plan to make it compatible or the cmsworkflow will become obsolete with SS3?

Move to archive?

cc @chillu