The following warnings occurred:
Warning [2] Undefined array key "allowautourl" - Line: 584 - File: inc/class_parser.php PHP 8.1.31 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/class_parser.php 584 errorHandler->error_callback
/inc/class_parser.php 228 postParser->parse_mycode
/printthread.php 203 postParser->parse_message
Warning [2] Undefined array key "allowautourl" - Line: 584 - File: inc/class_parser.php PHP 8.1.31 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/class_parser.php 584 errorHandler->error_callback
/inc/class_parser.php 228 postParser->parse_mycode
/printthread.php 203 postParser->parse_message



GetSimple Support Forum
PROBLEM Maintaining old/ outdated, but useful plugins - Printable Version

+- GetSimple Support Forum (http://get-simple.info/forums)
+-- Forum: GetSimple (http://get-simple.info/forums/forumdisplay.php?fid=3)
+--- Forum: Feature Requests (http://get-simple.info/forums/forumdisplay.php?fid=7)
+--- Thread: PROBLEM Maintaining old/ outdated, but useful plugins (/showthread.php?tid=9516)



Maintaining old/ outdated, but useful plugins - Tyblitz - 2017-02-21

Currently the Extend repository is home to maybe 40% of plugins that haven't been updated in 4+ years.
Some of these plugins still provide interesting features, but can use some polishing/ updates.
Think about .htacces file updates, UI enhancements, or feature additions.

How should we go about this? The Extend repository does not allow to 'transfer' ownership of a plugin/ allow collaborators to access the plugin's management interface. And I don't feel comfortable spamming the Extend repo with minor forks, ripping the original author of his/ her credentials.


RE: Maintaining old/ outdated, but useful plugins - shawn_a - 2017-02-24

Yeah I would provide patches via forums or gist.
Either way its a gray area.