Agenda for December 17th Support Meeting

The weekly support meeting will be held on Thursday, December 17th, 2020, 17:00 UTC in #forums 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/.. (a Slack account is required)

A note-taker for the meeting is requested, taking notes is a great way to get more involved with contributing to a team, and getting to know how they operate, so don’t be shy, no prior experiences needed, and volunteering happens at the start of the meeting!

Headlines / Community updates

  • WordPress 5.6 – How’s it going?
  • Final official checkin of the year 🎉

Checking in with international liaisons

This is the section where we reach out to the non-English speaking parts of our community, to see how they are doing, if there’s anything we can help each other with, or just interesting things going on that it would be nice to share with others.

There’s no requirements for previous participation or “fame” to share here, anyone is welcome, and we encourage newcomers to participate!

Unable to make the meeting, or maybe meetings just aren’t your thing? We would still love to hear how things are going in other non-English speaking parts of our community. Please feel free to let us know via the comment section below, in your own time, if there is anything you’d like to share, any questions or concerns you have, ort just to let us know you’re doing ok!

We will make a habit of putting this callout with every agenda post going forward, so that everyone has a chance to join in.

Open floor

This part of the meeting only happens if there is time, the team aims to cover the pre-planned topics first in any given meeting.

When open floor starts, any topic posted either as a comment to this agenda post will be looked at, or as many as there is time for. If there is still time left after this, then meeting attendees may step forward with questions, comments, remarks, anything relating to the support team that they’d like to handle.

It is also important to note that not everyone is comfortable posting things publicly, there is complete understanding of this, and users are welcome to contact the team representative (@clorith) via direct messages on Slack with whatever they wish the team to look at together.

For any other items to discuss, please add them to the comments below, or bring them up in the meeting.

Handling potential jQuery issues in WordPress 5.6

WordPress 5.5 stopped enabling the jQuery Migrate helper script by default, and with the upcoming release of WordPress 5.6, the bundled version of jQuery will be upgraded (from 1.12.4-wp to 3.5.1).

What this involves for users, is that any 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/ or can be cost-based plugin from a third-party or theme that previously relied on the jQuery Migrate tool to work as expected (due to being older code, or just a missed update to deprecated functions), may now have unexpected behaviors.

In the best of cases, this related to events not being triggered, this just means that some functionality may stop working behind the scenes, no major impact.
The potential issue is the use of function that were deprecated, these will now cause a fatal error, and prevent further pieces of JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. on your site from working as expected.

The 5.5 solution

For the release of WordPress 5.5, a plugin called Enable jQuery Migrate Helper was created, which would re-enable the jQuery Migrate tool on the site in question, and also make sure that the features making it a necessity were surfaced so the site users would know what is happening.

The initial plan for this plugin was to be a temporary stop-gap to allow plugin and theme authors a little bit more time to update, if they were caught off-guard by the changes in the 5.5 release.

Unfortunately, we can still see many plugins and themes (at time of publishing, before WordPress 5.6 has been released) relying on older code, and we are unaware of the potential impact of paid plugins or themes from across the ecosystem.

The 5.6 solution

With the above in mind, the Enable jQuery Migrate Helper plugin was updated for the release of WordPress 5.6, this provides a temporary downgrade path to run legacy jQuery on a site when needed.

The reason this is considered a temporary solution, is that the older version of jQuery no longer receives security updates, and the legacy version will not be patched manually if anything should occur that warrants updates to it.

The plugin presentation

The plugin provides features and tools aimed at transitioning a site between jQuery versions, either via plugin and theme authors updating their code, or giving a site owner time to find replacements.

Deprecation logging

To find the actual problems on your site, whenever you browser around with the plugin active, it will track any deprecations that are discovered.

Deprecations are warnings relating to outdated code that is being used, but has been made available for a short period of time during your transition. Any feature that is marked as deprecated should be replaced with modern code as soon as possible, to ensure nothing breaks.

The admin bar showing deprecation alerts

The first place you will encounter a deprecation-notice is within the admin bar, found on the top of all sites when you are logged into the backend, but also enabled in the frontend on many sites.

It will show you a count of any issues found on the current page, if it is the front-end, it will be logged to a separate page, dedicated to listing and educating about the warnings that were encountered, in the backend they may be shown instantly on screen, or also get logged, depending on your settings.

Admin menu showing a count of logged deprecations

If there are deprecations previously logged, they may also show an indicator of how many items have been logged in the admin bar, as seen in the provided screenshot, these will remain marked until you clear out the logs.

Deprecation logs, with example pluigins

The deprecation log page it self provides a visual representation of warnings often hidden away and intended for developers within the JavaScript console.

It will provide an easy link to a plugin or themes own website, or their authors site if no other link was available. This kind of direct access will hopefully help users reach out and get updated versions of their code in a more timely fashion than needing to find it based on a slug (a shortname used to reference plugins and themes).

Using legacy jQuery

The setting screen, offering options for changing jQuery versions

The settings screen offers the user the3 choice between using the legacy jQuery (with the tradeoff being an admin notice on every page alerting them to the scenario, and why they should be looking to remedy the need for it as soon as possible), and also a way to enable public deprecation logging.

Public logging may incur an added strain on your server, as any visitor who visits a page leading to an error will send a logging request automatically for the user to go over at their convenience.

Automatic version changes

The target audience are non-technical users, as such they may be unaware of the potential issues the plugin addresses when they upgrade WordPress, or maybe a support person told them to use it to resolve an issue.

In light of this, the first time a site visitor encounters an error caused by a now broken jQuery implementation, the plugin will facilitate an automated downgrade to a legacy jQuery version, and sends an email to the site administrator informing them of what has happened.

This automatic downgrade is a one-time event, changing versions after this will not make it trigger again in the future.

Automated emails, keeping you in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.

Example email sent when using a legacy jQuery version

Once per week, an email is scheduled to be sent out, letting the site administrator know the current state of their site. This email includes information about the plugin and which jQuery issues have been logged in the past week.

This will hopefully ensure site administrators get more involved in resolving problems with their own page.

The email will also encourage the removal of the jQuery Migrate helper plugin, if there have been no registered deprecations within the past week. This will help give a clearer indication of the underlying issue of outdated jQuery instances, by watching the amount of active plugin users.

Agenda for November 19th Support Meeting

The weekly support meeting will be held on Thursday, November 19th, 2020, 17:00 UTC in #forums 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/.. (a Slack account is required)

A note-taker for the meeting is requested, taking notes is a great way to get more involved with contributing to a team, and getting to know how they operate, so don’t be shy, no prior experiences needed, and volunteering happens at the start of the meeting!

Headlines / Community updates

  • WordPress 5.6-RC1Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 is now available.
  • Forum front page proposal – There is still a week left for providing feedback.
  • WordPress 5.6 Master List – Work on the new Master List begins in earnest now that RC1 is out.

Checking in with international liaisons

This is the section where we reach out to the non-English speaking parts of our community, to see how they are doing, if there’s anything we can help each other with, or just interesting things going on that it would be nice to share with others.

There’s no requirements for previous participation or “fame” to share here, anyone is welcome, and we encourage newcomers to participate!

Unable to make the meeting, or maybe meetings just aren’t your thing? We would still love to hear how things are going in other non-English speaking parts of our community. Please feel free to let us know via the comment section below, in your own time, if there is anything you’d like to share, any questions or concerns you have, ort just to let us know you’re doing ok!

We will make a habit of putting this callout with every agenda post going forward, so that everyone has a chance to join in.

Open floor

This part of the meeting only happens if there is time, the team aims to cover the pre-planned topics first in any given meeting.

When open floor starts, any topic posted either as a comment to this agenda post will be looked at, or as many as there is time for. If there is still time left after this, then meeting attendees may step forward with questions, comments, remarks, anything relating to the support team that they’d like to handle.

