Rikki

This is in the Core app, so it'll be part of your community when you upgrade to 4.2. The areas of the club that users can create would of course be linked to which applications you have (e.g. you'd only be able to have galleries in your Club if you have the Gallery app).

Great Scott! Future is coming.

Monosnap to record/edit the video, and then a simple MP4 -> Gif converter Monosnap does support saving as gif too but doesn't have any options to optimize/resize, so I use a different tool.

Who would have thought that the "Reactions" would get such a great reaction?

Monosnap to record/edit the video, and then a simple MP4 -> Gif converter Monosnap does support saving as gif too but doesn't have any options to optimize/resize, so I use a different tool.

They show anywhere the 'guest teaser' does, which includes the comments sections of all of the other apps.

They show anywhere the 'guest teaser' does, which includes the comments sections of all of the other apps.

They show anywhere the 'guest teaser' does, which includes the comments sections of all of the other apps.

New AdminCP design is AWESOME. Can't wait to try it out

Reading the stuff in the images... coudn't resist.

Waiting desperately.. will social groups be gifted to us ??

They weren't 'wrong' per se, but Google Analytics wouldn't track dynamic pages by default, and since we use ajax to load a lot of content in IPS4, those actions wouldn't count as a view. That goes a long way towards explaining why you'd see a drop in overall page views.
This change will enable those dynamic page views to be tracked.

They weren't 'wrong' per se, but Google Analytics wouldn't track dynamic pages by default, and since we use ajax to load a lot of content in IPS4, those actions wouldn't count as a view. That goes a long way towards explaining why you'd see a drop in overall page views.
This change will enable those dynamic page views to be tracked.

They weren't 'wrong' per se, but Google Analytics wouldn't track dynamic pages by default, and since we use ajax to load a lot of content in IPS4, those actions wouldn't count as a view. That goes a long way towards explaining why you'd see a drop in overall page views.
This change will enable those dynamic page views to be tracked.

They weren't 'wrong' per se, but Google Analytics wouldn't track dynamic pages by default, and since we use ajax to load a lot of content in IPS4, those actions wouldn't count as a view. That goes a long way towards explaining why you'd see a drop in overall page views.
This change will enable those dynamic page views to be tracked.

We do have the Javascript docs in the guide section right now, but I think you're right - they'd now make more sense in the Developers area. I'll plan to move those across soon.
For commenting, we considered it, but in reviewing the old docs, the vast majority of comments were people asking for help and that isn't what we want to happen inside the docs - people should go to the forum for that. If any developer has any suggestion or correction to make (or even wants to contribute a whole guide), just get in touch with me and I'm happy to work with you on it, and provide attribution of course.

We do have the Javascript docs in the guide section right now, but I think you're right - they'd now make more sense in the Developers area. I'll plan to move those across soon.
For commenting, we considered it, but in reviewing the old docs, the vast majority of comments were people asking for help and that isn't what we want to happen inside the docs - people should go to the forum for that. If any developer has any suggestion or correction to make (or even wants to contribute a whole guide), just get in touch with me and I'm happy to work with you on it, and provide attribution of course.

Alright, a slight modification to what @Rikki has above will allow you to use multiple feeds in to your individual forums.  I needed this as I have multiple Pages Databases that we use on one of our websites, and I wanted to pull information from more than 1 location.
{{if request.app == 'forums' && request.module == 'forums'}} {{$id = \IPS\Request::i()->id;}} {{if $id == '5'}} {block="forum_5a"} {block="forum_5b"} {block="forum_5c"} {{endif}} {{endif}} Now my ForumID is 5.  So when loading Forum5 in the sidebar it will now load 3 Custom Blocks.
You can extend on this easily enough to have a complete different set of feeds in each forum.

The hextorgb tag was new in... 4.1 I think, possibly a touch later, so it's pretty new. We use it for the main menu, so you can check out usage in the navigation.css sheet inside /framework  

The hextorgb tag was new in... 4.1 I think, possibly a touch later, so it's pretty new. We use it for the main menu, so you can check out usage in the navigation.css sheet inside /framework  

You don't need a dedicated server to use a newer version of PHP, just a reputable host that doesn't use software that has been unsupported for nearly a year  

Look at it this way - IPB supported PHP 5.4 almost a year after it was deemed End of Life by the creators - you can't expect IPB to maintain backwards compatibility AND take advantage of the latest technologies.
You can always choose not to upgrade your IPB install until your host decides to upgrade PHP - and as @Charles suggested in his comment, if your host is unwilling to upgrade (which is unsafe for a variety of reasons), then perhaps you should look at alternative hosting once your contract with them expires.

@Meddysong I'm afraid the answer isn't very exciting! Since we only have a handful of pages in the feature tour and they don't change much, if ever, they're simply hand-coded as part of the header of each page:
<div class='col-sm-2 col-sm-push-8 ipsType_right sFeatureTour_next'> <a href='/features/engagement' class='ipsButton ipsButton_link ipsButton_large'><span></span>Engagement   <i class='fa fa-user-plus'></i></a> </div> It would certainly be possible to make this dynamic using a block though, which would be better suited if you had lots of pages that regularly changed (or you needed to reorder them).
The way I'd approach that is to use a PHP array to store the correct order of my pages, and then use array positions to figure out what the next/previous page should be. Something like this (off the top of my head and subject to errors/bad logic!):
{{$myPages = array( 'features/page1' => "Page One", 'features/page2' => "Page Two", 'features/page3' => "Page Three"); }} {{$pageNames = array_keys( $myPages ); }} {{$curPageIndex = array_search( \IPS\Request::i()->page, $pageNames ); }} <ul> <li> {{if $curPageIndex !== FALSE && isset( $pageNames[ $curPageIndex - 1 ] )}} Prev: <a href='{$pageNames[ $curPageIndex - 1 ]}'>{$myPages[ $pageNames[ $curPageIndex - 1 ] ]}</a> {{endif}} </li> <li> {{if $curPageIndex !== FALSE && isset( $pageNames[ $curPageIndex + 1 ] )}} Next: <a href='{$pageNames[ $curPageIndex + 1 ]}'>{$myPages[ $pageNames[ $curPageIndex + 1 ] ]}</a> {{endif}} </li> </ul> Here I'm creating an array that represents the filenames, page titles, and they're in the order I want them to show. If I wanted to change the page order, or add new pages, I'd just change the $myPages array.
I'd build this as a block, and drop it into all the pages that should show the menu  

With a little jiggery-pokery, yep.
The below plugin allows you to redirect members of a group to a specific url
So, if your ban process currently involves also manually moving banned users off to a group then you're golden.
If, however, your process doesn't currently involve also manually moving banned users to a group then you could use the Rules application by @Kevin Carwile to intercept the ban action to move a user to a group upon them being banned.
 

No, that's not possible unfortunately - not without a backend plugin at least.