Announcing SilverStripe 2.1.0-rc1, the first release candidate leading up to the 2.1.0 release. It contains the following notable changes:
- Theme support
- Widget support
- Better extension API
- Unit testing framework
- Comment administration section, and comment moderation
- TinyMCE has been updated to 188.8.131.52
For a full list of changes see [url=http://doc.silverstripe.com/doku.php?id=changelog]the ChangeLog[/url]. Documentation for these features will be provided before the final 2.1.0 release, which will coincide with the release of the new blog module. You can download SilverStripe 2.1.0-rc1 from the following location:
Please test and provide feedback so we can make 2.1.0 nice and stable!
I am now running through the installation steps (this should take about 30 seconds)
If you receive a fatal error, refresh this page to continue the installation
# Creating 'mysite/_config.php'...
# Creating '.htaccess' file...
# Building database schema...
# Checking mod_rewrite works
# ERROR: mod_rewrite not working, redirecting to mod_rewrite test page
I will now try and direct you to rewritetest to troubleshoot mod_rewrite
there its stuck...
and this is what i get after installation failure,,,
FATAL ERROR: None of these templates can be found: Page.ss, ContentController.ss
At line 67 in C:\wamp\www\silverstripe-v2.1.0-rc1\sapphire\core\SSViewer.php
testing done using latest version of WAMP with rewrite_module enabled and working with other CMSes...
cheers, hopefully you help me out maybe i do something wrong coz i'm new to Silverstriper
15 September 2007 at 3:46am
(Last edited: 15 September 2007 3:56am),
Installed and seems to work for me. The save & publish is a nice improvement.
The access tab seems to be what I need, but unfortunately in 'security groups' you can't set group member permissions for sections of the frontend - as suggested in http://doc.silverstripe.com/doku.php?id=permissions:codes.
It would be nice if we could set this on certain id's and include subpages as well.
So I guess this access-tab is for people who can login into the backend only?
I think this would be much more useful if this would allow us to control 'frontend' users as well.