WordPress.org

Ready to get started?Download WordPress

Support Everything WordPress

Updates from November, 2012 Toggle Comment Threads | Keyboard Shortcuts

  • Siobhan 9:20 pm on November 27, 2012 Permalink | Log in to leave a Comment
    Tags:   

    Hi all!

    I’ve made a list of all of the things in the codex that I think need to be updated for WordPress 3.5: http://make.wordpress.org/docs/2012/11/27/if-all-goes-to-plan-wordpress-3-5-will/

    It’s in progress so please feel free to add to it.

    But what’s most relevant, is that some of the updates will be relevant to the user manual too. We’re already aware of the updates to media, but there have been a number of changes to the Settings as well. I’m not sure if they were considered when we created the manual.

     
  • Ipstenu (Mika Epstein) 5:49 pm on November 26, 2012 Permalink  

    3.5 Master List Post 

    What follows this is the boilerplate I use for the ZOMG! WordPress Upgrades Broke me!

    What I’d like is if you guys can think up quirks with 3.5 (plugins and themes you know won’t work, or have to be handled special) or other massive changes, that we collect them all here. Then I’ll craft the ‘final’ release.

    (More …)

     
  • Ipstenu (Mika Epstein) 11:56 pm on November 21, 2012 Permalink | Log in to leave a Comment  

    No Meetup Tomorrow 

    If everyone wants to meet and hang out, they can, but the US folks (hi) will be off eating turkey. :D

    For next week, since 3.5 RC should be coming out soon, everyone should think about putting the RCs on their site and helping us test ;) After all, you’re support! You gotta know what’s coming. Also I’ll be putting up the OMGWTFBBQ! post for review, and suggestions, early next week, and I’d love it if everyone came up with a list of weird things in 3.5.

    Oh and don’t forget to update your plugin readmes with ‘compatible up to…’ if they are.

     
    • Ipstenu (Mika Epstein) 12:06 am on November 22, 2012 Permalink | Log in to Reply

    • esmi 4:29 pm on November 22, 2012 Permalink | Log in to Reply

      I think we should push for a similar “compatible with” for themes – especially since there’s no mandatory obligation to support older versions of WP in the theme review guidelines. I seem to have seen quite a few forum topics where people with old versions of WP are installing new themes. wp_get_theme() seems to be the real killer.

      • Ipstenu (Mika Epstein) 4:30 pm on November 22, 2012 Permalink | Log in to Reply

        If it was as easy to update that in themes ( @chipbennett is it? ) I would, but IIRC you can’t just edit the readme like you can with plugins.

        • Chip Bennett 3:13 pm on November 23, 2012 Permalink | Log in to Reply

          No, it’s not. The infrastructure is entirely different. I’d love to see a way to update Theme metadata easily (such as compatible-up-to/tested-up-to/requires), but how to implement something like that would be a question for @otto42

    • esmi 5:43 pm on November 23, 2012 Permalink | Log in to Reply

      Maybe we could persuade him to add something to the theme template tags – maybe something along the lines of Min WP Version? There’s already something very similar being used for child themes to indicate the appropriate version of the parent theme.

  • Jen Mylo 6:50 pm on November 19, 2012 Permalink | Log in to leave a Comment
    Tags: Documentation, teams   

    Per discussions at the community summit, Documentation is now a separate official contributor group. @raggedrobins will be the acting team rep. Have at it, folks!

    http://make.wordpress.org/docs/

     
  • Ipstenu (Mika Epstein) 2:20 pm on November 19, 2012 Permalink | Log in to leave a Comment  

    3.5 Help Text Needs Our Help! 

    From @drewapicture:

    Hi folks,

    It’s that time of the cycle again to audit the Help text. The trac ticket for 3.5 is here: #22451http://core.trac.wordpress.org/ticket/22451

    I’ve already combed through every single-site Dashboard page and submitted grouped patches last week. But now I need your help! If anybody is willing and able to go through and review some or all of them, I’d be grateful for the collaboration and extra eyes.

    So please, hop in and while you’re at it, start thinking about what goes weird in 3.5 :) More on that later!

     
  • Siobhan 12:48 pm on November 16, 2012 Permalink | Log in to leave a Comment  

    Handbooks: Teams and Templates 

    Over the past few weeks I’ve been getting in touch with people who I’d like to see involved with the handbooks. I’m going to continue to do this over the next few weeks as we get started on working. I just wanted to give you an update on teams and templates.

    Teams

    Here’s who we’ve got so far:

    [update: am adding more people to teams as they contact me]

    Core

    Daniel Bachuber
    Japh Thomson

    Support
    Andrea Rennick
    Scott Basgaard
    Christine Rondeau
    Dean Robinson
    Phil Erb
    Mika Epstein

    Plugin Dev
    Pippin Williamson
    Dougal Campbell
    Tom McFarlin
    Thomas Griffin
    Maor Chasen
    Justin Sainton

    Theme Dev
    Chris Reynolds
    Tammie Lister
    Rachel Baker
    Jay Hoffman

    Theme Review
    (no one so far :( )

    Events

    Brandon Dove
    Ryan Imel
    Aaron Jorbin
    Sara Rosso

    Mobile
    (no one so far :( ) Except Isaac?
    Abhishek Ghosh

    Polyglots

    Zé Fontainhas

    Docs

    Andrea Rennick
    Christine Rondeau
    Dean Robinson
    Me!

    These things span all of the handbooks:

    General help

    Kari Leigh Marucchi
    Abbie Sanderson

    UX/UI
    Shane Pearlman
    @helenyhou or other person from UI
    Mel Choyce

    Accessibility
    Esmi

    We definitely need more people so if you know of anyone please send them this post. Or drop me an email: siobhan at wordsforwp dot com and I’ll get in touch with them personally.

    Template

    After having chats with different people in different contributor groups and reviewing the material that we have already, I’ve come up with a very loose schema that I think will work across the handbooks.

    Introduction

    Requirements
    All of the things you need to start contributing to this area

    Tools
    Useful tools to get started

    Pathways
    The different ways that you can get involved in this area

    Tutorials & Guides
    Practical guides to doing what you need to do

    Reference
    Glossaries etc (maybe useful email addresses etc?)

    Best Practice
    Coding Standards, Best Practices, UI Guidelines, UX Guidelines, Accessibility

    Credits
    Lists the contributors to that manual.

    This is a starting point, so please do make suggestions based on your own experience. There’s always a danger when you’re creating something generic that you lose the specific, which is why I’ve tried to keep the schema as loose as possible.

    Some other things

    I have a chat with Brad and Pippin about the plugin development handbook. They had some great ideas to keep in mind:

    1. We should use practical examples of code that will help people to learn
    2. We need a syntax highlighter of some description. We did discuss using Gists but then our docs are reliant on Github and that not something we want

    I think there may have been other things so Brad and Pippin if I’ve forgotten something please chime in. Soon we’ll get into discussions about the particularities of specific handbooks I’m sure, but I wanted to note these here for the record

    Next Steps?

    Next steps are as follows:

    1. Come up with schedule and workflow – I’ve got some stuff written down on this but will save for another post! Let’s aim for long term – we don’t want to burn ourselves out.
    2. Schedule some google hangouts with contributor groups and volunteers to discuss best practices
    3. Develop table of contents

    Okay, phew! That was a long post again. Let me know if I’ve missed anything, please do add any suggestions or tell me where things can be improved.

    Most importantly, spread the word. This is an exciting project in its beginning stages and over the next year we’ll be able to create something we’re genuinely proud of and that gets more people contributing to WordPress.

     
    • Siobhan 12:54 pm on November 16, 2012 Permalink | Log in to Reply

      Note to self: handbook translation. Bother @vanillalounge :D

    • toscho 1:07 pm on November 16, 2012 Permalink | Log in to Reply

      What would be the content of Support?

      • Brian 1:09 pm on November 16, 2012 Permalink | Log in to Reply

        Curious as well.

        • Siobhan 1:43 pm on November 16, 2012 Permalink | Log in to Reply

          Support already has the beginnings of a handbook here: http://make.wordpress.org/support/handbook/

          I guess it would include things like:

          Requirements – what you need to get started – level of knowledge. Encourage people to help answer questions even if they feel that they are still beginners.

          Tools – bbPress, and anything else that people use.

          Pathways – diving in and getting started. Finding an open support request, sorting the support requests to get unanswered ones. eventually becoming a mod, responsibilities etc.

          Tutorials & Guides: bbPress basics, How to Help, (other stuff from here: http://make.wordpress.org/support/handbook/)

          Reference – collection of stock responses. List of moderators

          Best Practice – support best practices. Dealing with problem users.

          Credits – all the awesome people who wrote the beautiful manual.

          That is totally off the top of my head. I’ve never actually provided support, am just in awe of others who do it. But I guess those would be the kinds of things.

    • karmatosed 1:24 pm on November 16, 2012 Permalink | Log in to Reply

      If it helps to fill spaces I can move into the theme review section – maybe that spreads the resources a little?

    • Andrea Rennick 1:53 pm on November 16, 2012 Permalink | Log in to Reply

      Put me down for Support & Docs.

    • Tom Auger 2:06 pm on November 16, 2012 Permalink | Log in to Reply

      As output from WPCS I have been working with Alex King on the Community Dev involvement piece. I think this could probably fit somewhere within the scope of Pathways, though perhaps our scope is a little larger. I would love to find a home for the work we are doing – this sounds like it.

    • Phil Erb 3:02 pm on November 16, 2012 Permalink | Log in to Reply

      I’ll also help out with Support.

    • Rachel Baker 3:21 pm on November 16, 2012 Permalink | Log in to Reply

      Shouldn’t Theme Dev & Theme Review be together?

      It seems to be that these handbooks would have much overlap, and keeping the content together would make it easier for them to be accurately maintained in the future.

      • christine 3:29 pm on November 16, 2012 Permalink | Log in to Reply

        I agree with Rachel. In fact developing themes without knowing about theme review and guidelines is not great.

      • kwight 3:58 pm on November 16, 2012 Permalink | Log in to Reply

        +1. It would be great to see theme review guidelines and best practices become the norm for theme development in general. The specifics of submitting to /extend/themes would become a footnote, instead of a frustrating new process for devs.

      • Siobhan 6:17 pm on November 16, 2012 Permalink | Log in to Reply

        I did think about putting them together, so here’s a bit of the reasoning behind why I think it’s a good idea to separate them.

        The aim of the handbooks is to get people to contribute to WordPress. They should make it as easy as possible. So rather than being comprehensive manuals that deal with every nuance of a contributor group, they should answer specific questions. For example:

        1. how do I contribute to WordPress core?
        2. how do I create a plugin for the repository?
        3. how do I help out on the support forums?

        When it comes to themes, I don’t think a single handbook that encompasses theme development and theme review is going to be as useful to users. Too much information is a barrier to learning. If someone wants to develop a theme, of course it’s useful for them to know how the theme review process works, but it’s not essential to them creating that theme. What they need to know is how to build a theme suitable for the repository. They shouldn’t have to filter through information about how the theme review team works.

        The theme review manual will be focused on the practicalities of reviewing themes for the WordPress repository. It should be focused on getting people to the point of “hmmm… I’d like to review themes” to actually reviewing themes. They should already know about theme development, and if they don’t we can direct them to the theme dev handbook. (this raises an interesting question about what level of knowledge we assume for each contributor group – i.e. for theme review do we assume that people can develop themes, for plugins do we assume that they are already experts in PHP? That’s something we’ll need to discuss around each manual).

        So:

        The theme development handbook will answer the question “how do I develop a theme for the WordPress theme repository?”

        The theme review handbook will answer the question “how do I review themes for the repository?”

        People don’t read documentation, so I think it’s important we give them what they need to achieve what they want to do, and nothing more. We can link to additional information, whether that’s in the codex or other manuals. After all, the handbooks will be one element of getting involved. Contributors are going to learn as more by getting involved with projects, hanging out in IRC chat rooms, and actually doing.

        Does that make sense? For the time being I’d like to conceive them separately. However, when it comes to creating the table of contents we may decide that there is a ridiculous amount of overlap and they should be merged. My concern with that is that by merging them we’re are conflating two different ways of getting involved with WordPress and they may lose their focus.

      • @mercime 8:50 pm on November 19, 2012 Permalink | Log in to Reply

        I agree with Rachel, Christine and Kwight. Theme development without knowledge of Theme Review rules/process == rejected theme.

    • Mel Choyce 4:28 pm on November 16, 2012 Permalink | Log in to Reply

      I started compiling/throwing together some UI guidelines a little while back: https://docs.google.com/document/d/1ZWPeUSFVYlMxClmHFjuAXuekXcZsLso49G3bDRquHcs/edit It’s kind of fallen to the wayside, but I’d be interested in continuing.

    • Justin Sainton 6:28 pm on November 16, 2012 Permalink | Log in to Reply

      Feel free to add me to plugins!

    • Abhishek Ghosh 8:42 pm on November 17, 2012 Permalink | Log in to Reply

      Umm, I am raising hand for Mobile and Theme Review. Theme Review needs 3-4 neutral peoples. Officially may be @raggedrobins you can keep yourself in the list.

      • Siobhan 6:42 pm on November 19, 2012 Permalink | Log in to Reply

        Thanks! Will add you to Mobile if that’s okay. I will probably add myself to Theme Review :)

    • Ipstenu (Mika Epstein) 4:45 pm on November 18, 2012 Permalink | Log in to Reply

      I’m in for Support (heh). And if you need a hand post-reviewing the Plugin one for ‘from the review team’s perspective’ I should be able to.

      Really we should all do ONE and no more than that, if possible. Otherwise we’ll all burn out :D

      • Siobhan 6:44 pm on November 19, 2012 Permalink | Log in to Reply

        Will add you to support :)

        I agree on the only one manual thing, particularly on the bigger ones – i.e. core, plugins, themes, mobile etc.

        Support and Docs should be pretty thin.

        I’ll also add you for reviewing the plugin one.

    • Carrie Dils 8:09 pm on November 19, 2012 Permalink | Log in to Reply

      Not sure where I fit in (Support or Docs?), but I’d like to jump in and help (Andrea made me do it). I’m probably most useful with reviewing, editing, or tutorials.

      • Siobhan 2:12 pm on November 20, 2012 Permalink | Log in to Reply

        We’d love to have your help! Either Support or Docs would be great. I’m also getting people to help with general editing and proofreading.

    • Isaac Keyet 8:56 pm on November 21, 2012 Permalink | Log in to Reply

      @mrroundhill, @koke, and @daniloercoli will help write the Mobile handbook. I’ll help out as needed as well, but these guys are the lead devs for our main app projects. We discussed the handbook in this week’s mobile dev chat, summary coming to make/mobile shortly.

    • @mercime 4:32 am on November 28, 2012 Permalink | Log in to Reply

      I can help out in Theme Development and Theme Review

    • curtismchale 9:30 pm on December 11, 2012 Permalink | Log in to Reply

      I could jump in on Theme Review and Mobile.

    • Siobhan 2:39 pm on December 21, 2012 Permalink | Log in to Reply

      Everyone: please see updates to this on the docs blog:

      http://make.wordpress.org/docs/2012/12/21/plugin-and-theme-developer-handbooks-schedule/

      http://make.wordpress.org/docs/2012/12/21/best-practices-for-handbooks/

      http://make.wordpress.org/docs/2012/12/21/contributor-handbooks-schedule/

      FYI: if you’re volunteering for a contributor handbook, you should already be a contributor in this area. Otherwise it might get complicated writing the docs!

  • Ipstenu (Mika Epstein) 11:51 pm on November 15, 2012 Permalink  

    Is your Forum ID a company rep account? 

    When you use the forums, are you doing so as your company?

    Let me know your forum ID and I’ll make your Title “Company Rep.” (or anything else officialish you want). This way folks in the forums can see you’re legit :) And yes, I’ll check on you guys first ;)

     
    • Pippin 12:36 am on November 16, 2012 Permalink

      I’d love to use “Pippin’s Plugins” :)

    • masonjames 12:39 am on November 16, 2012 Permalink

      We have a few on our staff who help out on occasion. Would you prefer them to leave a comment here or contact you via a different method?

      Also, hey Pippin!

    • Lee 7:31 am on November 16, 2012 Permalink

      Hi – great idea, but how about a more blanket change – defaulting the user’s description to “Plugin Author” automatically if they’re the author of the plugin that that forum relates to? Possible? Useful?

      • Ipstenu (Mika Epstein) 3:16 pm on November 16, 2012 Permalink

        If I could automate it, I would ;) Since that’s a bit beyond what we can do (it’s on our list of forum improvements now), and since not everyone actually posts in the right place, I figured a change to what you guys want will inspire some people ;)

        Yes, that’s my evil ploy. Get you all helping outside of your plugins/themes threads and people will go “Oh, she writes plugins. Maybe she kinda knows her stuff.” It should help (I hope) the credibility issue.

      • Brandon Kraft 3:16 pm on November 16, 2012 Permalink

        The only thing I’d worry about is if I post in a different author’s plugin’s forum having “Plugin Author” would be confusing. If there was a way to highlight that the poster was *that* plugin’s author would be nice, though.

        • Ipstenu (Mika Epstein) 4:38 pm on November 16, 2012 Permalink

          That got me to think of an idea. I passed it on to Otto. If it’s what I think it is, it’s possibly very trivial. Of course, I’m often wrong ;)

    • Brandon Kraft 3:14 pm on November 16, 2012 Permalink

      Would you be so kind to add “Coffea Web Services” to mine? User kraftbj. Much appreciated!

    • roblagatta 4:36 pm on November 16, 2012 Permalink

      Hi there Mika. Thanks for the offer here; I’d love to have my account on the dot-org forums (roblagatta) tied to the Modern Tribe brand. If there were a way to just get “Modern Tribe Support” added (and the “Slow down!” limitation removed) it would be fantastic.

      Let me know if you need anything else from me to make this happen. Thanks again.

      • Ipstenu (Mika Epstein) 4:39 pm on November 16, 2012 Permalink

        Your wish is granted :) (I’ve been removing the Slow Down! limit too for folks who do support. That always annoyed me when I tried to help ;)

        • roblagatta 4:45 pm on November 16, 2012 Permalink

          That is fantastic! Thanks so much for the quick turnaround on this Mika. I definitely appreciate the removal of the Slow Down as well (in my blog post recently I noted that as a time sink for me too).

          Just got word that Shane, Peter & Reid (the principals of Modern Tribe) would like to receive this as well. Is that possible, to give them the “Modern Tribe” – without “Support” – label? Their dot-org names are shanepearlman, peterchester and reidpeifer.

          Let me know if that’s possible. Sorry I didn’t do this in my first request, and thanks again.

          • Ipstenu (Mika Epstein) 5:27 pm on November 16, 2012 Permalink

            The field is free-form text, so if you wanted to be Modern Tribe Monkey Manager, that would work too ;) (I mean come on, I’m Half-Elf Support Rogue…)

            Done :D

    • roblagatta 6:39 pm on November 16, 2012 Permalink

      Awesome! If I had more creativity I’d go with something cool or otherwise unique for the name there…but I’m boring :)

      Thanks again, Mika.

    • aecnuorg 9:08 pm on November 16, 2012 Permalink

      Greetings :-)

      Handle aecnuorg – authority WPMU Dev Support Staff

      Joe :-)

    • Timothy Bowers 9:25 pm on November 16, 2012 Permalink

      Hey there.

      gmax21 = WPMU DEV

      Cheers :)

      • Ipstenu (Mika Epstein) 9:28 pm on November 16, 2012 Permalink

        Do you want WPMU Dev Support Staff like Joe? I think that might lessen the confusion with the formerly known as WPMU Multisite :/

    • pcwriter 9:48 pm on November 16, 2012 Permalink

      Hey Mika,

      Handle = pcwriter
      Auth = WPMU Dev Support Staff

      Thanks!

    • James 12:06 am on November 17, 2012 Permalink

      Hey Mika,

      Cool idea!

      These days we generally go by ‘WPMU DEV’ rather than ‘WPMU Dev’ (I know how much you guys like correct capitalisation ;) and we’re more than happy to have stuff setup as ‘WPMU DEV Support Staff’ or whatever you prefer (there are a bunch of us and more coming) – although I don’t see how ‘WPMU DEV’ would be at all confusing these days, it’s been WordPress Multisite for aeons now.

      BTW, I’m user ‘Farms’, but not support staff, can I be ‘WPMU DEV CEO’ or something?

      Cheers, James

      • Ipstenu (Mika Epstein) 12:10 am on November 17, 2012 Permalink

        I just went by what your other guys typed in :D

        I can easily make them all ‘WPMU DEV Support Staff’

        although I don’t see how ‘WPMU DEV’ would be at all confusing these days, it’s been WordPress Multisite for aeons now.

        Come, my friend, and see how many posts a day I have to correct people in ;)

      • Ipstenu (Mika Epstein) 12:14 am on November 17, 2012 Permalink

        Oh and done ;) (Sure you didn’t want WPMU DEV God?) I kid!

    • PC - WPMU DEV 5:27 am on November 17, 2012 Permalink

      Hey Mika,

      pranayachaudhary – WPMU DEV Support Staff

      Cheers, PC

    • Tom Willmot 6:27 pm on November 22, 2012 Permalink

      Hey Mika,

      Could we get all our staff listed as Human Made?

      Our handles are joehoyle, mattheu, tcrsavage & willmot.

    • Sol 8:10 pm on November 28, 2012 Permalink

      Hey Mika, could the AddThis Team get “AddThis Samurai” (I was talked out of AddThis Ninja). Our handles are:

      srijith.v, solchea, _mjk_, addthis_paul, joesullivan, vipinss

      Thanks.

      • Ipstenu (Mika Epstein) 9:19 pm on November 28, 2012 Permalink

        Samurais support with honor. Much like Kligons. ;)

        Done. Also lifted the ‘Slow down!’ flag.

        • Sol 7:32 pm on December 7, 2012 Permalink

          Thanks. We will serve with honor :-)

    • ellbristow 7:53 am on March 4, 2013 Permalink

      Hey Mika,

      I’m a new guy at WPMU…

      handle = ellbristow
      title = WPMU DEV Support Staff

    • aristath 5:02 pm on March 4, 2013 Permalink

      Hey Mica, that’s great!

      Add me too…

      handle= aristath
      title = WPMU DEV Support Staff

      Thanks! :)

    • tom.eagles 11:18 pm on March 18, 2013 Permalink

      Hi Mika

      Could you set me up also please

      Handle = Tom Eagles
      Auth = WPMU Dev Support Staff

      Kindest Regards

      Tom

      p.s. you normally see me around using the plugin authors user id, but we want to keep the two separate

      • Ipstenu (Mika Epstein) 12:10 am on March 19, 2013 Permalink

        Done :) Your handle is tom.eagles BTW ;)

        • tom.eagles 2:56 pm on March 22, 2013 Permalink

          Hi Mika

          Still not working as far as i see would you mind checking again please

          Kindest regds

          Tom

          • Ipstenu (Mika Epstein) 2:57 pm on March 22, 2013 Permalink

            http://wordpress.org/support/profile/tomeagles

            Is too. If that isn’t your ID, you gotta actually give me the REAL profile :)

            • Timothy Bowers 3:46 pm on April 8, 2013 Permalink

              Thanks Mika, Looks to be working from my end for Tom :)

              Just wondering though, we have a number of staff and they are assisting on a number of posts relating to our plugins from WPMU DEV however none can mark those threads as resolved.

              From the project pages it means unless the original poster marks resolved the stats on the project page will continue to show as “0 of X support threads in the last two months have been resolved”

              I know the work around for now would be to use the main author account but that kinda defeats the point of having these markers for rep accounts.

              Is there anything which could be done to allow our own reps to mark tickets resolved for our own plugins? Or maybe something planned?

              Thanks Mika.

            • Ipstenu (Mika Epstein) 4:58 pm on April 8, 2013 Permalink

              Timothy – Right, only the plugin author can do that. The only work-around would be to give you all Mod Access to the forums, which isn’t going to happen right now. We know it’s a problem, but we don’t have a fix yet. It’s something we’re kicking around, to try and find a better solution than using your author account.

              I do wonder if you added those reps to the plugins if they’d be able to edit it then, but that’s also not a great idea, eh?

            • Timothy Bowers 7:42 pm on April 8, 2013 Permalink

              Hey again.

              Sorry to backtrack, I see what Tom means now. He refers to when he posts:

              http://wordpress.org/support/topic/credit-card-payment-via-paypal-confirm-statement-misleads-users?replies=2

              Where as it works on mine – Shows the custom rep title:

              http://wordpress.org/support/topic/custom-css-12?replies=3

              Probably something we’re missing. :)

              Anyway, good to see you’re kicking ideas around. I’d love to see something happen here. :)

              I don’t know what you’re planning or if you’re open to input, but it would be cool if the plugin author could login, enter other staff usernames, maybe the custom title – both could be moderated for abuse if needed and then those accounts be able to close/resolve tickets – Maybe it lists them as a moderator of those plugins from the project pages.

              I guess by adding those staff to the to the plugin it would give them the same rights and access as being the main author account?

              Thanks Mika! :)

            • Ipstenu (Mika Epstein) 8:02 pm on April 8, 2013 Permalink

              Seriously….

              http://cl.ly/image/1k1b0I401417

              It works for me. Flush your cache?

            • Timothy Bowers 8:04 pm on April 8, 2013 Permalink

              hmm.. It does now and I didn’t flush cache.

              It works that’s all that matters. Sorry to be a pest on that.

              Anyway, thanks for listening Mika.

              Have a great week! :)

    • m0nty 7:41 pm on April 13, 2013 Permalink

      hey mika

      http://profiles.wordpress.org/m0nty/

      Auth: WPMU DEV Support Staff

      cheers

    • James Laws 3:21 pm on May 2, 2013 Permalink

      I would love to have The WP Ninjas for both jameslaws & kstover. We are obviously active in our plugin support forums and I try to hop on over to the regular forums whenever I get a chance. :)

    • Marvie Pons 5:50 pm on May 2, 2013 Permalink

      Hi Mika, could you add “TutsKid Ninja” to Users: marviepons & Triptripper? Thanks!

    • Marcus 11:41 am on May 3, 2013 Permalink

      This is very helpful… people get confused about who’s an ‘official’ supporter.

      Could you please add ‘Events Manager Support’ to caimin_nwl and angelo_nwl?

      • Ipstenu (Mika Epstein) 2:52 pm on May 3, 2013 Permalink

        Marcus, is this for a plugin? When answering posts in the plugin threads, they should already be getting green tags saying Plugin Author or Plugin Contributor. Just add them to the readme and they’ll show up :)

        • Marcus 4:56 pm on May 3, 2013 Permalink

          Thanks for the reply, yes, it is for a plugin.

          I’m aware of these readme tags, but since they’re not acutal developers, they’re just there to provide support, I’d rather they have these specific names instead to avoid confusion. That option was my last resort, esmi kindly pointed me here.

          I’m ok with just the green tag on my own account, that works pretty well for me :)

          • Ipstenu (Mika Epstein) 5:03 pm on May 3, 2013 Permalink

            I understand the confusion, however in this case, since these people (and you) are plugin specific, the right place is to list them as Author.

            Maybe @otto42 can change that ‘Contributors’ and not ‘Author’ on the sidebar (display only, not change the readme), and then it would be more clear?

            • Marcus 5:22 pm on May 3, 2013 Permalink

              Ideally that’d be possible too! Rather than green, something like a yellow label would be great (even for other plugins that have ‘known’ users to pitch in on the forums regularly)

              Since they are employees of the company NetWebLogic, I still think we should apply for this. If you don’t want to make it plugin-specific, how about ‘NetWebLogic Support’ instead? I’d still prefer my original suggesiton, but this would be my second option.

            • Ipstenu (Mika Epstein) 10:58 pm on May 3, 2013 Permalink

              Can’t make ‘em separate colors, but ‘NetWebLogic Support’ is better since they are company and not just ONE plugin. Done :) (you should still list them as Authors in the readme, so they get extra credits :)

            • Marcus 5:38 pm on May 3, 2013 Permalink

              I may be confusing things here… That yellow comment may be me getting confused… don’t know if adding contributors in the readme results in a green ‘Plugin Contributor’ tag, I assumed they all said ‘Plugin Author’ haven’t seen that label on the forums before.

              They’re company reps though, so my second point above still stands.

            • Marcus 11:28 am on May 6, 2013 Permalink

              Thanks Mika! Thinking about it your suggestion may work better actually (and am thinking about the readmes too)! I’m dusting off a few older plugins that may see them supporting too… then it definitely makes more sense.

    • Michael Copestake 3:50 pm on May 30, 2013 Permalink

      Hi Mika,

      I’ve just started at WPMU DEV so could you set my title too please?

      handle = michael-copestake
      title = WPMU DEV Support Staff

      You can see me here: http://premium.wpmudev.org/#teaser-about

      Thanks!

    • Mike 4:18 pm on May 30, 2013 Permalink

      That was quick! Thanks :)

    • Tom Willmot 2:13 pm on July 22, 2013 Permalink

      Hey Mika,

      Any chance you add stubbs123, noel_tock, pauldewouters & danielbachhuber to Human Made please :-)

    • Jack Kitterhing 8:03 am on July 24, 2013 Permalink

      Hi Mika,

      Could you set my title too please? :)

      handle = jack-kitterhing
      title = WPMU DEV Support Staff

      You can see me here: http://premium.wpmudev.org/#teaser-about

      Cheers
      Jack.

    • acub 11:25 pm on September 30, 2013 Permalink

      Hello, I’d like “Customizr Theme Support” for my account. I am one of the 2 persons granted the permission to post snippets on the theme’s official page. Here’s my author page on that website: http://www.themesandco.com/author/andrei/ (we just started it a week ago). I’d like to state we don’t charge anything for our support and we don’t know each other outside the forums. I personally am doing it because I love the theme. I’m also active on the theme’s WP support forum.

      • acub 11:26 pm on September 30, 2013 Permalink

        • I am one of the 2 persons granted the permission to post snippets – besides the theme author, that is.
      • Ipstenu (Mika Epstein) 11:52 pm on September 30, 2013 Permalink

        That’s … a little bit of an edge case. You’re not hired by them, you’re just a volunteer. I was intending to do this for companies who have a bit of a need to prove they’re part of the company.

        • acub 12:25 am on October 1, 2013 Permalink

          As of this point (and to the extent of my knowledge) Customizr is free and is trying to stay free. But its popularity makes it impossible for the theme author to answer all support requests, so we do help when and if we can. We’re trying to build a snippets database to answer most of the possible questions. I have found out about this thread from here http://wordpress.org/support/topic/lost-everything-when-updated?replies=17 , but if you’re saying this wasn’t intended for cases like mine or rdell’s, it’s ok. We’ll keep on doing our bits anyway. Thank you.

        • acub 12:27 am on October 1, 2013 Permalink

          On the other hand, if we need the theme author to vouch for us, I’m pretty sure it won’t be a problem. And I guess it’s fair to ask for that.

    • rdellconsulting 7:54 am on October 1, 2013 Permalink

      I’m with @acub on Customizr and had a little problem on the above thread last night! Although not employees of @nikeo, we dedicate a lot of time to the Theme. It was @esmi who directed us here for your kind consideration ;)

    • Bappi D Great 7:08 pm on October 2, 2013 Permalink

      Hey Mika,

      I’m a new guy at WPMU…

      handle = bappidgreat
      title = WPMU DEV Support Staff

      You can see me here http://premium.wpmudev.org/#teaser-about

    • David 8:53 pm on November 7, 2013 Permalink

      Could you set my title too please? :)

      handle = ugotsta
      title = WPMU DEV Support Staff

      You’ll see me here: http://premium.wpmudev.org/forums/profile/dmallonee

    • WPMU DEV 4:00 pm on December 18, 2013 Permalink

      Hi Mika,

      Could you set my title too please? :)

      handle = vinod-dalvi
      title = WPMU DEV Support Staff

      You can see me here: http://premium.wpmudev.org/forums/profile/mozillavvd

      Thanks,
      Vinod Dalvi

      • WPMU DEV 4:03 pm on December 18, 2013 Permalink

        Hi Mika,

        Please ignore it as it is replied using wrong account.

        Thanks

    • Vinod Dalvi 4:11 pm on December 18, 2013 Permalink

      Hi Mika,

      Could you set my title too please? :)

      handle = vinod-dalvi
      title = WPMU DEV Support Staff

      You can see me here: http://premium.wpmudev.org/forums/profile/mozillavvd

      Thanks & Regards,
      Vinod Dalvi

  • Ipstenu (Mika Epstein) 10:01 pm on November 15, 2012 Permalink | Log in to leave a Comment  

    Meetup Recap – Nov 15 

    Apparently DST is hard for more than me!

    Thursdays, 2100 UTC, location #wordpress-sfd

    • 9pm London
    • 4pm US Eastern
    • 1pm US Pacific
    • 2:30am (Friday) Bangalore

    Items of note?

    http://make.wordpress.org/training is live!

    That’s kinda all we have this week. It’s a status quo, however since 3.5 is getting near, I’m going to draft my OMGWTFBBQ forum post here later this week or next week, so we can all write it :D

     
  • Ipstenu (Mika Epstein) 6:15 am on November 14, 2012 Permalink | Log in to leave a Comment  

    Cross posting this link, cause people asked.

    Wanna help with videos?

    http://make.wordpress.org/events/2012/11/13/wordpress-tv-event-video-management/

     
  • Andrea Rennick 10:48 pm on November 8, 2012 Permalink | Log in to leave a Comment
    Tags: Chat,   

    Codex chat 

    During our regular meeting in IRC we discussed some changes to the codex, based on the roundtable discussion at the WordPress Community Summit.

    Before we started ripping things apart, I thought it would be good to look at some stats, if possible, and also to get community input. Because it’s one thing to come up with a good idea, but it’s another to make sure that’s what is needed based on numbers and user feedback.

    So this is basically our gut check. ;)

    To that end, here are the top 40 visited Codex pages in the last month or so:

    /Function_Reference/
    /Installing_WordPress,
    /Template_Tags/,
    /Version_3.4.2,
    /First_Steps_With_WordPress,
    /Class_Reference/,
    /Editing_wp-config.php,
    /Main_Page,
    /Plugin_API/,
    /Theme_Development,
    /Using_Permalinks,
    /Pages,
    /WordPress_Lessons,
    /Glossary,
    /New_To_WordPress_-_Where_to_Start,
    /Moving_WordPress,
    /Giving_WordPress_Its_Own_Directory,
    /Changing_File_Permissions,
    /Child_Themes,
    /WordPress_Backups,
    /Getting_Started_with_WordPress,
    /Using_Themes,
    /Create_A_Network,
    /Changing_The_Site_URL,
    /Roles_and_Capabilities,
    /Introduction_to_Blogging,
    /The_Loop,
    /Blog_Design_and_Layout,
    /Conditional_Tags,
    /Using_Custom_Fields,
    /Formatting_Date_and_Time,
    /Function_Reference,
    /WordPress_in_Your_Language,
    /Template_Hierarchy,
    /Creating_a_Static_Front_Page,
    /Post_Types,
    /Writing_a_Plugin,
    /Template_Tags,
    /Excerpt,
    /Updating_WordPress,

    And for perspective, the top page (function reference) got over 1.9 million hits, while the second page was hit only 280,000 times.

    To me this backs up our earlier conclusion of a divide between users and devs and where they go and what they look for. So the user handbook will likely be well received. Ipstenu made us a shortcode for the Codex so we can start marking pages that will considered for removal and send users to the user manual instead.

    The other thing we talked about, before we go too far, is to create a poll to get feedback on codex reorganization.

    Some suggested poll items:

    • I like the codex just as it is, it need some love!
    • separate user docs from dev docs
    • something else

    Your suggestions for poll options are welcome! Without it turning into an actual poll here… ;)

     
    • JerrySarcastic 12:07 am on November 9, 2012 Permalink | Log in to Reply

      Interesting list. I took a quick pass at categorizing it (user vs. dev) and this is what I came up with:

      Users

      • /Installing_WordPress
      • /First_Steps_With_WordPress
      • /Pages
      • /New_To_WordPress_-_Where_to_Start
      • /Moving_WordPress
      • /Giving_WordPress_Its_Own_Directory
      • /Changing_File_Permissions
      • /WordPress_Backups
      • /Using_Themes
      • /Create_A_Network
      • /Introduction_to_Blogging
      • /Creating_a_Static_Front_Page
      • /Updating_WordPress

      Developers

      • /Function_Reference
      • /Template_Tags
      • /Version_3.4.2
      • /Class_Reference
      • /Editing_wp-config.php
      • /Plugin_API
      • /Theme_Development
      • /Using_Permalinks
      • /Child_Themes
      • /Changing_The_Site_URL
      • /The_Loop
      • /Blog_Design_and_Layout
      • /Conditional_Tags
      • /Using_Custom_Fields
      • /Formatting_Date_and_Time
      • /Template_Hierarchy
      • /Writing_a_Plugin
      • /Template_Tags
      • /Excerpt

      A Little of Both

      These pages have content that is a bit mixed, so there is stuff here for developers and absolute beginners.

      • /WordPress_Lessons
      • /Getting_Started_with_WordPress
      • /Roles_and_Capabilities
      • /Post_Types

      Reference

      Pages that are possibly useful to either group, but not really something that belongs in one or the other exclusively.  More like the reference section at the library?

      • /Glossary
      • /WordPress_in_Your_Language
    • esmi 1:24 pm on November 9, 2012 Permalink | Log in to Reply

      What’s the new shortcode? I missed the early part of the chat and can’t find a reference to this shortcode in the log, At least 1 of my older Codex pages (on the Gallery) needs pulling in preference to the User Manual and I’d like to mark it whilst I remember.

      On a related note, when can we start sending people to the new manual from the forums?

    • Siobhan 5:18 pm on November 9, 2012 Permalink | Log in to Reply

      Polls suggestions:

      Are you:

      1. WordPress user (I use WordPress to run my website/blog)
      2. WordPress builder (I build and customize websites but I don’t write PHP)
      3. Novice developer (learning to write my first plugins/themes)
      4. Intermediate developer (I write plugins and themes and they’re pretty good)
      5. Advanced developer (I dream in PHP)

      What documentation do you currently use (can we do this in order of preference?):

      1. Codex – guides
      2. Codex – references
      3. Tutorials and guides on blogs
      4. Books
      5. Breaking WordPress/plugins/themes and putting them back together
      6. Premium services like WP101
      7. API Documentation

      How useful do you find the WordPress Codex:

      1-10

      What types of documentation/learning do you prefer?

      1. Tutorials
      2. User Guides
      3. Breaking stuff and putting it back together
      4. Screencasts
      5. Code references and API documentation
      6. In-person training

      What improvements to documentation would improve your experience of using or developing with WordPress:

      [open field]

      Have you ever contributed to the WordPress Codex:

      Yes/No

      Would you like to contribute to the WordPress Codex:

      Yes/No

      If you’ve never contributed to the Codex, can you please say why:

      • JerrySarcastic 6:36 pm on November 9, 2012 Permalink | Log in to Reply

        That looks pretty complete, Siobhan. Maybe instead of “Premium services like WP101″ it should say “videos” or “video tutorials” instead? Not everyone knows of WP101 so may may not be inclined to select that option. Also it might not be bad to have an open-ended fill-in question like “8. Other?”

      • Siobhan 8:00 pm on November 9, 2012 Permalink | Log in to Reply

        I guess I’d be more interested in whether people are using premium services, rather than videos. So maybe “premium services”?

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel