New plugin configuration policy

  • Resolved nicgios

    (@nicgios)


    10 years, 4 months ago

    Hi all,

    I wrote a set of functions and I want to package them as a plugin, but I have a problem.

    Many functions calls a configuration function which stores some general variables (I avoided global variables) defined by user. Is a good way to create a configuration page for the user in order to define such variables? In this case, should the variables be stored in the database directly?

    I’d like the user not to touch a function: better to configure a plugin with a proper page, isn’t it?

    Thanks for your help

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator James Huff

    (@macmanx)

    Is a good way to create a configuration page for the user in order to define such variables? In this case, should the variables be stored in the database directly?

    I’m not a plugin developer myself, but I can say for sure that the answer is “yes” to both questions.

    You should offer a settings page for the user and store the settings in the database. The days of asking users to directly modify plugin files or storing variables in a flat file are long gone (for the most part).

    Thread Starter nicgios

    (@nicgios)

    Hello MacManX,

    thanks for your help. I’m going doing this way.

    Moderator James Huff

    (@macmanx)

    You’re welcome!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘New plugin configuration policy’ is closed to new replies.