Opened 3 years ago
Last modified 3 years ago
#51507 new defect (bug)
Ability to use as a framework
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | |
Component: | Bootstrap/Load | Keywords: | |
Focuses: | Cc: |
Description
WordPress provides more than 600+ framework-like functions (get_option/set_option, transcients, sanitize-functions and more, which are seen in test).
I doubt that there may be other people like our company, where we use WordPress as a backend helper framework, to make use of it's goodies (hundreds of useful functions).
As speed & performance matter, people has asked for this feature many times (i.e. example1 or example2)
It might be some useful to have one additional alternative for "SHORTINIT" constant:
- SHORTINIT_WITHOUT_DB (to return from "wp-settings.php" right before
require_wp_db()
)
# Performance gains #
Per my tests, compared to SHORTINIT
, this approach loads wp-core about 10x faster (avoiding DB calls, etc).
Attaching the patches.
Attachments (1)
Change History (3)
Note: See
TracTickets for help on using
tickets.
To test simply:
However, this above approach requires a dummy
wp-config.php
file to exist. So there might be also need to make a check inwp-config.php
so as whenSHORTINIT_WITHOUT_DB
is set, it should not for checkwp-config
existence..However, in the meanwhile to avoid any check for
wp-config.php
existence, this can be used as an alternative too: