10930 Posts in 2613 Topics by 1810 members
Page: 1 2
|Go to End||Next >|
26 March 2010 at 1:49am
I have tried installing CMSWorkflow both on 2.3.6 and 2.4. its not giving me any error messages but just a blank white screen.
all my sites are in dev mode.
i have tried cmsworkflow-v1.0-rc3.tar.gz which is compatible with: SilverStripe 2.4
and 1.0-rc3 1.0-rc2/
all are not working for me. it was better if i had an error message
28 March 2010 at 2:27am
after a clean installation 1.0-rc2 worked for me.
30 March 2010 at 5:02pm
I have the same issue (blank screen) with CMS Workflow (rc2, rc3, and trunk-r101776).
silverstripe-v2.4.0-beta2 + genericdataadmin-trunk-r91391 + subsites-trunk-r101755
Errors from the apache logs:
PHP Fatal error: Class 'PopupDateTimeField' not found in ... /BatchSetEmbargo.php
CMS Workflow looks like it prefers TZDateTimeField and defaults back to PopupDateTimeField, neither of which exist in 2.4.0-beta2.
Tried Latest Daily (silverstripe.2.0.DailyBuild.2010-03-30) but that won't even let me run dev/build.
Based on errors in the apache error log, I copied the following from the Daily back into 2.4.0-beta2:
Flat specified but can't find parent.
$.concrete is not a function
this.icon is null
$("Form_EditorToolbarImageForm").respondToNodeChange is not a function
30 March 2010 at 9:57pm
I copied the following from the Daily back into 2.4.0-beta2:
You should install the legacydatefields module - it has the legacy form fields from 2.3 which you will need to keep workflow going. It appears workflow hasn't been updated to support the new date API yet so hence the need for that module.
30 March 2010 at 11:30pm
Cheers Willr, I was about to start off on a rant about how it isn't working for me either .
31 March 2010 at 11:08am
I found the module (http://open.silverstripe.org/browser/modules/legacydatetimefields) but failed to find the tarball for SVN dummies.
Instead I reverted to standard SS 2.4.0-beta2 and hacked the trunk of cmsworkflow to change reference to PopupDateTimeField to DateTimeField (tarball of changed files attached).
This gets things going but some of the workflow reports (Recently published pages, Published pages with Expiry on, Approved pages with Embargo on) don't work as DateTimeField does not have defaultToEndOfDay or allowOnlyTime which were functions of PopupDateTimeField.
This is working enough for me for now.
I'll keep an eye out for the CMS Workflow release that is updated for the new API.
10 April 2010 at 1:07am Last edited: 10 April 2010 1:09am
"You should install the legacydatefields module "
where is the link to this module
unfortunately my host does not support SVN
this http://open.silverstripe.org/browser/modules/legacydatetimefields/trunk?rev=102286 does not help people like me
10 April 2010 at 6:41pm
If a modules in the svn repo but the author hasn't created a module listing you can download anything as a archive straight from open. You can craft a URL like this in your webbrowser..
So in your case for legacy date fields
Note this URL does create a slightly weird folder structure - you just have to make sure that its the usual format.
Its a handy little trac trick to note. I have it bookmarked as a keyword in firefox.
Page: 1 2
|Go to Top||Next >|