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.