Title: 859-meta – Make WordPress.org --- # Tag Archives: 859-meta [ ](https://profiles.wordpress.org/coreymckrill/) [Corey McKrill](https://profiles.wordpress.org/coreymckrill/) 9:16 pm _on_ August 2, 2017 Tags: 2100-meta, [2907-meta ( 4 )](https://make.wordpress.org/meta/tag/2907-meta/), 2934-meta, 3003-meta, 574-meta, 859-meta, [recap ( 8 )](https://make.wordpress.org/meta/tag/recap/), [ticket-scrub ( 32 )](https://make.wordpress.org/meta/tag/ticket-scrub/), [wordcamp ( 42 )](https://make.wordpress.org/meta/tag/wordcamp/) # 󠀁[Recap of WordCamp.org Ticket Scrub for the week of July 31st](https://make.wordpress.org/meta/2017/08/02/recap-of-wordcamp-org-ticket-scrub-for-the-week-of-july-31st/)󠁿 Great attendance for our first-ever WordCamp.org ticket scrub! The next WordCamp.org Ticket Scrub meeting will be in two weeks, [2017-08-15 19:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170815T1900), in [#meta-wordcamp](https://wordpress.slack.com/archives/meta-wordcamp). Here is a summary of this week’s discussion: [#2907-meta](https://meta.trac.wordpress.org/ticket/2907) This patch makes some significant changes to the Instagram source in the Tagregator 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. to accommodate changes to the Instagram 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.. The current patch submitted by [@xkon](https://profiles.wordpress.org/xkon/) uses raw cURL commands, which is not ideal for compatibility. The suggested change was to try using `wp_remote_get` or `wp_remote_post` instead. [@ryelle](https://profiles.wordpress.org/ryelle/) volunteered to help test this and other Tagregator patches. ([#2100-meta](https://meta.trac.wordpress.org/ticket/2100), [#3003-meta](https://meta.trac.wordpress.org/ticket/3003)) [#2934-meta](https://meta.trac.wordpress.org/ticket/2934) This ticket has a patch from [@rmarks](https://profiles.wordpress.org/rmarks/) that partially addresses the issue. [@coreymckrill](https://profiles.wordpress.org/coreymckrill/) said he would try to get that patch committed, and suggested fixes for other parts of the issue should go in a separate patch. [#859-meta](https://make.wordpress.org/meta/tag/859-meta/) We discussed the patch for this ticket recently submitted by @grappleulrich. One aspect of the patch was to prevent users from publishing posts while Coming Soon mode is enabled, so that site subscribers wouldn’t get an email notification of a new post that might be incomplete and that they wouldn’t actually be able to access. As a group, we agreed that disabling the Publish button would actually be confusing and that there are times when you might want to publish a post while still in Coming Soon mode. Instead, we decided to change the approach so that email notifications are disabled in Coming Soon mode, and there is a warning near the Publish button to notify users that their post won’t be emailed to subscribers if they publish while still in Coming Soon mode. [#574-meta](https://make.wordpress.org/meta/tag/574-meta/) This is an old ticket with an old patch. We agreed that the feature described would still be useful, but the patch probably needs to be updated before it will be compatible with the current version of CampTix. [@coreymckrill](https://profiles.wordpress.org/coreymckrill/) said he would move the ticket over to the CampTix GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘ pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) repo. If you were unable to attend this meeting but have feedback, please share your thoughts in the comments on this post. In case there’s a need for further discussion we will ensure to make time for it in the next meeting. See you next time! [#recap](https://make.wordpress.org/meta/tag/recap/) [#ticket-scrub](https://make.wordpress.org/meta/tag/ticket-scrub/) [#wordcamp](https://make.wordpress.org/meta/tag/wordcamp/) [#2100-meta](https://make.wordpress.org/meta/tag/2100-meta/), [#2907-meta](https://make.wordpress.org/meta/tag/2907-meta/), [#2934-meta](https://make.wordpress.org/meta/tag/2934-meta/), [#3003-meta](https://make.wordpress.org/meta/tag/3003-meta/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2017%2F08%2F02%2Frecap-of-wordcamp-org-ticket-scrub-for-the-week-of-july-31st%2F%23respond&locale=en_US)