I recently migrated a customer’s WordPress website from Bluehost to RoseHosting.

It was a good 6 year run with Bluehost, but this specific customer finally outgrew Bluehost web hosting services.

In actuality, Bluehost kept their website running on PHP 5.6 instead of upgrading to 7.x. But that’s a different story for another day.

The party was good until cart-fragments.min.js shut it down

My WordPress struggles with this given client’s website occurred after updating WooCommerce and updating to WordPress. After the latter update, the pages loaded but key elements driven by JavaScript were nowhere to be found.  But where, oh where could they be?

2020 has certainly been a year of digital transformation and digital empowerment. In fact, the global economy has realized four years of growth in 10 months since COVID forever changed how we live and do business.

COVID is a lingering health nightmare that we all wish would end. Yet, COVID has forced brands of all types and sizes, including consumers, suppliers/vendors, etc., to embrace a progressively digital global economy.

Oh, the sheer panic of loading your WordPress website to discover that your website has encountered a fatal error.

Sometimes it’s the white screen of death without errors. Other times it’s the white screen of death with a message about a fatal error email sent to your site administrator.

In my most recent case, it was the latter. While it’s good on one hand to know a fatal error has occurred, such messaging is utterly useless if you’re not the administrator of the website. And this is the case of today’s tutorial.

Let me guess, you have a website that won’t perform ajax calls the add media button has stopped working, or woo commerce won’t go one action further on any front, right?

If not those three gnarly, yet common WordPress challenges, then maybe your web developer console is running amok with endless “uncaught type error” errors across multiple javascript files.

Nevertheless, hang around WordPress long enough, and the probability of themes, plugins, and/or core WordPress updates conflicting with one another will happen. Most theme and plugins don’t encounter technical challenges when updating unlike core WordPress updates. However, WordPress websites often perform extremely well as long as themes, plugins, and core updates are well maintained on a consistent basis.

Long before there were auto enabled updates across all three platforms, I made a decent living — still do to some extent — logging into clients environments and updating necessary themes, plugins, and core updates.

I’ve had my share of WordPress core updates that have halted any and all web activity, including the administrative dashboard — the latest experience was the WordPress 5.X update (nightmare). WordPress 5.5, jQuery Migrate 1.X was a planned stage removal in regards to updating WordPress’ overall jQuery version — virtually broke ever plugin and theme known to man, including the very popular Classic WordPress Editor and Yoast plugins.

Welcome back to KickstartCommerce.com! Well, you’ve finally arrived on this website in hopes of understanding and finding a solution to the pesky Divi or MotoPress ‘ET_Core_Cache_Directory’ not found error for the WordPress Emmet theme.

It took me the better half of a day to sort through this error code gibberish and remedy it. The good news is that the fix won’t require you to write code or perform some sort of risky workaround.

However, the bad news is that you’ll need to be familiar with using an FTP client — Filezilla recommended. Let’s dive in and help get you on your way!

Welcome back to KickstartCommerce.com! As with much of life, especially when it’s concerning WordPress, errors seem to appear in threes or bunches at a time.

Last week, it was a jQuery conflict error, and this week Bluehost forced the same customer’s hand by auto upgrading their website from PHP 5.2 directly to PHP 7.

Truth be told, the customer was forewarned a few times about how PHP 5.X was outdated and full of security issues that would no longer be supported in favor of having the customer migrated to PHP 6 or PHP 7.

As glitchy as WordPress is when doing simple tasks such as a theme or plugin update, I knew it was nothing but trouble to have upgraded from PHP 5 directly to PHP 7.😳

Welcome to KickstartCommerce.com! Let me guess, your website is not allowing you to update WooCommerce Product Attributes, right?

Or, if not WooCommerce, then maybe you’re encountering all sorts of javascript errors with a site that is severely hobbled in functionality if not completely dead in the water and not functioning at all.

Whether you have plugins beefing with plugins or themes beefing with plugins, I aim to help you rehabilitate your WordPress website back in order, functioning and in tip-top shape.