WordPress.org

Ready to get started?Download WordPress

Make.WordPress.Org Updates

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Kim Parsell 1:03 am on April 19, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Docs Team Update: Apr. 17, 2014 

    The following is a summary of the topics that were discussed during our weekly Docs chat.

    1. DevHub: Parser and theme work is ongoing. @DrewAPicture will be pitching in to help the team finish up work on both.

    2. Admin Help: @trishasalas said work continues on reviewing the original user testing videos. @jerrysarcastic attended this week’s meeting, and has volunteered to help with video reviews and preparation for the next round of user testing.

    3. Handbooks: @blobaugh is reviewing the current content in the Plugin Developer Handbook, and making notes for the spreadsheet. He still needs to review existing content in the Codex that can be moved over.

    4. Inline Docs: We’re done with hook docs!

    5. Codex Updates for 3.9: @siobhan put together a list of Codex pages that either need updated or created for the 3.9 release. If you have some time and want to help, please grab a page and make the appropriate edits. Anything not done before April 25th will be available for contributors to work on at the WordCamp Austin Contributor Day.

    6. Community Summit: There is a proposal to hold another community summit this year as part of WordCamp San Francisco. Anyone wishing to discuss doing another retreat-type summit instead of adding community discussions to the WCSF agenda should leave a comment on the post.

    You can read the chat logs here.

     

  • Joseph Karr O'Connor 6:17 pm on April 18, 2014 Permalink | Log in to leave a Comment  

    Accessibility Team Update: April 16, 2014 

    Team Member Thanks

    Thanks all the other teams who participated in making WordPress 3.9 happen and who reached out to the accessibility team for assistance. Many more people are asking us to check things than ever before. Special thanks to accessibility team members @davidakennedy, @grahamarmfield, and @joedolson who are mentioned in the 3.9 credits.

    Weekly Meeting Time

    There’s always confusion when the time changes and I regret that I compounded the confusion by being confused myself. I’m now using StatusClock.app by Pulsely for OS X set to GMT/UTC so I’ll be sure to call the weekly meeting to order at 19:00 UTC.

    Previous Test

    When the accessibility team did the last round of testing it was intended that it be done over a short period of time, but due to various factors it spread out over two months. That was a keyboard-only test because we were certain that, given our resources, we could not finish a full test. It turns out we could not finish even the attenuated test in a reasonable amount of time. This was not the intended outcome but I learned that we need many more testers to perform the testing in an effective manner. This is why I was very glad to make a testing plan with Jeanne Spellman of the W3C when we were at the International Technology and Persons With Disabilities Conference a month ago.

    New Test Round

    Jeanne Spellman of the W3C, the team contact for the User Agent Working Group and the Authoring Tool Accessibility Guidelines Working Group (AUWG), has committed to helping us test WordPress trunk using the Authoring Tool Accessibility Guidelines (ATAG). Jeanne has assembled a good number of volunteers to do the testing and they will file tickets or bump things up to me as soon as they have identified an issue. This time I feel confident that with current team members providing guidance the W3C team will be able to accomplish the task in a short enough period of time to be most effective. Testing is now scheduled to start the week of May 12, 2014.

    ATAG

    For those not familiar with ATAG, it is primarily for developers of authoring tools including software for generating websites such as content management systems. There are two areas of focus: making sure that the authoring tool user interface is accessible, and that the authoring tool supports the production of accessible content. Just as with WCAG 2.0, ATAG has three levels of success criteria in order of increasing compliance: A, AA, and AAA. We are testing to WCAG 2.0 level AA so it follows that the ATAG testing will also be done to level AA. ATAG testing will help us discover the issues we need to address next. ATAG at a Glance provides a short summary of the accessibility principles and guidelines in ATAG 2.0.

     

  • Jan Dembowski 7:55 pm on April 17, 2014 Permalink | Log in to leave a Comment  

    Support Team Update for April 17th 

    In today’s #wordpress-sfd support meetup the following items were discussed.

    WordPress 3.8.3 was released

    On April 14th the update to 3.8.3 was released. This fixed a bug with Quick Draft that was introduced with 3.8.2.

    WordPress 3.9 was released

    On April 16th WordPress 3.9 “Smith” was also released and the 3.9 Master list post was put up and updated as needed.

    As expected there have been some plugin related TinyMCE/Visual Editor issues. Impacted users have been asked to troubleshoot JavaScript problem using these Codex instructions.

    When a plugin is identified as requiring an update it gets put on the REPORTED OOPSES list and tracked there. When the plugin is confirmed as fixed then please update the post and cross it off the list with <del>…</del>.

    There do not seem to be any theme issues reported but if there are it will most likely have to do with the Masonry library update.

    Also discussed were topics related to image padding/borders and memcache issues.

    Better updates through education?

    Part of the discussion was the idea from @zoonini to not only have a sticky OMGWTFBBQ post but have another sticky post that refers users to the updating WordPress Codex article.

    I think that’s a good idea and for the next major release that should be done. Minor version number releases are and should be handled by the auto updates. If your installation is negatively impacted by an auto update then you may have a bigger problem with your plugins and theme.

    Major version number releases (3.8 to 3.9) should be upgraded via the dashboard as well but with planning. A user who follows the Codex update instructions (backups and knows how to restore to an earlier state) really can’t get into too much trouble. With that safety net if something breaks then they can roll back to a previous working state if they need to.

    I myself don’t know how to pull off educating the users but another brief sticky post may help more users be prepared for an upgrade.

    Today’s transcript can be read online via this link.

     

  • Jen Mylo 6:40 pm on April 17, 2014 Permalink | Log in to leave a Comment
    Tags: , ,   

    I posted a proposal for WCSF format over at the community team blog (since our team handles events and WCSF): http://make.wordpress.org/community/2014/04/17/putting-more-community-in-wcsf/

    Anyone wanting to talk about doing another retreat-type summit vs adding community discussions to the agenda of WCSF is welcome to comment there. Please share with your teams, thanks.

     

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

    Theme Review Update for April 14, 2014 

    Currently

    • 0 new tickets are waiting for review.
      • 0 tickets are older than 2 weeks
      • 0 tickets are older than 1 week
      • 0 tickets are older than 3 days
    • 57 tickets are assigned.
      • 23 tickets are older than 2 weeks
      • 34 tickets are older than 1 week
      • 54 tickets are older than 3 days

    In the past 7 days

    • 178 tickets were opened
    • 194 tickets were closed:
      • 164 tickets were made live.
        • 13 new Themes were made live.
        • 151 Theme updates were made live.
        • 24 more were approved but are waiting to be made live.
      • 30 tickets were not-approved.
      • 0 tickets were closed-newer-version-uploaded.
     

    • janaobx 1:41 am on April 16, 2014 Permalink | Log in to Reply

      Looking for support after updating client’s WordPress to 3.8.3. After attempting to login there is a redirect to the home page. Normally we login via /wp-admin which created the homepage redirection. After trying ‘wp-login.php’ we discovered that we were able to enter login credentials however that also redirected to ‘/wp-admin/upgrade.php?_wp_http_referer=%2Fwp-admin%2F’. Hostgator recommended downgrading to previous version of WordPress, but it seems to be unreliable.

      • Kim Parsell 1:10 am on April 19, 2014 Permalink | Log in to Reply

        Hi @janaobx – I’m sorry you haven’t gotten a reply before now. This site is for the teams to provide weekly updates, not for handling support issues. Can you create a post in the support forum so people can help you with your issue there please? :)

  • Kim Parsell 12:37 pm on April 13, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Docs Team Update: Apr. 10, 2014 

    The following is a summary of the topics that were discussed during our weekly Docs chat.

    1. DevHub: The parser has one bug left to be fixed. Theme work is ongoing, and could use everyone/anyone’s help.

    2. Admin Help: @trishasalas talked to @designsimply about starting user testing. Work continues on reviewing older usertesting.com videos.

    3. Handbooks: @sewmyheadon incorporated @philiparthurmoore‘s intro text into the Theme Developer Handbook. There have been some other contributions as well, so things are moving forward. The Seattle Docs Sprint last weekend went well. There were 9 contributors, and progress was made on both handbooks.

    4. Codex updates for 3.9: We need a volunteer (or volunteers) to compile the master list of pages in the Codex that need to be updated for 3.9. If you would like to help with this, please leave a comment on this post.

    5. Docs Conferences: If you are planning to be in Portland for Write the Docs-NA (May 5-6, 2014), please let @siobhan know so a WordPress get-together can be planned.

    You can read the chat logs here.

     

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

    Plugins team update for April 10, 2014 

    Repository stats for the last week:

    Requested : 194
    Rejected : 36
    Closed : 29
    Approved : 201
    Currently in the request queue: 48 (4 older than a week, 2 without a reply)

    3878 commits to the repo (887107-890985).

    Plugin support stats for the last week:

    15 open tickets, 3 with no activity in the last 7 days.

    Over on make.wordpress.org/plugins, Otto posted about the implications of the mysqli introduction in WP 3.9.

     

  • Jan Dembowski 10:01 pm on April 10, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Support Team Update for April 10th 

    In today’s #wordpress-sfd support meetup the following items were discussed (not necessarily in this order).

    WordPress 3.9 RC1 is live and security releases

    3.9 RC1 was released for testing. Please continue to abuse and try to break. Security related updates for 3.8.2 and 3.7.2 were released as well.

    There was some discussion about QuickPress (or Quick Draft) possibly being broken for 3.x.2 but that was unconfirmed as that’s not a feature many of us in the IRC chat use. Part of that concern is that other thing may have broken and that QuickPress (or QuickDraft) might just be a symptom.

    Next Wednesday April 16th is the targeted release date of WordPress 3.9. For now there are daily core IRC meetups at 20:00 UTC on #wordpress-dev for this effort.

    Forum topics regarding auto updates

    With the auto updates of 3.8 (and 3.7) there have been some topics regarding the patches and the notification emails from the WordPress installations.

    The auto updates are only for minor release number updates. So 3.8.1 will update to 3.8.2 but it will not update to 3.9. The major version number release upgrades have to be initiated manually in the WordPress dashboard.

    The auto updates can be tuned and that includes disabling update emails. In the majority of cases a minor point release should not break anything. It’s really encouraged that users leave the auto updates in place.

    That said, please understand that users who post to the forums about the auto updates have a problem and are looking for support. If you can help them out please do so but keep it positive and productive. Don’t reply if you are angry or reacting to someone else being upset.

    Make/support has a Blue Welcome box now

    Thanks to Kim Parsell the make/support has a blue welcome box with really helpful verbiage. It matches the other make blogs and I hope will encourage more people to participate in support.

    Plugin authors getting notification emails

    A lot of miscellaneous code changes will impact plugin developers, who for one reason or another, were doing things incorrectly. Some of those may have had a legitimate reason for doing that but those plugins will break with 3.9.

    To attempt to head that off the plugins team will be sending an email and a post will be published on make/core. The email and the replies will probably back up the plugin review queue. If there are any complaints about the queue then please ask them to be patient.

    Today’s IRC meetup transcript can be read via this link.

     

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

    Theme Review Update for April, 7 2014 

    • 0 new tickets are waiting for review.
      • 0 tickets are older than 2 weeks
      • 0 tickets are older than 1 week
      • 0 tickets are older than 3 days
    • 63 tickets are assigned.
      • 24 tickets are older than 2 weeks
      • 35 tickets are older than 1 week
      • 52 tickets are older than 3 days

    In the past 7 days

    • 169 tickets were opened
    • 192 tickets were closed:
      • 149 tickets were made live.
        • 12 new Themes were made live.
        • 137 Theme updates were made live.
        • 42 more were approved but are waiting to be made live.
      • 40 tickets were not-approved.
      • 3 tickets were closed-newer-version-uploaded.

    Round, Two, Go!

    Discussion for the proposal of 3.9 guidelines continues as well as theme activation standards.

     

  • Kim Parsell 3:15 am on April 5, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Docs Team Update: Apr. 3, 2014 

    The following is a summary of the topics that were discussed during our weekly Docs chat.

    1. DevHub: Work continues on the parser, and has resumed on the code reference theme.

    2. Admin Help: @Clorith said the team is still reviewing existing user tests to identify pain points in admin areas that haven’t been updated since the original tests were conducted.

    3. Handbooks: @blobaugh is currently reviewing the existing content in the Plugin Developer Handbook. He also plans to review content in the Codex to see what can be moved over to the handbook. @sewmyheadon wasn’t able to attend the chat, but sent a reminder about this weekend’s Seattle Docs Meetup – Saturday, April 5th at 10am PDT. You can also attend virtually in the #wordpress-sfd IRC channel.

    4. Docs Conferences: The list of talks was announced Thursday for Write The Docs NA. Both @siobhan and @DrewAPicture will be speaking – “Writing For Your Other Half” and “Putting the (docs) Cart Before the (standards) Horse“.

    5. Handbooks Master List: @DrewAPicture asked whether there should be a master list of all the handbooks (core/plugin dev/theme dev/team-specific) and who the point of contact for each is. If so, where should that live? The handbooks the Docs team is responsible for are listed in our handbook. It was suggested we could include a list of handbooks available on other Make sites in our handbook, with a link to each handbook and a point of contact.

    You can read the chat logs here.

     

← Older posts

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