As a newbie, the ‘Error establishing a database connection’ in WordPress can be a big headache for you, especially if it happens on its own without you change anything. If you have recently encountered this error in your WordPress, don’t panic at all. All you need to do is read this article until the end. I will provide you some exceptionally easy options to resolve this error.
But before that let’s see what this error actually is.
The ‘Error establishing a database connection means your site has no longer access to your database and for that reason, your website has gone down. It usually happens when a PHP code is unable to connect to your MySQL database.
There can be many possible scenarios that can cause this error. Some of the common are:
Corrupt Database-Anything which can cause your WP database to become corrupted
The server which hosts your database is down-It generally happens when the server of your hosting company is unable to handle heavy traffic on your website.
Inaccurate Login Credentials of your database- Many people don’t know but the database has separate login credentials (username & password). If for some reason those credentials
You’ve decided to take the leap. You or your client is going to start an online business. You’ve chosen WooCommerce and WordPress to power your store. You’re planning to include a subscriptions component to sell more with less work.
You’ve made some great decisions already, but that doesn’t mean it’s going to be easy!
WooCommerce Subscriptions now powers recurring payments for more than 15,000 stores. Over the last five years, as part of the team developing the software, I’ve learned a lot about subscriptions from a technical perspective and want to share these lessons.
Taking 10 minutes to read this article, then acting on its recommendations could give you a return of weeks and thousands of dollars in savings.
I’m going to focus on three important areas:
Choosing a host
Choosing a payment gateway and extension
Being discerning with code you run on your site
Let’s first look at why this information matters.
The greater responsibility required by open-source subscription software
With WooCommerce Subscriptions, you have almost complete ownership and control over your billing. Recurring payments data is stored and executed from within
Caching can give the impression of being the “holy grail” for all performance problems. It is no wonder that people raise an eyebrow when I say “Stop using caching” in my presentations, meetups or workshops. For some, especially in the WordPress Community I have become the guy that hates caching. Hence, it is time to make clear what I really mean about this topic, when and for what it should be used. And maybe most importantly, when not to use caching – and look for alternative solutions. When should you use Full Page Caching?
Let’s start with the biggest of them all. Full Page Caching, or just page caching. A technique where you temporarily store a pre-generated version of a page to deliver the exact same code (HTML) to visitors in a limited time span. This is how full page caching works:
Visitor A visits abc.com/page. This page is not in the cache, and hits PHP and gets generated from the database. Before it is served to Visitor A, it is also stored in the full page cache with an expiry of 10 minutes.
Visitor B visits abc.com/page 2 minutes after Visitor A, and is therefore served with the same page, but this time directly from the cache. The pages
This topic comes to us from ARC CTRL, and their article on the “Top 5 Business Website Myths, Debunked”. We talk about how WordPress service businesses can better handle the objections they face when trying to sell an assortment of business services. Whether you are trying to sell marketing, WordPress maintenance & support, or even a new WordPress website. Businesses will always have their objections (i.e excuses) to not see it worth their money to invest in, and we talk about how to combat or respond to those criticisms.
A little bit about our guests:
WP Buffs provides WordPress maintenance plans for serious website owners & white-label agency partners. They handle unlimited edits, performance enhancements, daily health maintenance and regular security troubleshooting so you don’t have to. This allows you to make bold decisions when it comes to your website without hesitating due to technical restraints.
With 24/7 support, a mission driven by their customers and an affinity to sponsor WordCamps, WP Buffs wants to be the very best technical support partner for any individual, business or organization with a WordPress website.
Since we talked about
Recently Team Cloudways decided to go to the Facebook WordPress Community to discover their pain points and expectations for WordPress. Since we know that the time of the WordPressers is precious, we decided against taking the traditional route of floating a questionnaire to individual users. Instead, we opted to go to the two Facebook groups and directly connect to the WordPress users. To make things interesting we decided to offer a prize for the most insightful and interesting answers — $100 worth of Cloudways Hosting Credit.
Anatomy of the Contest
We started by shortlisting the most active Facebook Groups for WordPress users. Fortunately, the number of groups was sufficient enough to get some really good answers. In addition, we were hoping that since most of the WordPressers are active on Facebook, they would also like to participate in the contest.
We were pleasantly surprised by the responses of Facebook Group admins. We contacted two groups (FreelancersTools and WordPress.) and they agreed to post questions and in fact, they were very helpful in advising us about the dynamics of their groups.
Here is the question that we asked in FreelancersTools and WordPress.
Looking back at the history of web design is a great reminder of how far we’ve come. When we take a trip down memory lane, we often think of the trends that shaped an era. But it’s also important explore the role various tools have played in helping those trends expand and evolve. WordPress, in particular, has been an important piece of the puzzle in both functionality (which it receives tremendous credit for) and design (which we don’t hear too much about). But to fully get a sense of its impact on design, we need to look back at what content management systems (CMS) were like around the time of the very first WordPress release in 2003.
An Era of Sameness
Yes, there were other open source CMS platforms available before WordPress. Drupal, for example, was initially released in 2000. But one particular system from those days that stands out is PhpNuke. It’s billed as the “first PHP CMS” and was quite popular at the time. These days, it’s in use on a miniscule number of websites.
The software was functional, but was somewhat complicated to design for. Thus, you could often tell which CMS a site was running just by looking at the design. It led