Wordpress Setup

# WP-CLI Essentials

## SSH Connection Patterns

### Inline SSH

```bash
wp --ssh=user@host/path/to/wordpress <command>
```

### Alias in wp-cli.yml (project-level)

```yaml
ssh:
  mysite:
    cmd: ssh -o StrictHostKeyChecking=no %pseudotty% user@hostname %cmd%
    url: /path/to/wordpress
```

Usage: `wp @mysite <command>`

### Global Aliases (~/.wp-cli/config.yml)

```yaml
@client1:
  ssh: user@client1.com/www/public
@client2:
  ssh: user@client2.rocketcdn.me/www/client2/public
```

## Common Flags

| Flag | Purpose |
|------|---------|
| `--fields=ID,post_title` | Limit output columns |
| `--format=json` | JSON output (pipe to jq) |
| `--format=csv` | CSV output |
| `--posts_per_page=N` | Limit results |
| `--post_type=page` | Filter by post type |
| `--post_status=publish` | Filter by status |
| `--allow-root` | Run as root (hosting that requires it) |
| `--skip-plugins` | Skip plugin loading (faster, useful for debugging) |
| `--skip-themes` | Skip theme loading |
| `--quiet` | Suppress informational messages |

## Useful Diagnostic Commands

```bash
# Site health
wp @site core version
wp @site option get siteurl
wp @site option get home

# Database
wp @site db size
wp @site db tables

# Plugins
wp @site plugin list --status=active --fields=name,version
wp @site plugin status elementor

# Users
wp @site user list --fields=ID,user_login,user_email,roles

# Cron (useful for scheduled posts)
wp @site cron event list
```

## Rocket.net SSH Pattern

Rocket.net sites typically use:

```bash
wp --ssh=sshuser@hostname.rocketcdn.me/www/sitename/public <command>
```

Or with their MCP server for direct API access without SSH.

## Troubleshooting

| Issue | Solution |
|-------|----------|
| `wp: command not found` on remote | Use full path: `/usr/local/bin/wp` or install via SSH |
| SSH key not accepted | Check `~/.ssh/config` for correct IdentityFile |
| `Error establishing a database connection` | DB credentials may differ — check `wp-config.php` |
| Timeout on large exports | Use `--skip-plugins --skip-themes` to reduce memory |
| `PHP Fatal error: Allowed memory size` | Add `--exec="ini_set('memory_limit','512M');"` |


---
name: wordpress-setup
description: "Connect to a WordPress site via WP-CLI over SSH or the REST API. Check CLI, test SSH, set up auth, verify access, save config. Use whenever the user wants to connect to a WordPress site, set up WP-CLI access, create an Application Password, or troubleshoot WordPress connection / auth issues."
compatibility: claude-code-only
---

# WordPress Setup

Connect to a WordPress site and verify working access via WP-CLI or REST API. Produces a verified connection config ready for content management and Elementor editing.

## Workflow

### Step 1: Check WP-CLI

```bash
wp --version
```

If not installed, guide the user:

```bash
# macOS/Linux
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
chmod +x wp-cli.phar
sudo mv wp-cli.phar /usr/local/bin/wp
```

Also ensure the SSH extension is available (needed for remote sites):

```bash
wp package install wp-cli/ssh-command
```

### Step 2: Connect to the Site

**Option A: WP-CLI over SSH (preferred)**

```bash
wp --ssh=user@hostname/path/to/wordpress option get siteurl
```

Common patterns:
- Rocket.net: `wp --ssh=user@hostname/www/sitename/public option get siteurl`
- cPanel: `wp --ssh=user@hostname/public_html option get siteurl`
- Custom: Ask user for SSH user, host, and WordPress path

Test with a simple command first:

```bash
wp --ssh=user@host/path core version
```

**Option B: REST API with Application Password**

If SSH isn't available:

1. Navigate to `https://example.com/wp-admin/profile.php` (or use browser automation)
2. Scroll to "Application Passwords" section
3. Enter a name (e.g. "Claude Code") and click "Add New Application Password"
4. Copy the generated password (spaces are part of it but optional in auth)

Test the connection:

```bash
curl -s https://example.com/wp-json/wp/v2/posts?per