The following warnings occurred:
Warning [2] Undefined array key "threadviews_countguests" - Line: 745 - File: showthread.php PHP 8.1.31 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/showthread.php 745 errorHandler->error_callback
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
/inc/functions_post.php 830 postParser->parse_message
/showthread.php 916 build_postbit
Warning [2] Undefined property: MyLanguage::$thread_modes - Line: 46 - File: showthread.php(1650) : eval()'d code PHP 8.1.31 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/showthread.php(1650) : eval()'d code 46 errorHandler->error_callback
/showthread.php 1650 eval




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Best place to define plugins' constants?
#1
Some plugins allow inserting constant definitions (define('WHATEVER','something');) to set custom values, usually near the beginning of the plugin file.

IMO the problem with this is, if the developer releases a new version, you have to remember to edit those lines in the new file before updating.

A simple alternative could be telling the user to insert those definitions in the root gsconfig.php

Another could be that e.g. MyPlugin did what GetSimple does: check if a myplugin/mypluginconfig.php file exists, if not it renames the (bundled) myplugin/temp.mypluginconfig.php. However I don't like this for small plugins...

What do you think about this? Other ideas?
Reply


Messages In This Thread
Best place to define plugins' constants? - by Carlos - 2011-07-15, 00:42:40



Users browsing this thread: 1 Guest(s)