Manoj Chacko
asked on
PHP Fatal error: Uncaught Error: Call to undefined function wp_normalize_path()
Trying to resolve certain wordpress php errors after upgrade.
PHP Fatal error: Uncaught Error: Call to undefined function wp_normalize_path() in (...)\wp-includes\plugin.p hp:654
Stack trace:
#0 (...)\wp-includes\plugin.p hp(755): plugin_basename('(...)\\wp ...')
#1 (...)\wp-content\plugins\b bpress-gen esis-exten d\init.php (44): register_activation_hook(' (...)\\wp. ..', Array)
#2 (...)\wp-content\plugins\b bpress-gen esis-exten d\init.php (89): bbpge_init->__construct()
#3 (...)\wp-settings.php(84): include('(...)\\wp...')
#4 (...)\wp-config.php(205): require_once('(...)\\wp... ')
#5 (...)\wp-load.php(37): require_once('(...)\\wp... ')
#6 (...)\wp-blog-header.php(1 3): require_once('(...)\\wp... ')
#7 (...)\index.php(17): require((...)\\wp...')
PHP Fatal error: Uncaught Error: Call to undefined function wp_normalize_path() in (...)\wp-includes\plugin.p
Stack trace:
#0 (...)\wp-includes\plugin.p
#1 (...)\wp-content\plugins\b
#2 (...)\wp-content\plugins\b
#3 (...)\wp-settings.php(84):
#4 (...)\wp-config.php(205): require_once('(...)\\wp...
#5 (...)\wp-load.php(37): require_once('(...)\\wp...
#6 (...)\wp-blog-header.php(1
#7 (...)\index.php(17): require((...)\\wp...')
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
the get header was on this line
PHP Fatal error: Uncaught Error: Call to undefined function get_header() in (...)\wp-includes\theme-co mpat\embed .php:13
Stack trace:
#0 {main}
thrown in (...)\wp-includes\theme-co mpat\embed .php on line 13
PHP Fatal error: Uncaught Error: Call to undefined function get_header() in (...)\wp-includes\theme-co
Stack trace:
#0 {main}
thrown in (...)\wp-includes\theme-co
ASKER
This is another Error I get a lot
All-in-One Event Calendar: ob_get_clean(): failed to delete buffer of zlib output compression (1) @ (...)\wp-content\plugins\a ll-in-one- event-cale ndar\lib\g lobal-func tions.php: 38 #8
All-in-One Event Calendar: ob_get_clean(): failed to discard buffer of zlib output compression (1) @ (...)\wp-content\plugins\a ll-in-one- event-cale ndar\lib\g lobal-func tions.php: 38 #8
All-in-One Event Calendar: ob_get_clean(): failed to delete buffer of zlib output compression (1) @ (...)\wp-content\plugins\a
All-in-One Event Calendar: ob_get_clean(): failed to discard buffer of zlib output compression (1) @ (...)\wp-content\plugins\a
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
My first 2 comments address the issue. Unless anyone else objects, I'll auto-close this with those comments as the accepted answers.
@David - Memory errors don't cascade into other problems. If a memory limit is reached it stops the script in its tracks. I'd suggest never recommending an increase in PHP memory limits until it's been well-established that there is no memory leak. Increasing the memory limits to fix an out-of-memory issue when the process is already taking up 1 gigabyte of memory is usually not a good idea. In fact, a 1 gigabyte memory limit is pretty outrageous for a WP site, since it dramatically decreases the number of possible concurrent visitors AND is pretty slow (it takes a while to load up 1 gigabyte of data, even in memory).
NOTE: I just noticed the OP asked follow-up questions about another plugin, which really should have been covered by my earlier comments about plugins, but since I wasn't specific about it, I'd suggest that your comment be included in the solution.
@David - Memory errors don't cascade into other problems. If a memory limit is reached it stops the script in its tracks. I'd suggest never recommending an increase in PHP memory limits until it's been well-established that there is no memory leak. Increasing the memory limits to fix an out-of-memory issue when the process is already taking up 1 gigabyte of memory is usually not a good idea. In fact, a 1 gigabyte memory limit is pretty outrageous for a WP site, since it dramatically decreases the number of possible concurrent visitors AND is pretty slow (it takes a while to load up 1 gigabyte of data, even in memory).
NOTE: I just noticed the OP asked follow-up questions about another plugin, which really should have been covered by my earlier comments about plugins, but since I wasn't specific about it, I'd suggest that your comment be included in the solution.
ASKER
PHP Fatal error: Uncaught Error: Call to undefined function get_header()
and
PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 262144 bytes) in (...)\wp-includes\class-wp
[22-May-2018 16:30:28 UTC] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 262144 bytes) in (...)\wp-includes\load.php