prupdated

The built in criteria are  retroactive BUT the award date isn't it. So if you install the application NOW, and you create a trophy with "member created 1 post" the awarded trophies will have NOW as award date and not the date from the first post... I've had a client who contacted me today, but unfortunately this isn't a bug and I'm not planing to change this.
Also please keep in mind that if e.g. a member has an avatar and you have a trophy "avatar", he'll loose the trophy once he removes the avatar. 
To clarify some other changes which were mentioned today:
A trophy WON'T be awarded automatically once the criteria are met. They are awarded by a IPS cronjob and also upgraded automatically when a member logs in.
The reason for this is, that the client who requested this application has a really huge board which is quite active and he requested to have as minimal queries as possible...
I can see that this workflow will cause confusion for some people, so this will be improved in a future release.
 
Yes
No ( but possible with a custom plugin or rules)
No ( but possible with a custom plugin or rules)
Yes

I completely missed this post, I apologize. 
It's interesting that it's timing out, I have clients running this mod and distributing to a couple hundred thousand members without a timeout. I will look into it and see if there is a way to improve this. 
Sparkpost's rate is hard-coded into IPS code and I cannot override it. I think it's 1500 emails per cycle.

Then exclude the moderator forums. I can't imagine a scenario where anyone would want to include moderator data in a public-facing newsletter... and that's the idea here, for this to be sent to a wide distribution base.
Also, if I checked permissions on distribution, performance would be shot. This wasn't an oversight, this was something to which I gave considerable thought. Right now, I generate the issue content on publish, store it once. Then I send it out to each email in the list, in batches. Checking permissions would require almost a full rewrite of the distribution process.
True. But for moderator forums, I would think just following the forum would be sufficient? 

I never used the app but I think it's enough you create one newsletter for the staff, with staff forums, then another to members, without staff forums.

Just realized I can't edit the first post anymore. lol

Getting a bit off-topic, but I appreciate the perspective.
In general, I would always advocate running a development/test copy of production, where you try any upgrades and changes before doing it live. That should help catch issues before they become much bigger issues. Routine backups are a good idea regardless. That being said:
I feel your pain. Lack of backwards-compatibility is definitely a big issue (my other app was plagued by it for a while, in one case they tweaked a feature three different ways in three consecutive releases), and contributor rants on the subject are long and numerous. There's not much to be done about it. IPS insists on being able to refactor and fix framework bugs as deemed necessary, at any time. To their credit, they have made an effort to try maintaining BC, post about breaking changes in advance, and make pre-release builds available. That's an improvement over what it was. Still, always unintended side-effects (see: this).
I understand their perspective, and they do what they have to do for their own business interests. Telling people, 'hey, we won't be able to fix this bug until the next major release in a year or two because it might break other stuff' isn't an option as far as they're concerned.
The flip side, of course, is that they've created an ecosystem with little semblance of stability. It's cumbersome to maintain anything substantial on it, and I think the number and state of contributors around is demonstrative.
It may be there are different design decisions they could've made to alleviate these issues--a more rigid and compact core, or a formal API and semantic versioning, or TDD, or using a common framework like Symfony... but that's largely immaterial. Not the reality we live in.
As for me, I try to fix my stuff when it breaks, but I've moved on to other pastures.

The 4.1.14 update was one of the most disruptive updates to my site in the last year or two. Immediately after updating I got tons of complains about members not being able to login and other issues. 
I have been running Easy Pages for quite a long time. I also experienced some of the same issues noted above. It didn't stop with the Easy Pages app either. There were many other problems - all of which worked fine before 4.1.14.
At first, I was able to partially work around the new login url problem  by doing some server based rewrites / redirects.
Ultimately, more problems surfaced and I gave up and converted what Easy Pages I had to the regular Pages app. It seems over time, the Pages app has added much of the Easy Pages functionality to it anyway.
This was still hard because many of the features I used it for I had to change or get rid of completely during the migration.
After this, I had to uninstall Easy Pages. Then I also had to reset my Furls to defaults. Then recached the site. 
This fixed most of the problems. User logins were now working properly rather than retuning error pages. 
However there were still problems unrelated to Easy Pages. It seems after resetting Furls to defaults, there were a few native IPS calls still using the old format that were not reflected in the new default Furls. So I had to go into the source code and work around those. 
And second to last of my problems, a number of url formats I used for custom theme changes previously were now broken - such as calling a topic with just a dash after it and nothing else now required two dashes. 
And the last present of 4.1.14 was some type of IPS search index task update that caused my sql server to nearly lock up so bad it caused my website to timeout while it was running. After a few days, I was able to isolate this as the problem and just set my site to only index 3 days of data so it would calm down this problem. There is a thread about this problem elsewhere on the forum.
So what went from a seemingly routine IPS incremental update, turned out to be the nightmare of the year for me. All told it probably took me a week to sort out the mess.
I will certainly take all updates very seriously from now on with full backups done immediately before so I can immediate roll back and research when this type of thing happens again. I will also likely skip many of the updates since they can cause so many problems.
As it is, it has become more common to find an increasing number of plugins and updates and template changes and urls breaking on each IPS update. I can see why the cost to develop modifications for IPS 4 has gone up. Their shelf life may be only as long as a few weeks until the next update. At the same time, the number of modifications and functionality / performance of the forum software itself are a mere fraction of what used to be available in the IPB 3 days.
For crying out loud, to this day I still have to rely on using a Google search for indexing my forum rather than the built in high performance Sphinx searching of days gone by.

The 4.1.14 update was one of the most disruptive updates to my site in the last year or two. Immediately after updating I got tons of complains about members not being able to login and other issues. 
I have been running Easy Pages for quite a long time. I also experienced some of the same issues noted above. It didn't stop with the Easy Pages app either. There were many other problems - all of which worked fine before 4.1.14.
At first, I was able to partially work around the new login url problem  by doing some server based rewrites / redirects.
Ultimately, more problems surfaced and I gave up and converted what Easy Pages I had to the regular Pages app. It seems over time, the Pages app has added much of the Easy Pages functionality to it anyway.
This was still hard because many of the features I used it for I had to change or get rid of completely during the migration.
After this, I had to uninstall Easy Pages. Then I also had to reset my Furls to defaults. Then recached the site. 
This fixed most of the problems. User logins were now working properly rather than retuning error pages. 
However there were still problems unrelated to Easy Pages. It seems after resetting Furls to defaults, there were a few native IPS calls still using the old format that were not reflected in the new default Furls. So I had to go into the source code and work around those. 
And second to last of my problems, a number of url formats I used for custom theme changes previously were now broken - such as calling a topic with just a dash after it and nothing else now required two dashes. 
And the last present of 4.1.14 was some type of IPS search index task update that caused my sql server to nearly lock up so bad it caused my website to timeout while it was running. After a few days, I was able to isolate this as the problem and just set my site to only index 3 days of data so it would calm down this problem. There is a thread about this problem elsewhere on the forum.
So what went from a seemingly routine IPS incremental update, turned out to be the nightmare of the year for me. All told it probably took me a week to sort out the mess.
I will certainly take all updates very seriously from now on with full backups done immediately before so I can immediate roll back and research when this type of thing happens again. I will also likely skip many of the updates since they can cause so many problems.
As it is, it has become more common to find an increasing number of plugins and updates and template changes and urls breaking on each IPS update. I can see why the cost to develop modifications for IPS 4 has gone up. Their shelf life may be only as long as a few weeks until the next update. At the same time, the number of modifications and functionality / performance of the forum software itself are a mere fraction of what used to be available in the IPB 3 days.
For crying out loud, to this day I still have to rely on using a Google search for indexing my forum rather than the built in high performance Sphinx searching of days gone by.

Did you seriously just log in and enable the plugin after I told you it crashes the site? Because that's what has happened!
I told you last time not to log in and enable it! 
 
I'm just going to uninstall it now just leave it.

I just want to enable the plugin to see the problem that I can not reproduce. Anyway, my bad, I'm so sorry.

I have uninstalled the plugin and removed your account. I am irritated that you just logged in and made changes without asking me (and going against what I told you).
The plugin obviously doesn't work with busy sites and I wont let you test changes on my production environment. 
I'll just cut my losses and move on. 

A solution is not going to come easily. Unless IPS changes something, I don't see any real option except changing all page URLs.
I opened a bug report. We'll see what happens.
 

I can reproduce the problem reliably now, on my own install. Definitely a 4.1.14 compatibility problem. Any root URL with a query string seems to do it -- login post-redirect happens to create such a URL.
Still working on how to resolve this.

'Has anything changed in fURL handling recently, that might explain why this was never a problem prior to now?'

@Ryan H., You can now fix it? Or return the money 34.99$?

And so the circle starts

Lol,
 

Nope.
This error was not on the previous version of IPB. This happens only on the 4.1.14.2. I sent you PM with my adress forum and my account. Check on your own.

+1 - but no matter what we say - it will never return. Only IPS knows why...

I've read a lot of topics criticising the activity stream feature and I find it utterly unuserfriendly as well. What was the logic behind this change? It seems like a case where someone was trying to fix something that already worked and made it worse. Like Microsoft and the whole Windows 8 debacle.
Activity stream may be useful for a low traffic board and works on Facebook where you only get certain "posts" in your stream. But what is the point of having an activity stream on a high traffic board? It's so clumsy at what it should be doing.
Instead of letting you know which topics have new posts so you can get up to date, you face an endless stream of new posts (often from one and the same topic).
Basically what I'm asking si how the h**** should I be using this feature to help me browse the board? It obviously isn't doing its job properly but I'll allow the possibility that I'm just not using it as it was intended.
Can anyone help me understand this thing better? And why we can't simlpy have a choice of both (the old new content list and activity stream)? This way it just seems it was forced onto users.

MY users are asking something similar. They want an easy way to find threads they have posted in which contain new content. I think it can be done with the activity feed but I am not sure exactly how. I linked my users to the feed and one said this to me "it's not notifying me of new posts.  This just shows me where I've posted in the past. "

Are the blocks also ajaxed? I mean is it possible to insert blocks that are updated in real time?

Can I bump my previous post as well please and also ask what the plans are now Activity Stream has been refreshed and does the same thing in 4.1 ?

Appreciate that its not planned but this would be a really useful addition, a live stream in the sidebar updating every x seconds, is it something you will consider doing please?
Currently when a thread is created, in the social stream it appears with a reply box underneath it for you to be able to type a response. However if a reply to a thread appears in the feed (which is the vast majority of all feed entries) there is no reply box to respond to the previous comment. The only time you get the option to comment is on brand new topics, not posts to topics.
Hopefully that makes sense?

This should really move up the priority list. I have a forum with nearly 4 million posts and 600k topics.
In IPB3, the size of the forums didn't seem to matter. In IPB 4, the site chokes up and delays about 2-3 seconds every time someone would click on a forum with a large number of topics in it. By large, I mean several hundred thousand topics and millions of posts. Clicking on a smaller forum is no problem and happens fast. This is a 12 core server with 32 GB of RAM running at 3.2 GHz, MariaDB, etc. and various optimizations, CDN, etc.
The only way I could even use IPB4 without reverting back to IPB 3 and reconsidering my alternatives, was to chop up the forums into smaller ones. The main forum being about 50k topics max. Most likely the way I do it is not the best through various SQL statements. But to keep the site moving with sub second load times, I push out topics over 90 days old into an annual forum.
I know there's an archive option, but the last time I tried that I didn't like that it took those topics out of searches and member's history. I'd rather just have an option to move topics to another forum after X days without the archiving.