Make WordPress Core

Opened 3 years ago

Closed 5 months ago

#54972 closed feature request (wontfix)

Change config variables from Settings

Reported by: fyremoon's profile fyremoon Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Bootstrap/Load Keywords: close
Focuses: administration Cc:

Description

Hi,

WordPress is installed in different ways these days than just FTP the files to the server, so having a non-technical person change the wp-config.php is a recipe for disaster.

A possible solution would be a page in the Settings section that enables the admin to increase or decrease the memory limit, upload limit, etc of their site but not beyond the php.ini limits. If this page wrote to a file such as .wp-settings, then it could be included in the wp-config.php file.

An import/export feature would be useful too, which saves a file like wp-settings.csv that the page could parse and import so it will ignore rogue settings.

Change History (3)

#1 @SergeyBiryukov
3 years ago

  • Component changed from WordPress.org Site to Bootstrap/Load
  • Focuses administration added

#2 @jorbin
5 months ago

  • Keywords close added

WordPress aims to avoid adding options except for those absolutely necessary. This especially includes more technical options. This is outlined in the WordPress Philosophies

Decisions, not options
When making decisions these are the users we consider first. A great example of this consideration is software options. Every time you give a user an option, you are asking them to make a decision. When a user doesn’t care or understand the option this ultimately leads to frustration. As developers we sometimes feel that providing options for everything is a good thing, you can never have too many choices, right? Ultimately these choices end up being technical ones, choices that the average end user has no interest in. It’s our duty as developers to make smart design decisions and avoid putting the weight of technical choices on our end users.

As such, I think this should be closed as wontfix.

#3 @jeremyfelt
5 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed
  • Version 6.0 deleted

Agreed. This seems like a good area for individual hosts to provide controls for so that non-technical site owners don't need to worry about wp-config.php or managing advanced options found there.

Note: See TracTickets for help on using tickets.