Jump to content


Daniel F

Invision Community Team
  • Posts

  • Joined

  • Days Won


 Content Type 



IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog



Everything posted by Daniel F

  1. The _title is a hash value, so the equal check with "Episodendatenbank" will fail! you should use always use the id for such checks! /** * Get database name * * @return string */ public function get__title() { return \IPS\Member::loggedIn()->language()->addToStack('content_db_' . $this->id); }
  2. There's no need to overcomplicate things:) $item->database()->_title should work fine in this case
  3. I changed it few hours ago. Didn't want to mention it, but now I have, just to make sure that nobody thinks that he's crazy:D
  4. There are at least 2 different ways to accomplish this which I've mentioned here: Depending on the ammount of fields you want to store, you could either use an own database table or a setting to store the data.
  5. We fixed recently a bug which caused the los of the redirect after the login process. This should be resolved in the next release.
  6. please submit a ticket so that we can look into this
  7. Why would you want to change a global setting when the widget is removed? What are you trying to achieve?
  8. I have logged the request internally. Thanks for the kind words!We're really thrilled to see what people will do with their Zaps.
  9. Do you see any errors in your browsers JS console?
  10. Check your purchases page where you should see the already existing renewals invoice. https://invisioncommunity.com/clients/purchases/
  11. We have an internal suggestion for this ๐Ÿ™‚
  12. It's of course a framework feature which can be used in 3rd party applications. We'll update the developer documentation once 4.5.5 is here and post instructions for theme designers with the breaking changes once ASAP, so that they're able to prepare their custom themes.
  13. You should be able to purchase it already.
  14. I've found following error in the MP test environment Error: Unsupported operand types (0) #0 /Users/danielf/Sites/localhost/mp/applications/core/extensions/core/Dashboard/BackgroundQueue.php(56): IPS\nbcontenttabs\extensions\core\Queue\_Delete->getProgress(Array, 0) #1 /Users/danielf/Sites/localhost/mp/applications/core/modules/admin/overview/dashboard.php(64): IPS\core\extensions\core\Dashboard\_BackgroundQueue->getBlock() #2 /Users/danielf/Sites/localhost/mp/system/Dispatcher/Controller.php(101): IPS\core\modules\admin\overview\_dashboard->manage() #3 /Users/danielf/Sites/localhost/mp/system/Dispatcher/Dispatcher.php(152): IPS\Dispatcher\_Controller->execute() #4 /Users/danielf/Sites/localhost/mp/admin/index.php(14): IPS\_Dispatcher->run() #5 {main}
  15. I'm working on the ticket right now, but to be fair, according to your system log it's def. a 3rd party issue: ArgumentCountError: Too few arguments to function IPS\core\modules\front\system\_register::_createMember(), 2 passed in /var/www/html/105119/init.php(893) : eval()'d code on line 26 and exactly 4 expected (0) #0 /var/www/html/105119/init.php(893) : eval()'d code(26): IPS\core\modules\front\system\_register::_createMember(Array, Array) #1 /var/www/html/105119/init.php(893) : eval()'d code(90): IPS\core\modules\front\system\hook1905::_createMember(Array, Array, NULL, Object(IPS\Helpers\Form)) #2 /var/www/html/105119/init.php(893) : eval()'d code(15): IPS\core\modules\front\system\hook2764::_createMember(Array, Array, NULL, Object(IPS\Helpers\Form)) #3 /var/www/html/105119/applications/core/modules/front/system/register.php(240): IPS\core\modules\front\system\hook2898::_createMember(Array, Array, NULL, Object(IPS\Helpers\Form)) #4 /var/www/html/105119/applications/core/modules/front/system/register.php(174): IPS\core\modules\front\system\_register->_registrationForm(NULL) #5 /var/www/html/105119/system/Helpers/Wizard/Wizard.php(181): IPS\core\modules\front\system\_register->IPS\core\modules\front\system\{closure}(Array) #6 /var/www/html/105119/applications/core/modules/front/system/register.php(181): IPS\Helpers\_Wizard->__toString() #7 /var/www/html/105119/init.php(893) : eval()'d code(27): IPS\core\modules\front\system\_register->manage() #8 /var/www/html/105119/system/Dispatcher/Controller.php(101): IPS\core\modules\front\system\nexus_hook_register->manage() #9 /var/www/html/105119/system/Dispatcher/Dispatcher.php(152): IPS\Dispatcher\_Controller->execute() #10 /var/www/html/105119/index.php(13): IPS\_Dispatcher->run() #11 {main} This error means literally that a plugin or application hooking the register::_createMember method is failing because it isn't compatible with IPS 4.5
  16. You can use icons and even emojis in the title field.
  17. https://invisioncommunity.com/settings/links/ You can change the default behaviour in the ACP => Members => Profiles => Profile Settings Tab.
  18. Since 4.5 users can configure where they want to be redirected https://invisioncommunity.com/settings/links/
  19. He means inside the ACP ( the new 4.5 ACP MP page) ๐Ÿ™‚ This was suggested before and I think it's something what we want to look into.
  20. Thereโ€™s at least one WhatsApp app/plugin in our marketplace
  21. Please submit a ticket and weโ€™ll take a look
  22. You mean something like this? That's included in 4.5.4 which was released yesterday ๐Ÿ™‚
  23. An issue was identified in this plugins upgrade code. You're iterating over almost all member rows in the step2 upgrade step which of course won't work on medium & big boards resulting in issues. foreach( \IPS\Db::i()->select( '*', 'core_members', array( 'warnLogs_tid>?', 0 ) ) as $row ) { \IPS\Db::i()->insert( 'warnlog_membersdata', array( 'member_id' => $row['member_id'], 'topic_id' => $row['warnLogs_tid'] ) ); }
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy