Working with the Elgg trunk in the SVN repository one finds many features of Elgg 1.1 beginning to appear. If you look at version.php, you’ll see that the current version has shifted from version 1.07 to 1.08. Be warned though, working with the trunk can be risky. The Elgg SVN is currently divided into releases and trunk. The trunk represents the latest code for Elgg, but it is not tested thoroughly like a release is. It is best to work with trunk on test sites. If you do so with a production site, make sure you have backups of both the files and the database!
There are new administrative tools including a profile editor. This is an often requested feature. It currently allows admins to insert additional fields in the Profile Block labeled now labeled: profile:edit:default.
Just type a label for your new profile field, then select the type of field. New fields will become options when users edit their profiles. For example, an education site might want to create a text field for school district.
Another new item in the administration toolbox is the Language tool.
Click to enlarge
This lists the progress of the translation of Elgg into various languages. This will help developers decide whether Elgg is viable in other languages. Click a language and it lists files not yet translated.
Click to enlarge
The final new item is the API Administrator.
Click to enlarge
To be truthful, I am not sure exactly what this will do. I assume that it will provide a way for other websites to tap into information for a given Elgg site like Google APIs which create pairs of key codes for a specific url.
Click to enlarge
I find this an exciting possibility and look forward to hearing more about this feature.
This overview of new features in the upcoming Elgg 1.1 gives us a glimpse into the directions in which the developers are heading with Elgg. We have more customization through the admin interface, a commitment to translations to other languages, and more possibilities in interacting with other sites.
Related Posts
Tags: administration, Elgg
-
In Elgg there is a framework for plugins to export functions via the restful interface – for this of course they need to be provided with a key.
The API admin pages provide one way get this key and give it to clients (another could be a plugin that provides a user side front end for self signup). This lets sites easily export functionality to client widgets.
-
Pingback from Elgg 1.09 in SVN | openedweb.com on October 16, 2008 at 5:10 pm
-
I think friend request and more privacy settings are a must for the next update.
-
Pingback from Elgg 1.1 Released | openedweb.com on October 30, 2008 at 10:47 am
This work by Stephen J. O’Connor is licensed under a Creative Commons Attribution 3.0 Unported License.
4 comments
Comments feed for this article
Trackback link: http://openedweb.com/blog/2008/10/15/elgg-11-admin-features-appearing-in-svn-trunk/trackback/