Proposal from IRC: Changes to doc-bot commands

The following is from, and was part of an IRC discussion. We can talk about this some more in this week’s SFD chat (1600 UTC at #wordpress-sfd, please come if you’re an IRC person!) and get a more updated summary. This one appears to be a couple years old and haphazzardly tacked on.


New text after release of WordPress 3.6:

Please disable or delete all plugins and switch to the default theme (Twenty Thirteen since 3.6). After making these changes does the problem still occur? If no, re-enable everything one by one to see which component causes the problem.


After many browsers added their own developer tools this doc-bot command seems somewhat deprecated.

May I suggest to add a new command .inspect instead:

.inspect – Tells the user to inspect code using developer tools of his browser

Text to show up after bot command: Please use the built-in Developer Tools of your browser to fix problems with your website. Right click your page and pick “Inspect Element” (Cr, FF, Op) or press F12-button (IE) to track down CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. problems. Use the console to see JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. bugs.


This doc-bot command covers third party plugins and themes, especially with code not being publicly accessible, hence making it impossible to help.

As an inversion of that argument, some users seem to expect answers to their themes or plugins as granted, when the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party or theme was downloaded from The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. (“But it isn’t proprietary, so you *must* support me.”). For such cases, I would suggest following new doc-bot command:


Tells the user not to expect support for each and every plugin or theme available at

Text to show up after bot command: We try our best, yet from a great variety of existing themes and plugins it is nearly impossible to know all. Your best chance is to contact the developer for support.

As a non-native speaker I would appreciate any improvement on the wording.

Pixolin, May 17th 2013

Feature Proposals

  • [nick] and [command] shortcodes that display the nick or command, e.g. “[user], please do foo”
  • Aliasing through a bot command (btw. could this be as simple as learn foo:[alias=bar]?)
  • str_replace of text, something like “replace #evil#inherently insecure#”
  • Alternate versions of info texts, like “Congratulations [user]! You have won (the US Presidency|a 300 baud modem)!
  • Bot actions, so that the bot runs /me slaps [user] around a bit with a large trout

Nkuttler 10:51, 10 September 2010 (UTC)

In /query, allow !list or !help (or something to that effect) to respond with a list of the existing one-word commands. (Saves referencing the Codex or other source when adding a new command.)

Please leave comments with suggestions as to new commands you’re interested in, or improvements to the ones we have.