Stay in school is the common mantra one hears early in life. Go to school. Make good grades. Get a good job.

It’s very rare to discover someone that drops out of high school at the age of 16 and MIT a few years later, especially a highly studious person.

But if dropping out of school twice doesn’t drop your jaw, then maybe being a Y-Combinator alum as well as receiving a $100,000 Thiel Fellowship grant after successfully founded Nambase.io — the premier domain registrar built on top of the new DNS protocol Handshake — just might grab your attention, a little more.

What is the next “big thing” on the horizon? This often tends to be the never-ending question about many things in life, domains included, decade after decade, year after year.

There are many big moments in and throughout the history of tech, especially when considering domains and their role in the existence of the Internet.

One of the latest topics up for discussion admits a world of civil unrest and #CancelCulture is the birthing and formation of a decentralized internet — the web 3.0.

From the legacy domains in a centralized structure of management to the decentralized management of handshake domains, the Handshake domain ecosystem is steadily growing day after day.

Can legacy and Handshake domains coexist in a new web ecosystem?

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!