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 the 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 in today’s tutorial.

Welcome to today’s tutorial where I reveal how to retrieve engagement activity using cURL, PHP, and Facebook’s Graph API version 8.

You may or may not recall the version JS, version 2, and version 3 tutorials I produced a few years ago. Since this time, I’ve been quite busy with a myriad of other projects, and completely missed 4, 5, 6, and 7 version updates to the Facebook Graph API.

Nonetheless, I aim to help you obtain your access token and Facebook engagement activity using the latest Graph API v8. Let’s get started!

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, your web developer console may be 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. Unlike core WordPress updates, most themes and plugins don’t encounter technical challenges when updating. 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 update (nightmare). WordPress, jQuery Migrate 1.X was a planned stage removal regarding updating WordPress’s overall jQuery version — virtually broke every plugin and theme known to man, including the very popular Classic WordPress Editor and Yoast plugins.

Hi there! Today’s tutorial is quick and, hopefully, easy. If you’ve ever had a web project requiring when the sun rises or sets, then today’s tutorial is just what the programming doctor ordered. Let’s get started!

Here’s a look at the top 5 podcasts for Kickstart Commerce in September, ranked by number of downloads:

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.

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 a more current version of PHP.

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.😳