r/ProWordPress • • 1d ago

I made a Local add-on to pull and push sites to any server over SSH

29 Upvotes

Local WP's Connect only works with WP Engine and Flywheel, and my sites are on different VPSs on different providers, so every time I wanted a site locally it was wp db export, rsync, wp db import and a search-replace...

So I ended up building an add-on for it, SSH Sync for Local. It just uses your SSH access (key or password), and it does pull and push of files and the database. Before a push it shows the files that will change, and the last push can be undone.

github.com/fabiomsnunes/local-addon-ssh-sync

A pulled site runs all the live plugins, so I added a safe mode that blocks emails, turns off backup plugins and puts Stripe in test mode. It only covers some use cases for now, but it's on by default.

There's also a small CLI (ssh-sync pull/push/undo) next to Local WP's localwp.

It's free and open source (MIT), no paid version, no upsell, nothing to sell. macOS only for now and still early (v0.1.3). I've only tested it on my own servers, so I'd really like feedback from other devs!!
And if it breaks please open an issue on GitHub.


r/ProWordPress • • 1d ago

Static Astro site + headless WordPress: security review, what am I missing?

3 Upvotes

I’m running a small business website as a static Astro build, with WordPress used only as a headless CMS on a separate subdomain. Content edits trigger a rebuild through GitHub Actions, and the result is uploaded to shared hosting via rsync. I’ve tried to harden everything and would love a second opinion.

Public site (static)
HTTPS only + HSTS, nosniff, X-Frame-Options, Referrer-Policy, Permissions-Policy
Any server-side script extension denied, dotfiles (.env, .git, .htaccess) denied, no directory listings
No source maps or secrets in the build, noindex by default unless production explicitly enables indexing

Content from the CMS
All rich text goes through an allow-list sanitizer (sanitize-html): no scripts, event handlers, iframes or forms; links limited to http/https/mailto/tel
Uploaded SVGs reduced to shapes/colors; social embeds reduced to the official blockquote (the embed script is loaded by the site itself)
~40 XSS payloads tested, the key ones run as unit tests in CI

WordPress (headless)
REST API closed to the public; the build reads it with a secret token + an application password of a subscriber-level user
User enumeration blocked, XML-RPC/feeds/comments off, login limited per IP, TOTP 2FA for the admin
File editor disabled, no PHP execution in uploads, core/plugin checksums verified, minimal plugins with auto-updates, real cron job

CI/CD
Private repo, read-only workflow token, actions pinned to commit SHAs, no PR trigger
Type check, unit tests and a Playwright check of every page (overflow, headings, broken links, JS errors) before deploying
CMS-triggered rebuilds skip the checks only if that exact commit already passed them
SSH with a pinned host key; the deploy key is bound to a forced command and a single folder

Questions
Is it worth adding HTTP Basic Auth in front of wp-login.php / wp-admin on top of 2FA and login limits, or is it mostly security theater at this point?
The hosting account is shared with a few other WordPress sites under the same system user. Apart from moving to a separate account, is there anything meaningful I can do to limit the blast radius?
For a static Astro build with lots of small inline scripts, is a hash-based CSP worth the effort, or is the benefit small when there’s no user input on the public side?
Anything obvious I’m missing for this kind of setup?


r/ProWordPress • • 3d ago

how do u guys manage domians when youre juggling a load of small client sites????

7 Upvotes

I look after a pile of small one page Wordpress sites for clients. Barely any traffic on any of them, but the client list keeps growing and I charge a flat yearly fee, so the margin gets thinner every time I take someone on.

Domains are scattered across Namecheap, Wix Domains and a couple of other places depending on who set them up originally. What used to be pretty manageable is now a mess of renewal reminders, DNS records, and different registrar accounts.

Been thinking about moving everything to one registrar just to make life easier, but not sure if that's worth the hassle of transferring a load of domains. I can handle the technical side, just don't fancy spending half my time babysitting renewals and DNS records.

Anyone managing a similar number of small client sites? Do you keep domains wherever they were originally registered or move them all to one place? And if you've consolidated, which registrar has been the least annoying to deal with?


r/ProWordPress • • 5d ago

Wordpress+ Woocommerce CPU Spike with low traffic?

0 Upvotes

I have a client whose site is built on woocommerce + woodmart theme + Elementor, approx 50 plugins with litespeed optimization enabled. I disabled guest optimization as it was adding load to CPU. Previously CPU usage was touching 100% every hour despite having low traffic. I tried query monitor , New relic logs but could not find any solid lead . Can any one suggest any method to fix this ? Admin-ajax.php is showing in log. I am using cloud 4GB ram.


r/ProWordPress • • 6d ago

I built a modern open source local PHP environment for Mac (public beta)

9 Upvotes

I asked the mods before posting this.

PHP sites are one part of my work, and the local tools I was using felt stuck in another decade. So I built Benbow and released it as free, open source software.

Yes, it's made with AI, obviously. Most of the code was written by Claude. In 2026 I don't think one person can build something like this in a reasonable time without it. I decided how it works and what it must never do, I reviewed what it wrote, and I use it every day on my client sites. The code and the tests are on GitHub if you want to check.

Each site gets its own PHP version, from 5.6 to 8.5, all running at the same time. HTTPS on .localhost works without browser warnings. You get MySQL or PostgreSQL, Redis and Mailpit, and a new WordPress or Laravel site takes one step. It can snapshot files and database together, and pull a site down from production over SSH, SFTP or FTP. If there's a Vite or Next.js front end next to the PHP site, that gets its own HTTPS address too.

A few technical choices:

  • PHP comes as static builds, with one PHP-FPM process per version behind Caddy. That's how a 7.4 site and an 8.5 site run side by side. Each site can still have its own php.ini values.

  • Benbow creates its own local certificate authority, limited with X.509 Name Constraints to .localhost, .test and .local. If its key ever leaked, it still couldn't sign a certificate for a real domain.

  • Snapshots use APFS clonefile, so they're instant and take almost no space until files change. A restore takes a snapshot first, in case you change your mind.

  • Nothing runs as root. Services are launchd agents under your user, and everything lives in ~/Library/Application Support/benbow. It doesn't use Homebrew and it never touches MAMP, Herd or a MySQL you already have running.

  • Every binary it downloads (PHP, MySQL, Caddy, wp-cli and so on) is checked against a SHA-256 from a signed manifest before it runs.

  • The core is written in Go and the app in SwiftUI, talking over a local Unix socket. So the CLI (every command has --json) and the MCP server can do everything the app does.

You can import sites from MAMP PRO, Local, Herd and XAMPP, and undo the import if something's off. benbow uninstall removes everything.

If you let Claude Code or Codex work on a site, Benbow saves it first. When the agent is done you see what changed and decide: keep it, or undo it all, database included. Benbow never calls a model itself, and agents can only read until you give them write access for a site.

Apple Silicon, macOS 14+, GPL-3.0. It's a beta, so please tell me what breaks.

https://benbow.dev

https://github.com/benbowdev/benbow

Thanks for reading!
Andrea


r/ProWordPress • • 8d ago

Jetpack signed media uploads: diagnosing body-hash canonicalization vs proxy rejection

2 Upvotes

I manage a self-hosted WordPress site connected through Jetpack. Draft creation and media listing work through the official WordPress.com MCP connection, but media.create using a public HTTPS source_url returns upstream HTTP 403, then an XML-RPC fallback error ixr_-32601.

Environment: WordPress 7.1.4, Jetpack 16.4, PHP 8.3.36/FPM, Nginx and a local backend proxy, on a Hostinger VPS. Upload Media was enabled; cycling that specific permission did not resolve one subsequent controlled test. A full client restart/new-conversation test is still pending.

Sanitized origin logs near that test show:

  • POST /wp-admin/admin-ajax.php: 403, 71 response bytes, a quoted field containing wordpress.com.

  • Two seconds later, POST / with jetpack=comms: HTTP 200, 250 bytes.

  • Each signed URL had one scalar body-hash parameter. Neither contained a literal +, %2B, %20 or %252B; modeled form decoding preserved SHA-1/Base64 shape without spaces.

These are time-correlated records, not requests linked by a unique ID. I have not captured their bodies, Content-Type, XML-RPC method or response bodies. HTTP 200 does not establish success. An earlier nearby Jetpack stored error matched the non-empty-body invalid_body_hash branch, but it also lacks a unique link to that earlier upload.

Jetpack's receiver code canonicalizes multipart POST data before signature validation. The missing piece is the actual WordPress.com sender's signed representation.

For developers familiar with this path:

  1. Is there an official specification or synthetic fixture for the sender/receiver multipart canonicalization contract?

  2. Which existing diagnostic metadata can distinguish a receiver body-hash mismatch from a proxy/WAF rejection without recording secrets or disabling signature checks?

  3. Does ixr_-32601 on this fallback commonly reflect authentication-dependent method registration, and what safe metadata identifies that stage?

I'm looking for a way to isolate the failing stage before changing configuration. No tokens, raw signed URLs or request bodies are included.

Disclosure: this question was prepared with AI assistance from verified diagnostic records.


r/ProWordPress • • 8d ago

Opinions on my WordPress git workflow?

9 Upvotes

Context: The agency I work for has many clients with different setups, many of them very specific. Some use deployments and some don't, so I always need to find a middle ground.

Projects are hosted in GitLab:

- Bedrock: core and plugins managed via Composer, only paid plugins pushed to the repo

- Regular WP: both core and plugins pushed to the repo

CI/CD pipelines with a build step for Deployer, a static build step for JS/CSS, and a test step for Pest tests (if running a Sage theme).

And last step for deployment

- Deploy to develop environment (on develop branch): automatic

- Deploy to production (on master branch): manual

DISALLOW_FILE_MODS is set to true on production so the client can't screw things up by updating anything. The downside is that the client can't upload plugins or make any changes to files through the WP panel.

Wordfence is installed with alerts on high/critical vulnerabilities.

When vulnerabilities are discovered, I update core and/or plugins: first I check locally that nothing broke, then on dev, and finally push to prod.

Once a month I bump everything to the latest version as part of the SLA.

---

Some hosts don't allow a symlink as the root dir, or are missing binaries that Deployer needs, so sometimes the flow is different. Everything stays the same, but when it's time to deploy to prod, I use UpdraftPlus Premium to back up core, plugins and themes (without the DB) on develop and restore them on prod. I don't think it's perfect, since updates can make changes to the DB and that's not part of the backup.

What do you think of this? Do you have any recommendations?

I don't really like that it relies heavily on Wordfence emailing me about what's wrong with the website. If something breaks with SMTP, I might miss something important. (In some projects, clients use their main account for sending mail instead of a separate forms email, and they keep changing the password.)

I can't really think of how to improve this flow. Since everything has to go through git, this seems like the only sensible option.

I think it would be great to have one shared panel to see everything that's happening on the websites. I'm working on one, since services like ManageWP, MainWP, etc. always have something that doesn't fit my needs. But that's a separate issue.


r/ProWordPress • • 11d ago

Plugin developers: what makes you trust a new plugin with business-critical data?

0 Upvotes

I’ve been thinking about the trust problem for newer WordPress plugins.

For something cosmetic, trying a plugin with very few active installs doesn’t feel particularly risky. That changes quickly when the plugin touches orders, customer data, payments, bookings, webhooks or scheduled jobs.

Active installs and reviews obviously help, but a new plugin can’t have years of history on day one.

So I’m curious what other developers actually inspect before trusting a relatively new plugin with a production workflow.

For example:

  • source code availability

  • database schema and migration strategy

  • uninstall behavior

  • webhook / retry handling

  • logging and diagnostics

  • privacy and telemetry

  • release frequency

  • support responsiveness

  • rollback compatibility

  • automated tests

Do you have a minimum set of signals that makes you comfortable installing something new on a business-critical site?

And are there any red flags that make you stop evaluating immediately?


r/ProWordPress • • 12d ago

Spam / Self-Promo

6 Upvotes

Right now we are fairly strict about our No Spam/No Self Promo rule: “Self-promotion of themes, plugins, and services is not allowed. No affiliate links.” We ask because this has occasionally impacted stuff that’s on WP.org and potentially useful to others.

As a member of /r/ProWordPress — what say you on this rule? Like it as is? Is it too harsh? Obviously the poll below won’t cover every option. If you have something else to add, please use the comments below.

86 votes, 9d ago
42 Keep it strict/as is.
15 Allow plugins/themes available via WordPress.org
11 Plugins/themes/services are okay as long as they aren’t AI-created and not overly-posted.
6 Allow plugins/themes/services regardless of where they’re available or how they were made.
10 I don’t care.
2 Get rid of the rule.

r/ProWordPress • • 12d ago

First free plugin on wp.org, 4 weeks in: how do you separate real adoption from bot downloads, and when do you ask for reviews?

0 Upvotes

Read the Product Hunt thread from last week (wp.org is the only channel that matters, reviews mostly come from the support forum, ask in the dashboard after a value moment). Useful, thanks to whoever wrote that. I'd like to go one level deeper with people who have been through it.

Context: free display plugin, live on wp.org for 4 weeks. Download stats look ok on paper but when I line them up with my own release dates almost every spike is a release day, so its mostly mirrors and scanners grabbing each new version. Active installs still says less than 10, zero reviews. One unusual part: the output can also be embedded on non WordPress sites (Webflow, Shopify), so part of the audience isnt even in the WP admin.

I also checked the plugin search API for ~30 terms. Top 50 on a few niche ones, invisible on the big generic ones, which matches what people say about installs and ratings outweighing the readme.

Questions:

  1. How do you measure real adoption this early, when active installs only moves in big steps? Opt-in ping, support forum activity, something else?

  2. In-dashboard review ask: what trigger worked for you, and what did you do to stay clearly within the guidelines (dismiss forever, no nagging, only for admins)?

  3. Did you push niche search terms first or did it make no difference until you had a few dozen installs?

  4. For a tool partly used outside WordPress, where did that kind of user come from for you, if you ever had one?

Real numbers welcome, even bad ones.


r/ProWordPress • • 14d ago

WordPress.org plugin approved, but SVN authentication fails in two different clients — need developer advice

7 Upvotes

Hello WordPress developers,

We're the Beat Aware™ Team. Our WordPress.org plugin was approved on October 13, 2026, but we're unable to complete our first SVN commit.

Plugin slug: beat-aware-visitor-intelligence
WordPress.org username: beataware

Error received:

Authentication failed — No more credentials or we tried too many times.

Here's what we've already tried:

  1. Installed and configured TortoiseSVN.

  2. Verified the correct WordPress.org username and repository URL.

  3. Checked locally saved Subversion authentication credentials.

  4. Installed SmartSVN and attempted the commit using a second client.

  5. Cleared SmartSVN's saved authentication credentials.

  6. Generated a completely new SVN-specific password through WordPress.org.

  7. Retried authentication using the newly generated password.

  8. Confirmed the repository exists and its trunk/ directory is empty.

  9. Verified that all 21 files and 9 directories are staged for the initial commit.

  10. Contacted the WordPress.org Plugin Review Team and posted in their official #pluginreview Slack channel.

Both SVN clients have encountered authentication failures.

Our questions:

Has anyone experienced this issue when making their first WordPress.org plugin commit?

Is there a reliable diagnostic method to determine whether the problem involves credentials, SVN authentication, or repository write permissions?

We're looking for specific technical guidance from developers who have successfully resolved this type of problem.

A Gesture of Appreciation

We recognize that troubleshooting takes time and expertise. If someone can help us successfully resolve this issue, we'd be happy to reciprocate privately with a complimentary license to our WordPress software as a thank-you for their assistance.

Our priority is simply getting our approved plugin published, and we sincerely appreciate anyone willing to share their experience.

Thank you!

Beat Aware™ Team


r/ProWordPress • • 18d ago

Tired of FTP clients for WordPress deploys. What do you use instead?

10 Upvotes

I got fed up with clunky FTP clients and juggling separate tools for local dev, migrations and deploys. I want one place to run a site locally and push or pull it to any host, without being tied to one vendor (Local is great, but its deploys are built around WP Engine and Flywheel).

What does your setup look like? Git plus rsync, WP-CLI scripts, a migration plugin, something else? And how do you handle the database and the URL replacement?


r/ProWordPress • • 19d ago

File integrity monitoring: how do you tell a host’s routine update from a planted backdoor in mu-plugins?

0 Upvotes

I maintain a WordPress security plugin and ran into a file-integrity case I’d like other people’s views on.

A client site on Hostinger flagged a change to wp-content/mu-plugins/hostinger-auto-updates.php. Hostinger had updated it themselves. Legitimate, but the alert kept showing up in every daily summary because the baseline only refreshed on upgrader_process_complete, and host-side changes never fire that.

The easy fix is to whitelist known host files by name. I didn’t want to: a backdoor can be called hostinger-anything.php, and mu-plugins is one of the first places attackers persist because it loads without activation. Per-host exceptions also don’t scale.

What I went with instead is a general rule. A change is treated as routine only when both of these are true:

  1. The file’s Version: header went up compared to the baseline

  2. The changed file passes the malware signature scan

php

$old = $baseline[ $path ]['version'] ?? '';
$new = get_file_data( $abs, [ 'v' => 'Version' ] )['v'] ?? '';

$routine = $old !== '' && $new !== ''
    && version_compare( $new, $old, '>' )
    && ! $scanner->scan_file( $abs ); // no findings

Routine changes are accepted into the baseline and logged quietly. Anything else is still an alert: no header, same or lower version, any scanner hit, or files like wp-config.php that never have a header. There’s also a manual “these changes are expected” button to re-baseline.

The weak spots I know of:

  • An attacker who knows the rule can bump the header

  • Signature scanning misses novel code

  • Files without headers always alert, which is noisy for some hosts

How do you handle this? Do you compare against vendor checksums where they exist (core has them, hosts mostly don’t)? Diff size heuristics? Just accept the noise and train clients to ignore it? Curious what’s worked on agency fleets.


r/ProWordPress • • 20d ago

What do you think about the WordPress Gutenberg editor?

2 Upvotes

I've been exploring the WordPress Gutenberg editor lately, and I'm curious about how other WordPress users feel about it.

Do you prefer Gutenberg for building pages and layouts, or do you still find yourself relying on the Classic Editor or page builders like Elementor?

What do you like most about Gutenberg, and what do you think could be improved?

Would love to hear your experiences!


r/ProWordPress • • 20d ago

RTC in WP - Realtime Collaboration in WordPress

5 Upvotes

I have been following the RTC phase development in WordPress open source.

This is one of the best ways to learn and deepen your knowledge around RTC while also understanding how the decision is made for a large scale project like WP.

Link: https://make.wordpress.org/core/2026/10/14/real-time-collaboration-a-guide-to-sync-engines/


r/ProWordPress • • 21d ago

What do you think is the most important thing when building a WordPress website?

0 Upvotes

I'm curious what other WordPress developers prioritize when starting a new project.

I'd be interested to hear what has worked best for you on real projects.


r/ProWordPress • • 21d ago

Does OrderCouponDataMigrator still have a valid invocation path in current WooCommerce?

1 Upvotes

Hi everyone! I'm reviewing WooCommerce's source code and came across OrderCouponDataMigrator. In older versions, it appears to have been registered through the dependency-injection container, but in current versions I can't find it in the explicit registration list. Does anyone know whether this was intentional, or if there's another supported path that invokes its register() or migration methods?


r/ProWordPress • • 21d ago

Ho creato un Anti-Spam "Zero-DB" per WordPress perché ero stanco di vedere i database dei miei server esplodere. Cerco feedback e tester!

0 Upvotes

Ciao a tutti, mi chiamo Simone (sulla directory WP mi trovate come SyGy) e gestisco diversi ambienti web su VPS.

Lavorando quotidianamente sui server, ho sempre odiato un problema architetturale dei classici plugin anti-spam e di sicurezza per WordPress: lasciano entrare i bot. Analizzano la richiesta, interrogano cloud esterni, e poi salvano montagne di log dentro le tabelle MySQL, creando colli di bottiglia e consumando CPU. L'alternativa classica è piazzare un reCAPTCHA ovunque, ammazzando il Core Web Vitals e infastidendo gli utenti reali.

Così, stanco di queste soluzioni "bloatware", ho deciso di scrivermi un plugin da zero basato su un concetto diverso: respingere le richieste sintetiche al livello più alto possibile (Early Return) e non toccare mai il database.

Dopo svariati mesi di sviluppo e test sui miei siti, il team di WordPress ha ufficialmente approvato e pubblicato il mio progetto: SyGy Security Log & Anti-Bot.

Come funziona sotto il cofano? Invece di analizzare lo spam dopo l'invio, il plugin usa uno scudo crittografico comportamentale. Genera un token dinamico HMAC-SHA256 (unico per ogni sito) basato sull'interazione umana reale. Se un bot cieco spara richieste POST dirette a wp-comments-post.php o alle API dei form, il server intercetta la mancanza del token valido e taglia la connessione all'istante con un HTTP 403, prima ancora che WordPress carichi le query pesanti.

Le feature tecniche principali:

  • Log su File Flat (Zero-DB): Gli attacchi respinti vengono registrati su un leggerissimo file .txt, blindato da un hash casuale a 16 caratteri e regole .htaccess. Il file ha un limite di auto-rotazione programmabile (es. 10 MB) per resistere ad attacchi botnet massicci senza saturare il disco. Il database MySQL non viene mai sfiorato.

  • Nessun CAPTCHA: L'utente reale non deve mai risolvere puzzle o cliccare semafori.

  • 100% Cache Compatible: Nessun problema con WP Rocket, LiteSpeed Cache, Cloudflare o funzionalità di "Delay JS".

  • Protezione Ecosistema Modulare: Riconosce e blinda in automatico (solo se installati) Contact Form 7, WooCommerce, WPForms, bbPress, Elementor Pro Forms e BuddyPress.

Perché scrivo qui? La versione base (v4.4.0) è appena atterrata nella repository ufficiale, open-source e gratuita. Attualmente sto già scrivendo il codice per la v5.0 (che introdurrà un visualizzatore log interattivo in bacheca e un modulo 2FA TOTP iper-leggero), ma prima di andare avanti ho un enorme bisogno di stress test nel mondo reale.

Cerco sviluppatori, sistemisti o smanettoni disposti a installarlo (anche solo su ambienti di staging) per verificare la compatibilità con i setup più disparati e cercare eventuali bug che mi sono sfuggiti.

Ogni critica al codice, consiglio o feedback costruttivo sarà oro puro per me. Grazie mille a chi dedicherà 5 minuti del suo tempo per aiutarmi a far crescere questo progetto!


r/ProWordPress • • 21d ago

Planning to launch my free WordPress plugin.

0 Upvotes

Has anyone tried launching a free WordPress plugin in Producthunt? Did it work? As of now, my goal is to increase the downloads and get a review for my plugin.

If not Producthunt for the plugin, where can I launch?

Need a help.


r/ProWordPress • • 22d ago

PHP2Shell: a quick way to check whether your host has patched PHP (no plugin needed)

0 Upvotes

