Kevin Carwile

Block placement is controlled entirely by IPS core. The same problem exists if you want a block to display only in a particular forum... there is no real way through IPS core to control that. It could potentially be built into the widget logic itself whether it should display itself or not, but the problem there is that GC does not control the internal widget logic (or the settings available on the widget configuration).

What really needs to happen is that the widget placement procedures in IPS core need to be changed to support global placement rules for widgets that resolve all the way down to individual pages instead of an entire app controller.

Subscribe to the marketplace download to be notified of updates.

You can control grid view on an app by app basis now from the collab category settings under the appropriate app tab.

I love the idea. And there is always a way. I just have no idea what that way is at the moment.

What does your code look like? And what isnt working? 

I could add a category override setting for that. But beware that it will affect other features such as the settings on forums to require a certain amount of posts to create a topic, etc. That feature will become useless to collab owners.

I do not maintain that module. I can say however that the standard unread indicators all work in the stock templates shipped with the collab app. Maybe you can compare differences and edit the templates used in your other module.

First part will be fixed in next release.

The second part is just a matter of practicality. Its going to cause big performance hits if every content item of every container of every app of every collab in every collab category is queried to find the latest post (with permissions) on every page load. I had to draw a line in the sand at the collab level resolution of latest post querying (with permission).

I'll have a look at the calendar issue you described.

Yes, set up the collab model as needed, then enable collab models on the category and make the model forced.

Could be done with some rules magic I suppose.

This is a built in behavior of the forums controller. But after you add a container forum and then a discussion forum, someone told me you can then reassign the discussion forum to have no parent and then remove the initial container forum.

If you set up a model this way, it can be replicated to new collabs as mentioned above.

{{if ! \IPS\collab\Application::affectiveCollab()}}

Sorry I missed this. Just invite the member and then set the membership to banned.

@d2dyno, it sounds like maybe something in your server config may be blocking submitted form data. Lets connect via PM for case specific support.

@JEFF MACK, I'm not sure about the general practicality for users to have the ability to turn private messages from multiple members into a public affair at the click of a button.

But a button to invite all PM participants to an existing collab... that sounds like a good idea.

Add it on the url.

http://www.yoursite.com/login/?ref=http%3A%2F%2Fwww.yoursite.com

Because the login redirects back to the last page that the user was on. When you enter your redirect url, add a "ref=" parameter to indicate which page should be redirected to once logged in.

What version are you running?

Not currently. You're options are to either move the forum out of the collaboration if it doesn't belong under collaboration control, or to remove the leader which is not playing nicely and install a new leader. But there may be an opportunity to do something like that in a future release.

@Ocean West,

Thanks for pointing out that issue with the container titles. I'll work on a way to correct that in the next release. As for the SQL "error", it's not really an error. It's more like the support tool chasing its own tail.

@Lukeroge,

Run some tests on the most recent version of Rules and get back to me.

What you can do is to create a single gallery category and put all other categories inside of it. Then the title of the root category will be used as the container, giving the flexibility to rename as appropriate.

Yes, turn on the option in the category settings to increase site post count when members post in the collabs in that category.

Any content containers (forums/categories/etc) will be replicated as will any roles and permissions. 

If you set a collab as a model, then depending on the settings in your category, new collabs in that category will automatically be clones of the model, or the user will have an option to select a model to use for their new collaboration.

For example, if you have in your category settings that the "collab model" feature is enabled, and that new collabs must use a model, and you only have one model flagged, then the user will not see an option to select a model, the only one available will be used automatically. But if you have multiple models flagged, then when the collab is being created, the user will see an option to select the model that their collab will be cloned from.

You may be making it more complicated than it needs be.

In the collaboration, the owner just has to give permission to "guests" to view/post/reply/etc. A guest is someone who is not an active member of the collab (i.e. everybody else on the site).

Thanks.

Create a custom action in your ACP. Then create a rule which is triggered by the custom action. In that rule, add two actions:

1. Create the new topic
2. Schedule the custom action for 1 month in the future

This way each time the custom action is ran, it will create the new topic and then reschedule itself to run again in one month.

Then you just have to trigger it for the first time to set the cycle in motion. You could set up a quick igniter rule that will schedule the custom action on a specific date and time, such as when you post a topic in a certain forum. Then after it's scheduled for the first time, delete or disable the igniter rule. The rest will take care of itself.

When you use the data property accessor in your template such as $topic->banned_member, it is going to respect the permissions that you have set up on the data field. I would double check that you have given group 20 permission to "view" the data in the permissions settings for the data field.

Also, since the data field "banned_members" is set up as an array of member objects, it's going to return an actual array of member objects in your code. So you would want to iterate that array in your template code.

{{if member.inGroup(array("4,20"))}}
{{if $topic->banned_member}}
  <br>
  <div class="ipsMessage ipsMessage_info ipsSpacer_bottomipsPad">
      <strong>Current Banned Members:</strong>
      <ul>
      {{foreach $topic->banned_member as $member}}
        <li>{$member->link()}</li>
      {{endif}}
      </ul>
  </div>
  {{else}}
  <div class="ipsPad">
    <i>Moderator Notice: No Members Are Currently Banned From This Thread</i>
  </div>
{{endif}}
{{endif}}