voinea

There's nothing new regarding @newbie LAC's health. I personally fear the worst.
Newbie wouldn't just abandon his work, plus I am of the mindset that he would've provided some sort of update if he could. We can only speculate, but I hope he's actually doing well or at least being taken care of. Maybe someone from IPS @Matt @Lindy @Charles could make some formal comment.
I am seeing a lot of comments on his resources about updates, along with frequent messages to myself.
The main concern is Newbie's health, perhaps even sorting something out to support him if he is having treatment of a serious nature. Resources don't remotely come near to life, but it's not knowing which makes things worst.
I don't think having resources remade would be a solution that is fair, without understanding what the situation may be.
PS. Perhaps the resources should be closed within the forum from comment? There's only so many times I, or another concerned customer tries to remind people that Newbie hasn't been well and was in hospital (as his signature stated).

How do I get this working on 4.6?

It depends on when you upgraded . 
We have patched the release 14h ago  with some slightly changed to avoid that people with 3rd party apps and specific hooks run into this 🙂 

Others have reported similar issues when updating to 4.6.10, see this topic for more information and possible solutions:
Would you be able to take a look at your PHP error logs?

There is probably a third-party app that has a hook on \IPS\Dispatcher directly (and not on \IPS\Dispatcher\Front or Admin instead). This is crashing new code IPS has in the init.php method in this latest version. You are a bit stuck until you figure out which app/plugin it is though. 
You'll need to look at core_hooks table, and then look at the 'class' column. You're looking for \IPS\Dispatcher there and NOTHING ELSE. Not \IPS\Dispatcher\Front; not \IPS\Dispatcher\Admin. If you see an entry there that's your app; if it is a plugin id, off to core_plugins you go to find the matching ID number and that's your plugin.
You'll need to set the RECOVERY_MODE constant (true) to stop all the hooks from loading to get access to everything again. You'll need to disable what you found before taking recovery mode off.... but with recovery mode on you don't actually get access to the ACP so you are in a bit of a loop here. You'll probably need access to the DB via phpadmin or something anyways to find what you need anyways (since recovery mode means no ACP etc. etc...) so once you've found your guy you can just set the application off there in that table, same for plugin.
On the off-chance things are still wonky, you may need to hack out the new IPS code in init.php and everything will work again but you'll need to still deal with whatever is crashing out here. If it gets to that point see my post in the dev area (if you have access there) or shoot me a PM.

Thanks to @Ocean West and @Myr for their input, and to @All Astronauts for the solution!  There was a plugin which needed updating - I had checked it in the Marketplace, and the revisions said something about "errors >=4.6.10" but it said nothing about errors related to upgrading, so I left it.
I assumed it wouldn't make any difference because only the system files were being upgraded and hey, why would any other apps/plugins need to be interacted with anyway?  Oh, did I mention I'm not a developer?
Anyway, I upgraded the plugin in question and the upgrade ran fine.  Thanks!

Omg. I did this and now it's working 😭
Thank youuuuu!!! 
 

Same issue here. Instagram embed not working on latest 4.5 IPS.