Support » Fixing WordPress » READ THIS FIRST WordPress 4.6 Master List

  • ResolvedModerator James Huff

    (@macmanx)


    Volunteer Moderator 🚀

    Hooray! WordPress 4.6 “Pepper” is here! But OMGWTFBBQ!? WordPress 4.6 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.
    t
    Still having problems? Okay, read on!

    This thread contains the known issues with plugins and themes found in 4.6. 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.6” 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 is a not a bug. 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 this entire thread and New Features in 4.6 Codex Article.

    Go to your own install’s about page – 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.
    • Troubleshooting with your browser. Your browser can help you identify JavaScript issues or conflicts and this article can assist you in doing that diagnosis. This could help identify Visual Editor issues as well.
    • 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 Sixteen 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 twentysixteen. 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.6 (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.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator 🚀

    Not a Bug

    The following features changed behavior.

    My Dashboard Fonts Look Different: It is true that WordPress used to have one font across all operating systems and browsers. It did this by basically downloading Open Sans from Google Fonts on every single Dashboard page load. Default system fonts have improved dramatically over the years, and the developers have decided to cut Google out of the mix and simply use the default system font of whichever device you’re currently using. Along with a new font, you should be noticing a slight speed increase and less data usage from your Dashboard pages.

    While every attempt has been made to ensure that there are no breaking issues with this change, if you notice that the font in your Dashboard is unreadable, please open a new thread in these support forums listing your operating system and browser (and versions of both), and a screenshot (which you can upload via Media -> Add New in your site’s Dashboard, click on the new file in the Media library, copy the File URL to the right, and add that File URL to your new thread’s content).

    Words from my theme/plugins have changed: Some plugins and themes still include their own translations, with WordPress 4.6 we made changes to how translations are prioritized. This means translations submitted by the community now get prioritized over ones submitted by the authors themselves, and may in some cases mean that words have seen some changes. If you run into any problems with this, please leave detailed feedback under #34213.

    The category and tags screens look strange: The ordering of elements on these pages were changed to be more intuitive as well as to improve accessibility. Some plugins may rely on the ordering, or add their own output here, which may look out of place or not work as intended after the update. Make sure you’ve updated your themes and plugins, and if it’s still looking strange, consider contacting the author to have them updated for the latest version of WordPress.

    I can’t link to malformed URLs: As a convenience feature, the Insert Link button in the Visual editor tab now prevents adding malformed URLs (links which would never work). We do understand that people use WordPress in surprising ways, so you can still link to malformed URLs in the Text editor tab.

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator 🚀

    Known Issues

    • Some users have reported altered Media titles after upgrading to WordPress 4.6.1. See #37989 for details. (fixed in 4.7)
    • When enabled, plugin auto-updates can fail if they involve several plugins in a row. See #38024 for details. (fixed in 4.7)
    • Some users have reported “cURL error 23: Failed writing body” when updating plugins or themes. See #38226 for details. (fixed in 4.7)
    • Some users have reported an increase in function calls to get_locale() since the update. See #37997 for details. (fixed in 4.7)
    • A very small number of users have reported seeing Warning: ini_get_all() has been disabled for security reasons after the update. Please contact your hosting provider and ask them to enable ini_get_all() (which is perfectly safe on a properly maintained server). Alternatively, you may be able to fix this issue yourself by upgrading your version of PHP to 5.6 or higher (if available in your hosting account’s control panel). The WordPress developers are considering an adjustment to WordPress as well to avoid this, see #37680 for details. (fixed in 4.6.1)
    • A very small number of users have reported seeing Warning: curl_exec() has been disabled for security reasons after the update. Please contact your hosting provider and ask them to enable curl_exec() (which is perfectly safe on a properly maintained server). Alternatively, you may be able to fix this issue yourself by upgrading your version of PHP to 5.6 or higher (if available in your hosting account’s control panel). The WordPress developers are considering an adjustment to WordPress as well to avoid this, see #37700 and below for details. (fixed in 4.6.1)
    • A very small number of users have reported seeing Notice: Undefined variable: collate after the update. Setting DB_COLLATE in wp-config.php will fix this for now. See #37683 for details. (fixed in 4.6.1)
    • A very small number of users have reported seeing symbols converted into invalid characters after the update. Commenting out the DB_CHARSET define in wp-config.php (adding a # in front of the line) will fix this for now. See #37689 for details. (fixed in 4.6.1)
    • A small number of users have reported emails not being sent out as expected. This is due to a new flag being added to show who sent the email which doesn’t function properly on all hosts. See #37736 for details. (fixed in 4.6.1)
    • This reply was modified 1 year, 8 months ago by  James Huff. Reason: confirmed and marked items as fixed in 4.6.1
    • This reply was modified 1 year, 8 months ago by  James Huff. Reason: added altered Media titles after upgrading to WordPress 4.6.1
    • This reply was modified 1 year, 7 months ago by  James Huff. Reason: added 38024
    • This reply was modified 1 year, 7 months ago by  James Huff. Reason: added curl error and get_locale() issues
    • This reply was modified 1 year, 5 months ago by  James Huff. Reason: all reported issues have been fixed
    Moderator James Huff

    (@macmanx)

    Volunteer Moderator 🚀

    Plugin and Theme Issues

    Genesis (StudioPress) users may experience a fatal error if they have not updated their theme yet, updating to version 2.3.1 or later ensures compatibility with WordPress 4.6

    Thesis 1.8 (which is very old anyway) and its child themes may see the following error:

    Error message is Fatal error: Cannot redeclare the_post_thumbnail_caption() (previously declared in /home/USER/public_html/wp/wp-includes/post-thumbnail-template.php:244) in /home/USER/public_html/wp/wp-content/themes/thesis_18/custom/custom_functions.php on line 617

    This is due to a poorly named (non prefixed) function which was added post install (that is – it’s NOT in core thesis, but a significant number of people have added it to the main theme). You can either rename the calls to the_post_thumbnail_caption or upgrade to Thesis 2.x. Also please remember – DON’T edit your parent themes directly 🙂 Make child themes.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Note: The following was fixed in WordPress 4.6.1.

    Warning: curl_exec() has been disabled for security reasons

    or

    Warning: http_build_query(): Parameter 1 expected to be Array or Object. Incorrect value given…

    There is a known issue in WordPress 4.6 that occurs on some hosting systems.

    The problem is that some hosts intentionally disable the “curl” parts of PHP. Sometimes, they only disable specific functions, like curl_exec instead of all of the curl functions.

    The check for this condition in the new Requests library did not take this possibility into account correctly. A ticket on this matter is here:
    https://core.trac.wordpress.org/ticket/37700

    The fix for this is as follows:

    Edit the file /wp-includes/Requests/Transport/cURL.php. On line 527 you will find this code:

    if (!function_exists('curl_init') && !function_exists('curl_exec')) {

    Change the && to an ||, like so:

    if (!function_exists('curl_init') || !function_exists('curl_exec')) {

    This fix will likely be included in future versions of WordPress. If you are having this problem now, or other similar problems with the curl transport, then you can make this change manually to correct the issue.

    Alternatively, if your host allows you to change which version of PHP you use, then select PHP 5.6 or PHP 7.0. On some hosting systems, these newer versions of PHP have the curl systems enabled, which will also eliminate the problem. Always select the latest version of PHP which is available to you.

    • This reply was modified 1 year, 8 months ago by  James Huff. Reason: confirmed and marked as fixed in 4.6.1
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘READ THIS FIRST WordPress 4.6 Master List’ is closed to new replies.