All Astronauts

That's a standard theme option. Customization, then edit the default themes settings. If you have a custom theme you'll need to see if the theme author included that.
I'll take a look at your other suggestion.

No guarantee on time table but I can add that to the list.
 
No reason why it wouldn't be doable though it might add some heft to the queries if that last post date isn't already present in the topic. I think it is though.
I tend to avoid the new features IPS introduces as they are often a bit raw and undergo streamlining fairly quickly. You make a good point and you should say as much in the Feedback forum. They do read that and it's a good request.

Non-Amazon S3 storage services do work with IPS 4.1x. Add your endpoint, key, secret, and sub-directory and custom url if needed, assign to some file category such as attachments or Gallery images and off you go!
However, these Non-Amazon S3 services are NOT officially supported by IPS - that's because some of the internal methods have not been altered to handle them. These methods are hard-coded for Amazon S3 exclusively.
If you are merely displaying images and the like on the front end, none of this is a problem. It becomes a problem if your end-users are going to download these files - that is when you hit the exclusively Amazon S3 code and the downloads will fail. For example, if you assign non-Amazon S3 storage to save IPS Downloads files, those files will not be downloadable. When the system attempts to make the download URL, it crafts that URL as if you were using Amazon S3, not some other S3-Compatible storage service.
The two major areas that this will impact are IPS Downloads files and Attachments (this is what the file storage is called in the Files list in the ACP - it encompasses all attachments such as those you would have anywhere the full editor is used and there is an attachment dropzone.)
This plugin intercepts the URL creation method called on Amazon S3 file storage objects, checks to see if it is an actual Amazon S3 request, and then just passes it on through as usual. If it is NOT an Amazon S3 request, it must be an S3 compatible method, in which case I provide a rudimentary URL to patch this up. It isn't anything fancy: just enough headers to push out the actual file name and trigger your browser to download it. If the attachment or file in question is an image your browser might just pop it up in a new tab, in which case just right click and download it there. This has been tested with the usual modern browsers (minus Safari), and various file-types. All testing was successful.
BTW, as an aside, external FTP storage for files is NOT COMPATIBLE with IPS Community in the Cloud. Might want to note that...
Free, support through the IPS Marketplace topic for now. Free also means lay off the instantaneous demands for support. I use this too so it's in my interest to keep this going. Support, and this plugin's existence, continues until IPS gets around to actually officially supporting Non-Amazon S3 storage.
WARNING!
The only item in the entire IPS Suite that marks files as private is IPS Downloads. This plugin will flag them as public. This means a few things:
1) If you are monetizing or otherwise require to fully control access to IPS Downloads files this is probably not the plugin for you. You will need to wait for complete 3rd Party S3 support, or at least specific mods to support obj.space, Digital Oceans Spaces, and so on. It really is just some hump work on getting the signatures correct (and it might be a V2 vs. V4 dance with varying providers as well - IPS just has a hard-coded-to-Amazon V4 method). Give it time, it will happen.
2) If you are using this plugin on an already existing bucket with Downloads files, those files will need to be flagged as public-read for them to download correctly. Again, this plugin is just getting rid of the signatures to allow public files to download correctly from 3rd-party S3 providers. 
3) IPS Downloads users on IPS Community in the Cloud may need to wait forever and ever before the plugin will work correctly (forever and ever being defined as more than handful of minutes) as CIC caching takes some time to get things working. You *will* need to be infinitely patient. Like, install and then go drink something for awhile, read a book, etc. Then test. Don't yell at me saying this is broken., It isn't. Tested and verified on both own-hosting and CIC.
Enjoy, good luck, etc...
 
 

Non-Amazon S3 storage services do work with IPS 4.1x. Add your endpoint, key, secret, and sub-directory and custom url if needed, assign to some file category such as attachments or Gallery images and off you go!
However, these Non-Amazon S3 services are NOT officially supported by IPS - that's because some of the internal methods have not been altered to handle them. These methods are hard-coded for Amazon S3 exclusively.
If you are merely displaying images and the like on the front end, none of this is a problem. It becomes a problem if your end-users are going to download these files - that is when you hit the exclusively Amazon S3 code and the downloads will fail. For example, if you assign non-Amazon S3 storage to save IPS Downloads files, those files will not be downloadable. When the system attempts to make the download URL, it crafts that URL as if you were using Amazon S3, not some other S3-Compatible storage service.
The two major areas that this will impact are IPS Downloads files and Attachments (this is what the file storage is called in the Files list in the ACP - it encompasses all attachments such as those you would have anywhere the full editor is used and there is an attachment dropzone.)
This plugin intercepts the URL creation method called on Amazon S3 file storage objects, checks to see if it is an actual Amazon S3 request, and then just passes it on through as usual. If it is NOT an Amazon S3 request, it must be an S3 compatible method, in which case I provide a rudimentary URL to patch this up. It isn't anything fancy: just enough headers to push out the actual file name and trigger your browser to download it. If the attachment or file in question is an image your browser might just pop it up in a new tab, in which case just right click and download it there. This has been tested with the usual modern browsers (minus Safari), and various file-types. All testing was successful.
BTW, as an aside, external FTP storage for files is NOT COMPATIBLE with IPS Community in the Cloud. Might want to note that...
Free, support through the IPS Marketplace topic for now. Free also means lay off the instantaneous demands for support. I use this too so it's in my interest to keep this going. Support, and this plugin's existence, continues until IPS gets around to actually officially supporting Non-Amazon S3 storage.
WARNING!
The only item in the entire IPS Suite that marks files as private is IPS Downloads. This plugin will flag them as public. This means a few things:
1) If you are monetizing or otherwise require to fully control access to IPS Downloads files this is probably not the plugin for you. You will need to wait for complete 3rd Party S3 support, or at least specific mods to support obj.space, Digital Oceans Spaces, and so on. It really is just some hump work on getting the signatures correct (and it might be a V2 vs. V4 dance with varying providers as well - IPS just has a hard-coded-to-Amazon V4 method). Give it time, it will happen.
2) If you are using this plugin on an already existing bucket with Downloads files, those files will need to be flagged as public-read for them to download correctly. Again, this plugin is just getting rid of the signatures to allow public files to download correctly from 3rd-party S3 providers. 
3) IPS Downloads users on IPS Community in the Cloud may need to wait forever and ever before the plugin will work correctly (forever and ever being defined as more than handful of minutes) as CIC caching takes some time to get things working. You *will* need to be infinitely patient. Like, install and then go drink something for awhile, read a book, etc. Then test. Don't yell at me saying this is broken., It isn't. Tested and verified on both own-hosting and CIC.
Enjoy, good luck, etc...
 
 

Non-Amazon S3 storage services do work with IPS 4.1x. Add your endpoint, key, secret, and sub-directory and custom url if needed, assign to some file category such as attachments or Gallery images and off you go!
However, these Non-Amazon S3 services are NOT officially supported by IPS - that's because some of the internal methods have not been altered to handle them. These methods are hard-coded for Amazon S3 exclusively.
If you are merely displaying images and the like on the front end, none of this is a problem. It becomes a problem if your end-users are going to download these files - that is when you hit the exclusively Amazon S3 code and the downloads will fail. For example, if you assign non-Amazon S3 storage to save IPS Downloads files, those files will not be downloadable. When the system attempts to make the download URL, it crafts that URL as if you were using Amazon S3, not some other S3-Compatible storage service.
The two major areas that this will impact are IPS Downloads files and Attachments (this is what the file storage is called in the Files list in the ACP - it encompasses all attachments such as those you would have anywhere the full editor is used and there is an attachment dropzone.)
This plugin intercepts the URL creation method called on Amazon S3 file storage objects, checks to see if it is an actual Amazon S3 request, and then just passes it on through as usual. If it is NOT an Amazon S3 request, it must be an S3 compatible method, in which case I provide a rudimentary URL to patch this up. It isn't anything fancy: just enough headers to push out the actual file name and trigger your browser to download it. If the attachment or file in question is an image your browser might just pop it up in a new tab, in which case just right click and download it there. This has been tested with the usual modern browsers (minus Safari), and various file-types. All testing was successful.
BTW, as an aside, external FTP storage for files is NOT COMPATIBLE with IPS Community in the Cloud. Might want to note that...
Free, support through the IPS Marketplace topic for now. Free also means lay off the instantaneous demands for support. I use this too so it's in my interest to keep this going. Support, and this plugin's existence, continues until IPS gets around to actually officially supporting Non-Amazon S3 storage.
WARNING!
The only item in the entire IPS Suite that marks files as private is IPS Downloads. This plugin will flag them as public. This means a few things:
1) If you are monetizing or otherwise require to fully control access to IPS Downloads files this is probably not the plugin for you. You will need to wait for complete 3rd Party S3 support, or at least specific mods to support obj.space, Digital Oceans Spaces, and so on. It really is just some hump work on getting the signatures correct (and it might be a V2 vs. V4 dance with varying providers as well - IPS just has a hard-coded-to-Amazon V4 method). Give it time, it will happen.
2) If you are using this plugin on an already existing bucket with Downloads files, those files will need to be flagged as public-read for them to download correctly. Again, this plugin is just getting rid of the signatures to allow public files to download correctly from 3rd-party S3 providers. 
3) IPS Downloads users on IPS Community in the Cloud may need to wait forever and ever before the plugin will work correctly (forever and ever being defined as more than handful of minutes) as CIC caching takes some time to get things working. You *will* need to be infinitely patient. Like, install and then go drink something for awhile, read a book, etc. Then test. Don't yell at me saying this is broken., It isn't. Tested and verified on both own-hosting and CIC.
Enjoy, good luck, etc...
 
 

Done, dl from Marketplace, etc.

KS 17 released!
A couple uncommon bug fixes. Built-in post bit compatibility fixes for a few 3rd-Party apps. New option to limit the number of attachments per post (probably affects all editors with file attachment areas) The 3rd party apps that have the fixes you can just scroll up through this support topic to see what they are. Fixes need to be toggled on/off under the misc tab in KS - they are not enabled by default.
The new option for limiting the number of attachments per post probably affects any content item that has a file attachment area. For now I have this setting at the bottom of the post tab. Choose between 1 and 100. Honestly, more than 50 attachments (maybe even less than that) and you are starting to stress things a bit. Over 100 and you are really just asking for trouble; especially those of you running IPS on servers with shall we say less than optimal resources? Default is 25 which is more than reasonable.
CIC users, as always, once you install KS and mess with things, you'll have to wait for the CIC caching system to wake the hell up and recognize there is new stuff going on. Took me a couple cache wipes and I still needed to wait awhile before the limit attachments option actually fired on through on the front end.

Done and dusted. Thx, enjoy, etc.

Done and dusted. Thx, enjoy, etc.

If anyone needs this now just yell, otherwise I'm holding off on a release for awhile to tackle some other things. FYI the fixes for both Bookmarks and Post Notes are on the Misc tab (last one) in KS. You will need to enable the fixes there, no need for them to run if they are not needed.
Also, just for completeness, these fixes both test whether you have enabled them or not and also if the application involved is enabled as well. This last bit is a good way to simultaneously test whether you have the application in the first place and that you have that app actually turned on. As both fixes are calling application-specific templates you can imagine the support hilarity that I would bring upon myself when people disable the application, but leave KS up and running with the specific app fix enabled, which would be calling for that now disabled template...

Kitchen Sink is patched for this. Yell if you need it otherwise it will be formally available with the next published release.

If anyone needs this now just yell, otherwise I'm holding off on a release for awhile to tackle some other things. FYI the fixes for both Bookmarks and Post Notes are on the Misc tab (last one) in KS. You will need to enable the fixes there, no need for them to run if they are not needed.
Also, just for completeness, these fixes both test whether you have enabled them or not and also if the application involved is enabled as well. This last bit is a good way to simultaneously test whether you have the application in the first place and that you have that app actually turned on. As both fixes are calling application-specific templates you can imagine the support hilarity that I would bring upon myself when people disable the application, but leave KS up and running with the specific app fix enabled, which would be calling for that now disabled template...

Anyone on 4.2.4 will need to hit the support tool in the ACP and apply the latest patch as IPS has been changing how settings are saved and that's been creating some problems. For Spacious it is the background image on login page - 4.2.4 wasn't saving them - if you left it alone it was fine but once you tried to change it, problems. 
Today's un-announced IPS patch fixes that.
However, there is a bug with dashboard widgets - new widgets will not be saved to the dashboard. You can add them, and they are there, until you navigate away - when you go back to the dashboard they aren't there anymore. Also, sometimes if you delete an existing widget it stays gone as you can't add new widgets to the dashboard (see above) *or* you try to delete them and they refuse to go away; you navigate away after deleting them, return to the dashboard, and they are there again.
Nothing I can do about that one.

It looks fine to me on lanos.com, that's with KS 16 installed. Screenshot? Or send me PMs to take this private if you like.

IPS has been mucking about with the meta tags and json output recently. If you want them to warn you this is happening prior to a release being released you'll need to poke the various parties responsible.
/* Wipe JsonLD for now until issues resolved */ \IPS\Output::i()->jsonLd = array(); That includes breadcrumbs. Sorry.

See - it's me.

For those of you having problems with Pinned Posts, Change Post Author, and any other plugin that interacts with the post menu (where the quote, edit, etc. options are) there is apparently some rough waters with how IPS is building the templates out. It would appear if you have more than a few things hooking on that area, the system will build the template out for a few hooks and then... stop. That's just me generalizing what's happening, I'm not sure exactly what's happening. KS does a bunch on the post menu too so I've been getting a few requests for support saying some items are not showing up.
Save me, and you, some time and just do this:
1) Clear caches with the Support tool (or why not buy Spacious ACP and add a clear caches button to your dashboard among other things?)
2) Go to your plugins page.
3) Leave KS enabled, but toggle off the plugins that are interacting with the post menu, like Pinned Posts, etc...
4) Go ahead and toggle them right back on. No need to do anything else. 
5) Now look on the front end. Everything should be fine.
Note that if you have an *application* that has a hook on the post menu, there will always be a problem with KS since I grab a bunch of stuff there. Just give a yell and I can give you a plugin to tackle that. The reason being as application comes first, then plugins, in how everything gets built out.
Owners of the Post Notes app take note (hah!) I've got a 4.2 plugin on hand already to get that post menu bit back in action alongside KS. Just shoot me a PM.

And there you go.
New format option, customize the FontAwesome icon, toggle the light/dark text, compatible with 4.2.
    

All good. Just a reminder to folks that other plugins can interfere with other plugins easily enough on install - nothing wrong with the plugins, just that you may need to refresh your browser cache, or in this case just dump all the IPS template caches with the support tool to get all the new stuff where in needs to be. Otherwise you can sometimes get old built templates conflicting with what plugins expect to be in place and so on...

Kitchen Sink 14 Released!
New! Option for Full Inbox Warnings. New! Option to restore multi-mod action on first post in a topic. Full inbox warnings is just a revamp of the free plugin in the Marketplace. Cleaned it up a touch and added an additional placement option beyond what you get in the free one. Option to not warn at all (default), a warning banner just below the breadcrumb line or there abouts, or a top of the browser full width warning. Warning displays on every page a member browses for as long as their inbox is at or over the limit for the number of messages their member group is allowed to have. Goes away once they cull below that line. Useful in that until they get below quota they will not be able to receive any new messages.

The multi-mod restoration was a request from @Bill Edwards who pointed out two long standing request threads for this feature to be restored. I've purposely locked this down to only merge. Reasons? The first post in a topic is a special snowflake and needs to be treated differently - even though it is a post (comment in the IPS parlance) it is considered locked in as a part of the topic itself. Most of the multi-mod actions already do treat it differently, or at least avoid it in some respects, but IPS still purposely disabled multi-mod actions on it for good reasons - mainly they haven't built in anything safe enough to prevent you from breaking the topic. If you need to do real moderation to the first post use the moderator actions button alongside the reply to topic button. 
What happens if I let you run free with all the usual multi-mod actions?
Assuming you select the first, second and third posts in a topic with the multi-mod button, here is what you could do and what would happen.
Hide: Would hide the second and third posts, leave the first post untouched. 
Trash: Trashes the second ans third posts, leaves the first post untouched (pretty sure, kinda forgot my test on this)
Merge: Safe! It will merge posts two and three into the first, allowing you to edit as needed before saving. 
Split: Here comes trouble... It does work; too well actually. Let's change the scenario a bit. Let's say we have five posts in a topic. With multi-mod enabled on the first post, you proceed to select the first, second, and third posts for splitting. Splitting doesn't let you split large posts into separate posts in the same topic, what it does is allows you to split the posts off into another already existing topic or start a new one with those posts. 
You hit save, and posts 1, 2, and 3 are now in a new topic. Believe it or not, not only do posts 4 and 5 bump up correctly in the old topic, post 4 gets flagged correctly as the first post in the database. Was surprised by that myself. 
So you think all is well? How about instead of splitting off posts 1, 2, and 3 we split off *all* of them?
You can do that with multi-mod and once you do? Congratulations! You've just turned this topic into a zombie. Oh it still exists, it just has no posts and there is no way to add posts back into it.
So, seeing as how the hide and trash multi-mod actions don't work on the first post, and the possibility to do stupid things with split, I've done some junk to make the first post in a topic visible as such to the js controllers and added a new bit of js. When you have selected the first post in a topic for multi-mod the only option you get is merge. Uncheck the first post and all the other options come back immediately.
Only tiny hitch is the multi-mod controller doesn't emit an event when the button options change so I had to listen for something else - and that just means the button controller that pops up will be slightly non-centered when the first post is selected. No big deal (though when I installed it on another test board on my dev installation it did pop up the multi-mod options with no checkboxes selected in the first topic I viewed. I just selected hide and save and it went away - this was 99% likely just a phantom resulting from me running multiple dev boards on the same laptop - some lingering browser js vars carrying across installations. Nothing to worry about)


