WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 4 years ago

#835 closed enhancement (fixed)

Update text for letter to Host with better text

Reported by: sc0ttkclark Owned by:
Milestone: Priority: normal
Component: General Keywords: dev-feedback
Cc:

Description

It's admitted by just about everyone, hosts are the problem to combatting outdated and insecure versions of PHP / etc. So it's probably long past time for us to update the letter we recommend folks send to their host (or potential new host).

https://wordpress.org/about/requirements/

The text reads:

Ask for it
Here’s a letter you can send to your host; copy and paste!

I'm interested in running the open-source WordPress <http://wordpress.org/> blogging software and I was wondering if my account supported the following:

PHP 5.2.4 or greater
MySQL 5.0 or greater
The mod_rewrite Apache module
Thanks!

If they are contacting their host, we should be having them talking about more recent non-EOL versions than this. Some additional wording that 5.2.4+ etc could then still be there.

Any ideas on how to improve this, and get people asking their hosts about more recent versions than this? To put this into perspective for folks from the US, the current letter essentially asks a host if they have any servers (or server images) that haven't been updated since Bush was in office in 2007.

Change History (3)

#1 @sc0ttkclark
4 years ago

We might also consider changing the text 'blogging software' to something else.

#2 @nacin
4 years ago

I've pushed an update to this page that:

  • Adds our recommendations next to our requirements
  • Changes the email to ask about our recommendations, not our requirements
  • Adds a note (right column) that we support the latest versions

(I've been meaning to do this for a while.)

I've not changed "blogging software" because it doesn't really bother me in the context of asking your shared host a pretty simple question. "publishing software" is more marketing speak here, as would something like "CMS".

#3 @coffee2code
4 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Closing as fixed after nacin's update noted above, especially since the change hasn't since been challenged.

Note: See TracTickets for help on using tickets.