Categories
WordPress WP Engine

How to Access phpMyAdmin at WP Engine

Last updated: October 12, 2026

Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.

If you’ve worked on WordPress for a while, you know phpMyAdmin. Sooner or later you need to look directly at the database to fix a broken option, find a bad serialized value, or check what a plugin left behind. Some hosts hide phpMyAdmin or put it behind an extra password nobody remembers. At WP Engine it’s one click.

How to open phpMyAdmin

  1. Log in to the User Portal at my.wpengine.com.
  2. Open Sites and click the environment you want (production, staging, or development).
  3. Click the phpMyAdmin button at the top of the environment’s overview page.

phpMyAdmin opens in a new tab, already logged in to that environment’s database. Each environment has its own database, so make sure you picked the right one before you change anything.

WPEngine PHPMyAdmin
phpMyAdmin in an older version of the WP Engine User Portal. It now lives in the environment’s header.

Back up first. Every time.

Direct database edits skip all of WordPress’s safety checks, and there’s no undo. Before you touch anything, click Backup at the top of the same environment page and wait for it to finish. Better yet, make the change on staging first.

When to use WP-CLI instead

For a lot of jobs, WP-CLI over SSH is safer than phpMyAdmin:

  • wp db export to take a quick SQL dump.
  • wp search-replace to change URLs. Unlike a raw SQL find and replace, it handles serialized data correctly.
  • wp option get and wp option update to read or fix a single setting.

I still use phpMyAdmin to browse tables and run quick read-only queries. For changes, I reach for WP-CLI.

Shopping for a host? Every WP Engine plan includes phpMyAdmin access, daily backups, and staging.

FAQ

How do I access phpMyAdmin on WP Engine?

Log in to the User Portal, open the environment from the Sites page, and click the phpMyAdmin button at the top of the overview page.

Can I use phpMyAdmin on WP Engine staging?

Yes. Each environment has its own database and its own phpMyAdmin button. Open the staging environment and use the button there.

Should I back up before editing the database in phpMyAdmin?

Yes. Create a backup from the environment page first. phpMyAdmin changes take effect immediately and can’t be undone.

Related

Categories
WordPress

How to Choose a WordPress Plugin: My 15-Point Checklist (2026 Update)

Last updated: October 17, 2026

Disclosure: some links in this post are affiliate links, marked as sponsored. If you buy through them I may earn a commission at no extra cost to you. I only recommend hosts I have used on real client sites.

Plugins are the fastest way to add features to WordPress, and the fastest way to slow it down, break it, or get it hacked. I build WordPress sites for small business clients with real budgets and average tech skills, so plugin choice matters for years after launch.

I first wrote this checklist in 2017. The core questions held up. What changed is how much security history matters, and how much your host can help.

The core questions

1. Do you really need this feature?

This is still the most important question. If the client won’t use it, or the site works fine without it, it is “extra.” Extras get installed last, and only if there is a well-built option.

2. Is the plugin popular?

The WordPress.org plugin directory shows “Active installations” on every listing. A popular plugin is popular for a reason. It also has a big user base finding bugs across thousands of setups before you do.

Plugin directory listing showing active installs and rating
Active installs, rating, and review count on a plugin listing (2017 screenshot).

3. Is it well maintained?

Popular is not enough. I open the Support tab on WordPress.org and look at how many threads are marked resolved, and how quickly the author replies.

Resolved support thread label on WordPress.org
You want to see lots of these on a plugin’s Support tab.

4. When was it last updated?

A plugin that hasn’t been updated in a year or more should be avoided, or used with great caution. WordPress.org now shows a warning when a plugin hasn’t been tested with the latest three major releases. Treat that warning as a red flag on anything important.

Last updated date on a plugin listing
The “Last updated” line on a plugin listing (2017 screenshot).

5. Who made it?

The person or team behind a plugin is who you depend on for updates, fixes, and support. A company with a paid product and a support team is a safer bet than an abandoned side project.

6. Does it have a clean security record?

This one is new to the list, and it is now near the top for me. Search the plugin name in a vulnerability database like WPScan, Patchstack, or Wordfence Intelligence. One fixed vulnerability is normal. A long pattern of them, or slow fixes, is not.

7. Does it support your PHP version?

The listing shows “Requires PHP.” If your site is still on an old PHP version, update that first. I explain how in changing your PHP version on WP Engine and Pressable.

8. Can you see it before you install it?

Screenshots, a demo, or a video save a lot of time. Often I install a plugin, try to set it up, and get turned off by the interface. Previews help you skip that.

9. Is there a paid version?

A paid tier or license is a good sign the authors will stick around. The price is often low enough that paying just for priority support makes sense.

10. How heavy is it?

Everyone loves a lean plugin, but feature creep is real. A plugin that does one thing very well beats one that does twenty things you don’t need.

11. Do the reviews hold up?

I don’t read individual reviews, but the star rating is useful when the review count is high. Reviews are easy to game one at a time. In aggregate they still say something.

Star rating breakdown on a plugin listing
Rating breakdown on a plugin listing (2017 screenshot).

Questions people skip

12. Is there an Automattic option?

Automattic, the company behind WordPress.com, makes a set of plugins (Jetpack is the big one) that may already cover what you need. See their author page in the directory.

13. Could a third-party service do it instead?

Video is the classic example. You can self-host video and add a player plugin, or you can upload to YouTube for free and embed it. No plugin, no extra maintenance, and your video can be found on YouTube.

14. Can your theme do it?

Some plugin features can be rebuilt with the block editor, a block pattern, or a little custom code in a child theme. Don’t cram PHP into functions.php without thinking it through, but don’t install a plugin for one button either. The theme handbook is the place to start.

15. Does your host allow it?

Managed hosts block some plugins that duplicate their own features or cause performance problems, like caching and backup plugins. WP Engine publishes a disallowed plugins list. Check before you build a feature around one.

Keeping plugins updated after launch

Choosing well is half the job. The other half is updating. Turn on auto-updates for plugins you trust, and test bigger updates on a staging site first. If you’d rather not babysit updates, WP Engine’s Smart Plugin Manager runs them for you and rolls back if a visual check fails. On Pressable, staging is included on every plan, and I show how to use it in Pressable staging sites.

Tired of plugin updates breaking things? WP Engine’s Smart Plugin Manager updates plugins on a schedule and rolls back automatically when something looks wrong.

FAQ

How many plugins is too many for WordPress?

There is no magic number. Ten badly built plugins can do more damage than forty well built ones. Remove anything you don’t use and watch for plugins that load scripts on every page.

How can I tell if a WordPress plugin is safe?

Check that it was updated recently, has many active installs, has resolved support threads, and has no pattern of unpatched issues in a vulnerability database like WPScan or Patchstack.

Should I use a plugin that hasn’t been updated in a year?

Avoid it for anything important. WordPress.org shows a warning when a plugin hasn’t been tested with the last three major WordPress releases.

Are premium plugins better than free ones?

Not automatically, but a paid version usually means the developers have a reason to keep updating and supporting it.

Why won’t my managed host let me install a plugin?

Hosts like WP Engine block plugins that duplicate built-in features, like caching and backups, or that cause performance or security problems. Check the host’s disallowed plugins list.

Related posts

Categories
Analytics WordPress

Should You Use a Google Analytics Plugin for WordPress? (Updated for GA4)

Last updated: October 15, 2026

I often find WordPress sites cluttered with unused, outdated, and abandoned plugins. When I clean one up, I start with plugins that do simple jobs you can easily do another way. Google Analytics plugins are a classic example.

I first wrote this in 2014. A lot has changed since then, so here’s the updated version.

What changed: GA4

Google’s old Universal Analytics stopped processing data on July 1, 2023. Every site now uses Google Analytics 4. If your site still has an old UA tracking code (it starts with UA-), it isn’t collecting anything. Your GA4 Measurement ID starts with G-.

Option 1: Add the code yourself

GA4 gives you a short gtag.js snippet to paste into the <head> of every page. Put it in a child theme’s header, or use a small code snippets plugin so it survives theme updates.

  • Pros: no extra plugin overhead, nothing to update, and no authentication to break.
  • Cons: awkward for non-technical users, and extras like excluding logged-in users have to be coded by hand.

Option 2: Use a plugin

  • Pros: easy setup, reports inside WP Admin, and extras like outbound link tracking and excluding logged-in users.
  • Cons: some overhead, another thing to keep updated, and occasional authentication headaches. Back in 2014 I had to re-connect Yoast’s GA plugin repeatedly; manual code never needs that.

Which plugins?

The plugins I mentioned in 2014 have all changed hands or names:

  • Google Analytics by Yoast is now MonsterInsights.
  • Google Analytics Dashboard for WP is now ExactMetrics.
  • Google’s own Site Kit plugin connects GA4, Search Console, and PageSpeed Insights, and it’s free.

My recommendation

  • If you only need the tracking code, add it manually or use Site Kit.
  • If you want reports in WP Admin and will actually use features like outbound link tracking, a plugin is fine. Pick one that’s actively maintained.
  • Either way, check whether you need a cookie consent banner. In the EU and UK you usually do.

GA plugins are lightweight enough that you can run one without much fear. Just don’t install one out of habit if you’ll never look at the extra data.

FAQ

Do I need a plugin for Google Analytics on WordPress?

No. You can paste the GA4 gtag.js snippet into your theme’s head. A plugin adds convenience and extra reports.

What is the best Google Analytics plugin for WordPress?

Site Kit by Google is free and official. MonsterInsights and ExactMetrics add more reporting inside WP Admin.

Does Universal Analytics still work?

No. Universal Analytics stopped processing data on July 1, 2023. Use Google Analytics 4.

Categories
Security WordPress

WordPress Security Best Practices: My 2012 List, Updated for 2026

Last updated: October 17, 2026

Disclosure: some links in this post are affiliate links, marked as sponsored. If you buy through them I may earn a commission at no extra cost to you. I only recommend hosts I have used on real client sites.

I wrote the first version of this post in 2012 as a follow-up to my almost perfect .htaccess file article. Some of that advice aged well. Some of it (Flash galleries, anyone?) did not. This is the updated list, based on what I actually do on client sites today.

