v5.0.9 nulled please and thank you sir
#4973: Fix an issue where members without a display name generated multiple errors
#4983: Fixes an issue where DB articles won’t sync if use forum comments is disabled
#4802: Statistic Reporting Updates
#4950: Force refresh R2 key
#3822: Fix TypeError in OAuth2 login handlers when there is no access token
#4693: Fixed minor UI issues with ACP tables and some widgets
#4952: Fix an issue where empty saved custom filters executed an invalid SQL query
#4955: Fixes an issue in the approval queue...
Attached.maybe the 4.x update also... lucky?
Hi!Attached.
What's the meaning of locking a forum script? It makes sense when you lock the theme and plugin. Do you want users to post unwanted resources to the forum, and who maintains these resources when they already leak to the forums? It's creating headaches for the forum admin.Invision Community v5.0.10 Nulled 5.0.10
By Matt
July 23 · 1,468 views
- Released 08/07/2025
- Current Release: Yes
- Beta Release: No
This is the latest version of Invision Community 5.0.10.
Key changes include:
- New: Quests ( Team, Business & Enterprise plans )
- Advert management improvements
- PWA improvements
- Pages rollback feature
#4947: Quests
#5090: Club Templates
#5018: Implement versioning for Pages
#5006: Improvements to Advertisements
#4749: PWA improvements
#5143: Fix an exception in database navigation widget
#5142: Fix an exception in sitemaps
#5132: Trigger a PII ACP Notifications Reset when a member is deleted
#5129: Show the report notification modal if there’s more then one predefined notification text
#5119: Fix an issue where sidebar ads would show when the sidebar was empty
#5118: Fix exceptions in some URLs
#5113: Fix an issue where Translation Tools did not work correctly
#5111: Throw the proper exception when attachment related content can’t be loaded
#5099: Added a template hook on Club details
#5110: Fix an issue where the last page of a large topic has the full number of comments per page
#5053: Persistent R2 Key Storage
#5114: Fix an issue where custom CSS was not loaded on a theme editor error page
#5107: Fixes an issue where the last comment data on large topics may be empty.
#5043: Fix an issue with theme editor settings not persisting through an editor session
#5086: Fix an issue where club blogs could not be edited
#5085: Fix an error on the Featured Content page when retrieving invalid content items
#5084: Fix an issue where database record image thumbs can return null
#5083: Fix incorrect sort order in Database Navigation widget
#5080: Fix an issue where tags with ampersands could be selected multiple times
#5079: Hide the Trending Content widget if it's not available
#5076: Added hook points to the topic submit form
#5075: Fix an issue where creating a similar event did not have the option to follow it
#5063: Ensure --i-data--max works when gap, borders and padding are defined
#5087: Fix an issue where custom template HTML comments were showing for hooks not in use
#5051: Fix an issue where custom JS defined in the ACP was not being parsed
#5049: Fix an issue where loading emojis generated an error in the logs
#5050: Fix issues with reordering club menus
#5052: Fix an issue where missing attachments generate an error in RSS feeds
#5044: Move app-specific groups columns to the core schema
#4979: Better handling of uploaded images for theme editor settings
#5022: Fix an issue where a required language string was in the forums app
#5028: Improved alignment of "Ranks are being recalculated" message
#5027: Prevent "Choose Options" and "Add to cart" buttons from being squashed in Commerce list view
#5026: Fix an issue with storing and loading custom package types
#5024: Ensure dailymotion iframes are 16:9
#5023: Fix an issue where a custom error page did not always show correctly
#5030: Fix broken warning email
#5010: Get Login Link from Write server
#5003: General Statistics Reports Fixes
#4999: Don't send login link emails as often
#4989: Implement support for multiple custom badges on a single node object
#4986: Fix FTP-related error messages
#4987: Fix an issue where an admin could create duplicate database templates
#4988: Fix an issue where content pending approval could not be hidden
#5094: Allow admins to set an API key for webhooks in the ACP
#5102: Fix webhook creation
#5103: Ban Webhooks
#5145: Reaction Webhooks
#5045: New Member Webhooks
#5061: Webhook log
#5092: Additional API calls
#5056: REST API Tags Endpoint
#5046: REST API endpoints for courses
Developer Notes
Additional API calls
Added API endpoints for:
Additional properties returned in API responses
- GET /core/members/{id}/messages
- GET /core/messages
- GET /core/messages/{id}
- GET /core/messages/{id}/replies
- GET /core/messages/{id}/reply/{replyId}
- GET /core/tags
- GET /core/tags/{id}
- GET /courses/courses
- GET /courses/courses/{id}
- POST /courses/courses/{id}/enroll/{member}
Added hook points to the topic submit form
- Forum: description, cardImage, followerCount
- Member: totalMessages, unreadMessages, badges
Added additional hook points in the create topic form template.
Webhook log
Added a page in the AdminCP to show all the webhook responses to make debugging easier.
Improvements to Advertisements
Various New Webhooks
- New property Output::$bodyAttributes, which is an array of data attributes that are added to the body tag.
- All content controllers now set Output::$bodyAttributes['contentClass'] to the $contentModel.
- All controllers that handle node views set Output::$bodyAttributes['contentClass'] to the node class.
Adds new web hooks which are fired when:
*** Hidden text: cannot be quoted. ***
- Content reported
- When Member follows & unfollows something
- Content assigned & unassigned
- When a member enrolls a course
- When a member finishes a lesson
- When members are flagged as spammers, or banned/unbanned.
There are very few of us left sharing resources on this forum, where everything is fairly up-to-date and, most importantly, free. I update my own resources, which I publish myself, and for almost all of them, I'm satisfied with a like. I update posts that aren't mine, and then the forum owner, or the person who shared the original resource, can download my file and update it for everyone. In other forums, you either pay or face numerous limitations. Resources here should be shared by everyone, but there are people who don't post anything themselves, instead complaining or requesting updates, without sharing anything with others. I think I'll also stop sharing resources or updating my own, so you never have to complain again.What's the meaning of locking a forum script? It makes sense when you lock the theme and plugin. Do you want users to post unwanted resources to the forum, and who maintains these resources when they already leak to the forums? It's creating headaches for the forum admin.
There are very few of us left sharing resources on this forum, where everything is fairly up-to-date and, most importantly, free. I update my own resources, which I publish myself, and for almost all of them, I'm satisfied with a like. I update posts that aren't mine, and then the forum owner, or the person who shared the original resource, can download my file and update it for everyone. In other forums, you either pay or face numerous limitations. Resources here should be shared by everyone, but there are people who don't post anything themselves, instead complaining or requesting updates, without sharing anything with others. I think I'll also stop sharing resources or updating my own, so you never have to complain again.