Adriano Faria
Content Type
Downloads
Release Notes
IPS4 Guides
IPS4 Developer Documentation
Invision Community Blog
Development Blog
Deprecation Tracker
Providers Directory
Forums
Events
Store
Gallery
Everything posted by Adriano Faria
-
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.
-
What's New in Version 1.1.6 IPS 4.7.12 compatibility.
-
What's New in Version 1.1.1 IPS 4.7.12 compatibility
-
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.
- 131 comments
-
- 13
-
-
-
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.
-
Awaiting eagerly any info about this in the related blog entry. No more template hook and now “fewer opportunities” to hook. I hope v5 is more than add links to menu content.
-
It’s been like that since forever. I think it’s just a case of creating a FAQ or something to let them know how to properly use the board.
-
If you're using PHP 8.2, go back to 8.1.
-
The date is also linked to the post.
-
Wrong. Look at the quote Stuart did. They're talking about the topic links to next unread topic. Before and what was resource intensive is that showed the topic title.
-
No one ever said it was a performance issue: https://invisioncommunity.com/forums/topic/457939-why-arent-posts-numbered-within-a-thread/?do=findComment&comment=2826125 https://invisioncommunity.com/forums/topic/457939-why-arent-posts-numbered-within-a-thread/?do=findComment&comment=2826149 Performance was related to the topic title in the NEXT topic link below in topics. #post is a very tiny thing perfectly doable via plugin and should be kept that way.
-
How to disable Account Deletion request option?
Adriano Faria replied to usmf's topic in General Questions
This is the Core feature, according to the screenshot. Plus: the user didn't even downloaded my resource. 🙂 -
There’s a pending version that will be compatible with 4.7.12. Wait for it to be approved and test again.
-
@Giray, it will use the same profile field permission for displaying in content: Although there's a permission to show in profile, this one is easier to implement, etc. Sooooo, it will show in profile card (hover) the fields allowed to be displayed in topics (posts). Setting to disply profile fields there:
-
What's New in Version 1.1.2 IPS 4.7.12 compatibility
-
What's New in Version 1.2.7 IPS 4.7.12 compatibility
-
I'll try to add it to my existing resource:
-
What's New in Version 1.1.1 IPS 4.7.12 compatibility
-
Ow sorry, user info pane = left side in posts.
-
The last 2 rows are profile fields:
-
What's New in Version 2.1.1 IPS 4.7.12 compatibility.
