Title: Call for Trac Tickets and Recap of 1/15/2016 Bug Scrub
Author: chriscct7
Published: January 22, 2016
Last modified: February 15, 2016

---

 [  ](https://profiles.wordpress.org/chriscct7/) [chriscct7](https://profiles.wordpress.org/chriscct7/)
8:36 am _on_ January 22, 2016     
Tags: [bug scrub ( 85 )](https://make.wordpress.org/core/tag/bug-scrub/),
[trac cleanup ( 6 )](https://make.wordpress.org/core/tag/trac-cleanup/)   

# Call for Trac Tickets and Recap of 1/15/2016 Bug Scrub

On [Friday January 15 at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160115T1700)
we held the second regularly scheduled bugbug A bug is an error or unexpected result.
Performance improvements, code optimization, and are considered enhancements, not
defects. After feature freeze, only bugs are dealt with, with regressions (adverse
changes from the previous version) being the highest priority. scrub of the WordPress
4.5 release cycle. As a reminder, for the 4.5 release, tracTrac An open source project
by Edgewall Software that serves as a bug tracker and project management tool for
WordPress. bug scrubs will be held weekly each [Friday at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160122T1700).
Bug scrubs are held in the [#core](https://make.wordpress.org/core/tag/core/) channel
of WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

Unfortunately, as I am unable to make today’s meeting, and was unable over the last
few days to find a replacement, today’s meeting is cancelled. I hope to see you 
all at the next meeting, which will be [next Friday at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160129T1700).
Regardless, please feel free to use the time to triagetriage The act of evaluating
and sorting bug reports, in order to decide priority, severity, and other factors.
tickets!

The Slack archive for last week’s meeting begins here: [https://wordpress.slack.com/archives/core/p1452877403010570](https://wordpress.slack.com/archives/core/p1452877403010570)

During the bug scrub, the following tickets were covered:

[#32318](https://core.trac.wordpress.org/ticket/32318) , [#32920](https://core.trac.wordpress.org/ticket/32920),
[#12955](https://core.trac.wordpress.org/ticket/12955) , [#25669](https://core.trac.wordpress.org/ticket/25669),
[#27056](https://core.trac.wordpress.org/ticket/27056) , [#28441](https://core.trac.wordpress.org/ticket/28441),
[#29660](https://core.trac.wordpress.org/ticket/29660) , [#34839](https://core.trac.wordpress.org/ticket/34839),
[#35100](https://core.trac.wordpress.org/ticket/35100) , [#13910](https://core.trac.wordpress.org/ticket/13910),
[#30352](https://core.trac.wordpress.org/ticket/30352) , [#2702](https://core.trac.wordpress.org/ticket/2702),
[#33045](https://core.trac.wordpress.org/ticket/33045) , [#33283](https://core.trac.wordpress.org/ticket/33283),
[#13459](https://core.trac.wordpress.org/ticket/13459) , and [#18877](https://core.trac.wordpress.org/ticket/18877)

Next week, the bug scrub will run approximately 1 hour. Participants need not be
present for the full duration, and everyone is welcome to attend.

We’ll start with a list of pre-submitted tickets, before going to an open floor.
As time permits, the remainder will be filled with a mix of tickets in the 4.5 milestone,
and abandoned tickets, taken from [report 43 (Ancient Tickets)](https://core.trac.wordpress.org/report/43)
on Trac.

If you would like to submit a ticketticket Created for both bug reports and feature
development on the bug tracker. for consideration for the bug scrub, please comment
below with the ticket number. If you have extensive knowledge of the ticket, accompanying
text which provides  a brief description of each ticket, its current status, and
what needs to happen for the ticket would be appreciated. Bug scrubs are a great
way to get extra eyes on tickets, feedback on patches, or suggestions on future 
routes.

During the WordPress 4.4 cycle, Trac experienced a net loss of approximately 600
tickets. The goal for the 4.5 release is to get to 2,500 tickets open on Trac. The
current count is 3,347, which is 847 tickets from this goal.

[#bug-scrub](https://make.wordpress.org/core/tag/bug-scrub/), [#trac-cleanup](https://make.wordpress.org/core/tag/trac-cleanup/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2016/01/22/call-for-trac-tickets-and-recap-of-1152016-bug-scrub/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2016/01/22/call-for-trac-tickets-and-recap-of-1152016-bug-scrub/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2016/01/22/call-for-trac-tickets-and-recap-of-1152016-bug-scrub/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2016/01/22/call-for-trac-tickets-and-recap-of-1152016-bug-scrub/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2016/01/22/call-for-trac-tickets-and-recap-of-1152016-bug-scrub/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2016/01/22/call-for-trac-tickets-and-recap-of-1152016-bug-scrub/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/023301ccdbfa4b7eafaf0840f8481be31ec99f3c3df612f4fe91827dedd53aad?
     s=32&d=mm&r=g)
 2.   [Sisir](https://profiles.wordpress.org/prionkor/)  8:48 am _on_ January 22, 2016
 3.  I have found a JSJS JavaScript, a web scripting language typically executed in
     the browser. Often used for advanced user interfaces and behaviors. bugbug A bug
     is an error or unexpected result. Performance improvements, code optimization,
     and are considered enhancements, not defects. After feature freeze, only bugs 
     are dealt with, with regressions (adverse changes from the previous version) being
     the highest priority.. Need more attention to it [https://core.trac.wordpress.org/ticket/35216](https://core.trac.wordpress.org/ticket/35216)
 4.   * ![](https://secure.gravatar.com/avatar/023301ccdbfa4b7eafaf0840f8481be31ec99f3c3df612f4fe91827dedd53aad?
        s=32&d=mm&r=g)
      *  [Sisir](https://profiles.wordpress.org/prionkor/)  9:00 am _on_ January 22,
        2016
      * Opps, I see it was already mentioned. Nevermind, I need to get some sleep!
 5.  ![](https://secure.gravatar.com/avatar/1dba75a903be8eb13bae6f961d81a99e5c76d5ca8c327a18bc25e96df2417b99?
     s=32&d=mm&r=g)
 6.   [Hugh Lashbrooke](https://profiles.wordpress.org/hlashbrooke/)  9:40 am _on_ 
     January 22, 2016
 7.  At risk of sounding like a stuck record, I would really like to see some more 
     eyes on [#27048](https://core.trac.wordpress.org/ticket/27048) as it really improves
     the current exporter a huge amount. The latest status is supplied on the ticketticket
     Created for both bug reports and feature development on the bug tracker. (working
     patchpatch A special text file that describes changes to code, by identifying 
     the files and lines which are added, removed, and altered. It may also be referred
     to as a **diff**. A patch can be _applied_ to a codebase for testing. and screenshot),
     but it’s worth noting here that this patch also has the side effect of closing
     5 other tickets at the same time, which is undeniably useful 🙂
 8.   * ![](https://secure.gravatar.com/avatar/5829b86926e8946e34585c1937a39cb188ee38e8f34030d74d6404c972ea514e?
        s=32&d=mm&r=g)
      *  [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)  4:28 
        pm _on_ January 22, 2016
      * + 1.
 9.  ![](https://secure.gravatar.com/avatar/cbed8bec22389cd32240aaa6b2266632ca36c3db03da9a6dc9f4b6408de261bf?
     s=32&d=mm&r=g)
 10.  [Laurens Offereins](https://profiles.wordpress.org/offereins/)  12:03 pm _on_
     January 22, 2016
 11. An easy win to get another one off the list & has-patchpatch A special text file
     that describes changes to code, by identifying the files and lines which are added,
     removed, and altered. It may also be referred to as a **diff**. A patch can be
     _applied_ to a codebase for testing.: [#35010](https://core.trac.wordpress.org/ticket/35010)
 12. ![](https://secure.gravatar.com/avatar/31806c32e6ffadec959bd082559954c827bf63b0fc77636a07e11b649aa4f318?
     s=32&d=mm&r=g)
 13.  [Dave Clements](https://profiles.wordpress.org/thewanderingbrit/)  3:45 pm _on_
     January 22, 2016
 14. I’m new to this, so I’m taking baby steps, but [#34887](https://core.trac.wordpress.org/ticket/34887)
     is a simple, textual change, making the use of “front end” and “back end” consistent
     throughout the software. It has the patchpatch A special text file that describes
     changes to code, by identifying the files and lines which are added, removed, 
     and altered. It may also be referred to as a **diff**. A patch can be _applied_
     to a codebase for testing. and more than anything, it just needs someone to double
     check it, make sure that the patch is in the correct format and to merge it. Will
     be happy to keep pushing it forward based on whatever comments are received.
 15. ![](https://secure.gravatar.com/avatar/5829b86926e8946e34585c1937a39cb188ee38e8f34030d74d6404c972ea514e?
     s=32&d=mm&r=g)
 16.  [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)  4:29 pm 
     _on_ January 22, 2016
 17. It would be nice to have a follow up on this: [https://core.trac.wordpress.org/ticket/35243](https://core.trac.wordpress.org/ticket/35243)
     
     Extending the text widgetWidget A WordPress Widget is a small block that performs
     a specific function. You can add these widgets in sidebars also known as widget-
     ready areas on your web page. WordPress widgets were originally created to provide
     a simple and easy-to-use way of giving design and structure control of the WordPress
     theme to the user. to also include the Visual editor.
 18. ![](https://secure.gravatar.com/avatar/e7933213b6af2cbb0e6cfa438951379506325e175d995391e03460e26dc46dbc?
     s=32&d=mm&r=g)
 19.  [Corey - The Theme Foundry](https://profiles.wordpress.org/coreymckrill4ttf/)
     9:23 pm _on_ January 22, 2016
 20. [#34851](https://core.trac.wordpress.org/ticket/34851)
 21. The CustomizerCustomizer Tool built into WordPress core that hooks into most modern
     themes. You can use it to preview and modify many of your site’s appearance settings.’
     s Cropped Image Control is currently unusable in some situations.
 22. ![](https://secure.gravatar.com/avatar/3203c856810a4a7d411fd41d8cc5b3f8344637259ab1909fadcf50168d357954?
     s=32&d=mm&r=g)
 23.  [thomaswm](https://profiles.wordpress.org/thomaswm/)  2:32 am _on_ January 23,
     2016
 24. I’d like to nominate [#32602](https://core.trac.wordpress.org/ticket/32602). It
     currently needs a patchpatch A special text file that describes changes to code,
     by identifying the files and lines which are added, removed, and altered. It may
     also be referred to as a **diff**. A patch can be _applied_ to a codebase for 
     testing..
      It’s about the “View Details” link on the plugins screen. On multisitemultisite
     Used to describe a WordPress installation with a network of multiple blogs, grouped
     by sites. This installation type has shared users tables, and creates separate
     database tables for each blog (wp_posts becomes wp_0_posts). See also **network**,**
     blog**, **site** networks, the URLURL A specific web address of a website or web
     page on the Internet, such as a website’s URL www.wordpress.org of this link points
     to the network_admin_url instead of the admin_url. Therefore, browsers do not 
     show the pluginPlugin A plugin is a piece of software containing a group of functions
     that can be added to a WordPress website. They can extend functionality or add
     new features to your WordPress websites. WordPress plugins are written in the 
     PHP programming language and integrate seamlessly with WordPress. These can be
     free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
     or can be cost-based plugin from a third-party. details tab. Instead, there’s 
     an error message in the browser’s developer console: “Refused to display ” in 
     a frame because it set ‘X-Frame-Options’ to ‘SAMEORIGIN’.”
 25. ![](https://secure.gravatar.com/avatar/1718b7c2f2afc31b4e94805b6f1f6ae2b802cc4c696f99b11fde2186006c82c9?
     s=32&d=mm&r=g)
 26.  [Pascal Birchler](https://profiles.wordpress.org/swissspidy/)  1:19 pm _on_ January
     24, 2016
 27. I’d like to see some feedback on [#26571](https://core.trac.wordpress.org/ticket/26571),
     [#33717](https://core.trac.wordpress.org/ticket/33717) and [#14853](https://core.trac.wordpress.org/ticket/14853)
 28. ![](https://secure.gravatar.com/avatar/5829b86926e8946e34585c1937a39cb188ee38e8f34030d74d6404c972ea514e?
     s=32&d=mm&r=g)
 29.  [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)  12:35 am
     _on_ January 30, 2016
 30. It would be great to sanitize file names:
      [https://core.trac.wordpress.org/ticket/22363](https://core.trac.wordpress.org/ticket/22363)

Comments are closed.

# Post navigation

[← Core Dev Chat Notes for Jan 20](https://make.wordpress.org/core/2016/01/20/core-dev-chat-notes-for-jan-20/)

[Feature Plugin Meeting on Tuesday, Jan 26 →](https://make.wordpress.org/core/2016/01/23/feature-plugin-meeting-on-tuesday-jan-26/)