Adriano Faria

I don't think this is enough, though. If a member is logged anonymously, the visit isn't registered.

For member listener: - Visit a profile - Ignore/stop ignoring something (posts/messages/mentions). - Enable/disable messenger All the stuff I’m suggesting is to replace code hooks from existing apps/plugins. Thank you.

@Matt @Esther E. Nit sure everything is listed in the content listener, but would be helpful to listen when a user: - react/unreact to a content (specially this one which is a trait). - follow/unfollow a content. In both, returning member ID, content type (global, not per app) and content ID. Probably there are more. I’ll make another post if I remember. Thank you.

True, thanks for this... but as you all already said, we can't say much now as we haven't the big picture yet. So waiting...

Me too. Anything we say won't have any effect. As you said yesterday, I hoped we would be heard before it started. Hoping the UIExtension will be a game-changer. 👍

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. 😂

Matt, could you clarify exactly what you mean with “less”. As far as we can see, there won’t be ways to use hooks anymore. Is that right? I don’t see the Hooks tab in dev center. What you’re calling listeners that is fired in specific events can’t be called hooks at all, so I guess that’s the reason for such confusion. At least to me. Once and for all, will we be able to hook in class? Thank you.

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.

Nope. As far as I can see, you can only add new fields. You won’t be able to change some behavior or “remove” fields as hooks won’t exist in V5 (no tab in the dev center image above). More to come though: https://invisioncommunity.com/forums/topic/474790-v5-news-coming-soon/?do=findComment&comment=2948528

So the answer is no as there is no HOOKS tab anymore. So resources from now on will extend only official apps that I have in my license. If the user has another 3rd-party resource, it won’t work anymore because I don’t have all the marketplace resources out there to add listeners since it checks for the class. Great improvement.

Am I still allowed to hook in \IPS\Content\Item, for example? “NOTE: You can only create a listener on an implemented Item/Comment/Review class. You cannot listen on \IPS\Content\Item” There are resources that extends the global class, like this or this. These are suite resources, not single apps resources. Thank you.

I guess this says it all: 👍

...which is pretty weird as the same info is available in the topic view (sidebar) and anyone can easily see what's the most reacted post/comment, or the images attached, or the busiest day, so this is hiding public information. Thank you.

This one is fixed in Beta 2. 👍 @Stuart Silvester, could you add also allow \IPS\Content\Views in the method stats? Otherwise, we'll have to upgrade all 3rd-party resources that use it. It also should be in Changes affecting third-party developers and designers section of 4.7.11 release note.

@Marc Stridgen, do you have any news about this? Is it a bug too?

We hope. 🙂

No, it won't show to anyone. It was indeed removed from the content items; they don't extend \IPS\Content\Views anymore, which the method stats rely on to display the number of views. Now they use a new trait (\IPS\Content\ViewUpdates), which is used to display the number of views in the new feature announced in the first post.

Similar info is available for guests in the topics:

Why is this a moderation thing? Why regular users can't view so basic statistics? Why Most Active Members, Most Popular Days or Top Reacted Comments have to be hidden from the general public, or even guests?

Will this replace the topic sidebar in the Forums app? Is this used in \IPS\Content\Statistics so we can use it in 3rd-party resources?

I have no private message from you; at least I didn’t find it on a quick search. Anyway, development stopped when I first hear about the IPS app a couple of months ago or so. Due to a current rule for marketplace submissions, we cannot recreate things added by IPS. I imagine that something that was built to add value to their cloud’s packages would be definitely not acceptable so I didn’t even try to talk to them via Contact form, as Matt already said a couple of times. Matt also said that they will rewrite the marketplace submissions rules, so up till there, I won’t do anything.

Please, stop mentioning me. 🤨

Oh ok. I’ll take a look. 👍

I thought there was a specific method in the extension for Push and I didn't want to waste time in the time I updated my resources so I disabled push. Thanks.

Push notifications should be supported in 3rd-party resources to make notifications from these resources to be available, right?