cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Go to solution

Updating to 5.0.3 fatal error

Hello,

 

How did you solve this Fatal error: Call to undefined function determine_locale() in /home/content/75/5267675/html/studentscholarshipgrant/wp-includes/class-wp-locale-switcher.php on line 48

1 ACCEPTED SOLUTION
Super User II

Hey there @ShirleyPH

 

That looks like there was a conflict update with the coding. This sometimes happens when updating due to packet loss on the internet connection. Basically, not all the updated code makes it and then you see an error like this. 

 

Since this seems to be a core WordPress file, one of the easiest things you can do is try a WordPress core file replacement. Before you do anything, however, make sure you have a backup!

 

Replacing WordPress core files can resolve many issues with your WordPress site, from a compromised site, wp-admin is not accessible, even the infamous WSOD (White Screen of Death). This task can seem difficult but once it is clear what is what when looking at the files, the task becomes very straight forward. So let’s take a look at a standard WordPress site from the web root.

 

 

From this view we can see all the core files, the database connection file and the wp-content folder, which is where all of user content lives. (Themes, plugins, images, etc.)

 

PRO TIP! It is always a good idea to disable plugins before removing the old core files.

 

When replacing core files we want to remove all of the core files keeping only the wp-content folder and the database connection file. (wp-config.php) Let’s see how that stacks up.

 

 

Once we deleted all of the core files, we want the newest version of WordPress which can be found here, Latest WordPress, Upload the downloaded file to your web root and extract it. Now we should have something like,

 

 

Inside of the WordPress folder is all of your new core files that have to be moved in place. Move all of the files EXCEPT the wp-content folder to the web root and finally, delete the wordpress folder and it’s contents. Once complete, log into the admin panel and reset permalinks to regenerate your htaccess file.

 

PRO TIP: Replacing the wp-config.php file is a good idea if the site was compromised. Doing so is as easy as copying the database connection strings into the supplied wp-config-sample.php and renaming it to wp-config.php.

 

That’s it! You should now have a functioning site if all went well. Time to turn plugins back on and check your links. If none of this works, I would contact GoDaddy about their WP Premium Support service or look at hiring a developer.



I am a GoDaddy End User - Just Like You
* Please note that I DO NOT answer private messages. Please ask your question in the proper forum so the answer can assist EVERYONE in the community and not just you. If you contact me via PM for help, I will give you a price quote for my personal services. Thanks! *

Once your issue is resolved,
please be sure to come back and click accept for the solution

Get Better Support on the Community Boards!
Etiquette When Asking for Help from the Community


View solution in original post

1 REPLY 1
Super User II

Hey there @ShirleyPH

 

That looks like there was a conflict update with the coding. This sometimes happens when updating due to packet loss on the internet connection. Basically, not all the updated code makes it and then you see an error like this. 

 

Since this seems to be a core WordPress file, one of the easiest things you can do is try a WordPress core file replacement. Before you do anything, however, make sure you have a backup!

 

Replacing WordPress core files can resolve many issues with your WordPress site, from a compromised site, wp-admin is not accessible, even the infamous WSOD (White Screen of Death). This task can seem difficult but once it is clear what is what when looking at the files, the task becomes very straight forward. So let’s take a look at a standard WordPress site from the web root.

 

 

From this view we can see all the core files, the database connection file and the wp-content folder, which is where all of user content lives. (Themes, plugins, images, etc.)

 

PRO TIP! It is always a good idea to disable plugins before removing the old core files.

 

When replacing core files we want to remove all of the core files keeping only the wp-content folder and the database connection file. (wp-config.php) Let’s see how that stacks up.

 

 

Once we deleted all of the core files, we want the newest version of WordPress which can be found here, Latest WordPress, Upload the downloaded file to your web root and extract it. Now we should have something like,

 

 

Inside of the WordPress folder is all of your new core files that have to be moved in place. Move all of the files EXCEPT the wp-content folder to the web root and finally, delete the wordpress folder and it’s contents. Once complete, log into the admin panel and reset permalinks to regenerate your htaccess file.

 

PRO TIP: Replacing the wp-config.php file is a good idea if the site was compromised. Doing so is as easy as copying the database connection strings into the supplied wp-config-sample.php and renaming it to wp-config.php.

 

That’s it! You should now have a functioning site if all went well. Time to turn plugins back on and check your links. If none of this works, I would contact GoDaddy about their WP Premium Support service or look at hiring a developer.



I am a GoDaddy End User - Just Like You
* Please note that I DO NOT answer private messages. Please ask your question in the proper forum so the answer can assist EVERYONE in the community and not just you. If you contact me via PM for help, I will give you a price quote for my personal services. Thanks! *

Once your issue is resolved,
please be sure to come back and click accept for the solution

Get Better Support on the Community Boards!
Etiquette When Asking for Help from the Community


View solution in original post