Fixing 404 Not Found Error on Divi Booster Files

Written by Dan Mossop

An issue I see crop up from time to time is that Divi Booster's settings aren't being applied due to 404 Not Found errors.

Normally, Divi Booster loads the following files to add the CSS / JavaScript code it generates to the site:

/wp-content/uploads/wtfdivi/wp_head.css
/wp-content/uploads/wtfdivi/wp_footer.js

If it can't find these files then it won't be able to make changes on the page.

Fixing the WordPress UPLOAD_PATH Setting

The most common reason I've seen for 404 errors on the Divi Booster files is that the WordPress "upload_path" setting is wrong. This setting tell WordPress (and Divi Booster) where the "uploads" folder is, and Divi Booster uses it to determine where to write its files to the server.

Normally, this setting is blank and WordPress uses a default value (i.e. the usual /uploads folder). However, sometimes the uploads_path setting will have been explicitly set on the server. This is fine if upload_path is actually set to the /uploads folder, or if the corresponding "upload_url_path" setting is set to allow WordPress (and Divi Booster) to determine the URLs for the files in a non-standard upload folder. But if the upload_path and upload_url_path do not point to the same place on the server, then Divi Booster will write its files in one place and attempt (and fail) to read them from another place. Hence the 404 Not Found errors.

In particular, I've seen this happen when migrating a site. If the main site has the upload_path explicitly set to the standard /uploads location, and the upload_url_path is left empty, then the main site will work correctly since both values refer to the same default location. But if the site is copied to another location and the values aren't updated, this can cause a problem. Now the upload_path still points to the uploads folder on the main site, while the upload_url_path points to the uploads folder on the new site. As a result Divi Booster will be trying to write to a different location that it tries to read from.

The solution is to correct the upload_path and upload_url_path on the site (the copied site, if you're having the problem after migrating). These values can be edited by going to /wp-admin/options.php on the site (manually type this in, adding your site URL to the start), and scrolling down until you locate fields for these two settings.

Unless you are actually using a non-standard uploads folder location, then simply deleting the contents of these two settings should restore WordPress to the correct default behavior. Here's how it should look:

Scroll to the end of the page and save the updated upload_path value, then head over to the Divi Booster settings page and re-save your Divi Booster settings. This will write the Divi Booster files to what should now be the correct uploads folder location. Now when you view the site, Divi Booster should be able to load its files and apply your configured changes.

Fix 404 Errors with Divi Booster — Get Divi Booster Now!

Ensure your Divi Booster is functioning perfectly by resolving 404 Not Found errors on your site's settings. This post guides you on adjusting the WordPress UPLOAD_PATH to ensure Divi Booster files load correctly, thereby applying all your customizations seamlessly. Keep your site running smoothly and effectively with the latest features.

About Dan Mossop

Dan is a Scottish-born web developer, now living in Brisbane with his wife and son. He has been sharing tips and helping users with Divi since 2014. He created Divi Booster, the first Divi plugin, and continues to develop it along with 20+ other Divi plugins. Dan has a PhD in Computer Science, a background in web security and likes a lot of stuff, 

0 Comments

Submit a Comment

Comments are manually moderated and approved at the time they are answered. A preview is shown while pending but may disappear if your are cookies cleared - don't worry though, the comment is still in the queue.

Your email address will not be published. Required fields are marked *.

We may earn a commission when you visit links on our website.