It is also important to note that not everyone is comfortable posting things publicly, there is complete understanding of this, and users are welcome to contact the team representative (@clorith) via direct messages on Slack with whatever they wish the team to look at together.

For any other items to discuss, please add them to the comments below, or bring them up in the meeting.

Agenda for November 12th Support Meeting

The weekly support meeting will be held on Thursday, November 12th, 2020, 17:00 UTC in #forums 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/.. (a Slack account is required)

A note-taker for the meeting is requested, taking notes is a great way to get more involved with contributing to a team, and getting to know how they operate, so don’t be shy, no prior experiences needed, and volunteering happens at the start of the meeting!

Headlines / Community updates

Checking in with international liaisons

This is the section where we reach out to the non-English speaking parts of our community, to see how they are doing, if there’s anything we can help each other with, or just interesting things going on that it would be nice to share with others.

There’s no requirements for previous participation or “fame” to share here, anyone is welcome, and we encourage newcomers to participate!

Unable to make the meeting, or maybe meetings just aren’t your thing? We would still love to hear how things are going in other non-English speaking parts of our community. Please feel free to let us know via the comment section below, in your own time, if there is anything you’d like to share, any questions or concerns you have, ort just to let us know you’re doing ok!

We will make a habit of putting this callout with every agenda post going forward, so that everyone has a chance to join in.

Open floor

This part of the meeting only happens if there is time, the team aims to cover the pre-planned topics first in any given meeting.

When open floor starts, any topic posted either as a comment to this agenda post will be looked at, or as many as there is time for. If there is still time left after this, then meeting attendees may step forward with questions, comments, remarks, anything relating to the support team that they’d like to handle.

It is also important to note that not everyone is comfortable posting things publicly, there is complete understanding of this, and users are welcome to contact the team representative (@clorith) via direct messages on Slack with whatever they wish the team to look at together.

For any other items to discuss, please add them to the comments below, or bring them up in the meeting.

Changing up the forum front page

The feedback period is over as of Novermber 25th, 2020, 23:00 UTC

