Chris Anderson

I would be happy to see a 4.6 compatible version without any new functionality and an update incorporating new ideas down the road. That seems to be the approach other developers are taking.
Stratagem might fill the bill for you.

Restore from your backup you made just prior to starting an update.

i've released 2.4.0 of stratagem to the marketplace and my website (the marketplace one might take a little bit to be approved, i heard they have quite a backlog).
here is the changelog for 2.4.0, a few new features and several fixes.
fixed issue with project filters (they now work again :)), also fixed it showing cards that meet 1 or 2 of the criteria for filters instead of all of them. fixed issue for notifications, when a user is removed from a private project, they should now no longer be able to receive new notifications. fixed issue with "limit card view", due to a permission misconfiguration, wouldn't show all cards with a team member who had the permission to "card sort" or "card assign"  fixed/change how calendar integration works. now we use a more custom solution, instead of directly using the calendar app. (still requires the calendar app to be installed, as this new method uses the css/js from calendar). this solution should prevent duplication of strategem calendars and duplicate stratagem events on that calendar, the calendar is now generated at access time, and the card events are generated then and there as well. NOTE: you can safely delete any stratagem calendars that were created by previous versions, as they will no longer be used. Copying: added in copying of project/column/cards. you will enable in project settings if you want copying to be enabled, and then assign the permissions to the teams as you see fit. Note: if a project is has limit card view enabled, then team members will only be able to copy the cards they can see (this also applies if they copy the project, it will only copy the cards they can see). This also applies to columns that have restrictions, if they aren't on the allow list (een if they can see the column and its cards), they will not have the copy option nor will they be copied if the project is copied. Note2: copying cards is a instant action, but copying a column or project runs thru a task, so there might be a delay between copying the column/project, before it shows up or is completed. Note3: A lot of the settings for a project will be copied, but things like "real time mode", "due date", "publish date", "slack hooks", "git repos", and a few others, will not carry over to a copied project, nor will teams. all copied cards from a project, will have their creation date and author updated to the time it was copied and the user who copied the project.  Several new history entries, mostly related to copying cards/columns/projects.  fixed issue with quick access, it should now update properly for any changes to columns. fixed "lock project" and limit card view settings, before if you locked a project with limit card view enabled, it would show the restricted cards to anyone who viewed the project, now it will function as it would before locking the project. 

From my point of view, situations like this call for an emergency email or front end push message to ALL admins. I installed the update on 5 sites and had no idea it had effectively deactivated sign-ups on all of them. (I don’t use quick-registration) And this includes sites with like 100 new members a day (and potential clients which might never come back). If I hadn’t seen this topic, the problem might have persisted for days, if not weeks. There isn’t even a backend warning. Having the main registration form working isn’t “optional” as the grey “optional update” link suggest, it’s absolutely CRUCIAL. 

I was totally unaware of the additional available constants that @Meddysongmentioned above as they are not listed in the constants.php Help Guide.
@Stuart SilvesterThere may be value in creating an detailed Help Guide for setting up and utilizing test sites effectively.  Especially considering you rely a great deal on your customers for testing each of your releases, and having fewer support requests benefits everyone.  This could be a collaborative effort between your company and your most knowledgeable customers.
Being an effective tester requires an entirely different mindset and knowledge base than being a community manager.  That is something you have experience with, why not share your knowledge in an easily digestible fashion.  
 

Added to the list for future guides.

It goes without saying that we all want every one of  the marketplace apps to be updated within days of a new release.  We need to better manage our expectations as Adriano has a very large collection of marketplace and custom apps that he supports. They will all be updated when they get updated and not a moment sooner.  
Coding and testing works best when you are in a good frame of mind.  Being constantly pestered for updates is unlikely to put Adriano in such a state.  Be of good cheer@Adriano Fariaand the other marketplace developers, we appreciate all of you...

It goes without saying that we all want every one of  the marketplace apps to be updated within days of a new release.  We need to better manage our expectations as Adriano has a very large collection of marketplace and custom apps that he supports. They will all be updated when they get updated and not a moment sooner.  
Coding and testing works best when you are in a good frame of mind.  Being constantly pestered for updates is unlikely to put Adriano in such a state.  Be of good cheer@Adriano Fariaand the other marketplace developers, we appreciate all of you...

It goes without saying that we all want every one of  the marketplace apps to be updated within days of a new release.  We need to better manage our expectations as Adriano has a very large collection of marketplace and custom apps that he supports. They will all be updated when they get updated and not a moment sooner.  
Coding and testing works best when you are in a good frame of mind.  Being constantly pestered for updates is unlikely to put Adriano in such a state.  Be of good cheer@Adriano Fariaand the other marketplace developers, we appreciate all of you...

It goes without saying that we all want every one of  the marketplace apps to be updated within days of a new release.  We need to better manage our expectations as Adriano has a very large collection of marketplace and custom apps that he supports. They will all be updated when they get updated and not a moment sooner.  
Coding and testing works best when you are in a good frame of mind.  Being constantly pestered for updates is unlikely to put Adriano in such a state.  Be of good cheer@Adriano Fariaand the other marketplace developers, we appreciate all of you...

It goes without saying that we all want every one of  the marketplace apps to be updated within days of a new release.  We need to better manage our expectations as Adriano has a very large collection of marketplace and custom apps that he supports. They will all be updated when they get updated and not a moment sooner.  
Coding and testing works best when you are in a good frame of mind.  Being constantly pestered for updates is unlikely to put Adriano in such a state.  Be of good cheer@Adriano Fariaand the other marketplace developers, we appreciate all of you...

As much as we all wish that IPS releases bug free code they consistently show they they are not up to the task.  Just like the rest of the software developers out there...
If anyone chooses to upgrade their site within hours of a new release they are likely to encounter problems and it will take time for IPS to investigate and fix.
If you want to minimize the potential for downtime, delay upgrading to allow for "all" issues to be discovered and addressed on people's test installs before updating your production site.

It goes without saying that we all want every one of  the marketplace apps to be updated within days of a new release.  We need to better manage our expectations as Adriano has a very large collection of marketplace and custom apps that he supports. They will all be updated when they get updated and not a moment sooner.  
Coding and testing works best when you are in a good frame of mind.  Being constantly pestered for updates is unlikely to put Adriano in such a state.  Be of good cheer@Adriano Fariaand the other marketplace developers, we appreciate all of you...

It goes without saying that we all want every one of  the marketplace apps to be updated within days of a new release.  We need to better manage our expectations as Adriano has a very large collection of marketplace and custom apps that he supports. They will all be updated when they get updated and not a moment sooner.  
Coding and testing works best when you are in a good frame of mind.  Being constantly pestered for updates is unlikely to put Adriano in such a state.  Be of good cheer@Adriano Fariaand the other marketplace developers, we appreciate all of you...

I think one issue is that when they release a bug fix for a new version but also mention a security fix (whilst not stating if it applies to just 4.6 or not), even more people will upgrade quicker, which is a pain for the Marketplace developers and designers because they are then under even more pressure to get their compatibility updates out. People were doing the old (when you going to realise a 4.6 compatible version of my plugin?) just days after the developer tools were released. 
I've personally come to dread big IPS upgrades because updating a local dev machine is scary because you don't know if it's going to work. Mixed and unclear advice, no documentation on doing so etc don't help reassure.
 

As much as we all wish that IPS releases bug free code they consistently show they they are not up to the task.  Just like the rest of the software developers out there...
If anyone chooses to upgrade their site within hours of a new release they are likely to encounter problems and it will take time for IPS to investigate and fix.
If you want to minimize the potential for downtime, delay upgrading to allow for "all" issues to be discovered and addressed on people's test installs before updating your production site.

As much as we all wish that IPS releases bug free code they consistently show they they are not up to the task.  Just like the rest of the software developers out there...
If anyone chooses to upgrade their site within hours of a new release they are likely to encounter problems and it will take time for IPS to investigate and fix.
If you want to minimize the potential for downtime, delay upgrading to allow for "all" issues to be discovered and addressed on people's test installs before updating your production site.

If you check the description of this app you would see that it hasn't been updated to be compatible with 4.6.2 as of yet.  Please exercise some patience with Adriano and all the other marketplace developers, as they all have lot of apps to update all of which are important to one person or another.  

If you check the description of this app you would see that it hasn't been updated to be compatible with 4.6.2 as of yet.  Please exercise some patience with Adriano and all the other marketplace developers, as they all have lot of apps to update all of which are important to one person or another.  

Will take a look . Work right now in the 4.6 version.

@Jordan Invision It might be nice to alert the entire customer base of these changes instead of putting the marketplace developers in a tough spot having to explain your business decision and deal with the customer angst that's bound to happen in the days ahead.
 

@Jordan Invision It might be nice to alert the entire customer base of these changes instead of putting the marketplace developers in a tough spot having to explain your business decision and deal with the customer angst that's bound to happen in the days ahead.
 

I would want this as a site-wide feature (for user content). A 5 MB PNG screenshot would usually just be 100 KB as JPG. 

I like this idea but there would need to be some way to end subscription (and revoke elevated access) if a member fails to complete one of the payments. A configurable grace period and set of warnings should also be included to gently prompt a member to complete their payment plan.  
There should also be a way to track these kinds of subscriptions in the ACP so the admins know which members are on subscription plans, and their status (such as: Payment 2 of 5, Days Late).  This would allow the admins to know how much money should be coming in and which members are behind on their payment plans.  "If" a member fails to complete a payment plan there should be a way to mark their account as such. 
 

https://invisioncommunity.com/4bugtrack/