Hi, the Community Team would like to start creating events.wordpress.org email addresses, to correspond with the sites we recently setup. Similar to WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. addresses, they would be hosted in the WordPress Foundation GSuite, and would take the format of firstname.lastname@example.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/, etc.
Are there any complications around that? If not, can you please set it up? I’ve added the domain to the email@example.com account, but it needs to be verified with a TXT record. You can get the value from https://admin.google.com/ > Account > Domains > Manage Domains. I’m assuming they’ll provide the MX values etc after that process is complete.
Let me know if you have any thoughts or if there’s anything else you need.
Can we please setup an email redirect for
This is the same destination as the
forum-password-resets@ email address.
Thank you in advance.
#email #prio2 #helpscout
Can we please setup an email redirect for
#email #prio2 #helpscout
Nao please be granted access to WordPress.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/ MC as part of her 5ftf work?
release access not required.
It’s time for forums.wordpress.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/ to cease executing bbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org.. This is the final component on WordPress.org running bbPress 1.x that I’m aware of. It’s not PHP8 compatible.
The mobile forums were deactivated a year ago, and the locale forums 7 years ago.
I’d personally like to simply remove the
forums role and the subdomain entirely, but that’ll break any old links that still remain. For now, can we just cease loading bbPress and instead…
In r20481-dotorg I’ve added a new file, index.php to the forums public_html.
Can we please:
1. Change the
root to be
..../public_html/ instead of referencing
2. Remove all bbPress rewrite rules from
wporg-forums.wordpress.org, replacing it with a singular rule that directs all traffic to
3. Add a DNS DNS is an acronym for Domain Name System - how you assign a human readable address to a website’s exact numeric coded location (ie. wordpress.org uses the actual IP address 220.127.116.11). A/CNAME entry for
forums.wordpress.org (Apparently this doesn’t have a DNS entry)
#bbpress #nginx #prio2
I currently have a wp.org sandbox but it doesn’t have access to wordcamp.org. Can I get access to help upcoming feature development?
#sandbox #prio2 #wordcamp
As reported in https://wordpress.org/support/topic/api-wordpress-org-is-on-abuseip-db-blacklis/ it looks like some hosts have been confusing outgoing connections to api.wordpress.org as being incoming brute-force requests, and reporting it as such.
It appears that some hosts/networks may be using this as part of a network DROP rules causing WordPress sites being unable to connect to the API 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.. I believe this might be the cause of some past issues where .251 was inaccessible but .252 was.
Can someone from systems request removal, specifically for https://www.abuseipdb.com/check/18.104.22.168
Can NodeJS 18.x be installed on the build server with the paired version of npm (currently 9.3.1)?
Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. currently uses NodeJS 14.x, which will reach EOL on April 30, 2023. Work is underway for both Core and Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ to support 18.x (see Core Trac-56658 and this Gutenberg PR/Issue list). The changes needed to support 18.x are being made now with the aim of changing the actual version used in both locations prior the EOL date in a few months.
There are currently no plans to update older branches receiving minor or security releases at this time, so 14.x will need to remain on the server for the time being.
CC: @gziolo who I’ve been coordinating with on the Gutenberg side of things.
As posted in #meta: https://wordpress.slack.com/archives/C02QB8GMM/p1670234270428419
I sorry if I chose wrong channel, but I’m having trouble accessing api.wordpress.org from multiple servers, like in these threads: https://make.wordpress.org/systems/2020/11/25/are-there-any-network-level-non-nginx/ https://wordpress.org/support/topic/server-ip-blocked/page/2/ https://wordpress.slack.com/archives/C02QB8GMM/p1605164522008700
For example 22.214.171.124. I can resolve api.wordpress.org, ping it – but not connect to 80 or 443 port: https://pastebin.com/r1B4PvPg
tcptraceroute to 80 and 443 ports: https://pastebin.com/qyQid5aB
tcpdump, GMT+3 time: https://pastebin.com/Tzd3JPMR
From another server (IP 126.96.36.199, same /24 subnet) everything is fine: https://pastebin.com/sHuCRkvG
Or, if i add custom route for 188.8.131.52 on the problem server, api becomes available: https://pastebin.com/1DnmeL1i , https://pastebin.com/hEKrWMwr
Looks like 184.108.40.206 is banned on api.wordpress.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/ or something in beetwin blocking traffic from api.wordpress.or to 220.127.116.11. Can anyone check this?
Can systems please check, and for future requests, state how they’d like these to be raised when they come in? I didn’t want to just tell them to email y’all without you expecting it.
Per https://wordpress.slack.com/archives/C02QB8GMM/p1666717073063339 it looks like two wordfence IPs have been blocked from plugins.svn.wordpress.org – other svn.wordpress.org hosts are accessible.
It appears they had an automated release process go wrong, causing the IPs to be blocked.
See the above Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. thread for IPs and backstory.