Support Everything WordPress

Updates from Ipstenu (Mika Epstein) Toggle Comment Threads | Keyboard Shortcuts

  • Ipstenu (Mika Epstein) 10:32 pm on January 26, 2015 Permalink |  

    A reminder for those who haven’t seen it.

    Please take a few minutes to fill in the Community Hub Poll as the poll closes Thursday at 00:00UTC.

    For more information on the Community Hub, please check out this post.

  • Ipstenu (Mika Epstein) 7:39 pm on January 15, 2015 Permalink |

    How to Properly Use Tags 

    This came up in this week’s slack chat. Using tags can be a fine art, and we may end up doing a tag-scrub some day soon, to get more people into helping triage posts in the forums.

    Tags usually aren’t used properly, and it’s OKAY that the masses don’t. This is actually a great job for someone who wants to get involved in support. By reading a post and determining it needs specific attention, you can improve the chances of someone getting help promptly.

    When you see a post, look at what the poster is asking and try to use a tag that makes logical sense for the issue. To help you get started, we have some standard tags that we use and encourage their appropriate use.

    Team Tags

    The following tags are used by the various make/teams on WordPress.org to track posts that need their attention.

    • Accessibility – a11y
    • Questions about the theme review process – thememod
    • Questions about the plugin review process – pluginmod
    • Moderator please come fix this – modlook
    • Not Safe For Work – nsfw
    • WordPress.com theme not in the .org repo – wpcom-theme

    Proper Use of Modlook

    Don’t use it if you are a moderator. This should go without saying.

    Be very careful with ‘modlook’ – Abuse of that tag will get your posting rights revoked. It should be used to flag moderator attention for things like duplicate posts, spam, abuse, harassment, etc. It is not to be used for getting help faster. That just gets you negative attention.

    When you use ‘modlook’ try to use it in conjunction with another tag. For example, if the issue is a spammer, use ‘modlook’ and ‘spam’ tags. If the issue is the post has personal information (like passwords) use ‘modlook’ and ‘private info’ – Basically try to make sure if a moderator is reading the post, they’ll see why the post needs attention. This is especially important when we’re talking about duplicate posts :) If you’re tagging spam and think it may not be obvious who is the spammer (things like ‘buy viagra!’ are pretty obvious), put the username of the spammer as another tag. Just in case. The mods will delete the tags once it’s handled.

    It’s also a great idea to actually reply to the legit posts. Telling someone “I’m alerting the moderators to this post. Never post your passwords in public!” is totally awesome!

    Keep in mind, we do not remove URLs from posts unless there’s a good reason. And by good reason we mean abuse, harassment, or legal reasons. Asking a URL be removed, or a post deleted, because someone is upset that Google picked up their URL in it’s search is not a good reason. If you don’t want something to be searched by google, don’t post it in a public forum.

    Plugin/Theme Tags

    This one is simple. Tag a post to match the slug of the plugin or theme that’s having the problem.

    For example. If someone is having a problem with Akismet, tag the post akismet. If it’s Hello Dolly, tag it hello-dolly.

    Pay careful attention to that plugin slug! Complicated plugins like https://wordpress.org/plugins/joes-awesome-twitter-widget may have the name “Joe’s Totally Wicked Cool Twitter Widget Plugin!” on the plugin page, but that slug of joes-awesome-twitter-widget is what you want to use for the tag.

    If the theme is one downloaded from WordPress.com, use the tag wpcom-theme

    Company Tags

    If someone specifically mentions a hosting company, make sure that company is tagged. Many hosts keep people on payroll in order to monitor posts tagged for them. The same goes for things like theme and plugin shops. It’s helpful to them to have, for example, GoDaddy or StudioPress tagged.

    When in doubt …

    Don’t tag :) Come on over to the #forums room in Slack and ask us for help. Someone’s almost always around.

  • Ipstenu (Mika Epstein) 5:41 pm on November 13, 2014 Permalink |  

    T-Shirt Ideas 

    The docs team has a t-shirt. Why don’t we? Because we’re incredibly lazy.

    I want to preface this with a reminder: This does not mean we will actually get the shirts. This is an idea, and eventually we’ll need to ask people like @andreamiddleton or @camikaos if we can do this at all.

    Proposed Text

    “You look like a WordPresser that supports 23% of the Internet. – #tyrell14″

    There’s a story there, but if you were at #wcsf you probably heard it. Suffice to say, Tyrell became our meme in a surprisingly safe for work way.

    Proposed Graphic

    Much to @macmanx‘s disappointment, we can’t use an animated GIF. The rest of us sigh in relief.

    I also can’t draw. Or design like that.

    Suggestions Welcome!

    I know the text is a little WCSF centric, but this shirt will be for the folks who were, y’know, at WCSF this year (if possible).

    • Jen 10:44 pm on November 13, 2014 Permalink | Log in to Reply

      If we do shirts for one team we should do them for all the teams to be fair. Would like te make sure the design adheres to our best practices for women (that’s a lot of text to have on your chest at legible size without forcing the below-the-breast reading, so make sure it doesn’t fall down that far, etc). It I’ll check with Matt to see if we can buy shirts for each team in general; if not we could do one for each team that peolpe could buy if we need to.

    • Jan Dembowski 11:19 pm on November 13, 2014 Permalink | Log in to Reply

      Pinging @jcastaneda @kenshino for input. 😉

      Ideally each team would do this but I like the idea of doing one for each team that people could buy.

      • Jose Castaneda 3:58 am on November 14, 2014 Permalink | Log in to Reply

        I think that would be awesome for each team to have their own. Have a jigsaw puzzle piece on each one ( or Lego ) and their own tag line of some sort. Polyglots would get a different letter from each language, core could be in ‘code’ elements, themes a paintbrush stylized look, plugins possible cogs.

        These are just random ideas keep in mind. :)

    • Jon (Kenshino) 3:17 am on November 14, 2014 Permalink | Log in to Reply


      I actually run a design firm and told @ipstenu that we’ll work on a design – that being said, I hope more people will throw up designs so we can have something to choose from!

      We had some discussions of using Wapuu – and I feel that we could go about this in a few ways –

      Literal support – Wapuu could be infront of a monitor (having a huge sweat drop down the head) – a situation we have all had

      Figurative support – Wapuu could be holding up the WordPress Logo (designed as a Globe)

      All these should be on the back, and the front should be something simple.


    • Kathryn 3:49 pm on November 14, 2014 Permalink | Log in to Reply

      Love the idea of a T-shirt! I’m not sure about mentioning a specific percentage since it’s a moving target and quickly goes out of date, so just something to consider.

      • Jan Dembowski 5:40 pm on November 14, 2014 Permalink | Log in to Reply

        I actually like the idea of dating it, especially the #tyrell14 reference (which will almost certainly not make the t-shirt).

    • Matthew 11:09 pm on November 14, 2014 Permalink | Log in to Reply

      Would someone just bulk order them and then sell them?

  • Ipstenu (Mika Epstein) 4:57 pm on August 28, 2014 Permalink |  

    Draft OMGWTFBBQ for 4.0 

    This post is the official DRAFT post.

    I’ve slapped up a template for us to use going forward, but here are the sections, after the break.

    Leave comments for corrections or (if you’re an editor) just edit this post. It’s okay, my feelers won’t be bent out of shape :)

    (More …)

  • Ipstenu (Mika Epstein) 4:09 pm on August 19, 2014 Permalink |  

    OMG WTF BBQ Post! 

    So 4.0 man. What do WE see as the features that will cause the biggest issues?

    • Media Library Grid – Any plugin that adds features to the media library may need serious work.
    • Post Editor – The editor staying on the screen is not a bug :)
    • Post Editor/TinyMCE – The color picker’s coming back!

    What do you guys see as catching people’s adverse attention? Themes and plugins you know are broken?

    • Drew Jaynes (DrewAPicture) 4:19 pm on August 19, 2014 Permalink | Log in to Reply

      • They changed the default priority for Customizer sections to 160 from 10, so I can see people’s options getting moved around, maybe.
      • Might be problems with any plugin that manipulates the plugins list table (now a card view)
    • MacManX (James Huff) 6:01 pm on August 19, 2014 Permalink | Log in to Reply

      We have had 4.0 on WordPress.com for almost a month now. Typical grain of salt disclaimer, what seems like a minor inconvenience to you could always be a major inconvenience to someone else for reasons you don’t understand, so be respectful no matter how insignificant it seems.

      Some notes on things which are still a problem for some users with work-arounds when possible:

      • The post/page editor now auto-expands as you type (it’s a bit more complex than that, but that’s the basic). Previously, the editor had its own scroll bar. This means that if you write a huge post, you need to scroll all the way up to return to the Publish button, categories, tags, etc. Work-around: Click in the editor and cmd/ctrl-up/down to move to top/bottom of editor content quickly. Click out of the editor and cmd/ctrl-up/down to move to top/bottom of the whole page.
      • When the editor is larger than the fold, it cannot be scrolled up by highlighting text, due to how the editor toolbar follows the primary scroll. Work-around: Highlight and scroll outside of the editor window to move the primary scroll instead.
      • Prior to 4.0, the last “Linked to” option chosen when inserting media persisted as a default for future inserts until it was next changed. This was handy for bloggers who always linked to the attachment page or chose a custom link when inserting media. In 4.0, “Media File” is now a persistent default for “Linked to,” and changes to it do not “stick” as they did prior to 4.0. There is a ticket for this: https://core.trac.wordpress.org/ticket/23847
      • The new default Media library view is the grid view. At the top-left of the Media toolbar is a button to switch back to the old list view. When switched to the old list view, the button to switch back to the grid view moves to the right.

      Obviously, be on the lookout for plugins which no longer play nice with the editor and Media library, and above all, try to find out exactly what the user doesn’t like and work with them to find a work-around.

    • Matthew 2:11 pm on August 20, 2014 Permalink | Log in to Reply

      I think the Media Grid will be big because it could effect a lot of gallery plugins.

      Hopefully it doesn’t cause to much trouble for people.

      • Ipstenu (Mika Epstein) 3:35 pm on August 20, 2014 Permalink | Log in to Reply

        What specifically are you thinking about with Gallery Plugins that mess with the library view? Remember, we’re ONLY talking about the media library :)

        • Matthew 6:31 pm on August 20, 2014 Permalink | Log in to Reply

          I think it may mess up the way they retrieve images from the media library. I may also affect plugins that add onto the WordPress gallery.

          • Ipstenu (Mika Epstein) 2:14 am on August 21, 2014 Permalink | Log in to Reply

            It won’t impact retrieving images. Have you actually looked at it? Again, the change is only to the media library separate page. This doesn’t touch the in-editor image adding at all.

            And what I would love to know js what plugins do YOU know of that edit the media library? Because we want to have an idea in advance instead of the nebulous stuff. The only one I know about is the Ewwww image optimizer, and he already fixed his code for 4.0


    • Jeff Chandler 11:55 pm on August 20, 2014 Permalink | Log in to Reply

      Hey James, do you mind if I republish the information in your post into a post for the Tavern on things to look out for in WordPress 4.0?

    • Ipstenu (Mika Epstein) 7:48 pm on August 21, 2014 Permalink | Log in to Reply

      Changes to Plugins:

      When you browse for new plugins, you’ll see Plugin Icons to help you identify the right plugin faster. Also if you click on ‘View Details’ on your installed plugin list, that screen has been greatly enhanced to show you exactly what you’re getting into.

  • Ipstenu (Mika Epstein) 6:33 pm on May 20, 2014 Permalink |  

    Comments are now disabled on the User Manual 

    Since people keep posting rants and requests for support there, I’ve just turned the comments off.

    They were MEANT for non-editors to submit corrections and edits. I know this means people can’t easily report things that are wrong, but that’s okay. This was meant to be a temporary home anyway. We’ll just end up taking this, porting it to the new docs setup (whenever that’s ready) and edit from there.

    Thank you everyone who helped make them!

  • Ipstenu (Mika Epstein) 5:59 pm on March 27, 2014 Permalink |
    Tags: , guidelines,   

    Discussion: A Better Do and Don’t List 

    The following are cribbed from another site’s Dos and Don’ts. They should not be considered the be all and end all of guidelines, but they’re a good start. I’m thinking that perhaps a simplified ‘dos and dont’s’ list may help some people who see our massive list of guidelines and panic.

    This list is not perfect and I want your help

    Please suggest changes and improvements. I don’t want to make it much longer, so if we can consolidate and combine, that would be good. There’s no point in even trying to get through everything, so really I’m trying to spell out the basics of etiquette on the forums.

    Good Manners and Respect Dos and Don’ts

    • DON’T use “um,” be snotty to another user, or make the argument personal
    • DO know the difference between differences of opinion and personal attacks
    • DO treat others the way you want to be treated
    • DON’T present your opinions as facts
    • DON’T post the same opinion over and over in the hopes of wearing other people down or “winning” a discussion; just move on
    • DON’T be a gosh-darn dirty spammer
    • DON’T be vulgar; if you’re not sure, don’t say it

    Starting New Threads Dos and Don’ts

    • DO search for existing topics before starting new threads
    • DO make a new topic if you find yourself saying “I have the same problem but …”
    • DO link back to a related topic (or closed) when approriate
    • DON’T use all-caps or excessive punctuation in thread titles
    • DON’T treat the support forums as your personal blog
    • DON’T get all meta and use the forums to rant about the forums

    Posting Messages Dos and Don’ts

    • DON’T post in a thread until you’ve read the whole thread
    • DON’T post “Me Too!” messages; add something of substance to the conversation
    • DON’T sign your posts
    • DO use proper spelling, capitalization, punctuation, et cetera
    • DON’T post just to pimp your site or product, et cetera
    • DON’T post the same thing in multiple areas; pick a spot and go with it

    Warnings, Bans and Trolls Dos and Don’ts

    • DO take any mod warnings you get seriously
    • DON’T bug the mods to remove moderation on your posts
    • DO help us out and report trolls, flame wars, and troublemakers by tagging a post with “modlook”
    • DON’T abuse the modlook tag
    • Andrew Nevins 6:18 pm on March 27, 2014 Permalink | Log in to Reply

      I don’t think we need a manners bit, we can just assume everyone knows what manners are.

      • Ipstenu (Mika Epstein) 7:09 pm on March 27, 2014 Permalink | Log in to Reply

        That isn’t entirely the point of that section. We know what manners are, but a lot of people fall short on applying them, so a quick “Hey yo, remember this stuff?” is clearly needed. If not, there would be far fewer people being moderated :)

    • Drew Jaynes (DrewAPicture) 6:19 pm on March 27, 2014 Permalink | Log in to Reply

      Are these for forum posters or moderators? I keed I keed. I was thinking about something like this last night, actually.

      I realize this is a work in progress, and I think even this list is too long. We can pare some of these out. Some of these are good but multi-part where I feel like some of the parts are just common sense and don’t need to be said.

      So for instance, “DON’T use “um,” be snotty to another user, or make the argument personal” could probably just be “DON’T make things personal”, etc.

    • Andrew Nevins 6:21 pm on March 27, 2014 Permalink | Log in to Reply

      And for this bit “DO search for existing topics before starting new threads”, I’ve heard people say “I searched first, just like the forum welcome said, then I found a thread and posted my issue there” – So that may need to be clarifying too

      • Ipstenu (Mika Epstein) 7:11 pm on March 27, 2014 Permalink | Log in to Reply

        Yeah, I think that would be “DO search for existing topics first, they may already have the solution” – Because we DO want you to search first so we don’t repeat the same things over and over :)

    • kmessinger 6:22 pm on March 27, 2014 Permalink | Log in to Reply

      I would put all the do’s first in each section.

    • Andrew Nevins 6:26 pm on March 27, 2014 Permalink | Log in to Reply

      What about a bit saying “Do help volunteers help you. If someone asks you a question that you may find pointless it may turn out to be an important step in a debugging process” – You know when people complain that you’re asking pointless questions

    • Kathryn Presner 8:22 pm on March 27, 2014 Permalink | Log in to Reply

      Don’t post anything you may not want found in Google searches in the future, such as personal information, your phone number, your client’s name, etc.

      Don’t ever post login details for your site.

    • Kathryn Presner 8:24 pm on March 27, 2014 Permalink | Log in to Reply

      Do take the time to do some basic troubleshooting before posting. That may include deactivating all plugins, switching to a default theme temporarily, looking at your site in a different browser, or anything else that might rule out culprits for your issue.

    • TheHandOfCod 10:46 pm on March 27, 2014 Permalink | Log in to Reply

      At the risk of being controversial I would say that list is too long. IMO people will read the first set and then move on. I would suggest that the people who come here are generally looking for help and often(maybe) want to get that help asap. I would therefore suggest you cut the list down to the 10 most heinous crimes and then have a disclaimer saying that there are more with a link to a more detailed post on etiquette. The top 10 being 5 Do’s and 5 Don’ts ?

      • Jan Dembowski 11:44 pm on March 27, 2014 Permalink | Log in to Reply

        I agree with keeping it concise when possible but it’s not about heinous crimes (I need to use the phrase at work tomorrow, thanks 😉 ).

        I mean, you could summarize this as

        • Do provide the level of support and help that you would want
        • Don’t respond in a way that you wouldn’t like

        But that wouldn’t make for a useful list…

    • Chris Olbekson 4:16 am on March 28, 2014 Permalink | Log in to Reply

      Nice list. I would also love to see a link to an article Michael wrote a few years ago which should be must reading for helpers and helpees. http://michaelbox.net/2012/05/welcome-aboard-support-channels/

    • Andrew Nevins 7:40 am on March 28, 2014 Permalink | Log in to Reply

      Will this list be links that go to other parts of the page in more detail?

    • Adrian Houle 5:18 am on April 10, 2014 Permalink | Log in to Reply

      I subscribed to the email list. Will i be notified of the meeting?

  • Ipstenu (Mika Epstein) 11:07 pm on December 18, 2013 Permalink |  

    Trac Tickets for 3.8 (AKA: Support Works Backwards) 

    I made a ticket for a weird caching issue: https://core.trac.wordpress.org/ticket/26676

    I think the ONLY other one that’s jumping out now is the plugins page is blank. If you’ve managed to solve that one (all I can see is ‘host fixed it!’), reply here. This is probably related to @andrea_r‘s comment: https://make.wordpress.org/support/2013/12/wherefore-the-wtfbbq-post/#comment-157012

    • Samuel Wood (Otto) 11:15 pm on December 18, 2013 Permalink | Log in to Reply

      This is a problem that was found in the forums and turned out to be a legitimate core bug:


      Warning signs: People (or plugins/themes) using the pre_get_posts filter combined with the is_category() check can trigger the issue.

      It is a regression from 3.7 behavior, so I think that it will probably be fixed in 3.8.1. In the meantime, there is a patch in the ticket.

    • Andrea Rennick 9:58 pm on December 20, 2013 Permalink | Log in to Reply

      ALso seeing issues with people unable to manage widgets. COuld be user error, dunno.

  • Ipstenu (Mika Epstein) 7:46 pm on December 17, 2013 Permalink |  

    Wherefore the WTFBBQ Post? 

    I made a conscious decision not to make one for 3.8. Not because I think the release was perfect, but because there wasn’t enough to make a post. There barely was last time. As long as we here are prepared.

    https://make.wordpress.org/support/handbook/forum-moderator/stock-answers/ has the stock replies, so I think… for the most part we;re going to be alright :)

    • Christine 7:50 pm on December 17, 2013 Permalink | Log in to Reply

      So far 3.8 has been great. I haven’t seen anything blow up or gone awry.

    • Jan Dembowski 8:54 pm on December 17, 2013 Permalink | Log in to Reply

      It’s all good. 😉 There’s a thread or two about the 3.8 admin interface CSS but that seems to be going alright. That was expected since changing the look or styling always gets a small but vocal group of people who don’t like those changes.

      Aside from that it’s been great.

      • Ipstenu (Mika Epstein) 9:32 pm on December 17, 2013 Permalink | Log in to Reply

        “I don’t like MP6″ and “I don’t like TwentyFourteen” are not ‘bugs’ so they don’t really deserve to be made much of in this case. Same thing happened in 3.0 and 3.1 when we moved things around.

    • Andrea Rennick 12:09 am on December 18, 2013 Permalink | Log in to Reply

      I actually went looking for this because we’re seeing a few tickets with plugin & widget issues. Like.. things disappearing. No I don’t have enough info yet.

  • Ipstenu (Mika Epstein) 5:26 pm on October 17, 2013 Permalink |
    Tags: omgwtfbbq   

    Lets Get Ready for 3.7! 

    Normally I do an OMGWTFBBQ post. Here’s everything in my current draft, ready for editing by everyone!

    The first section is ‘Stuff we, as mods, should be aware of.’ The second is the post itself :)

    Major changes

    Auto Upgrader
    * How to disable
    * In order for Automatic Updates to be enabled, there are a few simple requirements:
    * If the install uses FTP for updates (and prompts for credentials), automatic updates are disabled
    * If the install is running as a SVN or GIT checkout, automatic updates are disabled
    * If the constants DISALLOW_FILE_MODS or AUTOMATIC_UPDATER_DISABLED are defined, automatic updates are disabled
    * If the constant WP_AUTO_UPDATE_CORE is defined as false, automatic updates are disabled
    * Your WordPress install also needs to be able to contact WordPress.org over HTTPS connections, so your PHP install also needs OpenSSL installed and working
    * Wp-Cron needs to be operational, if for some reason cron fails to work for your install, Automatic Updates will also be unavailable
    * What gets updated?
    * What changed. ONLY changed files!
    * Only for minor releases (3.7 to 3.7.1 but NOT 3.7.1 to 3.8)

    Less Major Changes

    • Better search results
    • Password meter
    • Visual editor (TinyMCE) updated for Internet Explorer compatibility

    Under the Hood

    • New dev tools
    • New author queries
    • Multisite finally has a way to get an array of all sites on the network
    • Better inline documentation
    • Better date sorting in the posts page

    For the post…. (More …)

    • Lorenzo Orlando Caum 5:51 pm on October 17, 2013 Permalink | Log in to Reply

      Hello, I saw the link to this page over on #wordpress-sfd.

      Under the subheading Don’t Panic: it is discussing not posting multiple times. I believe that “Post one” should be “Post once” or “Post one time”

      Further down, there is a sentence about not liking the design of the WordPress Admin design. At the end of that sentence it says “…does not a bug make.” I would go with “does not make a bug.”

      There are some troubleshooting steps just above the subheading Core Changes. One of them covers manual upgrading. In this sentence “…download a fresh copy of the latest.zip file of 3.5.” Should 3.5 be 3.7?

      Under the subheading Not a Bug, it is talking about auto-updates. I think that “migitage security issues” should be “mitigate security issues”

      Hope this helps!


    • Ipstenu (Mika Epstein) 5:55 pm on October 17, 2013 Permalink | Log in to Reply

      • once -> once :)
      • “…does not a bug make.” is a kind of a joke, it’s common in US English to say it that way.
      • Yes, 3.5 -> 3.7 *facepalm* I copy paste this sometimes.
      • Mitigate fixed!
    • Amy Hendrix (sabreuse) 7:51 pm on October 17, 2013 Permalink | Log in to Reply

      Twenty Fourteen is scheduled for 3.8 (yeah, I know, it’s in trunk for anyone running nightlies etc, but it won’t be seen when people upgrade to 3.7 on normal installs)

    • Nick Halsey 8:33 pm on October 18, 2013 Permalink | Log in to Reply

      Switch to the Twenty Eleven theme should probably be updated to Thirteen or at least Twelve, since new installs don’t even get Eleven as of 3.6.

    • Daedalon 7:22 pm on October 23, 2013 Permalink | Log in to Reply

      “While you may disagree with this rational,”

      I believe there’s an e missing from the end of “rationale”.

    • Daedalon 7:23 pm on October 23, 2013 Permalink | Log in to Reply

      “While you may disagree with this rational,”

      I believe there’s an e missing in the end of “rationale”.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc