READ THIS FIRST WordPress 4.8 Master List

  • Moderator Marius L. J.

    (@clorith)


    7 years, 5 months ago

    Hooray! WordPress 4.8 “Evans” is here! But OMGWTFBBQ!? WordPress 4.8 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.8. 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.8” 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.8 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.
    • Flushing Managed host caches. Managed WP hosting often has special caches. If your host has a “Purge Varnish” or “Flush Memcache” tool, try that. You can ask your provider to flush memcache and Varnish for you if necessary.
    • 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 SFTP/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 SFTP/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.8 (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 6 replies - 1 through 6 (of 6 total)
  • Moderator Marius L. J.

    (@clorith)

    Core changes

    Moderator Marius L. J.

    (@clorith)

    Not a Bug

    The new media widgets don’t work in my theme.
    If your theme hides widgets by default in some way – like in a slide-out panel – then the new audio and video widgets may not be displayed correctly. If you are a theme developer, here is an example for solving this.

    Text from the updated text widget is going outside the designated area.
    Your theme will need to be updated to work with the new HTML that the editor will wrap content in after the update to 4.8.

    I am getting a “Failed to load content css” warning.
    This warning appears when a editor style isn’t properly set up (for example a child theme trying to include a parent editor style with @import with the wrong path). It will have to be fixed by your theme author so that any link to CSS files are correct.
    See the more detailed post below.

    • This reply was modified 7 years, 5 months ago by Steven Stern (sterndata). Reason: fixed spelling error
    • This reply was modified 7 years, 5 months ago by Kathryn Presner. Reason: edit for clarity
    • This reply was modified 7 years, 5 months ago by Kathryn Presner. Reason: formatting fix
    • This reply was modified 7 years, 5 months ago by Marius L. J.. Reason: Make note of 'Failed to load content css' in new TinyMCE
    Moderator Marius L. J.

    (@clorith)

    Known Issues

    • Editor tools are not showing as expected in WordPress 4.8.1 – Our editor, TinyMCE,
      was updated in this release, so your plugin or theme may need to be updated to reflect this change
    • This reply was modified 7 years, 3 months ago by Marius L. J.. Reason: Add TInyMCE issue reference
    Moderator Marius L. J.

    (@clorith)

    Plugin and Theme Issues

    • Visual Composer has some incompatibilities with WordPress 4.8.1 – Resolution: Update to Visual Composer version 5.2.1 or later.
    • This reply was modified 7 years, 3 months ago by Marius L. J..
    • This reply was modified 7 years, 3 months ago by Marius L. J.. Reason: Update VC compatibility issue
    Moderator Marius L. J.

    (@clorith)

    Failed to load content css

    This issue keeps popping up for users after the 4.8 update, so here’s a more in-depth process of what is happening.

    The error means that the editor window was unable to load one or more resources, generally added using the editor_styles function, this is primarily added by your theme, but can also be implemented by plugins (if you would like to identify the exact cause of it, please follow the regular troubleshooting steps outlined in the first post of this thread).

    This issue can have many root causes, I’ll run through some of them, so you know what you are looking for, or what to inform your theme developer about:

    • The style file does not exist at all
    • The style file uses one or more @import() calls to include files, but the path is wrong
    • Your site is using SSL (your URL starts with https://), but the resources being loaded are trying to use un-encrypted https:// links
    • The URL being included is an external one, and is incorrect. So far primarily seen with Google Fonts, where a %2C is added to the end of the link (this is considered a comma, and the link is invalid from Googles point of view if it ends like this)

    All of these situations, and probably some other scenarios we’ve not outlined, cause the warning to show up. What is important to take note of here is that this is just that, a warning, it will not affect the performance of your website, it just means the text editor window won’t preview what it will look like as accurately as it could.

    This is not a bug in WordPress 4.8, but rather a warning introduced to help you get the best possible editor experience, but unfortunately it is up to the theme and plugin developers to implement the features correctly.

    Moderator Marius L. J.

    (@clorith)

    HTML and text widgets in WordPress 4.8.1
    A new Custom HTML widget was introduced in WordPress 4.8.1 to give a proper home for little markup snippets that the existing text widget was commonly used for in the past.

    You may see some notices when using the Text Widget, these leave no cause for alarm, and are only there to help you use the right tools for the job.

    —

    Existing text widgets
    When an existing text widget has any markup in it, it will detect this. If this happens the widget will go into legacy mode, and show the warning This widget may contain code that may work better in the new "Custom HTML" widget. How about trying that widget instead?.

    Legacy mode means that the text widget will look and behave like before the 4.8.0 update, but it is not an ideal approach, which is why we show the notice and recommend moving it over to the new Custom HTML widget.

    Adding markup to the text widget visual tab
    If you attempt to paste a snippet of markup into the text editor, you will be presented wit ha notice stating Hey there, looks like you just pasted HTML into the "Visual" tab of the Text widget. You may want to paste your code into the "Text" tab instead. Alternately, try out the new "Custom HTML" widget!.

    This is presented because markup in the visual tab is stripped down and sanitized, and you will end up seeing HTML code on your front end.

    Adding markup to the text widget text tab
    When opening the text tab of the widget you may be presented with the notice Hey, did you hear we have a "Custom HTML" widget now? You can find it by scanning the list of available widgets on this screen. Check it out to add some custom code to your site!.

    The notice is there to guide users who to use the appropriate widget, as many tutorials online will say to use the text widget. It is still possibly to put markup in the text tab, but we highly recommend using the Custom HTML widget instead.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘READ THIS FIRST WordPress 4.8 Master List’ is closed to new replies.