There’s been multiple discussions about the forum front page (for the international forums, this is as https://wordpress.org/support/forums, make note that it is not the support landing page, which is currently presented with what is known as HelpHub, a series of categories showing relevant user-facing documentation).

With the upgrade to bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. 2.x, a revamp of the forums was also in order, and this was also the baseline for the HelpHub page.

A ticket does exist for revamping the forum listing page, with a lot of input and various directions, none of which truly take us where we want to go, as evident by various discussions still held publicly 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/. on a fairly regular basis.

The consensus is that it is not very forum-like, and it would be beneficial to bring it back towards its roots, to again make it clear that it is a forum, and help users find their way.

The problem to solve

There’s no reason to do anything, if it’s not to solve a problem, so let’s go over that here.

The biggest issue is discoverability, currently the landing page does not make it clear that it is a forum, to many it too tightly resembles the HelpHub landing page, and the blocks describing each forum are also very far below the fold (you need to scroll to find them).

Secondly, the aspect of clear identification. If the user does not see it is a forum, they will not know that this is a place they can interact.

The direction we want to take

Looking back at how things were, and some of the proposals in the ticket mentioned earlier, a good combination of both is likely where we want to land.

Tabular design suggestion, with current styling elements

The proposal to make it a forum listing (which it was, until HelpHub was introduced), uses the current 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/ design elements of colors, spacing and fonts to keep a consistent visual feel for the tabular element here.

Classic forum front

The above is the classic forum front, used in the old bbPress 1.x days, which gives a clear indication of what forums exist, but also allows an area for providing useful information to first time visitors like linking to guidelines, showing them how to search for content.

The tag cloud might even have a new life in the future, as work with curating tags, and removing the large amount of one-off tags that users generate is completed, but that is a different task, but ties in nicely with discoverability for those looking to volunteer.

Next step

The proposition, as it stands, is to combine the two options from above, into something that follows the current design-approach, but also makes the intent clear to users who are unfamiliar with the platform.

A quick mockup of what this mashup might look like is presented below, and should be the basis for any feedback at this time.

New forum front page mockup with two columns. Left side for user information, right side has a tabular list of forums and their description

What’s next

The floor is open for feedback, and will be for the next two weeks about what information should be included, how it should be presented, and so forth.

It should also be noted that this change would also affect the support front for rosetta forums, so we would love to hear from them as well in this regard.

Support team – November 5th – Summary

Headlines / Community updates

After some hearty discussions surrounding handling of support requests for commercial products on the 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/ forums, a set of guidelines for how moderators should respond to such topics was worked out.

This work spurred the now published Moderator Enforcement Guidelines, the goal of which is to ensure a unified response to scenarios that happen regularly, and make it easier to reference others to as well so they can see what the process is.

Open floor

We had a good discussion on how to get the forums more forum-like, there’s already a meta ticket for this (https://meta.trac.wordpress.org/ticket/4007), but it doesn’t quite hit all the right notes.
A post will follow with a proposal for how this could be approached, that would solidify their place as a forum, and also make discovery a bit easier.

#weekly-chat

Agenda for November 5th Support Meeting

The weekly support meeting will be held on Thursday, November 5th, 2020, 17:00 UTC in #forums 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/.. (a Slack account is required)

A note-taker for the meeting is requested, taking notes is a great way to get more involved with contributing to a team, and getting to know how they operate, so don’t be shy, no prior experiences needed, and volunteering happens at the start of the meeting!

Headlines / Community updates

Checking in with international liaisons

This is the section where we reach out to the non-English speaking parts of our community, to see how they are doing, if there’s anything we can help each other with, or just interesting things going on that it would be nice to share with others.

There’s no requirements for previous participation or “fame” to share here, anyone is welcome, and we encourage newcomers to participate!

Unable to make the meeting, or maybe meetings just aren’t your thing? We would still love to hear how things are going in other non-English speaking parts of our community. Please feel free to let us know via the comment section below, in your own time, if there is anything you’d like to share, any questions or concerns you have, ort just to let us know you’re doing ok!

We will make a habit of putting this callout with every agenda post going forward, so that everyone has a chance to join in.

Open floor

This part of the meeting only happens if there is time, the team aims to cover the pre-planned topics first in any given meeting.

When open floor starts, any topic posted either as a comment to this agenda post will be looked at, or as many as there is time for. If there is still time left after this, then meeting attendees may step forward with questions, comments, remarks, anything relating to the support team that they’d like to handle.

It is also important to note that not everyone is comfortable posting things publicly, there is complete understanding of this, and users are welcome to contact the team representative (@clorith) via direct messages on Slack with whatever they wish the team to look at together.

For any other items to discuss, please add them to the comments below, or bring them up in the meeting.

Agenda for October 29th Support Meeting

The weekly support meeting will be held on Thursday, October 29th, 2020, 17:00 UTC in #forums 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/.. (a Slack account is required)

A note-taker for the meeting is requested, taking notes is a great way to get more involved with contributing to a team, and getting to know how they operate, so don’t be shy, no prior experiences needed, and volunteering happens at the start of the meeting!

Headlines / Community updates

Checking in with international liaisons

This is the section where we reach out to the non-English speaking parts of our community, to see how they are doing, if there’s anything we can help each other with, or just interesting things going on that it would be nice to share with others.

There’s no requirements for previous participation or “fame” to share here, anyone is welcome, and we encourage newcomers to participate!

Unable to make the meeting, or maybe meetings just aren’t your thing? We would still love to hear how things are going in other non-English speaking parts of our community. Please feel free to let us know via the comment section below, in your own time, if there is anything you’d like to share, any questions or concerns you have, ort just to let us know you’re doing ok!

We will make a habit of putting this callout with every agenda post going forward, so that everyone has a chance to join in.

Open floor

This part of the meeting only happens if there is time, the team aims to cover the pre-planned topics first in any given meeting.

When open floor starts, any topic posted either as a comment to this agenda post will be looked at, or as many as there is time for. If there is still time left after this, then meeting attendees may step forward with questions, comments, remarks, anything relating to the support team that they’d like to handle.

It is also important to note that not everyone is comfortable posting things publicly, there is complete understanding of this, and users are welcome to contact the team representative (@clorith) via direct messages on Slack with whatever they wish the team to look at together.

For any other items to discuss, please add them to the comments below, or bring them up in the meeting.

Agenda for October 22nd Support Meeting

The weekly support meeting will be held on Thursday, October 22nd, 2020, 17:00 UTC in #forums 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/.. (a Slack account is required)

A note-taker for the meeting is requested, taking notes is a great way to get more involved with contributing to a team, and getting to know how they operate, so don’t be shy, no prior experiences needed, and volunteering happens at the start of the meeting!

Headlines / Community updates

  • WordPress 5.6-beta1 is available
  • Summary of our talking point on handling support requests for commercial products

Checking in with international liaisons

This is the section where we reach out to the non-English speaking parts of our community, to see how they are doing, if there’s anything we can help each other with, or just interesting things going on that it would be nice to share with others.

There’s no requirements for previous participation or “fame” to share here, anyone is welcome, and we encourage newcomers to participate!

Unable to make the meeting, or maybe meetings just aren’t your thing? We would still love to hear how things are going in other non-English speaking parts of our community. Please feel free to let us know via the comment section below, in your own time, if there is anything you’d like to share, any questions or concerns you have, ort just to let us know you’re doing ok!

We will make a habit of putting this callout with every agenda post going forward, so that everyone has a chance to join in.

Open floor

This part of the meeting only happens if there is time, the team aims to cover the pre-planned topics first in any given meeting.

When open floor starts, any topic posted either as a comment to this agenda post will be looked at, or as many as there is time for. If there is still time left after this, then meeting attendees may step forward with questions, comments, remarks, anything relating to the support team that they’d like to handle.

It is also important to note that not everyone is comfortable posting things publicly, there is complete understanding of this, and users are welcome to contact the team representative (@clorith) via direct messages on Slack with whatever they wish the team to look at together.

For any other items to discuss, please add them to the comments below, or bring them up in the meeting.

Agenda for October 15th Support Meeting

The weekly support meeting will be held on Thursday, October 15th, 2020, 17:00 UTC in #forums 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/.. (a Slack account is required)

A note-taker for the meeting is requested, taking notes is a great way to get more involved with contributing to a team, and getting to know how they operate, so don’t be shy, no prior experiences needed, and volunteering happens at the start of the meeting!

Headlines / Community updates

  • WordPress 5.6-beta1 is scheduled for next week
  • Procedures when blocking users
  • How is everyone doing

Checking in with international liaisons

This is the section where we reach out to the non-English speaking parts of our community, to see how they are doing, if there’s anything we can help each other with, or just interesting things going on that it would be nice to share with others.

There’s no requirements for previous participation or “fame” to share here, anyone is welcome, and we encourage newcomers to participate!

Unable to make the meeting, or maybe meetings just aren’t your thing? We would still love to hear how things are going in other non-English speaking parts of our community. Please feel free to let us know via the comment section below, in your own time, if there is anything you’d like to share, any questions or concerns you have, ort just to let us know you’re doing ok!

We will make a habit of putting this callout with every agenda post going forward, so that everyone has a chance to join in.

Open floor

This part of the meeting only happens if there is time, the team aims to cover the pre-planned topics first in any given meeting.

When open floor starts, any topic posted either as a comment to this agenda post will be looked at, or as many as there is time for. If there is still time left after this, then meeting attendees may step forward with questions, comments, remarks, anything relating to the support team that they’d like to handle.

It is also important to note that not everyone is comfortable posting things publicly, there is complete understanding of this, and users are welcome to contact the team representative (@clorith) via direct messages on Slack with whatever they wish the team to look at together.

For any other items to discuss, please add them to the comments below, or bring them up in the meeting.