spaces_panels.module: Full Spaces/Panels Integration (Patch!)

Here's a mega patch, an entirely new submodule: spaces_panels.module

Basically its full Panels integration, allowing for Panels to be used in the creation of full-fledged OpenAtrium features:

- Context: Adds "Space: OG Node Context" or "Space: User Context" to load current space's user or group node content. TODO: Taxonomy
- Access Plugin: Adds "Space: Feature Access" selection rule. Use this to have access control on Panels with menu items that you want controlled with the Features/Spaces UI. Same functionality of the Views access plugin, used to build Open Atrium

Needs Work:
- The two context plugins should load themselves automatically if they exist, just like the "Logged in User" context that is always present. This patch will not recognize your Spaces unless you manually add the one of the new "Space: xxx Context" contexts. I am looking into how to do this.
- Taxonomy Space Context.

Been doing some amazing things with this setup... "Context Exists" access checks are great, if its in a group, show one variant, if its in a user-space, show another.

This is much more powerful when you check out the other patch I just loaded, which makes users have their own path and space available, just like a group. This means, /blog can be /groupname/blog or /username/blog, using panels or views. Pretty fantastic.

Thanks!!!

P.S. still getting used to making patches with Git, if there's anything wrong let me know and I'll try to fix it.

Crudd... just realized this was built for beta4... updated patch coming soon, hopefully....

Setting back to active. This is something I'd be interested in and am attempting to update the patch to work with 6.x-3.0

Here's an updated version as a zip file.

Thanks for this, it's working for me to set access permissions on a panel based on Spaces: Feature Access. However, I'm seeing the following error messages:

The plugin definition of spaces is missing the title singular key. [error]
The plugin definition of spaces is missing the title plural key. [error]
The plugin definition of spaces is missing the title singular proper key. [error]
The plugin definition of spaces is missing the title plural proper key. [error]
The plugin definition of spaces is missing the schema key.

subscribe

Subscribing, because I'm about to try the module in #4 out.

This is AWESOME concept.

I was just asking about this on IRC.

I will try this out.

I see the same thing as in #5.

I can select the "Spaces: OG Node context" as a selection type for my panel.

It has no effect. The panel page is not accessible.

Edit:
I can use this module and og_panels to get an OG_conext for the group node and pull in description.

I am placing errors for the zip file in #4 here

I select Spaces: Feature Access as a context and get:

warning: Missing argument 2 for spaces_feature_access_settings(), called in /openatrium/modules/contrib/ctools/includes/context-admin.inc on line 632 and defined in /spaces_panels/plugins/access/spaces.inc on line 22.
warning: Missing argument 3 for spaces_feature_access_settings(), called in /modules/contrib/ctools/includes/context-admin.inc on line 632 and defined in /spaces_panels/plugins/access/spaces.inc on line 22.

I get this on admin/reports/status

Panels operating in Legacy mode	
Panels is operating in Legacy mode due to the following issues:
Panels 3.6 made changes to the rendering order in a way that affects certain style plugins. The above modules implement style plugins, but have not indicated their compatibility with this new system. See http://drupal.org/node/###FIXME for information on how to update style plugins to the new system.
spaces_panels - Style plugins

+1

+1

Just curious, does this allow for per space customizations to the panel page? I'm not talking about creating variants per space. I was hoping I could use Panels to build the default panels pages for a feature, but still allow the user to override those pages per space. Ex. choose different layouts per space

Spaces Dashboard does this with Contexts. You create the default context to display the boxes and any overrides are specific to that space.

Anyways, Spaces + Panels + Panels IPE would be awesome. Plus it would give end users a consistent editing user interface to work with.

I used panels for the content are only.
context handled all the other regions.
So define your different layouts via context and just allow panels to handle the content region.

can this be ported to 7.x too?