Lets Get Ready for 3.7!

Normally I do an OMGWTFBBQ post. Here’s everything in my current draft, ready for editing by everyone!

The first section is ‘Stuff we, as mods, should be aware of.’ The second is the post itself 🙂

Major changes

Auto Upgrader
* How to disable
* In order for Automatic Updates to be enabled, there are a few simple requirements:
* If the install uses FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients. for updates (and prompts for credentials), automatic updates are disabled
* If the install is running as a SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. or GITGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. checkout, automatic updates are disabled
* If the constants DISALLOW_FILE_MODS or AUTOMATIC_UPDATER_DISABLED are defined, automatic updates are disabled
* If the constant WP_AUTO_UPDATE_CORE is defined as false, automatic updates are disabled
* Your WordPress install also needs to be able to contact WordPress.orgWordPress.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/ over HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. connections, so your PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. install also needs OpenSSL installed and working
* Wp-Cron needs to be operational, if for some reason cron fails to work for your install, Automatic Updates will also be unavailable
* What gets updated?
* What changed. ONLY changed files!
* Only for minor releases (3.7 to 3.7.1 but NOT 3.7.1 to 3.8)

Less Major Changes

  • Better search results
  • Password meter
  • Visual editor (TinyMCE) updated for Internet Explorer compatibility

Under the Hood

  • New dev tools
  • New author queries
  • MultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. finally has a way to get an array of all sites on the network
  • Better inline documentation
  • Better date sorting in the posts page

For the post….

Troubleshooting WordPress 3.7 Master List

Hooray! NEWVERSION is here. But OMGWTFBBQ!? WordPress 3.7 broke everything?

Don’t Panic!

This thread contains the known issues with plugins and themes found in 3.7. 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 3.7” 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 Admin 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 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. or even test via SVN). What you’re seeing today is the result of months 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 3.7 Codex Article – https://codex.wordpress.org/Version_3.7

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.
  • 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 pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party(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 Twelve or Twenty Thirteen 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 twentythirteen. That will force your site to use it.
  • manually upgrading. When all else fails, download a fresh copy of the latest.zip file of 3.7 (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. Read the Manual Update directions first.

CORECore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CHANGES

What’s new:

  • Background Updates:  WordPress now auto-upates minor releases for security fixes. So when 3.7.1 comes out, you will be automatically updated to that provided you meet certain criteria. – If you’re using SVN/GIT/Any-versioning-software or have to enter your FTP credentials to upgrade, the background updates are disabled.



I don’t want background updates you suck!

The core team and many others sat and discussed this for a long time. The auto-updates are there to mitigate security issues, and they’re on by default because the people who need them the most are the same people who would be less likely to notice and turn it on. While you may disagree with this rationale, it’s not a bug. It was a conscious decision. Keep in mind, they’re turned off for people who legitimately SHOULD have them off, like folks who have to enter their FTP credentials when installing plugins etc.

If you don’t like it, you can turn them off. Go into `wp-config.php` and put this above the ‘stop editing here’ line:

`define(WP_AUTO_UPDATE_CORE, false);`

Need more? `WP_AUTO_UPDATE_CORE` can be defined instead to allow more fine grained control. Set it to one of these:

  • false = no updates
  • true = ALL updates
  • minor = Minor releases only

Filters exist to allow you to allow specific kinds of updates as well. Return true to allow each of these, false to disallow them:

  • `allow_dev_auto_core_updates` – if you’re on a development version, and this filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. gets returned a true value, then it will enable dev/beta updates.
  • `allow_minor_auto_core_updates` – Allows minor updates (default true)
  • `allow_major_auto_core_updates` – Pretty much what it says on the box (default false).