Content Types

Some of the functionality of this site is new to me and I'm trying to learn.   If I create a new contect type and want it to have the group  characteristics of already existing content types do I need to create a new feature? How is a system-defined content type created?   If someone could point me the right direction I would appreciate it.   Thanks

Comments

mike.stefanello

Hi, Unfortunately, the

Hi,

Unfortunately, the process of creating new content types and having them act within groups as the others do, isn't very simple. The complicated part, is having them reside as a section via the tabs on the group home page.

  1. Create a new content type as you would with Drupal normally (/admin/content/types/add).
  2. On this form, under the Organic groups fieldset, tick Standard group post.
  3. Set the desired permissions (/admin/user/permissions).

Now, you'll see a "Create *content-type*" link on the group block when inside a group. If you want to create a new tab for this content type, you must:

  1. Clone an existing content-type view - for example, Blog posts (View: og_tab_blogs)
  2. Change the needed fields: Title, Header, Empty text, Path, Menu, (Argument) Organic groups/Title, (Filter) Node type
  3. Feel free to change the fields, sort, and filters as you desire.

That should do. Please let me know if you have any problems or questions.

Thanks,

Mike

jlocke

Thank you

Actually it was pretty easy once I understood what was happening.  That really helped me get an idea of how the system works.  Thanks for the prompt and helpful reply,  I really appreciate it.

goatcheeta

Thank you

Your directions were great - I added a gallery type the first time

jay

Excellent!

Glad to hear people are pushing the boundaries beyond what Commons does "out of the box."

Is your site going to be public-facing when complete? (Or internal?)

goatcheeta

Internal currently

Internal only right now.  I manage churchsp.org for St. Peter's Episcopal  Church in Port Royal, a Drupal 6 site.  I don't plan to add Commons unless my wife the rector and the Vestry give me the go ahead. (That's the only reason beyond testing since Commons already is great!).  Then the existing site would keep the same theme and Commons will have its own to differentiate.  (Churchsp.org is currently non-iteractive according to the wishes of the Vestry). 

The content types  for this site and Commons do not overlap except for gallery-assist. I used the modules themekey with themekey properties to separate galleries intended for the non-interactive portion and those related to groups.  Maybe there is a better way to do this.  

I have a long way to go to test all of it but so far so good.   

juan_g

Great for Commons customization

Mstefanello's instructions on this thread open many, many customization possibilities. It's really one of the deciding factors to use Drupal Commons.

nik

Thanks

Thanks for the step by step instructions to add a content type that is accessible within a group!

davidgibbens

New content type in group works but for page title

Hi Mike (or anyone)

I'm on DC 1.6.

I too followed your instructions and found them relatively easy to follow.  We needn't give the message this is difficult to do. That's the good news.

However, when I tried it i did find what seems to be a glitch.  On what is effectively a test site I created a new content type "Teachers".  I cloned the group_tab_blogs view as the basis for the group_tab_teachers view.  Changed the title of the display to Teachers (double-checked that).

All fine and in accordance with your instructions and results: the Teachers tab appears in the group menu block and if I  click the tab in the group up comes the view of the Teacher nodes as specified in the View. But the page header says All users group - blog posts.  This seems to be put together from the name of the group plus ???. And where is it put together?  How do I change it?

Here is a Link to screenshot

davidgibbens

Sorted - in organic groups arguments

Thought I would leave my original post and reply with the solution in case anyone else gets stuck. I haven't used OG before and was just focusing on the "normal" view attributes visible on editing the view.

The fix is in the Organic Groups: Groups argument, which was mentioned in Mike's original post.  That contains a Title.   Thanks for the info.  RTFM.

jay

Great info, David

Thanks.

We really need to get started on good documentation here; and guess what? We're going to start real soon.  We actually have a person at Acquia who is going to start doing this in a couple of weeks. We'll have him troll around for stuff that's useful (like yours here) and pull it all together. I'm going to start tagging comments so we can search for stuff like this.

Good find!

#documentation

jefflocke

I am working on a church site as well

I am building a conventional church website with the typical Drupal functionality and using Commons, more behind the scene, to allow small groups within the church grow.  I hope Commons will be a helpful way for volunteer committees to keep their work moving forward between conventional meetings.  Once the site is functional I will be happy to provide the URL.  We will probably purchase one of the Fusion themes from Top Notch and sign up for Acquia support.  Thanks for providing such a great tool

bribiz

A resource for churches

You may want to check out opensourcecatholic.com.  It's a community for developers working on church projects using drupal and other open source software like wordpress.

bribiz

Features

I figured out how to do this before I found this thread.  If there are common content types people want to add, perhaps the commons community should explore creating features.  Commons already uses features and  the features module.

For example, I'm working on adding the case tracker module.  It's really the only major feature I found missing from open atrium as long as you don't want separate spaces for each group.  I don't need each group to have unique customizations.  In fact, I want all my groups to work the same to keep it simple for users.

So I've found that I need to:

  1. Install the case tracker module
  2. Add a project content type
  3. Add a case content type
  4. Configure case tracker
  5. Clone one of the 'og_tab' views for cases and one for projects
  6. Create a panel to mimic the project and case views in open atrium.

I believe this could all be combined into a feature set that can be added to a site using the features module.  I haven't created any features in drupal yet but I plan to utilize them in the future.

Right now I'm working on the panels functionality.  Once panels are done I believe I will enjoy the ability to easily add new functionality.  Unfortunately I've found the learning curve for open atrium and the creating customizations to suck up too much time.  I like the fact that commons is based on typical drupal functionality.

I do have a couple issues with passing arguments into panels and keeping the the tabs at the top of the page but I will open those issues in another thread later.

jay

Case Tracker?

Hi -

Interesting to see your work to bring in Case Tracker.  If you end up creating a Feature out of it, please let us know (here).  I'd consider making it available as part of the Distro (whether or not enabled by default).

I'm curious about what your functional requirement is, and whether Case Tracker actually meets it well. I started a wiki page to capture about what people want with regard to projects / tasks; could you note your thoughts there?

SkyWombat

Thanks

...works like charm.

One point I still do not quite understand regarding groups and content types is the following

If I have two types of groups and would like certain node types only to appear in one of the group types, how is this achieved?

Thanks and best regards

SkyWombat

mike.stefanello

Unfortunately, as of now,

Unfortunately, as of now, it's not. But it's being worked on.