Opened 15 years ago
Closed 15 years ago
#11762 closed enhancement (fixed)
inconsistent function name conventions in newly introduced files
Reported by: | Denis-de-Bernardy | Owned by: | |
---|---|---|---|
Milestone: | 3.0 | Priority: | normal |
Severity: | normal | Version: | 3.0 |
Component: | Multisite | Keywords: | needs-patch |
Focuses: | Cc: |
Description
newly introduced MS files have at least one function, whose name (wpmu_checkAvailableSpace) is inconsistent with the typical conventions used in WP.
For the sake of improving the code's quality, we should rename/deprecate them accordingly.
Change History (6)
#2
@
15 years ago
- Keywords needs-patch added
For that one we could get rid of that function entirely and put the code directly in media_upload_form() (rboren's suggestion) or rename the function.
There are also duplicate functions in the multisite code that perform similar but not exactly the same as the wp_ ones. Example: wpmu_create_user, wp_create_user. We would look at a patch to deprecate those as well.
#4
@
15 years ago
We should give priority to eliminating functions that duplicate core WP API and fixing CamelCase intrusions. wpmu_* cleanup that doesn't meet those two criteria should be lower priority.
Perhaps related, we need to decide how to handle everything with "wpmu" in it (a lot of stuff: filters, functions, variables, etc.). Deprecate? Continue to use?