7.x

Ok, ok, ok. Without further ado, finally a D7 1.0 release for Boxes.

Changes since 7.x-1.0-beta8:

• issue #1491618 by lefnire: stdClass::cache_setting()? when visiting space enable user page
• issue #1444544: Box visibility settings do not save

#1535284: Add option reset either database, files, or both

Corrected access control bugs

First official beta release.

Development release.

Achievements 7.x-1.5, 2012-05-01
--------------------------------
* API CHANGE! API CHANGE! API CHANGE! API CHANGE! API CHANGE! API CHANGE!
* If you have any 'hidden' type achievements, retype them to 'secret'.
* "secret achievement" is more commonly known than "hidden achievement".
* "secret" reads better with the newly available "invisible" type (below).
* IF YOU DON'T RETYPE, HIDDEN ACHIEVEMENTS WILL BE EXPOSED TO USERS.

* 'invisible' achievement types can now be created.
* These will NOT display on a user's Achievements tab (unless unlocked).
* They will display elsewhere as needed (leaderboards, per-page, etc.).
* Some possible uses of 'invisible' achievements include:
* Tenure-based achievements to thank long-time users, beta testers, etc.
* To "reveal" a user's achievements instead of defaulting to all locked.
* You can set an achievement to be both 'secret' and 'invisible'.
* Makes it invisible on the user's Achievements tab (unless unlocked).
* Shows the secret placeholder text when displayed elsewhere.
* New hook added: hook_achievements_access_earn().
* Allows you to programmatically determine if a user can earn achievements.
* See the new submodule, achievements_optout, for an example of its use.
* A new and optional submodule is added: achievements_optout.