Maxxius

Already in, but we've not spoken about it yet.

Some.
We added the following methods to the Member listeners:
onReact onUnreact onFollow onUnfollow As mentioned in previous comments on this entry, we allowed for listeners on base classes, like \IPS\Content\Item.
I'm not sure what other suggestions you're referring to regarding listeners. Was there something specific?

Basically, I have a content item that has a "privacy" column. If it is private, it shows to the item creator only; public shows to everyone. I can't use my getItemsWithPermission() because, you know, it is static so I can't check the author against the logged member. Even if I could use it, I wouldn't use it because the item must be accessible by direct link. It just can't be listed.

Unfortunately, that won't work:
CSS is not an option because it would hide the fields for everyone, not just specific members/groups. In any case, they'd still be there in the output. Javascript would allow hiding the fields based on some extra JS variables in the output. Again, they'd still be there in the output. Since the fields are in the output, a person with some knowledge or a bot can still fill them in without trouble. Removing them completely, and not processing the values when the form is saved were requirements for the modification. (Don't ask me why it needs to be like that, but that was the request.)
 
Being able to easily extend all forms and adding new fields to them is nice, but being unable to alter the other fields is a severe limitation.

@Matt Please consider open sourcing v4 when you release v5.

You wouldn't need VC funding as you already have IPS Cloud business generating capital to invest in software development. Anyway, this is OT now, but it occurred to me that not having an open source version of your product is hindering your ability to grow to a large player in this industry.
And, I fear that you are about to lose even more third-party developers with your transition to v5 resulting in IC being a very niche product. Third-party developers are key to almost all successful growing internet companies.

We are not open sourcing anything.

Not every person has applications/plugins associated with the Marketplace. Many people downloaded the resource in xml/tar format and just installed it.
There are definitely more installations. IMHO.

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

They will be there for a couple of years for those who won’t jump in V5 right away.
File edits will be back with resources being sold in dev’s board. And for those who use marketplace and can’t use FTP, will get limited resources.
But there’s no doubt it will be the end of this marketplace and I truly believe that’s what IPS is after for a while now.
I haven’t decided yet if I will keep developing for IPS, as I told somewhere else… and I must confess the answer its getting clear at every blog entry. 
Anyway, if I remain, certainly will reduce from 300 to 50 maximum, due to… framework limitations. 😂

Controversial topic, I like it. 🫢 Adriano, good luck with the update over 300 resources 😁

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.

The second plugin is something that should be included by default really, but, leaving that aside, my main issue is the first one I linked. I have plenty of similar (custom) modifications. That's the biggest problem, and your reply doesn't help at all, unfortunately. 😔

I was silent so far, hoping for some revolutionary idea, but I have to agree with Adriano: with these changes modding is dead.
 
Listeners are basically the old Library hooks from 3.x, and we can no longer overload any other methods (unlike before). I won't be able to update 85%+ of my modifications with this system.
 
@Matt As an example, I see no way to update these plugins for 5.x:
 
 
Unless I'm missing something, or you have more coming to still allow them.

Thank you. 👏👍
Still, remove the ability to hook is a huge step back and will make marketplace even worse and smaller but I guess that’s the point after all. A massive number of resources are dead.
We’re basically back to IP.Board 2 (file edits will be required for custom jobs as we can’t hook) and IP.Board 3 (back to hook points era). 
Anyway, just my feedback. Not trying to annoy anyone; just my honest feedback.
Tks.

@Daniel F, it this something we can use internally in IPS? Without 3rd party service?
For example:
if user registers, then create a new Welcome PM for him if a database record updated, update the date of the parent record in the reciprocal database (database relationship) if user RSVP an event, join him to closed club if user subscribes to newsletter, gives him achievement points etc.