The day after attempting to submit my first WordPress plugin, I learned that the smallest details can sometimes carry more weight than you expect.
When I created my WordPress.org account, I was moving quickly. The goal that day was simple: submit the Dreamy Tags plugin. During the signup process, I was prompted to fill out some basic profile information. For the “Interests” field, I typed “Stuff.”—a throwaway placeholder and a small joke to myself, fully expecting I’d return later and fill it in properly.
I didn’t realize that people—or automated systems—would treat that field seriously right away.
While attempting to submit the plugin, my account was suddenly disabled. At the time, I had no indication why, and I wasn’t able to log in and complete the submission process. It wasn’t until I contacted support that I learned the block had nothing to do with the plugin itself. The WordPress.org team explained that their anti-spam system had flagged my profile and that it occasionally gets things wrong. Once reviewed, the block was removed.
Only then was I able to go back and update the profile properly.
You were not blocked for submitting a plugin. You were blocked because our anti spam system didn’t like your profile. It gets that wrong a lot. You’re unblocked now. Sorry for the inconvenience.
WordPress.org Password Resets
In hindsight, it makes sense. From the outside, a brand-new account submitting a plugin with an empty or jokey profile doesn’t provide much context. But from my side, it was simply a case of focusing on the code and treating the profile as something I’d “clean up later”—a habit that works fine on personal sites, but not always in shared ecosystems.
After the block was lifted, I rewrote the profile to actually reflect who I am, my history with WordPress, and the broader interests that shape the work I do. I added a real bio, a detailed WordPress origin story dating back to 2005, linked my GitHub account, and enabled two-factor authentication.
With that context in place, the plugin submission went through cleanly, passed an automated plugin scan, and entered the review queue as expected, with 292 reviews ahead of mine (the day before, there were 246). I also received confirmation that the plugin had been assigned the slug ‘dreamy-tags,’ which it will use in the plugin directory once it passes review and is approved.
The whole experience was a good reminder that in open platforms—especially ones as large and long-running as WordPress—context matters just as much as code. Even a single placeholder word can carry more meaning than intended, and sometimes the systems watching don’t know it was meant as a joke.
Lesson learned.