That's all. If I can get IPS to emit an event on the rebuildButton thingy it will be centered. No matter, I think you can live with it.

@Ramzzes @Apfelstrudel @Nathan Explosion 
Kitchen Sink will have this in the next version. Merge only though.
 

@Azoun
Version 4 released.
Adds option to change the CSS button class.

I'll just add it as an option. Give me a bit, just woke up after 17 hours of driving.

Just a general reminder to everyone that just like IPS will not do support requests when a custom theme has broken something, most/all Marketplace devs have the same policy. If whatever app/plugin is working with the IPS default theme, the problem lies with whatever changes the theme maker has done.
I'll give a hand where I can, time permitting, or if I'm curious, but there is really nothing I can do unless you want to pay me my hourly rate.
You can trouble shoot theme problems yourself you know.
Suppose your site crashes with a generic 500 code error. If you are told there is a problem with the theme as whatever app/plugin works fine with the IPS default theme, now what?  Is the themer going to track down the error for you? They should... But lets assume they won't.
1) Go to your ACP and make a copy of the theme that is breaking things. Edit the theme settings so your member group has access to this copy on the front end.
2) Naturally, on the front end, change your theme to this new copy. Refresh. Of course, if the app/plugin that conflicts with the theme is running, on refresh you get that 500 error page. Good.
3) Back in the ACP, on the theme pages, for our newly copied theme click the </> button for the theme to bring up the template editors.
4) Its opens up already in Core - Front - Global where all the global front end templates are. Now it's just a slow game of Whack-a-Mole.
5) As you scroll up and down the templates in this area, you'll see some of them are flagged with an "m". That means they are modified away from the IPS default theme. What you are going to do is load up these, one at a time, and then click the REVERT button in the upper right of the page. That will reset the entire template back to the IPS default version. One at a time, revert, then go back to the front end (you probably have this open in another browser tab), refresh the page. Did the site start working again? Congratulations! You found the theme template that has broken everything. Still throwing the 500 error? Back to the ACP revert another modified template, back to the front, refresh the page, and so on.
If the problem only flares up in a certain application, then open up the templates in that area and do the same.
AP in the post above has the Nerva theme for 4.2. KS works just fine with with 4.2 but not with this theme. Throws a site crashing 500 error and the error logs that result are just random not working correctly things with no evidence that KS is involved at all - no hooks, no ks code, nothing.
I was curious so I looked (and yes, if you want me to do this for you in the future you'll need to pay me - problems like these are on the themer, not the app/plugin author)
Reverted the global template, still 500 errored. Well there is navBar, and KS does some stuff there and that's been modified, let's revert that one.
And there we go, everything starts working again.
So whats the problem? Conveniently the user above had the 4.1.19 version of the theme still present. I just needed to "diff" the file (compare side by side the changes between the two versions of the navBar template)
Can you spot the problem? (this is the 4.2 navBar template with the first couple of lines)

AP doesn't get to answer as I already gave it to him. First *correct as deemed by me* answer gets a free copy (renewals are on you) of Sound Board!
 

FYI I've just ghost-patched KS to tackle a few odds and ends. No version bump though. For 4.2 users just download KS 13 again and upload a new version over top your already installed KS as usual.
I'd love to be able to change the file associated with KS 12 in the versions area but alas, I cannot. So, when you click the download file button now for KS 13 along for the ride is a patched version of KS 12 for legacy 4.1.19.4 and lower users. Same deal for you guys; just upload a new version over top your existing install.
And of course, remember: KS 13 = 4.2 onward. KS 12 = 4.1.19.4 and lower.