Auto-updates for WordPress 4.9.6 were enabled last night, and should be flowing out steadily at this time.<\/p>\n
Besides the usual need to clear caches after an update (especially one that includes editor updates).<\/p>\n
We can note that there is a known regression in TinyMCE which may cause a handful of plugins to break when viewing the editor. The coreCore<\/span> Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> team is already aware of this and are working on sorting that.<\/p>\n \u00a0<\/p>\n Shelters are stocked for a weekend of fun! With the forums seeing around ~10k GDPR related topics and posts on the forums, we\u2019re expecting more once the regulations kick in on the 25th. To address this, and the constant topics on pluginPlugin<\/span> 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\/<\/a> or can be cost-based plugin from a third-party.<\/span><\/span><\/span> pages asking if they\u2019re compliant or not, we\u2019ve created a sticky post<\/a> that will show up on the support forums, to hopefully help users find out where to go to get the right answers to their questions, and most specifically: Not to seek legal advise on the forums.<\/p>\n \u00a0<\/p>\n The Swedish<\/a>, Russian<\/a>, Greek<\/a>, Serbian<\/a>,\u00a0German<\/a>\u00a0and Brazilian<\/a> community representatives dropped by this week to join the discussions.<\/p>\n \u00a0<\/p>\n @<\/span>abdullahramzan<\/a>, @<\/span>amboutwe<\/a>, @<\/span>bcworkz<\/a>, @<\/span>bemdesign<\/a>, @<\/span>clorith<\/a>, @<\/span>contentiskey<\/a>, @<\/span>felipeelia<\/a>, @<\/span>fierevere<\/a>, @<\/span>geoffreyshilling<\/a>, @<\/span>ipstenu<\/a>, @<\/span>jdembowski<\/a>, @<\/span>joyously<\/a>, @<\/span>keesiemeijer<\/a>, @<\/span>lakenh<\/a>, @<\/span>macmanx<\/a>, @<\/span>nikolam<\/a>, @<\/span>numeeja<\/a>, @<\/span>otto42<\/a>, @<\/span>presstigers<\/a>, @<\/span>pross<\/a>, @<\/span>stephencottontail<\/a>, @<\/span>t-p<\/a>, @<\/span>tobifjellner<\/a>, @<\/span>valeriosza<\/a>, @<\/span>xkon<\/a> and @<\/span>zodiac1978<\/a> attended.<\/p>\n \u00a0<\/p>\n Read the meeting transcript in the Slack archives<\/a>. (A Slack account is required<\/a>)<\/p>\nThe GDPR approaches<\/h2>\n
Checking in with international liaisons<\/h2>\n
Attendance<\/h2>\n