Kevin Carwile

It appears you are using custom theming. In order to change the background colors of text and other stylings, you will need to do it with custom css on your theme layer.

You just need to update a language string in your system to accomplish that. No rule needed.

The latest version of rules lite implements a new strategy which significantly reduces the overhead caused by this to the point where it should not be a major bottleneck now for low powered sites. The full version has no decoding overhead.

No, there is not a built in process such as that because its not really necessary. Barriers can be easily removed by setting permissions on content in the collab to be open to guests. Its not mandatory for site members to be an active member of the collab to use it. And the join mode can be set to allow instant membership if needed. Plus, there is a rule set already in the marketplace to automatically add members to collabs if they post content to it (created by Police Community).

Ryan, Found a bug. You have a hook on \IPS\Node\Model where you join your node_settings database table to the construct query when the node is loaded, which means that the fields get added to the $node->_data array, which also means that it breaks the $node->save() method to save the node back to the database because it attempts to write to database columns that don't exist.

Plans, yes. Progress, no. Honestly, I wish I could say it was on its way, but sadly it's still just a sparse development folder and a bunch of notes on a piece of paper buried on my desk. Commerce is a BIG application. At some point my work will lead me into tackling the ECA extension for it, or another dev will do it first. I just cannot say when.

Sure. It's possible. It's a matter of creating a custom data field attached to members to hold point balance. Then creating a scheme of rules to add to one members total and subtract from another. With the rules app, you can even create a custom log attached to members to record the transactions. The only part that would be tricky is setting up the right event mechanism to capture the points transfer request. Since you don't build user interfaces with rules, you must somehow re-use/adapt an existing one. Such as adding a couple of custom fields to enter a username and a number value and attaching it to topics in a certain forum and using that as a "points transfer request" forum of sorts. You would be basically building your own custom application with rules. Now that I think about it, an excellent way to build a transfer request form would be to use a custom form builder such as the app from @Mike John. However, that app does not currently provide any events for you to use in rules. Man, that would be an awesome combination. That's an excellent idea. Not sure how I managed to miss that particular content event. I will add an event in for the next release of rules.

The lite version uses encoded files that seem to be slowing servers down as they have to decode and run them. The full version does not use encoded files so this is not a problem. I'm looking into how I can mitigate this in the lite version.

OK, I've updated your site with a pre-release copy of GC 1.3.3 which allows you to break down the configuration process for collab content settings even further. You can now configure your individual content types for a specific app one at a time. Furthermore, if you have the "expanded category configuration" setting turned off in GC settings, then the process is broken down even further into a wizard interface that splits up the form into 3 different steps. This puts your 68 member group permission matrix on a page by itself.

You must be using prefixed database tables. See my bug report here:

I'll look at turning it into a step by step process.

Probably. I believe blue jeans have the same problem. :P

Or maybe excessive configurations could use server settings that would support that excess. Such as increasing the max_input_vars to account for the requirement.

Yes, I see your problem. The server is not accepting all of the form data submitted by your configuration form because your PHP max_input_vars is set to 3000. However there are over 5000 form elements which get submitted with that particular form. There are a couple of reasons why this number is so high. You have 68! different member groups on your site and 5 different databases which qualify for use in collaborations. Each database has roughly 8 configuration options which amounts to roughly 15 form variables. Then there are 25 moderator options and a permission matrix for each database. The 25 moderator options amount to a total of 50 form variables when submitted (because IPS uses 2 form variables for each checkbox/radiobutton). And then the permission matrix is the beast. Each member group has 7 permissions available, each of which takes two form variables, multiplied by 68 member groups equaling roughly a thousand form variables just for each matrix. When you do the math, it adds up to a lot of form variables. I'm not sure what to do here. Do you really need 68 different member groups?

On version 1.3.2 of GC, go to the Settings page for the app and disable the "Expanded Category Configuration" option. This will remove all of the app configuration settings from the collab category setup form. You can then configure each collab app for the category individually. Use the action dropdown on the category to choose the app you want to configure.

The lite version is encoded, so some scanners will incorrectly flag it as having a virus because the see its encoded. It contains NO malware. Alternatively, you can buy the full version and download that. The full version is not encoded.

Hang in there. I'm working on a solution for your issue.

You could create a custom data field for the flag. And you could create a custom action with a forum as the argument and schedule it to run for all forums (bulk processing option) on a regular basis. Within the custom action, create a condition to check the last post date in the forum and set the flag value if needed.

I analyzed it last night. All of the lag is attribited to slow performance in the language subsystem when displaying all of the words on the category form. I singled out a single SQL query in \IPS\Lang which is taking 20+ seconds to execute as soon as the number of language strings on the page becomes of significant size. I'm considering what I can do to mitigate this problem.

There is a setting in moderator permissions in ACP under the collab tab to bypass collab permissions. Make sure that is turned on for the administrators group.

I believe that was my point. This is the first I've heard of that. I've personally submitted a hundred or more bug reports for IPS4 over the past year helping IPS get problems fixed. If you've found any particular problem with my app, I would appreciate if you would communicate that with me instead of quietly pointing fingers and leaving me in the dark. There is nothing "wrong" with your hosting. I'm not trying to attack your service (although some frustration probably was apparent in my words). It just doesnt seem to be a good fit for GC. When a client can't get their php max_input_vars configuration changed to support their application, that doesnt make a bad host. It's just not very flexible. Thats all I'm saying.

Please PM me some details for your site if I am to have any hope of helping you fix your problem.

I agree, it should not take longer than 30 seconds to save a category. In fact, it should not take longer than a couple of seconds max. Does anybody not using IPS Hosting have these issues? Unfortunately, I have found that IPS Hosting is a shared server environment that does not meet certain requirements for the GC app. It is configured specifically to meets the needs of IPS core, which is great, but as soon as you step outside of those operating parameters then it becomes problematic and rigid. For example, the category configuration form for GC typically contains more form elements than the configuration of IPS servers will allow to be submitted at one time. Most servers support this without a configuration change, but occasionally a server will have its limits set too low for GC. Usually you can make the configuration change yourself or ask your host to loosen things up which will solve many problems. IPS cloud community however is not one of those where the configuration can be customized. Because of this, I'm not sure what can really be done to rectify the problem. With that said, if you want to go ahead and PM me with details for your site, l'll have a look at it to see if there is anything I can do.

There are no out of the box apps that I know of that allow you to create your own dynamic member view filters. However, I dont really stay on top of everything in the marketplace as it is very much a mess. You may be able to dig through and find something. The logical way to accomplish it would be with an app that does what you are needing to do or close to it. Thats what I meant by "custom programming".

You may want to adjust some settings on your server so that scripts arent prematurely halted after 30 seconds. Not currently, but that seems like an appropriate setting to place in collab category settings.