Opened 13 years ago
Closed 13 years ago
#19552 closed enhancement (fixed)
Split functions.php
Reported by: | ryan | Owned by: | |
---|---|---|---|
Milestone: | 3.4 | Priority: | normal |
Severity: | normal | Version: | 3.3 |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
It's big, too big. Options/settings/transients, for example, could move to a new file. To maintain back-compat for those including functions.php separately, new files should be required from functions.php rather than wp-settings.php.
Attachments (2)
Change History (14)
#2
@
13 years ago
19552.diff moves setting/option/transient functions to option.php. It does an svn copy to preserve history. The functions are left in the same order as they currently are in functions.php to make the diff more readable. They can be reorganized in a follow-up commit.
#3
@
13 years ago
General patterns I'm seeing:
- option functions, including *_option, *_transient, *_site_option, *_site_transient, other option functions, and potentially the *_user_setting(s) functions.
- date/time/timezone functions
- remote functions, including do_enclose(), xmlrpc_*, debug_f*, wp_get_http*.
- security-related functions, including nonces, referers, wp_die(), SSL functions, frames, protocols, magic quotes
- upload-functions, including filetype/mime/ext
- lots of utility functions
- internal debug functions — _deprecated*, _doing_it_wrong
- boot functions including _config_wp_home|siteurl, wp_maybe_load_widgets/wp_widgets_add_menu, dead_db, is_blog_installed.
Note: See
TracTickets for help on using
tickets.
List of functions in functions.php: