DocsWP — WordPress Help

4.4 OMGWTFBBQ draft post

It’s a little rough and copy-pasta but here’s the 4.4 draft.

Starting with the boilerplate, first introduction post.

Hooray! FIX TITLE is here! But OMGWTFBBQ!? WordPress 4.4 broke everything?

Don’t Panic!

Before you go any further, make sure you’ve updated your plugins and themes to the latest versions, clear your browser’s cache and cookies and re-log into your WordPress dashboard.

Still having problems? Okay, read on!

This thread contains the known issues with plugins and themes found in 4.4. Please read this WHOLE topic and come back and check again later, as it will be updated.

Remember to be calm, be patient and be respectful. Volunteers are out here to try and help you, but we need your help too. All of the normal forum rules still apply. Remember, you are just as important as everyone else.

If your post doesn’t show up right away, please be patient. With the higher than normal post volume, more posts get flagged as spam by our auto-spam tool. We’re working hard to keep the queue clear, but making multiple posts slows us down, as we have to go back and check if you already posted. Post once.

  • Do use proper capitalization in post titles and body. Punctuate your sentence properly and humanely, it helps us read.
  • Do use descriptive subject lines. “All permalinks broken since 4.4” is much better than “Augh! Help ASAP! This version is terrible!”
  • Do describe the problem clearly. Explain what you’re seeing, include error messages and link to screenshots if needed. Linking to your site, if the problem is on the front-end, also helps.
  • Do be patient. We know it sucks to be down, but posting multiple times doesn’t get you help any faster.
  • Do make your own topic unless you are using the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme and configurations as the original poster. You may find it weird, but it will be easier for us to help you specifically if you have your own topic.
  • Do mark your topic as resolved when it’s fixed so we know not to come looking there anymore.
  • Do remember you’re not alone.

Also keep in mind that not liking the direction of WordPress’s design does not a bug make. If you don’t like a feature, please don’t make a series of posts complaining about it. Look and see if someone already did, and post there, or consider joining the process earlier on (like in Beta or even test via SVN). What you’re seeing today is the result of thousands of hours of work and testing, and unless something is outright broken, it’s highly unlikely to be changed.

Again, before you post:

Make sure you’ve read the entire Master List post – and the New Features in 4.4 Codex Article – https://codex.wordpress.org/Version_4.4

Go to your own install’s about page – `http://example.com/wp-admin/about.php` – to see what’s new.

And then make sure you’ve tried…

  • Flushing any caching plugins you might be running, as well as server and/or browser caches. Not just your browser, but any op cache or content network cache as well such as Cloudflare. That will solve many weird Javascript issues.
  • If your host provider has a “Purge Varnish” option or if you can ask your provider to flush memcache on your server.
  • Deactivating all plugins (yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin (read “How to deactivate all plugins when you can’t log in to wp-admin” if you need help). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to `mu-plugins-old`
  • Switching to the Twenty Fifteen theme to rule out any theme-specific problems. If you can’t log in to change themes, you can remove the theme folders via FTP so the only one is `twentyfifteen`. That will force your site to use it.
  • Manually upgrading. When all else fails, download a fresh copy of the latest.zip file of 4.4 (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server (NOTE: do not delete the `wp-content` directory or your `wp-config.php` file) Read the Manual Update directions first.

Next post for CORE CHANGES

What’s New:

  • Twenty Sixteen is the new default theme.
  • Externally embeddable. WordPress 4.4 will now act as an oEmbed provider for posts. This can be disabled with a plugin.
  • Responsive images support This will display alternate size images for different view sizes in the browser via the srcset attribute. You don’t need to worry about anything. While your existing images won’t be ‘converted’ they also don’t need to be as the code is really smart and uses the image sizes you already have rather than make new ones. If you want to regenerate your images to use the new `medium-large` size, you can use one of the existing plugins (e.g. the Regenerate Thumbnails plugin).
  • Changes to the comment form layout.
  • REST API support – You really want to use the REST API Plugin if you want to use the API. If you were already using it, please upgrade to either 1.2.4 for the v1 branch or beta8 for v2 so things continue to work.
  • Term Meta – It’s awesome! the term meta functions will return a WP_Error object if the term has not been split.

What’s Changed:

Next post for NOT A BUG

NOT A BUG

My layout is all weird on the Dashboard

Flush your cache. If you’re using server caches, or a plugin, flush them too, especially Memcached/APC stuff. They can be sticky. This includes Cloudflare and Pagespeed and Varnish. Anything that caches.

I’ve upgraded and the posts are not styled correctly

Check if you are running `mod_pagespeed` and if you are try disabling it to see if your posts render correctly.

I’m on 4.4 but I have no JSON Endpoints!

You have to install the Rest API plugin to actually activate the endpoints.

Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration.

Despite how it sounds, this typically means that openssl on your server is out of date, unless of course WordPress.org is actually offline. You’ll need to ask your hosting provider upgrade openssl on the server to the latest release (currently 1.0.2e).

Next post for KNOWN ISSUES

Known Issues

  • WP CLI – Needs to be upgraded to WP-CLI v0.21.1 or v0.20.4 otherwise it won’t work.
  • JSON/REST API – Needs to be upgraded to the latest version of whatever branch you run to work.

Hopefully we will not need this one, with 4.3 we did not.

REPORTED OOPSIES