Kevin Carwile

custom-action-recount-the-content-for-a-member.xml

All of that is very simple to do since iAwards works together with rules. It was very smart to include the integration.
@-RAW-, If you get me a release copy of the app, I can set up a simple rule for each of those scenarios and you can then bundle them in with the app so users can hit the ground running.

Is this the message you are referring to?
What is the error? I don't see one there.

We've discussed this. You have an issue that I cannot reproduce on my systems and you are unable to provide me with the means to troubleshoot the problem on your particular system.
I'm sure the fix is simple. But impossible to guess.

It will not work with 3.x. It's exclusively for IPS4. Sorry. It's an inexpensive mod. No demo either, just the description and screenshots.

Album Link Field
The album link field is a plugin which adds a new custom field to your cms databases called "Album Link". The album link field allows you to link albums to your database records.
You can configure the field to allow the selection of existing albums, or to allow the creation of a new album in a specific category, or both.
Features
Built for IPS Pages / CMS Link existing gallery albums with records Allow new albums to be created and linked on the fly Record workflow and image upload workflow are chained together Built-in mini-album display on records pages Built-in "linked" content display on album pages Set custom permissions for linked albums Control album placement categories Marketplace:
Album Link Field

@Gabriel Torres
Try uploading the following two patch files to your community.
./applications/advancedtagsprefixes/hooks/forumLastPostPrefix.php
./applications/advancedtagsprefixes/hooks/addPrefixToForm.php
 
addPrefixToForm.php forumLastPostPrefix.php

Sorry, I didn't realize that I was not subscribed to this topic. I have just updated Group Collaboration for 4.4 compatibility. I'll look into Tags & Prefixes next.

Sorry, I didn't realize that I was not subscribed to this topic. I have just updated Group Collaboration for 4.4 compatibility. I'll look into Tags & Prefixes next.

Sorry, I didn't realize that I was not subscribed to this topic. I have just updated Group Collaboration for 4.4 compatibility. I'll look into Tags & Prefixes next.

Sorry, I didn't realize that I was not subscribed to this topic. I have just updated Group Collaboration for 4.4 compatibility. I'll look into Tags & Prefixes next.

Praise the Lord and hallelujah to sweet baby Jesus, we have a savior in the house! Thank goodness you're taking over this app.  
I would have been sad if this app died.  

Is this still the case? I can't verify with my account since I own the resource, and I don't have another account with a valid IPS license to be able to log into. So I cannot tell.

Nope. Sorry. It will require a new version build to be released (unknown timeframe).
Well then I would question the event which you are creating the rule under. The event is going to determine what data is available. If it is the content approved event provided by rules, then the content item should be an event argument and the content author can be derived from that. If it is another event provided by the application plugin, then without the actual application as one of the event arguments, there is no way to know who the author of the application is if the rule doesn't even have access the application which has been approved.

No, you wont lose any rules.
That would be an event that needs to be included by the awards app.

You could dig into the IPS\calendar\Event object class to see what kind of methods you could use to retrieve a usable date within your rules.
I found this one with a quick look over:
/** * Find the next occurrence of an event starting from a specified start point * * @param \IPS\calendar\Date $date Date to start from * @param string $type Type of date to check against (startDate or endDate) * @return \IPS\calendar\Date|NULL */ public function nextOccurrence( $date, $type='startDate' )  

@christopher-w That seems like it should work. But the global template is used on all pages, not just forum pages, so that template will not have a reference to any particular forum to grab the custom field value from.
My suggestion would be to find a template which is used by the forums app and insert the class in a wrapper element from that template. Otherwise, getting the forum reference to access the custom data field is going to be much more difficult.

Right, so the question is if a slightly more organized codebase is worth trading for the openness and flexibility of the product to be extended in new ways.
Because I can tell you right now. There is no way to hook into a trait to provide enhanced functionality without knowing the specific base class that is going to use it. So instead of having one hook on the base implementation, you have to hook into specific child classes that use it (which is not practical when your enhancement is abstract) such as Automation Rules, which needs to trigger an event for any arbitrary class that uses the trait.
End result is either no enhancement of the base product, or way more hooks than necessary on every conceivable content item that may use it (how's that for a performance gain).

The intro text is customizable from the collab edit page. Change the collab description. The heading has a customizable photo so that any backdrop can be placed behind it.
Beyond that, you are getting into very specific theme related tweaks, at which point the best approach is to customize the templates according to your theme.

I will test this out and get it patched up.

After click to delete menu item...

Let me put it this way. Group collaboration doesnt add fearures to forums. Forums work exactly the same in a collab as they do outside a collab. So if you need guidance on how to use the forums app, then the documentation for that is on the IPS site.

Oh, if you need a Topic\Post, just return the $content then. I thought you needed the topic.

I see your sticking point.
The form is asking for the topic which you are attempting to update the custom data for (which is the stock action I referred to). But unless there is an explicit topic in the event arguments, how could rules give you an option to choose from? In this case, not just topic comments can be reported, but all sorts of other content can be reported. It cannot be assumed that you can derive a topic in from any given piece of reported content. If I report a comment on an image, and that rule event is invoked, how is rules going to get a topic from that comment? It's undefined.
This is why you only have the option to use PHP code to provide the topic for which the stock custom data update action will operate on. Rules knows that it cannot know what topic to use. Therefore you must tell it.
You could put a condition on the rule that checks if the content is an object of the 'IPS\forums\Comment' class, which would ensure the rule only runs when a topic comment is reported. This will prevent errors when other types of content are reported, but you are still left with the need to provide the topic itself for the custom data update action. You need to return the topic from your PHP snippet:
return $content->item();  

I see your sticking point.
The form is asking for the topic which you are attempting to update the custom data for (which is the stock action I referred to). But unless there is an explicit topic in the event arguments, how could rules give you an option to choose from? In this case, not just topic comments can be reported, but all sorts of other content can be reported. It cannot be assumed that you can derive a topic in from any given piece of reported content. If I report a comment on an image, and that rule event is invoked, how is rules going to get a topic from that comment? It's undefined.
This is why you only have the option to use PHP code to provide the topic for which the stock custom data update action will operate on. Rules knows that it cannot know what topic to use. Therefore you must tell it.
You could put a condition on the rule that checks if the content is an object of the 'IPS\forums\Comment' class, which would ensure the rule only runs when a topic comment is reported. This will prevent errors when other types of content are reported, but you are still left with the need to provide the topic itself for the custom data update action. You need to return the topic from your PHP snippet:
return $content->item();