Kevin Carwile

GC is an app management system. By fundamental design it does not manage content. In other words, it is an app that manages other apps (and those apps manage the content).

What Im trying to explain is that in order to get your roster management features "added on" to your site running GC, an application must first be built to manage that roster content. GC would then in turn manage that app in collaborative mode.

So when I say that it would be a separate app, it actually needs to be separate app by mere necessity, not just because I want to make more money from it.

Thats member management, and yes, GC does that. Member permissions, roles, ranks, and invite system is all included.

I believe that the roster management request is in reference to building some sort of a tournament management system into GC.

But that would be a separate app with its own objectives and its own price point. 

I see that you purchased the app and gave it a review. Thanks so much for that, I really appreciate it!

But you docked me a star because it isnt a roster management app also? Man, thats harsh.

Ive never claimed that it is a roster management app nor is it supposed to be. It is a collaborative app that allows you to designate apps (such as a roster management app) for collaborative use.

Its outside the scope of what GC does, and it is just impractical to make it more than that.

You want to use it for teams, someone else wants to use it for client project management, yet another person wants to use it for school groups. Should the guy who wants to use GC to help facilitate his collaboration with clients expect GC to manage his timesheets also?

​Well, you could move the forum out of the collab and then move the topic and then move the forum back into the collab if this is a relatively infrequent task you will need to be performing.

Otherwise, you could do some magic with my Rules App.

• Add a custom integer data field to Forums Topics, call it "Move Topic to Forum ID".
• Make it "administrative" so admins can edit it on the topic form
• Add a rule that is triggered when the custom data field is updated
• Add a condition that checks if the value is greater than zero
• Add an action that moves the topic to the new forum with the updated ID value
• Add an action that resets the updated ID value back to zero

End Result:  move-topics-to-any-forum.xml

Topics will have a field called "Move Topic to Forum ID" that can be updated by administrators, and when an id is entered and the topic is saved, it will be moved to the forum with that ID. Rules are cool, eh?

Currently, you must log in as member.

Next release is ready to go. I'll package it and update the marketplace this evening.

Click your user name in top right of page and then click the link for collaboration memberships. You can transfer it from there.

Yes, I recently noticed that too. I was previously supressing that core IPS behavior via my own code, but they made a change in the latest version that undid it.

My next release will contain a fix for that.

BTW, there will also be another option included in my next release to apply collab restrictions to owners to prevent them from specific collab management abilities. I know you were eager to see that functionality added.

 @Nathan Explosion, totally achievable.

The first part of creating the topic for the calendar event with the appropriate title can be easily done with all stock rule ECA's + the calendar expansion pack.

The second part about keeping the topic title synchronized can also be done, but we'll likely have to write a couple more creative rules to get that done.

If you purchase the app, PM me with details for your site and we can work on it together.

​Done. This will be in the next release of GC.

​Unfortunately, you need to have a category to hold the collabs. Also, the category is where all the settings are stored for how the collab should behave (such as what apps are available to collab owners to use).

But I understand your need. I'll consider what I can do to make the category display by default when the navigation is clicked when the category is the only one.

​Collin, PM me for direct support on this.

But from the looks of it, you are trying to use a variable in your template that doesn't actually exist inside the template. For example, if you are trying to use $member->getRulesData( 'data_key' ), then the $member variable must be part of the template, otherwise you need to access a globally available variable such as \IPS\Member::loggedIn()->getRulesData( 'data_key' ).

@icedream, download the latest version of the app. I've added some missing "content item viewed" event triggers which is why your rule was not being triggered.

Also, after taking a look at your rule, I noticed a few problems with your custom condition code:

• In order to return a result from the database you need to use the first() method of the select object.  i.e. \IPS\Db::i()->select()->first()
• Also, in the condition where you check the profile field for the member, you are using the "$member" variable, but that variable name is not included with the event, so you need to use \IPS\Member::loggedIn() instead.

I've made the appropriate changes to your rule for you:  check-adult-file.xml

Make sure you use at least version 1.0.8 of the Rules app for the event to be triggered. Also, I'm glad to see you're taking advantage of the custom PHP code fields! Good job!

​Easy peasy. Just use the "Calendar: Event has been created or updated" event, add a condition that the event is "new", and then add the "Create new topic" action to the rule and customize the title, content, and author of the posted topic.