PHP released fixes for PHP2Shell (CVE-2026-109618 and CVE-2026-109619) on October 21. The bugs are in PHP itself, so updating WordPress and plugins doesn't cover it.

To check: Tools → Site Health → Info → Server → PHP version. You're patched on 8.5.12, 8.4.27, 8.3.36 or 8.2.35 and later in each branch. 8.1 and older have no official release, so ask your host about a backport or move to a supported version.

Attacks started on October 17, before the fixes were public, so it's worth checking for PHP files in uploads and admin users you don't recognise.

I wrote up the steps with sources here: https://jeromesgorman.com/php2shell-wordpress

Disclosure: I built PHP Threat Watch, a plugin that checks this automatically. The steps above work without it.


r/ProWordPress • • 22d ago

What frustrates you the most about WordPress, and what needs to be improved?

0 Upvotes

Hey everyone, I’m curious about the native limitations of WordPress that annoy you the most. For example, the lack of a proper, built-in folder management/sorting system for the media library drives me crazy.

What are your biggest pain points with core WordPress features? What makes you think "this should be a built-in feature by now"?


r/ProWordPress • • 22d ago

Hi, Suspicious WordPress Attacks Using Cloudflare and a Backend Plugin Named xdevtracker — Anyone Else Seeing This?

2 Upvotes

I wanted to bring attention to some suspicious activity involving WordPress websites that I’ve been looking into recently.

There are concerns about malicious attacks targeting WordPress sites, with Cloudflare appearing to be part of the traffic or security setup and a suspicious plugin named xdevtracker appearing in the WordPress backend.

#WordPress #WordPressSecurity #Cloudflare


r/ProWordPress • • 24d ago

I helped build a desktop app that sets up WordPress Core and Gutenberg dev with no Git, Node or Docker. 2.0 just shipped with a redesign

0 Upvotes

I'm a developer advocate at Automattic, and I work on the WordPress Contributor Toolkit, a desktop app (macOS, Windows, Linux) that sets up a full WordPress Core or Gutenberg development environment without needing Git, Node, npm or Docker on your machine. It started as a fix for Contributor Days, where newcomers would spend the whole session on local setup and never get to the ticket.

Version 2.0 came out this week, and the big change is the look. The window is rebuilt on the WordPress Design System, so it should feel familiar if you've used the block editor.

And here's what else changed in 2.0:

- A settings dialog for the theme, the language, the PHP version and the `WP_DEBUG` / `SCRIPT_DEBUG` flags

- A dark theme, and a custom theme built from a background and a primary color you pick

- Ten languages, following your operating system's language by default

- A tree of changed files after you apply a patch or check out a pull request, each one opening in your editor

- Trac ticket details that stick around after you quit and reopen the app

- About 350 MB smaller once installed

Download: https://wordpress.github.io/contributor-toolkit/

Release post: https://make.wordpress.org/core/2026/10/23/wordpress-contributor-toolkit-2-0-a-redesigned-app-in-your-language/

It's free and open source. If you try it, I'd like to hear what broke or what felt off. Issues go to https://github.com/WordPress/contributor-toolkit/issu


r/ProWordPress • • 25d ago

Google's new AI guidance covers titles, meta, schema and alt text. How are you building review into WP publish flows?

3 Upvotes

Google updated its Search Central page on generative AI content on October 1. It now says it's "critical to manually factcheck and review all AI-generated content" before publishing, and it spells out that this includes title elements, meta descriptions, structured data and image alt text.

On a lot of client sites those last four never get looked at by a person. An SEO plugin fills the meta, something auto-generates alt text on upload, schema comes from a template. Nobody writes them, so nobody reviews them.

Curious how people here are handling it on the dev side:

Are you gating publish on review, like a pre-publish panel check or a custom status, when meta or alt text was machine-generated?

Do you store provenance anywhere (a post meta flag, a revision note) so an editor can see which fields came from AI?

Or is this a process problem you leave to the content team and don't touch in code?

Interested in what has held up in production, not the ideal setup.