The information in this wiki hasn't been maintained for a good while. Some of the projects described have since been deprecated.

In particular, the "Ushahidi Platform v3.x" section contains information that is often misleading. Many details about this version of Platform have changed since.

This website is an extraction of the original Ushahidi wiki into a static form. Because of that, functions like logging in, commenting or searching will not work.

For more documentation, please refer to

Skip to end of metadata
Go to start of metadata

This page doesn't document all changes in 2.4, but specifically documents breaking changes that may effect developers migrating to v2.4

Full list of changes since 2.3.2

What's changed

  • New parameter added to category::tree();
    • parameters are now: tree($categories, $hide_children = TRUE, array $selected_categories, $form_field, $columns = 1, $enable_parents = FALSE)
    • This may break themes with a custom reports_submit.php view
    • To work around this change the line


* Session driver changed to 'database' by default

    • This was tried previously and reversed in 2.3.2
    • Bugs with this were due to access control in the base controller always called $auth->auto_login() instead of $auth->logged_in()
  • XSS security fixes
    • Lots more fields are now properly escaped with strip_tags() or html::specialchars()
    • This shouldn't break anything, but if you had previously used html in some fields you might not be able to any more
      • Mostly this is user fields or report fields
  • Access level's for admin, member and superadmin roles have changed
    • This shouldn't break anything as previously the permissions checks that relied on these (in custom forms) didn't work
    • New access levels: superadmin = 100, admin = 90, member = 10
    • If you have custom roles and use custom forms, make sure you check your access levels are in the right order
  • Openlayers updated
    • Again, this shouldn't break anything.
    • Just includes a fix to stop the google maps attribution popup.
  • New format for the Settings table
    • Configuration settings are stored as key-values pairs, instead of using a single record with multiple fields
    • This should not be a problem, but be careful if you have scripted installs or updates using this table