Title: Community Priorities Author: Scott Taylor Published: June 7, 2014 --- [ ](https://profiles.wordpress.org/wonderboymusic/) [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 8:46 pm _on_ June 7, 2014   # Community Priorities Triaging tickets takes a lot of time and is often thankless work. Testing patches and making sure they are committable is equally as time-consuming. Being a gatekeeper to those tickets going into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is also tough – sure, you can commit anything, but you are also the first person responsible when it breaks or there weren’t unit tests in place (when there should have been). As a community, we often have 2 major goals: 1) Fix everything 2) Make everything better Since we are still in the midst of defining what 4.0 will ultimately be, I would like to ensure that the community once again has a voice as far as “priority” tickets go, outside of dev chat. If there is an important ticketticket Created for both bug reports and feature development on the bug tracker. that you feel has been neglected, comment below. Seriously. There is always frustration from those who say “my ticket never gets looked at!”– for anyone feeling especially disillusioned, remind us publicly to give you some feedback. This does not mean that every ticket deserves to ultimately go in right away, but let’s talk about it. Speaking for myself, I often sit down at the computer and say “my goal today is to commit 100 tickets!” – I usually end up committing 8, over the course of 5 hours. And most of those tickets haunt me for weeks. Everyone is held to a high standard and expected to follow through when they make a decision for everyone else. We ALL want the same thing. Let’s work together to get there! ### Share this: * [ Threads ](https://make.wordpress.org/core/2014/06/07/community-priorities/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2014/06/07/community-priorities/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2014/06/07/community-priorities/?share=bluesky) * [ X ](https://make.wordpress.org/core/2014/06/07/community-priorities/?share=x) * [ Facebook ](https://make.wordpress.org/core/2014/06/07/community-priorities/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2014/06/07/community-priorities/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/96555b596b7b85dc63b4e6ae6f84e7ec9efe1dc826c66c20328fccae50d99639? s=32&d=mm&r=g) 2. [Robert Dall](https://profiles.wordpress.org/rdall/) 8:53 pm _on_ June 7, 2014 3. This has 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 just needs a review…  plugins cannot filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. `the_content` for Gallery post format on index views 4. [https://core.trac.wordpress.org/ticket/25335](https://core.trac.wordpress.org/ticket/25335) 5. It has been debated whether is it worthy to patch something so “trivial” but if it is still a default theme and bundled with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. then I think it is something that should be fixed… 6. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 3:39 pm _on_ June 9, 2014 * wontfixwontfix A resolution on the bug tracker (and generally common in software development) that indicates the ticket will not be addressed further. This may be used for acceptable edge cases (for bugs), or enhancements that have been rejected for core inclusion.’d – if there are other tickets you think should be looked at, let us know 7. ![](https://secure.gravatar.com/avatar/c39ed3047e1c6b1b7a01743640a8851c32b5ca1420d7af112c720eccede719d4? s=32&d=mm&r=g) 8. [Jonathan Brinley](https://profiles.wordpress.org/jbrinley/) 9:00 pm _on_ June 7, 2014 9. Thanks for asking, Scott. It’s hard to get attention to 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. without coming across as a whiny attention seeker. I appreciate having this forum. Without further ado… 10. [https://core.trac.wordpress.org/ticket/17817](https://core.trac.wordpress.org/ticket/17817)– Fixing filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output./action recursion 11. Has a patch, has unit tests, has performance tests, has plenty of community feedback, and it fixes a 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. that’s lived in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for seven years. 12. The ticketticket Created for both bug reports and feature development on the bug tracker. itself had a fair amount of feedback for a while, but now that all the concerns have been addressed, it’s gone silent. Is there anything else I can do to help advance this ticket? 13. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 9:18 pm _on_ June 7, 2014 * This will get looked at – moved it to 4.0 for consideration * ![](https://secure.gravatar.com/avatar/0ae24a18e27a39d6a7ddfe2e2c4d6f3175f4770c31b3b670d91698ac4b6828c8? s=32&d=mm&r=g) * [Ryan Urban](https://profiles.wordpress.org/ryancurban/) 2:11 pm _on_ June 9, 2014 * +1 on getting this looked at and ultimately implemented in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 4:19 pm _on_ June 9, 2014 * The first time I ran unit tests, it took 1.5 minutes longer. The second time, 45 seconds. I think we need to squeeze some more performance for this to be viable. 14. ![](https://secure.gravatar.com/avatar/206d1802847cb2f71607a9eb2442cd03fb17aeedabcfc9b2dda8ecd89ed9d89e? s=32&d=mm&r=g) 15. [Niklas](https://profiles.wordpress.org/niklasbr/) 9:31 pm _on_ June 7, 2014 16. I’m unsure whether or not there are tickets on all of these subjects and my tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.-fu is not good today… But here are some wishes: 17. • The ability to use TinyMCE in widgets. • The ability to prevent plugins from breaking when WP auto-updates. I know the fault does not lie with WP, but sometimes plugins break things, and when the break things during auto-update things get worse because you are not there to discover it right away. Some setting to only allow auto-update if all enabled plugins are marked as compatible with the new version would be awesome! • Combine/compress CSSCSS Cascading Style Sheets./JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. files. This one I found a four year old ticketticket Created for both bug reports and feature development on the bug tracker. for ([https://core.trac.wordpress.org/ticket/11453](https://core.trac.wordpress.org/ticket/11453)) but I believe this might be reconsidered now that a CSS preprocessor has been impleneted ([https://core.trac.wordpress.org/ticket/22862](https://core.trac.wordpress.org/ticket/22862)). What do you say? The code is already there to sort JS files correctly according to dependencies. 18. * ![](https://secure.gravatar.com/avatar/e1a850bca164e3d29c1d8ae8117fa4b341ed150ea4d8ab29a285726c944c453b? s=32&d=mm&r=g) * [Marius Jensen (Clorith)](https://profiles.wordpress.org/clorith/) 5:20 am _on_ June 11, 2014 * Regarding 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. breakage from automated updates, I don’t see this as something that should be a problem for the default behavior. The default behavior of the updater is to only apply minors which generally mean security and 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. fixes for the most recent version. * I guess this does become a whole other question if you enable automatic major updates, perhaps adding a new configurable option alongside major updates to check compatibility of existing enabled plugins? (this should ONLY apply for manually enabled major updates, I think it’s important to maintain the default behavior of potential security patches etc be handled as they are;“ instantly”) - ![](https://secure.gravatar.com/avatar/206d1802847cb2f71607a9eb2442cd03fb17aeedabcfc9b2dda8ecd89ed9d89e? s=32&d=mm&r=g) - [Niklas](https://profiles.wordpress.org/niklasbr/) 12:53 pm _on_ June 14, 2014 - I’ve had a dozen or so things break over the last year and a half on minor updates, there have been three types of error: - a) It breaks because caching plugins (W3 TC, and WP Super Cache, I’m looking at you… 🙂 ) does not update their cache properly. b) A 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. author has created a work- around for a 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. that was fixed in the minor update and the two fixes now collide. c) The plugin author depended (for some stupid reason) or otherwise made code assumptions on the erroneous behaviour and therefore the update broke the site. 19. ![](https://secure.gravatar.com/avatar/688e591b5d1baee94cff30ae8308c1ff5b54e336deabc134eb625d0de86020d3? s=32&d=mm&r=g) 20. [@ubernaut](https://profiles.wordpress.org/ubernaut/) 10:04 pm _on_ June 7, 2014 21. heres mine: 22. [https://core.trac.wordpress.org/ticket/11302](https://core.trac.wordpress.org/ticket/11302) 23. basically ht issue is that in bulk editing mode there is no way to remove categories which can make for an incredibly arduous manual process of removing the categories one by one. i believe all the ui issues have been resolved at this point and there is also end user interest on this one: 24. [https://wordpress.org/ideas/topic/deselect-categories-in-bulk-edit](https://wordpress.org/ideas/topic/deselect-categories-in-bulk-edit) 25. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:40 pm _on_ June 9, 2014 * Agree, but 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. - ![](https://secure.gravatar.com/avatar/688e591b5d1baee94cff30ae8308c1ff5b54e336deabc134eb625d0de86020d3? s=32&d=mm&r=g) - [@ubernaut](https://profiles.wordpress.org/ubernaut/) 4:38 am _on_ June 13, 2014 - yeah i would do it but i don’t know any php thanks for weighing in nonetheless! 26. ![](https://secure.gravatar.com/avatar/043b2a659fd7954f6d4ecab63363a7a9ed9f6e427a047b02cb20b32cd0f999e3? s=32&d=mm&r=g) 27. [Bryan Petty](https://profiles.wordpress.org/bpetty/) 10:50 pm _on_ June 7, 2014 28. You asked me to list all of my high priority tickets in the IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are **[#wordpress](https://make.wordpress.org/core/tag/wordpress/)** and **[#wordpress-dev](https://make.wordpress.org/core/tag/wordpress-dev/)**, on irc.freenode.net. channel. Nobody actually cares, but I built a whole report for it. I honestly feel like most of the 600+ tickets here have been terribly neglected: [https://core.trac.wordpress.org/report/46](https://core.trac.wordpress.org/report/46) 29. Seriously… This report contains roughly the same number of unreviewed patches now as it did when I wrote the Bug Gardening guide two years ago. There’s patches in here that go for years without any feedback from the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team at all, not even to say that it’s not acceptable, or to even suggest that it could use some improvements. This report should only contain new patches submitted in the last couple weeks. Everything else should have either been rejected (with explanations), or committed. 30. I’m not going to sit here and list off all of my open patches that have been neglected (and yes, I do have some). That’s not fair to anyone else that also submitted patches to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. that isn’t here to speak for themselves. You aren’t asking them, and that’s part of the problem itself. Just the mere fact that 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. is uploaded and submitted to Trac *is* the indication that it’s important to someone in the community, and that the contributor thinks it’s important enough to donate their work to the entire community. 31. * ![](https://secure.gravatar.com/avatar/fb6525bdf0b9bc628522d50e4b3dbb0e790500c154b0de255cf133619843efd0? s=32&d=mm&r=g) * [solarissmoke](https://profiles.wordpress.org/solarissmoke/) 12:44 pm _on_ June 8, 2014 * +1 * Come here to say exactly this! There are tickets in that report which (at the time) had working patches, and were even tagged for commit, but were ignored. Some of them are now 7 or 8 years old. * Would be very, very happy to see a more systematic tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. process, so that each ticketticket Created for both bug reports and feature development on the bug tracker. is funnelled through a review process within a specified timeframe (during which it is either accepted and actively wrangled, or rejected with reasons). That way we would not end up with hundreds of abandoned tickets (and just as many disillusioned contributors). * ![](https://secure.gravatar.com/avatar/e05110ddfc422ecfc3c68f61f2b08a404343ef8514fed12b460fc9c9aaa47d27? s=32&d=mm&r=g) * [Helen Hou-Sandi](https://profiles.wordpress.org/helen/) 1:43 pm _on_ June 8, 2014 * 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. review from anybody in the community, particularly those who have more patches under their belt, is immensely helpful. While I wouldn’t expect that to fix the issue of ticketticket Created for both bug reports and feature development on the bug tracker. and patch rot completely, as I don’t think any one thing can, it really does go a long way toward helping ease the bottleneck that comes from an expectation that every single patch be reviewed by whatever is defined as the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team. - ![](https://secure.gravatar.com/avatar/043b2a659fd7954f6d4ecab63363a7a9ed9f6e427a047b02cb20b32cd0f999e3? s=32&d=mm&r=g) - [Bryan Petty](https://profiles.wordpress.org/bpetty/) 2:58 pm _on_ June 8, 2014 - This report is filtered specifically down to bugs only. There’s actually another 750 tickets with unreviewed patches for enhancements and new features. The reason the list is filtered, and why this is a high priority report is because assuming the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team doesn’t have the time to review everyone’s 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 not a problem, features can still go in a 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. most of the time. I don’t expect the team to review every single patch. However, you can’t do that with 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. fixes, and if developers with commit access can’t even keep up with reviewing bug patches (which account for less than 50% of the unreviewed patches), the team needs some serious reform. - It’s one thing to ignore a bug report because you don’t have the time or required information to investigate it (and I get that), but it’s not acceptable when those with commit access on an open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project can’t be bothered to review patches. It’s literally the only job developers with commit access are absolutely required to do because no-one else can do it. Anyone else can fix the same issues and develop the same new features the core team has been working on if they’d let them. What the community can’t do is review and commit patches. - It’s pathetic because someone else already did most of the heavy lifting, and it’s arrogant because the team assumes that only those with commit access have the ability to write quality patches. Above all else though, it’s a terrible cycle of abuse that WordPress is stuck in because someone invested a lot of their own (and their company’s) time writing it, and by ignoring it, the core team has consistently discouraged new contributors from getting involved. It’s also telling companies that hiring contributors or giving their developers extra time to contribute is just a waste of time and money. And without those dedicated long-term contributors, it becomes even more difficult to find worthy developers to grant commit access, and the team fails to find the time to review more patches yet again. - You’re assuming that patch rot is a regular and normal thing in an open source project, and that’s partly true, but not to this extent. There’s a serious problem here, and there *are* solutions to that problem that the core team isn’t adopting. * ![](https://secure.gravatar.com/avatar/92c9b71af01db9777d29870c622c80ef94d1344158eb2f5965f4bbe8efed251a? s=32&d=mm&r=g) * [Eric Andrew Lewis](https://profiles.wordpress.org/ericlewis/) 4:20 am _on_ June 9, 2014 * I think you do have a point, but I don’t think grandstanding and talking trashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level( administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. at length about the process is productive. - ![](https://secure.gravatar.com/avatar/2b176abd9c34a3f9f7b4319eaedd4db072bcc7ddd2ecb4e1a2bc7754ea30cbe7? s=32&d=mm&r=g) - [Denis de Bernardy](https://profiles.wordpress.org/denis-de-bernardy/) 9:26 pm _on_ June 14, 2014 - Imho, he’s absolutely not talking trashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days.. He’s simply laying things out as they are. The issue got raised every year or so since 2005, and things haven’t changed to date except for the addition of extra committers — something yours truly vocally fought for. Fixing bugs is still lowest priority for all intents and purposes, and it’s shameful. I’m not holding my breath for things to change this year any more than it did when I abandonned the idea of contributing to WP in any material manner, but seeing a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., however junior, actually initiate the discussion is a very welcome ray of light imho. - ![](https://secure.gravatar.com/avatar/de70e9de702178bf758acb9e4265259c2772bd01b7581cc656fa37c222787e09? s=32&d=mm&r=g) - [Robert Chapin](https://profiles.wordpress.org/miqrogroove/) 4:44 pm _on_ June 8, 2014 - I agree with Bryan. This is an area where the community has made incremental yet inadequate changes over the years. We have a well-organized TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., unit testing to prevent old bugs from returning, and a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team willing to listen now, but 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. fixes still take the absolute last priority in WordPress. The untapped potential of this community is mind boggling. 32. ![](https://secure.gravatar.com/avatar/3f01bc6fcb89d2e9781596460a0018ac5cbdc64590ab88c2f41bdb9645d8609c? s=32&d=mm&r=g) 33. [Tom Lynch](https://profiles.wordpress.org/unknowndomain/) 11:05 pm _on_ June 7, 2014 34. I have been advocating changes to the Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. and actually using it or providing hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. or something to the Adminadmin (and super admin) settings and Networknetwork ( versus site, blog) admin settings for years and it seems like someone higher up needs to make some decisions and garner support for it, because people have submitted patches only to be told we need to do XYZ… It’s hard to believe coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. still uses table based forms. 35. ![](https://secure.gravatar.com/avatar/023301ccdbfa4b7eafaf0840f8481be31ec99f3c3df612f4fe91827dedd53aad? s=32&d=mm&r=g) 36. [prionkor](https://profiles.wordpress.org/prionkor/) 6:48 am _on_ June 8, 2014 37. Here is mine 🙂 do_shortcode() for caption text. Was mentioned in dev chat. 38. [https://core.trac.wordpress.org/ticket/24990](https://core.trac.wordpress.org/ticket/24990) 39. ![](https://secure.gravatar.com/avatar/d94bdc8e970ce9c05a299f54838f522dafcf3d9379cfbea2ca2c848497bb6732? s=32&d=mm&r=g) 40. [leemon](https://profiles.wordpress.org/leemon/) 8:16 am _on_ June 8, 2014 41. [https://core.trac.wordpress.org/ticket/5809](https://core.trac.wordpress.org/ticket/5809) Updating a term in one taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies). affects the term in every taxonomy [https://core.trac.wordpress.org/ticket/23292](https://core.trac.wordpress.org/ticket/23292) Media uploader loads full size image and slows down, please change to thumbnails. 42. ![](https://secure.gravatar.com/avatar/85b3ccf3d505b40e64c56ee29c72bfa9f166468c4998288edcb561b53c804c64? s=32&d=mm&r=g) 43. [Torsten Landsiedel](https://profiles.wordpress.org/zodiac1978/) 12:38 pm _on_ June 8, 2014 44. It is not my ticketticket Created for both bug reports and feature development on the bug tracker., but I think it would be hilarious to fix these: [https://core.trac.wordpress.org/ticket/17268](https://core.trac.wordpress.org/ticket/17268) 45. It seems to be a little bit tricky to check if the server does provide the right languages and modules, but maybe these plugins help to bring this into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: [https://wordpress.org/plugins/native-gettext-diagnosis/](https://wordpress.org/plugins/native-gettext-diagnosis/) [https://wordpress.org/plugins/wp-performance-pack/](https://wordpress.org/plugins/wp-performance-pack/) 46. Less memory usage and faster sites for non-english WP installations is maybe not important for many english developers and so it this seems to be lost in the last 4 years. Would be cool if this would gain more community power 😉 47. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:25 pm _on_ June 9, 2014 * Re: 17268 – causes fatal errors in unit tests 48. ![](https://secure.gravatar.com/avatar/de70e9de702178bf758acb9e4265259c2772bd01b7581cc656fa37c222787e09? s=32&d=mm&r=g) 49. [Robert Chapin](https://profiles.wordpress.org/miqrogroove/) 4:33 pm _on_ June 8, 2014 50. Wouldn’t it be nice if 4.0 was a community-driven quality assurance release? 51. [#10041](https://core.trac.wordpress.org/ticket/10041) This is my highest priority and must not wait for betas. 52. These were punted from 3.9: [#23185](https://core.trac.wordpress.org/ticket/23185)– NBSP compat for dashes. [#27587](https://core.trac.wordpress.org/ticket/27587)– NBSP compat for smilies. [#27588](https://core.trac.wordpress.org/ticket/27588)– NBSP compat for shortcodes. [#19550](https://core.trac.wordpress.org/ticket/19550)– FilterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. wptexturize. 53. I have several patches for problems that are being caused by wptexturize: [#12690](https://core.trac.wordpress.org/ticket/12690) Do not texturize HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. and shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. elements! (Fixes several tickets) [#19308](https://core.trac.wordpress.org/ticket/19308) Do not texturize hexadecimal expressions. [#8775](https://core.trac.wordpress.org/ticket/8775) Fix curly quotes around numbers. [#22823](https://core.trac.wordpress.org/ticket/22823) Fix possesive numbers. 54. The wptexturize tickets below can be ready for 4.0, but I’m not going to waste time on them if we can’t get the above tickets finished first. [https://core.trac.wordpress.org/ticket/28483](https://core.trac.wordpress.org/ticket/28483) Stack errors in wptexturize. [#20342](https://core.trac.wordpress.org/ticket/20342) Allow dashes before curly quotes. [https://core.trac.wordpress.org/ticket/6969](https://core.trac.wordpress.org/ticket/6969) Duplicates several other tickets, just needs review. [https://core.trac.wordpress.org/ticket/4539](https://core.trac.wordpress.org/ticket/4539) Duplicates several other tickets, just needs review. [https://core.trac.wordpress.org/ticket/17571](https://core.trac.wordpress.org/ticket/17571) Probably invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also _notabug_) that indicates the ticket is not a bug, is a support request, or is generally invalid.. 55. * ![](https://secure.gravatar.com/avatar/de70e9de702178bf758acb9e4265259c2772bd01b7581cc656fa37c222787e09? s=32&d=mm&r=g) * [Robert Chapin](https://profiles.wordpress.org/miqrogroove/) 2:46 am _on_ June 11, 2014 * Also ready [https://core.trac.wordpress.org/ticket/27426](https://core.trac.wordpress.org/ticket/27426) * And a big thank you for the commits! * ![](https://secure.gravatar.com/avatar/de70e9de702178bf758acb9e4265259c2772bd01b7581cc656fa37c222787e09? s=32&d=mm&r=g) * [Robert Chapin](https://profiles.wordpress.org/miqrogroove/) 4:51 pm _on_ June 17, 2014 * [https://core.trac.wordpress.org/ticket/26850](https://core.trac.wordpress.org/ticket/26850) has a reasonable 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. now. It resolves the reported test cases and reaches a compromise on some others. 56. ![](https://secure.gravatar.com/avatar/894d1b6c075c81dc8826e1f592397ef9e4852d5c4838c12cd9d11ad60d98bc6c? s=32&d=mm&r=g) 57. [Till Krüss](https://profiles.wordpress.org/tillkruess/) 1:11 am _on_ June 9, 2014 58. I’d like to see these two simple improvements: [https://core.trac.wordpress.org/ticket/19992](https://core.trac.wordpress.org/ticket/19992) [https://core.trac.wordpress.org/ticket/23076](https://core.trac.wordpress.org/ticket/23076) 59. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 3:35 pm _on_ June 9, 2014 * [#19992](https://core.trac.wordpress.org/ticket/19992) is committed – [#23076](https://core.trac.wordpress.org/ticket/23076) 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. - ![](https://secure.gravatar.com/avatar/f3be1972cdd27bfc2f3d5ffeae483bb4982a9d6659d1af51f1f9d2e6b1db3173? s=32&d=mm&r=g) - [Nick Halsey](https://profiles.wordpress.org/celloexpressions/) 5:35 pm _on_ June 9, 2014 - I just added 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. to [#23076](https://core.trac.wordpress.org/ticket/23076); did this in my Menu 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. project. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:39 pm _on_ June 9, 2014 * Committed in [[28707]](https://core.trac.wordpress.org/changeset/28707) 60. ![](https://secure.gravatar.com/avatar/48d1838e467e34d462392573a18221810b9e1e8ac53688aae53f93cae21b8b17? s=32&d=mm&r=g) 61. [Lachlan MacPherson](https://profiles.wordpress.org/lachlanj/) 9:13 am _on_ June 9, 2014 62. Would really love to see this ticketticket Created for both bug reports and feature development on the bug tracker. looked at: [https://core.trac.wordpress.org/ticket/17379](https://core.trac.wordpress.org/ticket/17379)( Filtered exports drop attachments and featured images). 63. It’s something that I encounter many times a week. 64. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:13 pm _on_ June 10, 2014 * [https://core.trac.wordpress.org/ticket/17379#comment:26](https://core.trac.wordpress.org/ticket/17379#comment:26) 65. ![](https://secure.gravatar.com/avatar/cb62f42408d53d8191492388ebc9885bbc673a15b22f4ef77fa0ec978310c168? s=32&d=mm&r=g) 66. [Chris Van Patten](https://profiles.wordpress.org/chrisvanpatten/) 12:28 pm _on_ June 9, 2014 67. Not my ticketticket Created for both bug reports and feature development on the bug tracker., but I’d kill (not literally) for [#21195](https://core.trac.wordpress.org/ticket/21195): [https://core.trac.wordpress.org/ticket/21195](https://core.trac.wordpress.org/ticket/21195) As far as I can tell, there’s currently no clean way to get an avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org without leaning on regex, which is not fun. 68. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:20 pm _on_ June 10, 2014 * [https://core.trac.wordpress.org/ticket/21195#comment:37](https://core.trac.wordpress.org/ticket/21195#comment:37) 69. ![](https://secure.gravatar.com/avatar/1dc85457417601db220b14e7fa96c842700fbd1cceecd21d65306c26fffb92cc? s=32&d=mm&r=g) 70. [Rodrigo Primo](https://profiles.wordpress.org/rodrigosprimo/) 1:49 pm _on_ June 9, 2014 71. Thanks for asking Scott. 72. The highest priority ticketticket Created for both bug reports and feature development on the bug tracker. for me is a better algorithm for listing hierarchical post types in the adminadmin (and super admin). This ticket has 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. and is waiting for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. developers feedback. 73. [https://core.trac.wordpress.org/ticket/15459](https://core.trac.wordpress.org/ticket/15459) 74. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:24 pm _on_ June 10, 2014 * [https://core.trac.wordpress.org/ticket/15459#comment:25](https://core.trac.wordpress.org/ticket/15459#comment:25) - ![](https://secure.gravatar.com/avatar/1dc85457417601db220b14e7fa96c842700fbd1cceecd21d65306c26fffb92cc? s=32&d=mm&r=g) - [Rodrigo Primo](https://profiles.wordpress.org/rodrigosprimo/) 12:46 pm _on_ June 11, 2014 - 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. updated. Thanks for looking into this. 75. ![](https://secure.gravatar.com/avatar/c858a06465595fdc35033f1e9edc77627794753c383a97c281e54a813a52d670? s=32&d=mm&r=g) 76. [Aubrey Portwood](https://profiles.wordpress.org/aubreypwd/) 4:03 pm _on_ June 9, 2014 77. [https://core.trac.wordpress.org/ticket/27533](https://core.trac.wordpress.org/ticket/27533) 78. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:28 pm _on_ June 10, 2014 * [https://core.trac.wordpress.org/ticket/27533#comment:6](https://core.trac.wordpress.org/ticket/27533#comment:6) 79. ![](https://secure.gravatar.com/avatar/f348bdb68525f927a7883eb704ea56763c44b50716f9308c97c66d54a4221c1d? s=32&d=mm&r=g) 80. [Amanda Rush](https://profiles.wordpress.org/arush/) 6:26 pm _on_ June 9, 2014 81. I think it would be great if 4.0 were a release that focused on accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility). The media library has several problems just by itself, and we have of course been working on this along with testing coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. features for accessibility. Plus, by making 4.0, (or some other release if that’s not possible), an accessibility release, more credibility would be lent to WordPress as a platform that is serious about accessibility. 82. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:28 pm _on_ June 10, 2014 * Are there specific tickets you would like us to look at? Are there tickets that should be filed? 83. ![](https://secure.gravatar.com/avatar/cd257f389c91f137dab25f343b527123e887135b01921ebb6206e40cfa2eb636? s=32&d=mm&r=g) 84. [Knut Sparhell](https://profiles.wordpress.org/knutsp/) 10:32 pm _on_ June 9, 2014 85. It’s a bit late to change the focus for 4.0 now. I would like to suggest 4.1 to focus on fixing bugs, bringing down the number of open tickets, and continue making internationalisation, password handling, 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** and taxonomies better according to the roadmaps lined out on this blogblog( versus network, site). 86. My only open ticketticket Created for both bug reports and feature development on the bug tracker. with 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. is [https://core.trac.wordpress.org/ticket/27951](https://core.trac.wordpress.org/ticket/27951) 87. * ![](https://secure.gravatar.com/avatar/27e1ec1c5ddd320f2cca5aa10cdf696b132db9230fa77ed87df5ca3c3ba6cbd9? s=32&d=mm&r=g) * [Scott Taylor](https://profiles.wordpress.org/wonderboymusic/) 6:49 pm _on_ June 10, 2014 * [[28729]](https://core.trac.wordpress.org/changeset/28729) 88. ![](https://secure.gravatar.com/avatar/8ba681e63c40cede58c43a7c1787ead83d78ed8c4c5b739a9ce0a54eb28a47f5? s=32&d=mm&r=g) 89. [Jesper Johansen (jayjdk)](https://profiles.wordpress.org/jayjdk/) 8:12 pm _on_ June 10, 2014 90. I’d love to get some kind of feedback on my 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. on [https://core.trac.wordpress.org/ticket/16784](https://core.trac.wordpress.org/ticket/16784) 91. ![](https://secure.gravatar.com/avatar/6bbf6733c209208ceba31d55df0293748c7b5f0db106a0c0e7adff0aeccbfbb1? s=32&d=mm&r=g) 92. [Patrick Hesselberg](https://profiles.wordpress.org/compute/) 8:15 am _on_ June 11, 2014 93. Adding a composer.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. to WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. would still be awesome. *bump* [https://core.trac.wordpress.org/ticket/23912](https://core.trac.wordpress.org/ticket/23912) 94. ![](https://secure.gravatar.com/avatar/39bfb8ebf8c99856f07d90c116ff2d861e4bfe516906beb5fbcc968d6c1f0839? s=32&d=mm&r=g) 95. [Ben Huson](https://profiles.wordpress.org/husobj/) 11:15 am _on_ June 11, 2014 96. Would appreciate any devs who have a good knowledge of how the Media Modal works giving their input/views/suggestions on this: [https://core.trac.wordpress.org/ticket/28053](https://core.trac.wordpress.org/ticket/28053) 97. ![](https://secure.gravatar.com/avatar/8f88913e701e7ab61a1fe6e929ca5265629d88ca4e51ccdbbba9b8caaefda9d2? s=32&d=mm&r=g) 98. [Vincent Mimoun-Prat](https://profiles.wordpress.org/vprat/) 8:41 pm _on_ June 11, 2014 99. I have submitted patches for that one and that would help plugins depending heavily on post metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.. Query can go from hundreds of seconds to a few ms with that optimisation. 100. [https://core.trac.wordpress.org/ticket/24093](https://core.trac.wordpress.org/ticket/24093) 101. * ![](https://secure.gravatar.com/avatar/8f88913e701e7ab61a1fe6e929ca5265629d88ca4e51ccdbbba9b8caaefda9d2? s=32&d=mm&r=g) * [Vincent Mimoun-Prat](https://profiles.wordpress.org/vprat/) 8:44 pm _on_ June 11, 2014 * Let me know if I can improve on those patches. 102. ![](https://secure.gravatar.com/avatar/d7f59286b1dd707bfcfa8b4f4ce492be2b79973271369c91e4ce39e56eea3289? s=32&d=mm&r=g) 103. [programmin](https://profiles.wordpress.org/programmin/) 4:42 am _on_ June 16, 2014 104. I consider this to be a serious regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2014/06/07/community-priorities/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in 3.9: [https://core.trac.wordpress.org/ticket/28169](https://core.trac.wordpress.org/ticket/28169) 105. In earlier versions the edit/delete buttons for shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. placeholders were duck-punch-able to allow custom edit/delete behavior, but you must now resort to uglier workarounds in 3.9. Is there a good reason the developers don’t want the edit/delete buttons to be consistently used for shortcodes introduced by other plugins? 106. ![](https://secure.gravatar.com/avatar/2b414585f4eb82c96e7a2888dc70769981f4873f7fec6b71c6709cbae6ff4beb? s=32&d=mm&r=g) 107. [Tunbosun Ayinla](https://profiles.wordpress.org/tubiz/) 5:36 pm _on_ July 13, 2014 108. I will appreciate a follow up for my 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. [https://core.trac.wordpress.org/ticket/24398](https://core.trac.wordpress.org/ticket/24398) Comments are closed. # Post navigation [← WP Metadata API / UI team meeting hours vote](https://make.wordpress.org/core/2014/06/05/wp-metadata-api-ui-team-meeting-hours-vote/) [SSL taskforce →](https://make.wordpress.org/core/2014/06/11/ssl-taskforce/)