This release features both security and maintenance upgrades.
For new users, this is the best version to download and install. The download tarball contains a directory named "Instructions" that contains some instructions on getting started. For additional help, and/or to get involved with the DrupalEd community, submit issues to the issue queue or join the DrupalEd group.
For existing users, you do not need to download and install this tarball. Rather, you should be managing your upgrades by using the update status module. This module will help you keep your DrupalEd install current and secure. If you have an existing DrupalEd site, you should upgrade immediately to keep your site secure.
The code upgrades included in this release include updates to the Calendar, Organic Groups, Pathauto, Date Range Filter, and Tagadelic modules, in addition to an upgrade to Drupal core.
For more information on the security upgrade, see the announcement.
Comments
More info on DrupalEd?
I went looking for more description (marketing/education collateral) about DrupalEd, and couldn't really find much at DrupalEd.org or DrupalEd Profile. Is there more information anywhere that I can use to compare DrupalEd to other solutions, like Edline?
Erik Britt-Webb
drupal@bwaccounts.net
Erik Britt-Webb
drupal@ebrittwebb.com
If you have the time to write them up
we'll be glad to work with you to include them in support of the profile --
Add any suggestions/ideas to the issue queue, and we can work on them there -- http://drupal.org/project/issues/drupaled
This would be great documentation to get in place, and we will definitely support any efforts from within the community to make this happen.
Cheers,
Bill
FunnyMonkey
Tools for Teachers
FunnyMonkey
Noshow under profile listings?
Any idea why the DrupalEd Profile doesn't show up in the listing of Drupal Profiles?
Erik Britt-Webb
drupal@bwaccounts.net
Erik Britt-Webb
drupal@ebrittwebb.com
Yes.
There is no install profile built for DrupalEd -- the install process uses a .sql file instead. Pages listed here: http://drupal.org/project/Installation+profiles all have downloads.
This approach makes for a slightly more complex install, but allows for a cleaner site -- this approach allows us to have, for example, tinymce installed and configured correctly, with the javascript compressor in place, out of the box -- this saves end users the complexity of downloading the tinymce module, downloading and unzipping the tinymce package from moxiecode, and downloading and unzipping the compressor, and then moving the files into the proper location, and then uploading the module into the proper place.
This also allows us to ship with the audio module pre-configured with the getid3 libraries in place, and to target specific versions of modules.
There is a long and storied history about external code and its place on drupal.org -- and I'm not bringing this up because this issue needs revisiting, but simply to provide context.
The current approach allows us to maintain a balance between supporting a secure body of code that is fairly easy to install and fairly easy to use.
As noted in this very thread, we would love folks to pitch in with documentation/ideas and execution on how to make improvements -- using the issue queue allows us to centralize these efforts.
Cheers,
Bill
FunnyMonkey
Tools for Teachers
FunnyMonkey
See this thread for a good
See this thread for a good discussion of the pros and cons of install profiles: http://groups.drupal.org/node/6820
Cheers,
Bill
FunnyMonkey
Tools for Teachers
FunnyMonkey