Here is an example rule:

 create-forum-topic-for-new-calendar-events.xml

​Not sure what full integration with nexus means, but it uses the core node and content api of IPS4 so it behaves like any other core application so any nexus features that work with core applications should also work with GC.

I don't plan on adding rosters and such to GC directly. That falls outside the scope of what GC is. GC's role is to allow members to form their own groups, and for their groups to own and manage their own content using existing IPS4 applications. For example, if a tournament application is built which adds a new "rosters" content type to the system which allows you to create tournament rosters and provides all the functionality related to managing that tournament, then GC would allow you to give groups the ability to use that application within their group.

In other words, the purpose of GC is not to be all things to all people, but rather allow all people to do all things.

1. There will be an expansion pack coming for downloads which will add ECA's for files. Even though post attachments arent necessarily part of the downloads app, I will include triggers for all downloads in this expansion pack.

2. Shouldn't be a problem. 

3. Only through rules and the member edit screen in the ACP. I had some technical difficulties finding a practical hook point on the front end for public edit mode. I'lI work it out.

You would only need to do it once to select the forum as a destination. The import will work on the forum while it is part of a collaboration or not. In fact, there is no internal difference between a collab forum and a non collab forum. Only GC knows the difference.

The hook you speak of is already in place. It actually does the reverse of what you said. It filters the forums out that GC knows are part of a collab, because the core system doesnt know the difference. Otherwise management would become very messy with main site forums being buried and sandwiched in groups of collab forums (that could also possibly have the same names making it difficult to know if you even have the correct forum selected).

Not only that, but the IPS framework uses the same method to list forums in the main site index as it does in the forum select form field, so without the filter in place, all collab forums would also be listed in the main site index as well. And there is no practical way for the hook to know if the forum list is being requested for a form field or for the index page, so you cant have one without the other. In other words, if its exposed to the form select field, its also exposed to the forum index and every other part of IPS core that works with forum lists.

I think the best solution is to just move the individual forum in question out of the collaboration temporarily to expose it to the select field on a case by case basis rather than exposing every forum in every collab all at the same time.

​Here's what you could do as an administrator:

1. Move the forum out of the collaboration temporarily.
2. Set up the RSS import.
3. Move the forum back into the collaboration.

I believe that will accomplish your goal.

How do you currently import rss feeds to forums and how is GC preventing you from doing it for collab forums? Is this something you want collab owners to be able to do?

I'd import it and take a look at how it works. You may be able to use it as is with a few tweaks to fit your needs. 

Not sure what postbit is, but yes, it goes into a user facing template on the theme layer. Also, you'll need to make sure that the $member variable is available in whatever template you are adding it to.

​Hi Collin,

Check out the "Prestige Reputation System" example in the rules starter pack. It is very similar:

In order to display the field data in your template, you'll want to add the following template tag:

{expression="$member->getRulesData( 'fieldkey' )"}

Collab owners could possibly delete all content within the collab, but not the collab itself. You do have the option to remove the collab owners ability to delete content on an app by app basis in the collab category settings.

You could definitely do that with rules. But that might not be a bad fearure to add to GC.

Updated For 4.0 Gold! Plenty of new features!

• Updated for compatibility with IPS 4.0.0 "gold"
• fixed the ability to hide the front navigation link
• fixed incorrect post recounting issue
• Added built in import utility for rsyvarth social groups 2.x
• content feeds (widgets, etc) on collab pages will now only show content from that collab
• content feeds on non-collab pages will only show non-collab content and content the user has access to see in collabs
• added new private listing mode for collab categories
• added ability to move/copy non-collab content into collabs
• added ability to extract content from collabs into main site
• added featured/latest collabs widgets
• added autofill of member name when inviting to collab
• added support for disabling "view other members topics" inside collabs
• collab title in the group header now links to the collab homepage
• collabs now inherit join mode of models
• collabs now inherit default member title of models

​It appears that IPS has made some changes to the codebase that is breaking my existing build of the GC application. I've been working on a fairly large update for the GC software that includes a lot of the suggestions and features already discussed in this thread, so I'm very close to another significant release. I guess I'll need to add this fix to the app and release it a little early.

Look for a new GC version in the marketplace within the next 24 hours that should get you fixed.