WordPress.org

Ready to get started?Download WordPress

Make.WordPress.Org Updates

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Boone Gorges 1:42 am on July 25, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Plugins update for July 24, 2014 

    Repo stats for the week:

    Plugins requested : 192
    Plugins rejected : 34
    Plugins closed : 15
    Plugins approved : 163

    30 plugins in the queue, 4 without a reply and 2 older than seven days.

    4518 commits to the repository (949987-954505).

    Support stats: 20 open tickets with 5 older than a week.

     
  • Jan Dembowski 12:10 am on July 25, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Support Team Update for July 24th 

    Items discussed at today’s #wordpress-sfd meetup:

    WordPress 4.0 beta2

    The second 4.0 beta is going smoothly. All the media related issues have tickets and is being worked on and the two holdouts are considered minor.

    There was a question from the week before if the Alpha/Beta sub-forum shows up in no-replies and all topics; it does.

    The handbooks for support

    The support handbook really is for moderators and the troubleshooting handbook is for everyone. That doesn’t really explain it clearly but at some time soon the troubleshooting handbook will be linked in the blue welcome box when you visit make/support.

    Upgrading plugins will protect you. Honest.

    In the recent past a certain popular plugin had an exploit that permitted Bad People™ to install code and backdoors onto your WordPress installation. If you were not compromised and upgraded the plugin then you were not impacted by this exploit. If you were exploited prior to the patched version of the plugin being released then you have to clean out your installation.

    However if you did not upgrade when the update arrived or continued to run the vulnerable version then your installation was a prime target for bots and most likely was compromised as a result of that.

    Please keep your plugins, themes and WordPress versions up to date and patched. It can protect you and save you hours of grief down the line.

    Speaking of exploits, there appears to be an uptick in XML-RPC brute force attacks. While some hosts may recommend that the users delete that xmlrpc.php file that will likely break things. The best reply to those topics really is “Please speak with your host.” Real firewalls that can rate limit http requests from attack hosts from ever reaching your installation can be the best way to solve it. Using .htaccess won’t really help as 10,000 404 pages will bring down any host.

    The transcript for today’s meetup can be read at this link.

     
  • Jose Castaneda 12:00 pm on July 21, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    Theme Review Update for July 21, 2014 

    Currently

    • 93 new tickets are waiting for review.
      • 28 tickets are older than 2 weeks
      • 58 tickets are older than 1 week
      • 73 tickets are older than 3 days
    • 57 tickets are assigned to 32 reviewers.
      • 53 tickets are older than 2 weeks
      • 56 tickets are older than 1 week
      • 57 tickets are older than 3 days

    In the past 7 days

    • 108 tickets were opened
    • 118 tickets were closed:
      • 101 tickets were made live.
        • 5 new Themes were made live.
        • 96 Theme updates were made live.
        • 27 more were approved but are waiting to be made live.
      • 16 tickets were not-approved.
      • 1 tickets were closed-newer-version-uploaded.
     
  • Jan Dembowski 10:29 am on July 18, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Support Team Update for July 17th 

    Items discussed at the #wordpress-sfd meetup:

    Status of the handbooks (not just the Troubleshooting one)

    @samuelsidler (sams) asked about the difference between the handbooks and the organization of them. He was at WCKC and there was some confusion when trying to locate items in the handbooks.

    The Support Handbook really is for moderators and people providing support in that role. For example many of the pre-defined replies in that handbook deal with managing topics. That’s for solving forum problems. It’s written for moderators.

    The Troubleshooting Handbook in development is for people who want to assist others with WordPress problems. It’s a different audience and is definitely needed.

    This item neatly segued into the next topic of

    The Troubleshooting Handbook status

    It’s looking good and parts of the new handbook are fleshed out. It still needs content but as @Ipstenu reminded me release and iterate also applies to documentation too. Contributions don’t have to be perfect but they have to be started or things will never get done.

    That last sentence was more of a note to myself but all contributions to the handbook are welcomed. ;) If you want to contribute but don’t have access then contact me via the comments and we’ll figure something out.

    There was discussion of how and what belongs on the new handbook and the consensus was to keep it basic and inviting to new users.

    Portions of the new Troubleshooting Handbook that do a deep dive into setting up things like WAMP, LAMP, MAMP, VVV, etc. will be directed to other more technical resources. Their will be technical details there (see the break/fix examples) but the goal is to get users started and invite them to provide support.

    We all want to get more people helping and keeping it basic may get that started.

    Section topic titles

    The sections and examples were obtained from @Ipstenu‘s Break/Fix site. The titles work with the content of the article but some of them may be unclear when people are looking around. Those titles are fun though and when you get into the examples you’ll understand Mika’s gift for titles. ;)

    If you have a suggestion for modifying a title in the handbook please ping the gang here.

    BETA!

    I couldn’t figure out a good way to type that title with a Kirk “KHHAANNN!!!” effect.

    The WordPress 4.0 beta1 is out and please test and beat up. There are some nice enchantments (the media library made me yell “Oh that’s cool!”) and feed back is needed and bugs should be reported to the Alpha/Beta sub-forum. For a good status or progress on the beta consider subscribing to make/core.

    When you see topics in the Alpha/Beta sub-forum that have a ticket assigned and posted in that topic please mark that topic resolved. Don’t close the topic unless it becomes a run-away train or off topic in a bad way. Then the usual applies and that topic can be closed.

    The transcript for this meetup can be read at this link.

     
    • Samuel Sidler 3:18 pm on July 18, 2014 Permalink | Log in to Reply

      I’m still confused.

      The consensus at the chat seemed to be that the support handbook was for getting people involved in WordPress support, including both the forums and codex. But your post here says it’s just for moderators, presumably that’s forums-only.

      My question wasn’t specifically about what it was for, it was more that the contents aren’t currently great for helping new contributors get involved. The topic got intertwined with another one, sadly.

      Is there anyone working on improving the support handbook so that new contributors (who, obviously, aren’t moderators yet) can get involved in the forums and support-related codex articles?

      • MacManX (James Huff) 5:09 pm on July 18, 2014 Permalink | Log in to Reply

        The Troubleshooting Handbook is being made exactly so that “new contributors (who, obviously, aren’t moderators yet) can get involved in the forums.”

        Once it’s done, it will essentially supersede the support bits of the Support Handbook, except for its moderator-only and codex bits.

        Think of it as “Here’s this bigger better support resource, and here’s everything else.” Rather than having one handbook which is 90% support and 10% everything else, think of it as one handbook which is equal thirds where one third directs folks to a larger handbook elsewhere.

        I’m sure there’s a better way of explaining it, but the short version is that no effort is being made to improve the support bits of the Support Handbook because all hands are on deck for the Troubleshooting Handbook, which will replace those bits.

        • MacManX (James Huff) 5:14 pm on July 18, 2014 Permalink | Log in to Reply

          My apologies, I mean “which will replace *most* of those bits.” Obviously, there will still be support bits which direct off to the larger Troubleshooting Handbook.

  • Jose Castaneda 2:40 pm on July 14, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    Theme Review Update for July 14, 2014 

    Currently

    • 112 new tickets are waiting for review.
      • 21 tickets are older than 2 weeks
      • 46 tickets are older than 1 week
      • 85 tickets are older than 3 days
    • 67 tickets are assigned to 34 reviewers.
      • 61 tickets are older than 2 weeks
      • 64 tickets are older than 1 week
      • 67 tickets are older than 3 days

    In the past 7 days

    • 111 tickets were opened
    • 113 tickets were closed:
      • 89 tickets were made live.
        • 14 new Themes were made live.
        • 75 Theme updates were made live.
        • 22 more were approved but are waiting to be made live.
      • 23 tickets were not-approved.
      • 1 tickets were closed-newer-version-uploaded.
     
  • Joseph Karr O'Connor 6:07 pm on July 11, 2014 Permalink | Log in to leave a Comment  

    Accessibility Team Update: July 9, 2014 

    WordPress 4.0 Beta 1

    In our meeting this week, Sam Sidler gave us the heads-up that 4.0 Beta 1 was about to be released and told us that it is “incredibly important that you test it and all of its new features.” In her post WordPress 4.0 Beta 1, Helen Hou-Sandi announces the release and talks about new features.

    Testing

    This Saturday, July 12, some of us will be testing 4.0 Beta 1 for accessibility and other issues. If you want to get involved the start time is 15:00 UTC. Log in to the #wordpress-ui IRC channel. Also refer back to and update the Make WordPress Accessible page for information about what has been tested and what needs to be tested.

    Test Environment

    Remember, we’re testing 4.0 Beta 1 so you’ll need an installation of WordPress with the WordPress Beta Tester plugin set to download and install “bleeding edge nightlies.” You don’t want to do this on your live site, so use a tool like DesktopServer by ServerPress to create a virtual server on your desktop computer.

     
  • Jan Dembowski 2:34 am on July 11, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Support Team Update for July 10th 

    Items discussed at today’s #wordpress-sfd meetup:

    WordPress 4.0 Beta1 has dropped this morning

    Early today the release announcement for the next beta was posted. Please test and report any issues. You can install the WordPress Beta Tester plugin to do that easily.

    Forum moderators: if you see a topic in the Alpha/Beta sub-forum and a ticket has been created in trac then please mark that topic as “resolved” and post that link.

    Contributing to the Troubleshooting Handbook

    The troubleshooting handbook needs contributions and the topic was raised for how that can be accomplished. There’s not really a method to grant that access in a good way. If someone has some content they would like to contribute then perhaps posting it on their own site first may be how to get started.

    It’s easy to grant access to someone who has been collaborating with the different teams for years but granting that access to new people is delicate. It’s an idea that needs working on.

    Status of the Troubleshooting handbook

    @jerrysarcastic has generously offered to post a separate status update on that topic. ;)

    The transcript of today’s meetup can be read via this link.

     
  • Boone Gorges 12:25 am on July 11, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Plugin Team Update for July 10, 2014 

    Repository stats this week:

    Plugins requested : 194
    Plugins rejected : 55
    Plugins closed : 12
    Plugins approved : 133

    93 plugins currently in the queue, 70 without a reply and 3 older than a week.

    4116 commits to the repo (942513-946629)

    Support stats: 20 open tickets, with 4 older than a week.

     
  • Jose Castaneda 12:23 pm on July 7, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    Theme Review Update for July 7, 2014 

    Currently

    • 98 new tickets are waiting for review.
      • 15 tickets are older than 2 weeks
      • 40 tickets are older than 1 week
      • 74 tickets are older than 3 days
    • 69 tickets are assigned to 40 reviewers.
      • 62 tickets are older than 2 weeks
      • 66 tickets are older than 1 week
      • 68 tickets are older than 3 days

    In the past 7 days

    • 96 tickets were opened
    • 90 tickets were closed:
      • 70 tickets were made live.
        • 0 new Themes were made live.
        • 70 Theme updates were made live.
        • 36 more were approved but are waiting to be made live.
      • 18 tickets were not-approved.
      • 2 tickets were closed-newer-version-uploaded.
     
  • Jan Dembowski 2:00 am on July 4, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Support Team Update for July 3rd 

    Items discussed at today’s #wordpress-sfd meetup:

    Domain trademark violations

    This comes up from time to time in the forums. Someone (well meaning I am sure) uses WordPress in their domain name and posts that link in the forums or in their forum profile. When that happens they usually get a reply such as “Hey, could you please stop using that domain name? Here’s some links explaining it better.”

    Volunteer support is not trademark police and I’ve not seen a case where someone didn’t correct that when pointed out. Support volunteers are there to help people and not really get into topics like that. But if necessary this link can be used to report that to the WordPress foundation.

    http://wordpressfoundation.org/contact/

    Again it’s not that support is to tell people right and wrong but if an instance needs to be escalated then that link should work.

    Troubleshooting Handbook status

    The new Troubleshooting Handbook is making progress and both @jerrysarcastic and @podz (Markr) have been working on it. It still needs contributors so please take some time to look it over and contribute where you can.

    https://make.wordpress.org/support/trouble/

    Section 3 can use some attention and would really benefit from some content.

    For examples of good (and not so good) support it was discussed to possibly take topics from the forum and modify/anonymize the text so that the examples remain just examples. It’s important that the handbook doesn’t seem to call out people for their behaviour. It’s a handbook after all and everyone should benefit from the verbiage.

    Expiring topics earlier than 1 year?

    When a topic is a year old it gets expired meaning no one can reply to those topics anymore. Moderators can still edit the posts in the topic but not reply either. This morning on the wp-forums list the idea came up about the possibility of reducing that time.

    Expiring topics around 3 months was well recieved in IRC and that became 6 months after some talking it out. I suggested sending an email to the list asking Otto about it. His reply on the list touched on something important: what is the best experience for the users?

    Topics are expired because after a time they’re no longer useful. That time is currently 1 year but more or less could be a tough thing to nail down. It’s something that will continue to be discussed on the wp-forums list.

    This really isn’t a critical item (it only really came up today) and I think the 1 year age out will stay. Moderators can still close topics that have gone off the rails and are no longer productive.

    The transcript of today’s #wordpress-sfd meetup can be read at this link

     
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