I think something is wring with your WordPress installation. plugins_url() function which calls wp_normalize_path() is a built in function and should be available. Please check your WordPress Core files and try to reactive again.
WordPress is fully up to date, and I have reinstalled the most up to date version several times. wp_normalize_path() function exists as its supposed to in link-template.php:
function plugins_url( $path = ”, $plugin = ” ) {
$path = wp_normalize_path( $path );
$plugin = wp_normalize_path( $plugin );
$mu_plugin_dir = wp_normalize_path( WPMU_PLUGIN_DIR );
Hello @fightsmarttrav,
Based on the error message and the steps you’ve already taken, it appears the wp_normalize_path() function is being called before WordPress core is fully loaded, despite you confirming its existence in link-template.php. This is definitely a peculiar issue.
As the root cause can be deeply connected with the specific environment of your website (e.g., plugin conflicts, server configuration, custom code), the best course of action would be to investigate your specific setup directly.
I would highly recommend creating a support ticket through the WPManageNinja Support Portal. When you do, please provide the following information to help our experts diagnose the issue more efficiently:
- Hosting Environment Details: (e.g., shared hosting, VPS, etc.)
- Access Details: Providing temporary access to your WordPress admin area or server (with your consent, of course) can significantly speed up the debugging process. If you are hesitant to provide these details, we will try our best to find the cause through other methods.
Our team can then delve deeper into your configuration and pinpoint the exact cause of this premature function call. We can examine your active plugins, theme, and server environment to identify any potential conflicts or custom code that might be interfering with the WordPress loading sequence.
Thanks for your patience and understanding!
Hey Ibrahim,
Thanks for the reply!
So, I switched from Litespeed server and Litespeed cache to an Nginx server running WP-Rocket and the problem has completely resolved.
No sense in looking any further into it, but thank you again.
