Comments Component Bug Scrub – May 9, 2016

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

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. scrub focused on open tickets in the Comments component will be held in the #core channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. at May 9, 2016 19:00 UTC.

Meeting Goals

Give attention and feedback to the tickets gathering dust in the Awaiting Review milestone
Reduce the number of tickets in the Awaiting Review milestone to 20 (currently at 37)
Have an open floor for anyone to request feedback for any Comments component ticketticket Created for both bug reports and feature development on the bug tracker.

If you have a ticket you want included in the open floor feedback leave a comment below. I promise to “read the comments”.

#4-6, #bug-scrub, #comments

BackuPs 4:49 pm on May 4, 2016

Hi

Could you please include this to be fixed?

https://core.trac.wordpress.org/ticket/34722

Thank you

Best regards,
BackuPs
David Anderson 4:54 pm on May 4, 2016

This issue causes work every time we push a new release:
https://core.trac.wordpress.org/ticket/33571

Allow plugins to identify themselves as not being from wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ (and so prevent clashes):
https://core.trac.wordpress.org/ticket/23318

Provide 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. so that plugins can replace the default WP cron system:
https://core.trac.wordpress.org/ticket/32656
Boone Gorges 5:26 pm on May 4, 2016

💥
Rachel Baker 9:14 pm on May 4, 2016

Clarification: tickets mentioned here should be within the Comments component.
- David Anderson 10:27 pm on May 4, 2016
  
  Apologies – I didn’t read that carefully enough!
David Shanske 12:29 am on May 9, 2016

I have a few I’d like to see if I can get into 4.6 or get an opinion on.

https://core.trac.wordpress.org/ticket/36427 – Just a simple addition of a variable to match another hook.
https://core.trac.wordpress.org/ticket/36784 – And similarly, matching update comment to new comment.

https://core.trac.wordpress.org/ticket/36564 – A simple suggestion to track last modified for comments that can be consistent
https://core.trac.wordpress.org/ticket/36765 – A split of my attempt on #34419 with a narrower scope
https://core.trac.wordpress.org/ticket/36766 – An attempt to offer better source verification and a filterFilter Filters are one of the two types of 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. to Pingbacks
https://core.trac.wordpress.org/ticket/33735 – Still curious if there is a better way to do this. I tried to solve this problem last year.

https://core.trac.wordpress.org/ticket/34420 – I know it isn’t in the specification, but I think either we build something into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to protect against this or we might as well deprecate trackback entirely.

Comments are closed.

Welcome!

Communication

Meeting Goals

Share this: