panels_frame 7.x-1.0-alpha3

HEY! If you exported your "frames" to code (i.e. Features, etc.) this release will break your stuff. This is how you can fix it manually:

But why did it break??

Panels Frame changed how it's exposing its objects to Ctools' Export API. The "owner" has changed from "panels" to "panels_frame", and the "api" has changed from "layouts" to "frames".

• Move your hook_default_panels_frame() into module_name.frames.inc.
• In hook_ctools_plugin_api(), keep in mind that the $module is "panels_frame" (not panels) and the $api is "frames" (not layout).
• If you're using features, make sure your .info file contains features[ctools][] = panels_frame:frames:1

Why is there no automatic upgrade path?

Because this is an alpha release. That doesn't mean the code lacks quality or sustainability, it's just that maintaining backwards compatibility slows down the development of making this project even more awesome. This is pretty standard across any open-source project. Remember that I still love you all, though :)

Changes since 7.x-1.0-alpha2:

• Changing owner/api, as I realize this may confuse robots.
• Added object-cache helper functions.
• Managing own object cache instead of relying on export ui form wizards.
• Upgrade path for new object cache identifiers.
• Removing cruft in update hook.
• #1765746: Rebuilding theme registry after saving a stack.
• Handling clearing object caches in parent class in both add/edit and delete callbacks.
• Added test plugin "color" and associated callbacks.
• Additions to test module..
• Retrospective nitpicking.
• Added test layout.
• Added cache identifier helper.
• Delegating stack edit table to stack-admin include.
• Renaming form_state "object" with "item" to follow export-ui nomenclature.
• Stack edit form is now embeddable, and can be used to replace itself via ajax command.