Alexaner Pachkovsky

An interesting app.
Do you plan to implement the choice of language?
I have a forum in two languages, I would like to display footer depending on the user's chosen language.

An interesting app.
Do you plan to implement the choice of language?
I have a forum in two languages, I would like to display footer depending on the user's chosen language.

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.

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.

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!