• Shame but its too much of a hassle as it is. All the variables ought to be able to be set by the plugin and should only require a single click to set a profile.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author joeguilmette

    (@joeguilmette)

    I’m not sure if you are bemoaning the fact that the settings are stored in the wp-config file or that the plugin isn’t able to automatically read/write its settings to the wp-config file.

    Configuring the settings manually in wp-config.php was a conscious decision. We’ve done this to enable you to migrate your database between different server environments without taking the WP Local Toolbox settings along the way.

    It wouldn’t make any sense to store the server name or anything else in the database. If we did that then every time you deploy your database from A to B you’d need to go into the admin panel and change your settings, which would defeat the whole point of this plugin.

    If you want WP Local Toolbox to read/write settings to the wp-config file, well, that’s a lot of code to write so we can avoid copy/pasting a handful of lines. Pull requests are welcome: https://github.com/joeguilmette/wp-local-toolbox

    Thread Starter Terence Milbourn

    (@pubdirltd)

    Its OK, its just me being lazy.

    Staging is such a finicky thing, requiring too much work more often than not. Which its rarely done in the WordPress ecosystem, and why ~if you do ~ you only seem to find it in closed systems, where it can be highly specific with most if not all of the variables know.

    I just thought this plugin might be able to make it simpler than it does, and having you tell me you deliberately made it that way doesn’t really help me.

    One day, maybe.

    Peace.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Not optimal yet’ is closed to new replies.