The short version: most hacked WordPress sites I clean up were not hit by anything clever. They had an outdated plugin, a reused password, or no backups. Fix those three and you are ahead of most of the web.

The 2026 checklist

  1. Keep WordPress, plugins, and themes updated. Minor core releases update automatically. Turn on auto-updates for plugins you trust from the Plugins screen.
  2. Delete what you don’t use. Inactive plugins and themes can still be exploited. If it is not active, remove it.
  3. Use strong, unique passwords and a password manager. Every account, not just yours.
  4. Turn on two-factor authentication for every administrator. A plugin like Two Factor or the 2FA in your security plugin handles this.
  5. Give people the lowest role they need. Your content writer does not need to be an Administrator.
  6. Keep backups off the server. A backup stored on the same server as the site is not much of a backup. Test a restore at least once.
  7. Use HTTPS everywhere. Certificates are free now. There is no reason to send a login over plain HTTP.
  8. Use SFTP or SSH, never plain FTP. Plain FTP sends your password in clear text.
  9. Turn off the built-in file editor so a stolen admin login can’t be used to edit PHP from the dashboard.
  10. Put a firewall in front of the site. Cloudflare, a security plugin, or your host’s own edge protection all count.

My original 2012 tips, revisited

2012 tip2026 verdict
Change the wp_ table prefixLow value. Fine on a new install, not worth the risk of changing on a live site.
Remove the “admin” usernameStill good. The installer has asked you to pick a username for years now.
Restrict wp-admin by IP in .htaccessWorks on Apache, but most people’s IPs change too often. 2FA is the better fix.
Remove unused themes and pluginsStill one of the best things you can do.
Password protect /wp-admin/Optional extra layer. It can break admin-ajax requests, so test it.
Lock down file permissionsStill valid. 644 for files and 755 for folders is the usual baseline.
Hide the WordPress versionLow value. Attackers scan for vulnerable plugins, not version numbers.
Turn off debug output on live sitesStill important. Never leave WP_DEBUG_DISPLAY on in production.
Strong passwordsStill essential. Add 2FA on top.
Monitor or disable user registrationStill valid. Only allow it if you need it.
Secure FTPStill valid. Use SFTP or SSH keys.
Admin over SSLNow the default. Run the whole site on HTTPS.
Protect wp-config.phpStill valid on Apache. Managed hosts usually block it for you.

A few settings worth adding to wp-config.php

These go above the line that says “That’s all, stop editing!”

// Turn off the theme and plugin file editor in WP Admin
define( 'DISALLOW_FILE_EDIT', true );

// Never show PHP errors to visitors
define( 'WP_DEBUG', false );
define( 'WP_DEBUG_DISPLAY', false );

If you use the REST API or connect apps to your site, use Application Passwords (Users > Profile) instead of sharing your real password. You can revoke one without touching your login.

XML-RPC: block it unless you need it

xmlrpc.php is a favorite target for password guessing. If you don’t use the WordPress mobile app or a service that depends on it, block it. My .htaccess guide has the Apache rule. Jetpack does use XML-RPC, so test after blocking it if you run Jetpack.

What your host should handle for you

This is the biggest change since 2012. A good managed WordPress host now does a lot of this list for you, which is a big part of why I moved client sites off cheap shared hosting.

  • Pressable includes Jetpack Security on every plan, plus daily backups. I walk through restores in my Pressable backups post.
  • WP Engine blocks a lot of bad traffic at the platform level and offers Global Edge Security as an add-on. It also runs automatic backups, which I cover in WP Engine backups.

Both hosts give you SFTP and SSH access instead of plain FTP. On WP Engine, see my guides to SFTP and SSH keys. Plugin updates are where most of the risk lives, and WP Engine’s Smart Plugin Manager can update them for you and roll back if something breaks.

Older PHP versions stop getting security fixes, too. If your site is still on PHP 7.x, read how to change your PHP version before anything else.

Want security handled at the host level? Every Pressable plan includes Jetpack Security, daily backups, and a 30-day money-back guarantee.

Other things to worry about

  • Plugins. Even up-to-date plugins can carry risk. Keep the count low and read my checklist for choosing a WordPress plugin.
  • Your own computer. A compromised laptop leaks saved passwords and SFTP logins. Keep it updated and scanned.
  • Other admins. One person with a weak password undoes everything else on this list.

FAQ

What is the most important WordPress security step?

Keeping WordPress core, plugins, and themes updated. Outdated plugins are the most common way WordPress sites get hacked.

Do I need a WordPress security plugin?

Not always. On a managed host with a firewall, malware scanning, and backups, a heavy security plugin often duplicates what the host already does. On basic shared hosting, a security plugin is worth adding.

Should I change the WordPress database table prefix?

On a new install it does no harm. On an existing site the benefit is small and the risk of breaking something is real, so I don’t bother.

Should I disable XML-RPC?

Yes, unless you use the WordPress mobile app, Jetpack, or another service that needs it. It is a common target for password guessing attacks.

Is hiding the WordPress version number worth it?

Not much. Automated attacks look for vulnerable plugins directly, so hiding the version adds little real protection.

Related posts