The following warnings occurred:
Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.2.25 (Linux)
File Line Function
/global.php(961) : eval()'d code 26 errorHandler->error
/global.php 961 eval
/showthread.php 28 require_once





× This forum is read only. As of July 23, 2019, the UserSpice forums have been closed. To receive support, please join our Discord by clicking here. Thank you!
UserSpice   ›   General   ›   UserSpice 5 - Roadmapping the Future   ›   A Plugin/Module API & Repository

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
A Plugin/Module API & Repository
Brandin
Lead Developer
*******
Joined: Oct 2016
Posts: 1,297

Reputation: 7
#7
11-23-2017, 10:06 PM
I am in agreement with a plugin/api/repository system, but with that, as mudmin suggested, could easily get left behind. This requires a strong level of community-development and support, regular updates and users following updates on an-as released basis, which just doesn't always happen. We're fortunate for those who are extremely active in the community, but we run into vulnerabilities, instability, and compatibility issues when plugins get left behind.
  Website
  Reply


Messages In This Thread
A Plugin/Module API & Repository - by Trioxin - 11-28-2016, 12:23 AM
A Plugin/Module API & Repository - by mudmin - 11-28-2016, 12:52 AM
A Plugin/Module API & Repository - by plb - 01-22-2017, 09:40 AM
A Plugin/Module API & Repository - by mudmin - 01-26-2017, 03:52 AM
A Plugin/Module API & Repository - by mudmin - 11-23-2017, 01:10 PM
A Plugin/Module API & Repository - by Brandin - 11-23-2017, 10:06 PM

Forum Jump:


Users browsing this thread: 3 Guest(s)