Announcements
For some reason we can't grasp there's a sense that concrete5 was designed for small sites. Is this just because it's easy to use and our interface is sexy? So much enterprise software is horrible to use that it's easy to believe "no one would possibly want to use this, so enterprise ready = ugly."
I walked through the Occupy Portland encampment before it was broken up....
Last year we were pleasantly surprised to be mentioned as one of two systems to watch and the fastest growing community in the 2010 open source market share report.
This year the data gathering notice email got buried, and we're way behind. This is bad news.
Only you can help.
I know surveys are a complete drag, but it would really mean a lot to me and the community if we continued to be accurately represented in this report for 2011.
If you feel like concrete5 has saved you any time at all, please help us by giving just a few minutes back and filling out this survey. Tell your friends, tweet your link, stick it on your G+facebook-umbler thingie. This has got to be one of the easiest things you could ever do to give back to the community, so please help us all continue to grow!
Check out the new Editor's Guide wiki in the documentation section. Built by the community for the community - how cool.
Date: Wednesday October 12th
Time: 7pm onwards
Venue: Phoenix Square, Leicester, LE1 1TG
Ryan just posted the current development version of the wordpress site importer to github:
https://github.com/concrete5/wordpress_site_importer
When this is ready for showtime it'll be a free add-on.
This was originally written by ScottC, then GregJoyce picked it up at concrete5. It's status is described in the README in the code, but it basically works, even with really large imports, but it's formatting is a bit rough and the data that's imported is not complete.
If anyone has energy to put into it it'd be much appreciated.
Love concrete5 but haven't told everyone you know about it? Well let these awesome T-Shirts do the job for you.
Versions of concrete5 feature rudimentary anti-spam tools, including an IP ban-list and captcha support, but no unified settings page for managing these items. Furthermore, there is no support for any captcha besides the SecureImage library, which is a bit long in the tooth (and somewhat ineffective), nor is there any support for a third party anti-spam service like Typepad Anti-Spam or Akismet. We would like to change this in concrete5 5.5.
While concrete5 can support multiple authentication methods, and has built-in support for OpenID (in addition to the core concrete5 authentication method), there's no framework for building these authentication methods, making their settings available to administrators in the dashboard, grouping them on a login page or managing which authentication methods are available or how they are displayed. The Authentication Framework will change that.