Support Team Update for April 17th

In today’s #wordpress-sfd support meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on will help you find options in your area. the following items were discussed.

WordPress 3.8.3 was released

On April 14th the update to 3.8.3 was released. This fixed a bug with Quick Draft that was introduced with 3.8.2.

WordPress 3.9 was released

On April 16th WordPress 3.9 “Smith” was also released and the 3.9 Master list post was put up and updated as needed.

As expected there have been some 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 Plugin Directory or can be cost-based plugin from a third-party related TinyMCE/Visual Editor issues. Impacted users have been asked to troubleshoot JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. problem using these Codex instructions.

When a plugin is identified as requiring an update it gets put on the REPORTED OOPSES list and tracked there. When the plugin is confirmed as fixed then please update the post and cross it off the list with <del>…</del>.

There do not seem to be any theme issues reported but if there are it will most likely have to do with the Masonry library update.

Also discussed were topics related to image padding/borders and memcache issues.

Better updates through education?

Part of the discussion was the idea from @zoonini to not only have a sticky OMGWTFBBQ post but have another sticky post that refers users to the updating WordPress Codex article.

I think that’s a good idea and for the next major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. that should be done. Minor version number releases are and should be handled by the auto updates. If your installation is negatively impacted by an auto update then you may have a bigger problem with your plugins and theme.

Major version number releases (3.8 to 3.9) should be upgraded via the dashboard as well but with planning. A user who follows the Codex update instructions (backups and knows how to restore to an earlier state) really can’t get into too much trouble. With that safety net if something breaks then they can roll back to a previous working state if they need to.

I myself don’t know how to pull off educating the users but another brief sticky post may help more users be prepared for an upgrade.

Today’s transcript can be read online via this link.