Jump to content

Orioni

Clients
  • Posts

    33
  • Joined

  • Last visited

Profile Information

  • Location
    Belgium

Recent Profile Visitors

3,343 profile views

Orioni's Achievements

  1. Thank you @Sonya*. That is certainly something to consider. Does this work for adding reputation points, or can it also remove points? For example: If I were to (1) set-up this automation via achievements, and (2) someone changes or removes their response, will this also (3) update the reputation?
  2. Right now, reactions have a fairly limited impact on reputation: Positive (+1) Neutral Negative (-1) What I'd love to be able to do is introduce more customisation here. For example: React with 👍 “Like” = positive +1 React with 🏆 “Thanks” = positive +2 React with ❤️ “Love” = positive +5 Because sometimes you're really happy with what someone did, and you'd like to give them an even bigger reputation increase. (Obviously, this also works negatively, but I've yet to come across such detrimental behaviour in my community.)
  3. @Marc Stridgen – Thank you for your clarity. I can live with the fact that a solution does not yet exist. Perhaps in the future this small feature might be considered. @GazzaGarratt & @Nathan Explosion – True. I'd also considered setting 365.25 days as a year. Then again, since not all members join in the same year, you're still guessing when the leap year will be. So the actual date will still be off.
  4. Good afternoon, dear Invision Community, Context Some members of my own community have been around for years, if not decades. I would like to display this with automatic achievements. Problem A custom rule would allow me to do so. Unfortunately, the highest level you can set for this rule is “weeks”. Now, I considered using custom “days” to do this (1 year = 365 days; 2 years = 730 days; etc.). However, leap years throw a wrench, making the anniversary inaccurate. Question Is there another way to solve this, and achieve the result I'm looking for?
  5. Looking forward to seeing much more of v5. Especially any editor improvements.
  6. Having this feature stripped from the core is really unfortunate. Seeing someone is having their birthday is a prompt to reach out. Now that's no longer possible. That makes me sad. Perhaps because today is mine, and now nobody will notice.
  7. This evening I received this banner informing me that a patch is available. This struck me as odd for several reasons: There is no mention of this patch on invisioncommunity.com Invision is out-of-office for July 5th (says the blue banner up top), so who's pushing this patch? Does anyone have the same notice?
  8. Good evening @TDBF. How are you doing? With the recent release of IPB v4.6 do you have any plans for updating this plugin to be compatible? That would be neat to know. Thank you.
  9. Congratulations on the ongoing effort. Invision remains the obvious right choice. It shows in the vision you present and the delivery quality.
  10. GTM is the way to go. Especially with the new GA4 on the horizon. Working in online marketing, our default setup for the past years is always via GTM. Having the option to work with GTM would be a good upgrade to the tracking possibilities of Invision Community.
  11. While I don't have a solution for this, I'll be following this topic since my dispatcher is throwing a similar error. #0 /var/www/html/105118/system/Dispatcher/Front.php(582): IPS\_Widget::load(Object(IPS\core\Application), 'announcements', 'announcements', Array, NULL, 'horizontal') #1 /var/www/html/105118/system/Dispatcher/Dispatcher.php(154): IPS\Dispatcher\_Front->finish() #2 /var/www/html/105118/index.php(13): IPS\_Dispatcher->run() #3 {main}
  12. While duplicating one trophy to create another, I recieved this error after hitting "save". My changes were not saved. TypeError: Argument 2 passed to IPS\trophies\extensions\trophies\TrophyCriteria\_Expression::memberMeetsCriteria() must be an instance of IPS\trophies\Trophy, instance of IPS\trophies\_Trophy given, called in /var/www/html/r278479/applications/trophies/sources/Trophy/Trophy.php on line 433 (0) #0 /var/www/html/r278479/applications/trophies/sources/Trophy/Trophy.php(433): IPS\trophies\extensions\trophies\TrophyCriteria\_Expression::memberMeetsCriteria(Object(IPS\Member), Object(IPS\trophies\_Trophy), NULL) #1 /var/www/html/r278479/applications/trophies/sources/Trophy/Trophy.php(478): IPS\trophies\_Trophy->memberMeetsCriteria(Object(IPS\Member)) #2 /var/www/html/r278479/applications/trophies/extensions/trophies/TrophyCriteria/Criteria.php(45): IPS\trophies\_Trophy::updateTrophiesForMember(Object(IPS\Member)) #3 /var/www/html/r278479/applications/trophies/sources/Trophy/Trophy.php(233): IPS\trophies\extensions\trophies\TrophyCriteria\_Criteria::handleForm(Array, Array) #4 /var/www/html/r278479/system/Node/Controller.php(413): IPS\trophies\_Trophy->formatFormValues(Array) #5 /var/www/html/r278479/system/Dispatcher/Controller.php(90): IPS\Node\_Controller->form() #6 /var/www/html/r278479/system/Node/Controller.php(62): IPS\Dispatcher\_Controller->execute() #7 /var/www/html/r278479/applications/trophies/modules/admin/trophies/trophy.php(54): IPS\Node\_Controller->execute() #8 /var/www/html/r278479/system/Dispatcher/Dispatcher.php(152): IPS\trophies\modules\admin\trophies\_trophy->execute() #9 /var/www/html/r278479/admin/index.php(14): IPS\_Dispatcher->run() #10 {main}
×
×
  • Create New...