Matt

He will stare at me without blinking until I add in new tools. He can be quite scary.

I typed "The PHP programming language crying" into an AI image generator and all it gave me was a sullen, cosplaying Esther. BTW, next concert flyer? This.

PHP just started crying.

PHP just started crying.

1. You should all cool down and wait for the upcoming news and also the final product before getting in such a  panic rage.
2. Please see my reply in the SEO topic:
3. See the first point. We're listening to feedback and implementing changes based on it, just like Esther and Matt implemented changes today based on the provided feedback.
4. I think you're all way too scared.
There's still so much that can be done, it's 2023, and there are other ways and solutions than to edit files..
ALPACAS! I'll repeat very very slowly just for you: AL PA CAS

💩

Very nice inside jokes. Maybe someone spotlight it a little?

He will stare at me without blinking until I add in new tools. He can be quite scary.

He will stare at me without blinking until I add in new tools. He can be quite scary.

He will stare at me without blinking until I add in new tools. He can be quite scary.

Correct, there is less opportunity to overload/hook into/touch Invision Community 5. If you can give me some examples of why you'd want to overload those methods, we can help guide you to newer tools or understand why there is a need and consider adjustments to the dev toolkit.
Monkey patching (code hooks) were convenient but the cost was very high in that we couldn't significantly alter our code without destroying most existing modifications causing WSOD, ISE500 or other errors on client communities. As PHP 8 becomes more strict about typing, return types, etc - a simple function signature change could break modifications.
Clearly, allowing almost every single class and method to be overloaded is not something that we could continue doing.
We also want to be a little more protective of some of our UI and flows. We want to build a toolkit that lets you build amazing add-ons and extra functionality but it will mean there is less scope for smaller apps that change some of our existing functionality.
The good thing about these blogs is that we get to have a conversation and learn from each other.

The hooking of methods seemed to me close to ideal in IPS4 (although it had big problems), I did not think that IPSs would abandon this coding trick in IC5, which helped to fill the market with excellent solutions. Disappointed. But I still hope the team will please us with good news. Pending.

Thank you for the well written and detailed blog @Esther E.. I am happy to see that Ipb 5 is coming along very nicely and I am looking forward to the next blogs. And congratulations on joining the Ips team 😊
 

I'm always keen to get information out as soon as we have it fixed on our end. There are pros and cons but the earlier the feedback, the more chance we have at addressing it and making sure we've not missed any angles. Give it a few months and the v5 codebase will be much stabler and we'll be more reluctant to make big changes.
Some of the tools we're still actively working on, and stuff like theme tools are only about 80% complete, so there may be some gaps between blogs but we'll post them as soon as we have them ready.
Not exactly, it's more like the JS event system, you can listen in on events and execute your code when those events are triggered.

I'm always keen to get information out as soon as we have it fixed on our end. There are pros and cons but the earlier the feedback, the more chance we have at addressing it and making sure we've not missed any angles. Give it a few months and the v5 codebase will be much stabler and we'll be more reluctant to make big changes.
Some of the tools we're still actively working on, and stuff like theme tools are only about 80% complete, so there may be some gaps between blogs but we'll post them as soon as we have them ready.
Not exactly, it's more like the JS event system, you can listen in on events and execute your code when those events are triggered.

As mentioned in my first blog, there will be things you can’t do in 5 and this is deliberate. But there is still a lot you can do. 

I'm always keen to get information out as soon as we have it fixed on our end. There are pros and cons but the earlier the feedback, the more chance we have at addressing it and making sure we've not missed any angles. Give it a few months and the v5 codebase will be much stabler and we'll be more reluctant to make big changes.
Some of the tools we're still actively working on, and stuff like theme tools are only about 80% complete, so there may be some gaps between blogs but we'll post them as soon as we have them ready.
Not exactly, it's more like the JS event system, you can listen in on events and execute your code when those events are triggered.

I'm always keen to get information out as soon as we have it fixed on our end. There are pros and cons but the earlier the feedback, the more chance we have at addressing it and making sure we've not missed any angles. Give it a few months and the v5 codebase will be much stabler and we'll be more reluctant to make big changes.
Some of the tools we're still actively working on, and stuff like theme tools are only about 80% complete, so there may be some gaps between blogs but we'll post them as soon as we have them ready.
Not exactly, it's more like the JS event system, you can listen in on events and execute your code when those events are triggered.

I'm always keen to get information out as soon as we have it fixed on our end. There are pros and cons but the earlier the feedback, the more chance we have at addressing it and making sure we've not missed any angles. Give it a few months and the v5 codebase will be much stabler and we'll be more reluctant to make big changes.
Some of the tools we're still actively working on, and stuff like theme tools are only about 80% complete, so there may be some gaps between blogs but we'll post them as soon as we have them ready.
Not exactly, it's more like the JS event system, you can listen in on events and execute your code when those events are triggered.

I'm always keen to get information out as soon as we have it fixed on our end. There are pros and cons but the earlier the feedback, the more chance we have at addressing it and making sure we've not missed any angles. Give it a few months and the v5 codebase will be much stabler and we'll be more reluctant to make big changes.
Some of the tools we're still actively working on, and stuff like theme tools are only about 80% complete, so there may be some gaps between blogs but we'll post them as soon as we have them ready.
Not exactly, it's more like the JS event system, you can listen in on events and execute your code when those events are triggered.

As always, we are listening. We have a lot to announce yet. 

As always, we are listening. We have a lot to announce yet. 

We are discussing your feedback Adriano.

Thank you. It made for a very interesting reading. It looks like developing apps for Ipb 5 will be much easier. I am looking forward to the other blogs. 😃