![\"Graph](\"https://i0.wp.com/wordpress.org/news/files/2019/03/w3techs-content-management-systems-usage.png?w=632&ssl=1\")
WordPress now powers over 1/3rd of the top 10 million sites on the web according to W3Techs. Our market share has been growing steadily over the last few years, going from 29.9% just one year ago to 33.4% now. We are, of course, quite proud of these numbers!
The path here has been very exciting. In 2005, we were celebrating 50,000 downloads. Six years later, in January 2011, WordPress was powering 13.1% of websites. And now, early in 2019, we are powering 33.4% of sites. Our latest release has already been downloaded close to 14 million times, and it was only released on the 21st of February.
Over the years WordPress has become the CMS of choice for more and more people and companies. As various businesses use WordPress, the variety of WordPress sites grows. Large enterprise businesses all the way down to small local businesses: all of them use WordPress to power their site. We love seeing that and we strive to continuously make WordPress better for all of you.
\n\n\n\nWe’d like to thank everyone who works on WordPress, which is built and maintained by a huge community of volunteers that has grown alongside the CMS. This incredible community makes it possible for WordPress to keep growing while still also remaining free. And of course, we’d like to thank all of you using WordPress for using it and trusting in it. To all of you: let’s celebrate!
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6789\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 5.1.1 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Mar 2019 03:34:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:5:\"5.1.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6736\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:365:\"WordPress 5.1.1 is now available! This security and maintenance release introduces 14 fixes and enhancements, including changes designed to help hosts prepare users for the minimum PHP version bump coming in 5.2. This release also includes a pair of security fixes that handle how comments are filtered and then stored in the database. With a maliciously […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Luke Carbis\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4080:\"\nWordPress 5.1.1 is now available! This security and maintenance release introduces 14 fixes and enhancements, including changes designed to help hosts prepare users for the minimum PHP version bump coming in 5.2.
\n\n\n\nThis release also includes a pair of security fixes that handle how comments are filtered and then stored in the database. With a maliciously crafted comment, a WordPress post was vulnerable to cross-site scripting.
\n\n\n\nWordPress versions 5.1 and earlier are affected by these bugs, which are fixed in version 5.1.1. Updated versions of WordPress 5.0 and earlier are also available for any users who have not yet updated to 5.1.
\n\n\n\nProps to Simon Scannell of RIPS Technologies who discovered this flaw independent of some work that was being done by members of the core security team. Thank you to all of the reporters for privately disclosing the vulnerabilities, which gave us time to fix them before WordPress sites could be attacked.
\n\n\n\nOther highlights of this release include:
\n\n\n\nYou can browse the full list of changes on Trac.
\n\n\n\nWordPress 5.1.1 was a short-cycle maintenance release. Version 5.1.2 is expected to follow a similar two week release cadence.
\n\n\n\nYou can download WordPress 5.1.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.
\n\n\n\nIn addition to the security researcher mentioned above, thank you to everyone who contributed to WordPress 5.1.1:
\n\n\n\nAaron Jorbin, Alex Concha, Andrea Fercia, Andy Fragen, Anton Vanyukov, Ben Bidner, bulletdigital, David Binovec, Dion Hulse, Felix Arntz, Garrett Hyder, Gary Pendergast, Ian Dunn, Jake Spurlock, Jb Audras, Jeremy Felt, Johan Falk, Jonathan Desrosiers, Luke Carbis, Mike Schroder, Milan Dinić, Mukesh Panchal, Paul Biron, Peter Wilson, Sergey Biryukov, and Weston Ruter.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6736\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"The Month in WordPress: February 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2019/03/the-month-in-wordpress-february-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 01 Mar 2019 10:00:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6652\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:363:\"A new version of WordPress, significant security enhancements, important discussions, and much more – read on to find out what has been going on in the WordPress community for the month of February. Release of WordPress 5.1 Near the end of the month, WordPress 5.1 was released, featuring significant stability and performance enhancements as well […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:7509:\"\nA new version of WordPress, significant security enhancements, important discussions, and much more – read on to find out what has been going on in the WordPress community for the month of February.
\n\n\n\nNear the end of the month, WordPress 5.1 was released, featuring significant stability and performance enhancements as well as the first of the Site Health mechanisms that are in active development. Most prominent is the new warning for sites running long-outdated versions of PHP.
You can check out the Field Guide for this release for a detailed look at all the new features and improvements. The next release is already in development with plans to improve the Site Health features, PHP compatibility, and a number of other things.
Want to get involved in testing or building WordPress Core? You can install the WordPress Beta Tester plugin, follow the Core team blog, and join the #core channel in the Making WordPress Slack group.
\n\n\n\nThe block editor that is now a part of WordPress core started out as a project named Gutenberg with the lofty goal of creating a whole new site-building experience for all WordPress users. The first phase of Gutenberg resulted in the block editor that was included in WordPress 5.0, but development didn’t stop there – phase 2 of the project is well underway.
This month, one of the initial goals for this phase was reached with all of the core WordPress widgets being converted to blocks – this will go a long way to allowing full sites to be built using blocks, rather than simply post or page content.
Want to get involved in developing Gutenberg? Check out the GitHub repository and join the #core-editor channel in the Making WordPress Slack group.
\n\n\n\nAs Gutenberg development continues, the Mobile team has been working hard to integrate the new block editor into the WordPress mobile apps. Near the end of February, the team shipped a complete integration in the beta versions of the apps – this a significant milestone and a big step towards unifying the mobile and desktop editing experiences.
Both the iOS and Android apps are open for beta testers, so if you would like to experience the block editor on mobile today, then join the beta program.
Want to get involved in developing the WordPress mobile apps? Follow the Mobile team blog, and join the #mobile channel in the Making WordPress Slack group.
One of the goals for 2019 that Matt Mullenweg (@matt) announced in his State of the Word address last year was to form a team who would work to manage the ever-increasing number of tickets in Trac, the bug tracker that WordPress Core employs.
\n\n\n\nThis team, known as the Triage Team, has been announced. Their work will involve coordinating with component maintainers, release leads, project leadership, contributors, and other WordPress related projects with issue trackers outside of Trac to ensure that everyone is empowered to focus on contributing.
\n\n\n\nThe team was formed based on nominations of volunteers to take part and will be led by Jonathan Desrosiers (@desrosj). The other members of the team are Chris Christoff (@chriscct7), Tammie Lister (@karmatosed), Sergey Biryukov (@sergey), and Sheri Bigelow (@designsimply) – all of whom have a strong track record of contributing to WordPress, have exhibited good triaging practices, and are overall good community members.
\n\n\n\nHave a story that we should include in the next “Month in WordPress” post? Please submit it here.
![\"\"](\"https://s.w.org/images/core/5.1/update.svg\")
Version 5.1 of WordPress, named “Betty” in honour of acclaimed jazz vocalist Betty Carter, is available for download or update in your WordPress dashboard.
\n\n\n\nFollowing WordPress 5.0 — a major release which introduced the new block editor — 5.1 focuses on polish, in particular by improving the overall performance of the editor. In addition, this release paves the way for a better, faster, and more secure WordPress with some essential tools for site administrators and developers.
\n\n\n\n\n\n\n\n![\"\"](\"https://s.w.org/images/core/5.1/site-health.svg\")
With security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.
\n\n\n\nWhen you install new plugins, WordPress’s Site Health features will check them against the version of PHP you’re running. If the plugin requires a version that won’t work with your site, WordPress will keep you from installing that plugin.
\n\n\n\n\n\n\n\n![\"\"](\"https://s.w.org/images/core/5.1/editor-performance.svg\")
Introduced in WordPress 5.0, the new block editor continues to improve. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother.
\n\n\n\nExpect more performance improvements in the next couple of releases.
\n\n\n\n\n\n\n\n5.1 introduces a new database table to store metadata associated with sites and allows for the storage of arbitrary site data relevant in a multisite / network context.
\n\n\n\nThe Cron API has been updated with new functions to assist with returning data and includes new filters for modifying cron storage. Other changes in behavior affect cron spawning on servers running FastCGI and PHP-FPM versions 7.0.16 and above.
\n\n\n\nWordPress 5.1 features a new JavaScript build option, following the large reorganisation of code that started in the 5.0 release.
\n\n\n\nMiscellaneous improvements include:
\n\n\n\nWP_DEBUG_LOG constantwp_unique_post_slug(), WP_User_Query, and count_users()human_readable_duration functionLIKE support for meta keys when using WP_Meta_Query…and more!
\n\n\n\nThis release was led by Matt Mullenweg, along with Gary Pendergast as Senior Code Reshuffler and Poet. They received wonderful assistance from the following 561 contributors for this release, 231 of whom were making their first ever contribution! Pull up some Betty Carter on your music service of choice, and check out some of their profiles:
\n\n\n0x6f0, 1265578519, 1naveengiri, 360zen, aardrian, Aaron Jorbin, Abdullah Ramzan, Abhay Vishwakarma, Abhijit Rakas, Achal Jain, achbed, Adam Silverstein, Ajit Bohra, Alain Schlesser, aldavigdis, alejandroxlopez, Alex, Alex Concha, Alex Shiels, Alexander Botteram, Alexandru Vornicescu, alexgso, allancole, Allen Snook, Alvaro Gois dos Santos, Ana Cirujano, Anantajit JG, Andrea Fercia, Andrea Gandino, Andrea Middleton, andrei0x309, andreiglingeanu, Andrew Duthie, Andrew Lima, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrey Savchenko, Andrés Maneiro, Andy Fragen, Andy Meerwaldt, Angelika Reisiger, Antal Tettinger, antipole, Anton Timmermans, Anton Vanyukov, Antonio Villegas, antonioeatgoat, Anwer AR, Arun, Ashar Irfan, ashokrd2013, Ayesh Karunaratne, Ayub Adiputra, Barry Ceelen, Behzod Saidov, Ben Byrne, benhuberman, Benoit Chantre, benvaassen, Bhargav Mehta, bikecrazyy, Birgir Erlendsson, BjornW, Blair jersyer, Blobfolio, bobbingwide, boblinthorst, Boone Gorges, Boro Sitnikovski, Brad Parbs, Bradley Taylor, bramheijmink, Brandon Kraft, Brandon Payton, Brent Swisher, Brian Richards, bridgetwillard, Brooke., bruceallen, bulletdigital, Burhan Nasir, Bytes.co, Caleb Burks, Calin Don, campusboy, carolinegeven, ccismaru, chasewg, Chetan Prajapati, Chouby, ChriCo, chriscct7, Christopher Spires, claudiu, Clifford Paulick, Code Clinic, codegrau, coleh, conner_bw, Corey McKrill, croce, Csaba (LittleBigThings), Cyrus Collier, Daniel Bachhuber, Daniel James, Daniel Koskinen, Daniel Richards, Daniele Scasciafratte, danimalbrown, Danny Cooper, Danny de Haan, Darko A7, Darren Ethier, Dave Pullig, David A. Kennedy, David Anderson, David Binovec, David Cramer, David Herrera, David Lingren, David Shanske, David Stone, dekervit, Denis Yanchevskiy, Dennis Snell, designsimply, dfangstrom, Dhanendran, Dharmesh Patel, Dhaval kasavala, Dhruvin, DiedeExterkate, Dilip Bheda, dingo-d, Dion Hulse, dipeshkakadiya, Dominik Schilling, Donncha O Caoimh, dontstealmyfish, Drew Jaynes, Drivingralle, dschalk, dsifford, eamax, eArtboard, edo888, ElectricFeet, Ella Van Durpe, Emil Dotsev, Eric Andrew Lewis, Eric Daams, Erich Munz, Erick Hitter, ericmeyer, etoledom, Evan Solomon, Evangelos Athanasiadis, Faisal Alvi, Felipe Elia, Felix Arntz, Fernando Claussen, flipkeijzer, Florian TIAR, FPCSJames, Frank Klein, fuchsws, fullyint, Gabriel Maldonado, Gareth, Garrett Hyder, Gary Jones, Gennady Kovshenin, Gerhard Potgieter, Girish Panchal, GM_Alex, gnif, graymouser, greg, Grzegorz Ziółkowski, Guido, GutenDev, Hafiz Rahman, Hai@LiteSpeed![\"⚡\"](\"https://s.w.org/images/core/emoji/11.2.0/72x72/26a1.png\")
, Hans-Christiaan Braun, Hardeep Asrani, Hardik Amipara, Harsh Patel, haruharuharuby, Heather Burns, Helen Hou-Sandi, Henry Wright, Herre Groen, Hitendra Chopda, Ian Belanger, Ian Dunn, ibantxillo, Ignacio Cruz Moreno, Igor, Igor Benic, imath, ionvv, Irene Strikkers, isabel104, ishitaka, Ivan Mudrik, J.D. Grimes, Jack Reichert, Jacob Peattie, Jake Spurlock, James Nylen, janak Kaneriya, janalwin, Janki Moradiya, janthiel, Jason Caldwell, javorszky, Jaydip Rami, Jayman Pandya, Jb Audras, Jeff Farthing, Jeffrey de Wit, Jeffrey Paul, Jennifer M. Dodd, Jenny, Jeremey, Jeremy Felt, Jeremy Herve, Jeremy Pry, Jeremy Scott, Jesper V Nielsen, Jesse Friedman, Jimmy Comack, Jip Moors, Jiri Hon, JJJ, joanrho, Job, Joe Bailey-Roberts, Joe Dolson, Joe Hoyle, Joe McGill, Joel James ![\"❤\"](\"https://s.w.org/images/core/emoji/11.2.0/72x72/2764.png\")
, Joen Asmussen, Johan Falk, John Blackbourn, John Godley, johnalarcon, johnpgreen, johnschulz, Jonathan Champ, Jonathan Desrosiers, joneiseman, Jonny Harris, Joost de Valk, Jorge Costa, Joseph Scott, JoshuaWold, Joy, jpurdy647, jrdelarosa, jryancard, Juhi Patel, Julia Amosova, juliemoynat, Juliette Reinders Folmer, Junaid Ahmed, Justin Sainton, Justin Sternberg, Justin Tadlock, K.Adam White, kapteinbluf, keesiemeijer, Kelly Dwan, kelvink, khaihong, Kiran Potphode, Kite, Kjell Reigstad, kkarpieszuk, kmeze, Knut Sparhell, konainm, Konstantin Obenland, Konstantinos Xenos, kristastevens, krutidugade, laghee, Laken Hafner, Lance Willett, laurelfulford, lbenicio, Leander Iversen, leemon, lenasterg, lisannekluitmans, lizkarkoski, Luca Grandicelli, LucasRolff, luciano-croce, Luke Carbis, Luminus, Mário Valney, maartenleenders, macbookandrew, Maja Benke, Mako, mallorydxw-old, Manuel Augustin, manuel_84, Marc Nilius, marcelo2605, Marco Martins, marco.marsala, Marcus Kazmierczak, marcwieland95, Marius L. J., mariusvw, Mariyan Belchev, Mark Jaquith, Mathieu Sarrasin, mathieuhays, Matt Cromwell, Matt Gibbs, Matt Martz, Matthew Boynes, Matthew Riley MacPherson, mattyrob, mcmwebsol, Mel Choyce, mensmaximus, mermel, metalandcoffee, Micah Wood, Michael Nelson, Michiel Heijmans, Migrated to @sebastienserre, Miguel Fonseca, Miguel Torres, mihaiiceyro, mihdan, Mike Gillihan, Mike Jolley, Mike Schroder, Milan Dinić, Milan Ivanovic, Milana Cap, Milind More, mirkoschubert, Monika Rao, Monique Dubbelman, moto hachi ( mt8.biz ), mrmadhat, Muhammad Kashif, Mukesh Panchal, MultiformeIngegno, Muntasir Mahmud, munyagu, MyThemeShop, mzorz, nadim0988, nandorsky, Naoki Ohashi, Naoko Takano, nataliashitova, Nate Allen, Nathan Johnson, ndavison, Ned Zimmerman, Nextendweb, Nick Diego, Nick Halsey, Nick Momrik, Nick the Geek, Nicolas Figueira, Nicolas GUILLAUME, Nicolle Helgers, Nidhi Jain, Niels Lange, Nikhil Chavan, Nilambar Sharma, Noam Eppel, notnownikki, odyssey, Omar Reiss, Omkar Bhagat, Ov3rfly, Paal Joachim Romdahl, palmiak, panchen, parbaugh, Parham Ghaffarian, Pascal Birchler, Pascal Casier, Paul Bearne, Paul Biron, Paul Paradise, Paul Schreiber, Perdaan, Peter Putzer, Peter Wilson, Petter Walbø Johnsgård, Pierre Saïkali, Pieter Daalder, Piyush Patel, poena, Pramod Jodhani, Prashant Baldha, Pratik K. Yadav, Pratik K. Yadav, precies, Presskopp, Presslabs, PressTigers, programmin, Punit Patel, Purnendu Dash, Qucheng, Rachel Baker, Rachel Cherry, Rachel Peter, Rafsun Chowdhury, Rahul Prajapati, Raja Mohammed, Ramanan, Rami Yushuvaev, Ramiz Manked, ramonopoly, RavanH, redcastor, remyvv, rensw90, rhetorical, Riad Benguella, Rian Rietveld, Richard Tape, Ricky Lee Whittemore, Rinku Y, Rishi Shah, Robbie, robdxw, Robert Anderson, Robin Cornett, Robin van der Vliet, Ryan McCue, Ryan Paul, Ryan Welcher, ryotsun, Sébastien SERRE, Saša, sagarnasit, Sami Ahmed Siddiqui, Sami Keijonen, Samuel Wood (Otto), sarah semark, Sayed Taqui, Scott Lee, Scott Reilly, Sean Hayes, Sebastian Kurzynoswki, Sebastian Pisula, Sergey Biryukov, Shamim Hasan, Shane Eckert, Sharaz Shahid, Shashwat Mittal, Shawn Hooper, sherwood, Shital Marakana, Shiva Poudel, Simon Prosser, Sjardo, skoldin, slilley, slushman, Sonja Leix, sonjanyc, Soren Wrede, spartank, spyderbytes, Stanimir Stoyanov, Stanko Metodiev, stazdotio, Stephen Edgar, Stephen Harris, stevenlinx, Storm Rockwell, Stoyan Kostadinov, strategio, Subrata Sarkar, Sultan Nasir Uddin, swift, Takahashi Fumiki, Takayuki Miyauchi, Tammie Lister, Taylor Lovett, teddytime, Terri Ann, terwdan, tharsheblows, ThemeZee, Thomas Patrick Levy, Thomas Vitale, thomaswm, Thorsten Frommen, Thrijith Thankachan, Tiago Hillebrandt, tigertech, Tim Havinga, Tim Hengeveld, Timmy Crawford, Timothy Jacobs, titodevera, Tkama, Tobias Zimpel, Tom J Nowell, TomHarrigan, Tommy Ferry, tonybogdanov, Tor-Bjorn Fjellner, TorontoDigits, Toshihiro Kanai, Towhidul Islam, transl8or, Ulrich, upadalavipul, Usman Khalid, Utsav tilava, uttam007, Vaishali Panchal, Valérie Galassi, valchovski, vishaldodiya, vnsavage, voneff, vortfu, warmlaundry, wbrubaker, Weston Ruter, Will Kwon, William Earnhardt, williampatton, wpzinc, xhezairi, Yahil Madakiya, Yoav Farhi, Yui, YuriV, Zane Matthew, and zebulan.\n\n\n\nFinally, thanks to all the community translators who worked on WordPress 5.1. Their efforts bring WordPress 5.1 fully translated to 34 languages at release time, with more on the way.
\n\n\n\nIf you want to follow along or help out, check out Make WordPress and our core development blog.
\n\n\n\nThanks for choosing WordPress!
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6589\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:54:\"\n \n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"WordPress 5.1 RC2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/2019/02/wordpress-5-1-rc2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 19 Feb 2019 02:58:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6585\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:333:\"The second release candidate for WordPress 5.1 is now available! WordPress 5.1 will be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time! There are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Gary Pendergast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3550:\"\nThe second release candidate for WordPress 5.1 is now available!
\n\n\n\nWordPress 5.1 will be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time!
\n\n\n\nThere are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).
\n\n\n\nFor details about what to expect in WordPress 5.1, please see the first release candidate post.
\n\n\n\nThis release includes the final About page design. It also contains fixes for:
\n\n\n\nPlease test your plugins and themes against WordPress 5.1 and update the Tested up to version in the readme to 5.1. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.
\n\n\n\nThe WordPress 5.1 Field Guide has also been published, which goes into the details of the major changes.
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages!
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nWordPress Five Point One:
It’s so slick, shiny, and new.
Lands in a few days!
The first release candidate for WordPress 5.1 is now available!
\n\n\n\nThis is an important milestone, as the release date for WordPress 5.1 draws near. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.1 is scheduled to be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time!
\n\n\n\nThere are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).
\n\n\n\nInspired by Archie Bell & The Drells, WordPress’s theme for 2019 is to “tighten up”, and WordPress 5.1 focussed on exactly that.
\n\n\n\nWith security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.
\n\n\n\nFurthermore, when installing new plugins, WordPress’s Site Health features will check whether a plugin requires a version of PHP incompatible with your site. If so, WordPress will prevent you from installing that plugin.
\n\n\n\nThe new block editor has kept improving since its introduction in WordPress 5.0. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother. There are more features and performance improvements planned in upcoming WordPress releases, you can check them out in the Gutenberg plugin.
\n\n\n\nPlease test your plugins and themes against WordPress 5.1 and update the Tested up to version in the readme to 5.1. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.
\n\n\n\nThe WordPress 5.1 Field Guide has also been published, which goes into the details of the major changes.
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages! This release also marks the hard string freeze point of the 5.1 release schedule.
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nThis is my release
candidate. There are many
like it. This is mine.
The momentum from December’s WordPress 5.0 release was maintained through January with some big announcements and significant updates. Read on to find out what happened in the WordPress project last month.
\n\n\n\nIn a milestone announcement this month, WordPress project lead, Matt Mullenweg (@matt), named two individuals who are coming on board to expand the leadership team of the project.
As Executive Director, Josepha Haden (@chanthaboune) will oversee all the contribution teams across the project. As Marketing & Communications Lead, Joost de Valk (@joostdevalk) will lead the Marketing team and generally oversee improvements to WordPress.org.
Both Josepha and Joost have contributed to the WordPress project for many years and will certainly have a much larger impact going forward in their new roles.
\n\n\n\nImmediately after the 5.0 release of WordPress, work started on version 5.1 with some highly anticipated new features coming out in the first beta release. Since then, the second and third betas have been made available.
One of the core updates in this release — a feature to improve the way in which WordPress handles PHP errors — has been pushed back to version 5.2 due to unforeseen issues that would have caused significant delays to the 5.1 release.
Want to get involved in testing or building WordPress Core? You can install the WordPress Beta Tester plugin, follow the Core team blog, and join the #core channel in the Making WordPress Slack group.
\n\n\n\nHave a story that we should include in the next “Month in WordPress” post? Please submit it here.
WordPress 5.1 Beta 3 is now available!
\n\n\n\nThis software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
\n\n\n\nThere are two ways to test the WordPress 5.1 beta: try the WordPress Beta Testerplugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).
\n\n\n\nWordPress 5.1 is slated for release on February 21, and we need your help to get there!
\n\n\n\nOne of the features originally slated for WordPress 5.1—the PHP error protection handler—will target WordPress 5.2 instead. Some potential security issues were discovered in the implementation: rather than risk releasing insecure code, the team decided to pull it out of WordPress 5.1. The work in #46130 is showing good progress towards addressing the security concerns, if you’d like to follow development progress on this feature.
\n\n\n\nA handful of smaller bugs have also been fixed in this release, including:
\n\n\n\nrel attributes to links, ensure the value isn’t empty (#45352), and that it works as expected with customizer changesets (#45292).WordPress 5.1 has many changes aimed at polishing the developer experience. To keep you informed, we publish developers’ notes on the Make WordPress Core blog throughout the release cycle. Subscribe to the Make WordPress Core blog for updates over the coming weeks, detailing other changes in 5.1 that you should be aware of.
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 2 release also marks the soft string freeze point of the 5.1 release schedule.
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nIn just a few weeks
WordPress Five-One will be here.
Your testing helps us!
WordPress 5.1 Beta 2 is now available!
\n\n\n\nThis software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
\n\n\n\nThere are two ways to test the WordPress 5.1 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).
\n\n\n\nWordPress 5.1 is slated for release on February 21, and we need your help to get there!
\n\n\n\nOver 110 tickets have been closed since beta 1, many of which are documentation and testing suite improvements. Here are the major changes and bug fixes:
\n\n\n\npre_render_block and render_block_data filters have been introduced allowing plugins to override block attribute values (#45451, dev note coming soon).get_template_part() will now return a value indicating whether a template file was found and loaded (#40969).orderby values for post__in, post_parent__in, and post_name__in has been standardized (#38034).WordPress 5.1 has many changes aimed at polishing the developer experience. To keep you informed, we publish developers notes on the Make WordPress Core blog throughout the release cycle. Subscribe to the Make WordPress Core blog for updates over the coming weeks, detailing other changes in 5.1 that you should be aware of.
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 2 release als marks the soft string freeze point of the 5.1 release schedule.
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nDo you enjoy bugs?
I don’t. So, we fixed them all.
Well, not all. But close.
WordPress 5.1 Beta 1 is now available!
\n\n\n\nThis software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
\n\n\n\nThere are two ways to test the WordPress 5.1 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).
\n\n\n\nWordPress 5.1 is slated for release on February 21, and we need your help to get there. Here are some of the big items to test so we can find as many bugs as possible in the coming weeks.
\n\n\n\nSite Health Check is an ongoing project aimed at improving the stability and performance of the entire WordPress ecosystem. The first phase of this project is included in WordPress 5.1. For the first time, WordPress will catch and pause the problem code, so you can log in to your Dashboard and see what the problem is (#44458). Before, you’d have to FTP in to your files or get in touch with your host.
\n\n\n\nAdditionally, in April 2019, WordPress’ will increase its minimum supported PHP version to 5.6. To help you check if you’re prepared for this change, WordPress 5.1 will show you a warning and help you upgrade your version of PHP, if necessary.
\n\n\n\nWP_DEBUG_LOG can be set to a custom log location (#18391).wp_blogmeta table (#37923).LIKE support to meta_key comparisons in WP_Meta_Query (#42409).There have been over 360 tickets closed in WordPress 5.1, with numerous small bug fixes and improvements to help smooth your WordPress experience.
\n\n\n\nKeep your eyes on the Make WordPress Core blog for more developer notes (which are assigned the dev-notes tag) in the coming weeks detailing other changes in 5.1 that you should be aware of.
Do you speak a language other than English? Help us translate WordPress into more than 100 languages!
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nMiss my haiku?
I will have plenty for you
in the coming weeks.
GitHub users may soon be able to contribute to projects on behalf of an organization. This feature has often been requested by developers who are contributing on behalf of their employers.
\n“Corporate contributions to the third-party open source projects can still be a source of friction and ambiguity,” GitHub Product Manager Ben Balter said. “We’re beta testing a new platform-agnostic commit pattern we hope can help you contribute on behalf of your employer.”
\nCommitters who are members of an organization can add a commit trailer in the following format:
\nOn-behalf-of: @ORG <ORG CONTACT EMAIL>\n
The committer must use an email that matches the organization’s verified domain and sign the commit. Committing on behalf of an organization can also be done via the command line.
\nBalter posted a demo of how the organization’s badge appears next to the committer’s. The feature is now in public beta:
\nIt will be interesting to see how well this is adopted among individuals and organizations committing to open source projects. Some projects have more overt contribution from commercial entities than others. Having individuals commit on behalf of their employers makes it easier to track contributions funded by organizations. It may also provide project owners a more accurate picture of how deeply companies are invested in a project, especially in scenarios where the lines between individual and employer contributions are blurry or unclear.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 16 Mar 2019 01:17:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"WPTavern: Deploy WordPress Plugins from GitHub to the WordPress.org Plugin Repository\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87994\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"https://wptavern.com/deploy-wordpress-plugins-from-github-to-the-wordpress-org-plugin-repository\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2439:\"10up has released a GitHub Action that enables developers to deploy to the WordPress.org Plugin repository by tagging a new version on GitHub. Helen Hou-Sandí, 10up’s Director of Open Source Initiatives, explained how it works:
\n\nYou’ll be able to manage your entire development lifecycle in GitHub—no more futzing with local Bash scripts or controlling commit/push access in multiple places. You reference our action in your plugin repo’s workflow file, filtered to only run when a tag is pushed, and set your username/password secrets. After that, each time you tag a new version on GitHub, whether by pushing a Git tag from the command line or making one using the GitHub releases interface, your plugin will be deployed to WordPress.org.
Developers who want to use this Action will need to sign up for beta access to GitHub Actions in order to create their own Actions-enabled repo for pushing plugin releases to WordPress.org. Check out 10up’s release post and the README file for instructions on how to use and customize the WordPress.org Plugin Deploy action.
\nReception from the WordPress development community has been enthusiastic, as anything that removes WordPress.org’s requirement to use SVN qualifies as a little piece of magic. 10up is working on more WordPress Actions that they plan to release soon.
\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 15 Mar 2019 15:52:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"WordPress.org blog: One-third of the web!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6789\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2019/03/one-third-of-the-web/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2168:\"This project makes me want to make a plugin again
\nhttps://t.co/aTtTpu6562
— Jeremy Felt (@jeremyfelt) March 14, 2019
WordPress now powers over 1/3rd of the top 10 million sites on the web according to W3Techs. Our market share has been growing steadily over the last few years, going from 29.9% just one year ago to 33.4% now. We are, of course, quite proud of these numbers!
The path here has been very exciting. In 2005, we were celebrating 50,000 downloads. Six years later, in January 2011, WordPress was powering 13.1% of websites. And now, early in 2019, we are powering 33.4% of sites. Our latest release has already been downloaded close to 14 million times, and it was only released on the 21st of February.
WordPress market share on the rise over the last 8 years. Image source: W3Techs.\n\n\n\nOver the years WordPress has become the CMS of choice for more and more people and companies. As various businesses use WordPress, the variety of WordPress sites grows. Large enterprise businesses all the way down to small local businesses: all of them use WordPress to power their site. We love seeing that and we strive to continuously make WordPress better for all of you.
\n\n\n\nWe’d like to thank everyone who works on WordPress, which is built and maintained by a huge community of volunteers that has grown alongside the CMS. This incredible community makes it possible for WordPress to keep growing while still also remaining free. And of course, we’d like to thank all of you using WordPress for using it and trusting in it. To all of you: let’s celebrate!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 15 Mar 2019 13:16:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Joost de Valk\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:112:\"WPTavern: WordCamp Miami to Livestream Workshops, Sessions, and a Worldwide WordPress Trivia Contest March 15-17\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87992\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://wptavern.com/wordcamp-miami-to-livestream-workshops-sessions-and-a-worldwide-wordpress-trivia-contest-march-15-17\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2166:\"WordCamp Miami (WCMIA) is heading into its 11th year running this weekend, making it one of the longest running non-profit tech conferences in South Florida. Known for its many learning opportunities and workshops, the event spans three days from March 15 – 17 at Florida International University.
\nFor the vast majority of the WordPress world that cannot make it to Miami, the next best alternative is tuning into the free livestream. WCMIA will be broadcasting a selection of workshops and sessions from the schedule, beginning with the Freelancer’s Workshop on Friday, March 15. The main event features six different tracks, and Saturday’s live broadcast will include sessions from “WordPress & The Web” and the “Design & Community” tracks. Sunday’s livestream will broadcast sessions from the Business track.
\nWCMIA is also hosting a worldwide WordPress trivia contest on Saturday, March 16, at 6PM EST. It is open to both in-person attendees and livestream viewers. Directions for how to sign into kahoot.it remotely for the game show are available on the event’s website. Digital prizes may be awarded to those playing online and winners will be announced on the WCMIA Twitter account.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 15 Mar 2019 02:28:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"WPTavern: Automattic Takes on Facebook with “A Meditation on the Open Web”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87971\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://wptavern.com/automattic-takes-on-facebook-with-a-meditation-on-the-open-web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3913:\"Last week Automattic published a video titled “A meditation on the open web” that calls out Facebook as the antithesis of the open web:
\n\nAs you get closer the air gets smoggier and you realize it’s a vast metropolis. It’s surrounded by high concrete walls, completely contained. Inside it’s bustling, lots of honking traffic, people everywhere, the sound is deafening. You see people arguing in bars and chatting on street corners. Billboards and advertisements are everywhere, touting ever kind of good and service. It’s noisy and dense and overwhelming.
\nThis is Facebook.
The video also likens Instagram to a cookie cutter housing development that is actually just a collection of billboards with no one living there.
\nMy expectation before playing the video was that it would enumerate the positive aspects of the open web but I was surprised to find it juxtaposed with Facebook and Instagram in a somewhat jarring fashion midway through. It effectively communicates the stark contrast between the limitations and restrictions of social media silos and the freedom of owning your own website.
\n\nOpen Web Meditation was created as a design experiment at Automattic that encourages viewers to look beyond the walls of dominant social media platforms and consider how our experiences on the web differ based on where we choose to share our ideas. The company is looking to gain global exposure for the video by inviting people to create their own versions of it in their own languages.
\nAutomattic’s video is a timely message, as the world pauses to reflect on the 30th birthday of the World Wide Web this week. In his open letter published by the Web Foundation, Tim Berners-Lee urged companies, governments, and the web’s citizens not to give up on building a better web. He identified “system design that creates perverse incentives,” where user value is sacrificed, as one of the most dangerous threats to the web at this time.
\n“You can’t just blame one government, one social network or the human spirit,” Berners-Lee said. “Simplistic narratives risk exhausting our energy as we chase the symptoms of these problems instead of focusing on their root causes. To get this right, we will need to come together as a global web community.”
\nMany commercial entities have enjoyed extraordinary and unprecedented opportunities and influence because of the creation of the world wide web. Berners-Lee underscored their responsibility toward the public as stewards of the open web.
\n“Companies must do more to ensure their pursuit of short-term profit is not at the expense of human rights, democracy, scientific fact or public safety,” he said. “Platforms and products must be designed with privacy, diversity and security in mind. This year, we’ve seen a number of tech employees stand up and demand better business practices. We need to encourage that spirit.”
\nIn an interview with the BBC, Berners-Lee said that global action is required tackle the web’s “downward plunge to a dysfunctional future.” This 30-year anniversary is a good time to re-examine our complex relationships with centralized services and return to the guiding principles that have made the web a universal, open place of opportunity.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 14 Mar 2019 19:56:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"Matt: The Web Turns 30\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=49261\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://ma.tt/2019/03/the-web-turns-30/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1358:\"\n\n\n\n“Vague, but exciting.” Thirty years ago yesterday, Sir Tim Berners-Lee submitted his original proposal for an information management system to his boss at CERN — what would later become the World Wide Web (and, it turns out, a huge influence on my life and career).
\n\n\n\nTo help celebrate, I tweeted WordPress’s contribution to the web’s grand timeline (above), and I got to participate in The Economist’s Babbage podcast looking back at the pioneers of the early web. Listen to the whole episode below:
\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 14 Mar 2019 18:28:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"WPTavern: WordPress 5.1.1 Patches Critical Vulnerability\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87953\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wptavern.com/wordpress-5-1-1-patches-critical-vulnerability\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2091:\"WordPress 5.1.1 was released yesterday evening with an important security update for a critical cross-site scripting vulnerability found in 5.1 and prior versions. The release post credited Simon Scannell of RIPS Technologies for discovering and reporting the vulnerability. Scannell published a post summarizing how an unauthenticated attacker could take over any WordPress site that has comments enabled:
\n\nAn attacker can take over any WordPress site that has comments enabled by tricking an administrator of a target blog to visit a website set up by the attacker. As soon as the victim administrator visits the malicious website, a cross-site request forgery (CSRF) exploit is run against the target WordPress blog in the background, without the victim noticing. The CSRF exploit abuses multiple logic flaws and sanitization errors that when combined lead to Remote Code Execution and a full site takeover.
Since WordPress ships with comments enabled by default, an attacker could exploit this vulnerability on any site with the default settings. Auto-updates went out yesterday but administrators who have background updates disabled are advised to update immediately.
\nThe maintenance release also includes the ability for hosts to offer a button to prompt their users to update PHP ahead of WordPress’ planned minimum PHP version bump in 5.2. The “Update PHP” notice can be filtered to change the recommended version.
\nVersion 5.1.2 is expected to follow in two weeks.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 14 Mar 2019 03:42:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"WPTavern: Dark Mode WordPress Plugin Up for Adoption\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87912\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"https://wptavern.com/dark-mode-wordpress-plugin-up-for-adoption\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3804:\"Daniel James is putting his Dark Mode plugin up for adoption.
\n“I’m stepping back from plugin development (and WordPress contributions) and would like to see someone passionate about it pick it up,” James said.
\nDark Mode has 2,000 active installations and is the most popular among a handful of dark or “night mode” plugins in the official directory. In August 2018, James submitted a merge proposal for including Dark Mode in core, but it was shot down the same day it was published. Gary Pendergast said the proposal “seemed premature” and noted that the project was lacking several merge criteria outlined on the Handbook page for feature plugins. He cited a lack of weekly chats, no kickoff and update posts, and no testing from the Flow team, among other concerns.
\n“I decided recently that because of the direction WordPress is going in with the move towards React with Gutenberg that I should probably focus my efforts elsewhere,” James said.
\n“That’s mostly to do with the merge proposal getting rejected fairly quickly without any helpful next steps on how to improve it. Plus, with how rapidly Gutenberg is being developed, I’d have to pretty much work in tandem with the Gutenberg team to ensure the Dark Mode plugin styled the UI correctly. That’s spare time I just don’t have.
\n“I feel like WordPress leadership is another reason. It’s really difficult (I think/feel) to get something like Dark Mode pushed through. It’s very much near the bottom of the priority list, which I get, but sucks a bit when you’re volunteering in spare time of course.” James said the plugin currently requires a few hours per week in support and maintenance.
\nThe popularity of dark modes for applications has taken off after macOS Mojave introduced a dark mode, and has also been spurred on by the news that Apple’s 2020 iPhone lineup will be produced with OLED screens. Many popular applications, such as YouTube, Facebook Messenger, Twitter, and Google Maps already have a dark mode that either works automatically based on light conditions or can be manually enabled. Chrome also recently added a dark browsing mode for Mac users. Fans of dark mode claim it is easier on the eyes and conserves battery.
\nUsers who tend to gravitate towards dark mode are still a small subset, but the feature is gaining momentum. A dark mode may one day come to WordPress core but it doesn’t seem likely in the near future. Daniel James’ Dark Mode plugin isn’t ready for core, since it doesn’t support the new editor, but he said he hopes the new owner will find the time to take it where it needs to go.
\n“I’m happy to transfer the plugin to someone else to continue it, as long as they’re well known/respected,” James said. “I won’t just be giving it away for security reasons. It would be great for it to be included in core one day, but at the very least it would be nice for someone who really likes it to just continue it.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Mar 2019 22:51:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"HeroPress: Work Life “Balance” With WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=2711\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:138:\"https://heropress.com/essays/work-life-balance-with-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=work-life-balance-with-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6674:\"![\"Pull](\"https://s20094.pcdn.co/wp-content/uploads/2020/03/031619-1024x512.jpg\")
I always knew I wanted to have a career, and I also knew I wanted a family. As my family grew, I realized that a typical job where you have to show up at an office every day didn’t work with the dynamic and unpredictable nature of kids. I didn’t understand why being at a physical office was a requirement: wasn’t the most important thing getting the work done? I could work just as well from home, and the flexibility would mean I could do my work at hours that worked for me. Who cares if I finished a project at 11 pm, if I did it well and on time?
\nSo after my fourth kid was born, I decided to create that flexibility for myself, and went freelance, but with a vision to grow into a company. That’s why from the beginning I created a brand for my services, and called the “company” illuminea. At first I offered content related services, like marketing writing, and Hebrew to English translation. Increasingly the work I was doing was related to company websites, and the power websites had in terms of communicating messages and content marketing really caught my attention. I also had always been fascinated by technology.
\n\nSo I started to teach myself how to build websites, using Google as my teacher.
At first I built basic HTML websites, but as I also learned about web marketing I realized that a site that can’t be easily updated is not doing any favors for its owners. Website content needs to be quickly and easily updatable. So I started researching CMS options. Many companies in those days were using expensive and clunky proprietary CMSs, and I was not impressed. I tested the three leading Open Source CMSs, and fell in love with WordPress. I was impressed by the templating system, the plugin ecosystem, and the community.
\nAt that time companies did not take WordPress seriously as a CMS. Blogging was catching on, so companies would install a WordPress blog as a subdomain, but they weren’t using it for general site management. I thought it could be more, and managed to convince a few clients to let me build their sites on WP.
\n\nAnd then version 3.0 was released, and WP became a full-fledged CMS.
Companies started to become sick of the limitations and costs of their proprietary CMSs, and since I was one of the first in the Israeli market to offer WP as a service, I started to get more and more clients for full website projects.
\nRight before I had my fifth kid, I made my first hire: Rebecca Markowitz. I taught her whatever I knew, and she quickly surpassed me with her skills in many areas. We have been working (and laughing) together ever since!
\nOne thing led to another and illuminea became one of the leading providers of custom WordPress business solutions in Israel. We were privileged to work with inspiring innovators and generally nice people.
\nI had had many ideas for products throughout the years, but managing a business and having babies meant I could not realistically build a product on the side. However, after about twelve years of illuminea, and when my youngest was no longer a baby, I had an idea for a WordPress-related product: our clients, and ourselves, were suffering from issues related to speed and security. No matter what we did, we could never speed up client websites as much as they or we would have liked; and no matter what we did on the security side, sites still had vulnerabilities too often. So I thought: why not convert WordPress websites to serverless and static versions of themselves so they’ll be fast and secure?
\n\nI decided to go for it. I got accepted to a Jerusalem startup accelerator called Siftech, and they gave me the tools and access to resources and mentors that I needed to take the next steps.
I called that venture Strattic, and today we are a venture-backed team of seven with a great product that our clients love.
\nI can’t imagine how I could have ever achieved my goal of integrating family and an impactful career without WordPress. To this day I love that I am always challenged and learning more, and always meeting more people in our amazing community, while also having the flexibility I need to be a mom. Of course it’s not perfect, but it’s pretty good, thank God.
\nThe post Work Life “Balance” With WordPress appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Mar 2019 20:00:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Miriam Schwab\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:102:\"WPTavern: Google Announces Season of Docs Program to Match Technical Writers with Open Source Projects\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87914\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:113:\"https://wptavern.com/google-announces-season-of-docs-program-to-match-technical-writers-with-open-source-projects\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2280:\"Google is launching a new program called Season of Docs with the goal of fostering collaboration between technical writers and open source projects. The initiative is very similar to Google Summer of Code, except it is focused on documentation and technical writing contributions instead.
\nProspective participants can apply during the month of April 2019. Google plans to publish a list of accepted organizations with their ideas for documentation projects. Technical writers can choose a project and submit a proposal to Season of Docs. The accepted proposals will be published July 30, 2019, and participants will then spend a month bonding with their open source communities and collaborating with mentors. The Season of Docs program officially runs from September 2 – November 29, and participants will receive a stipend of $2400 – $6,000 USD, calculated based on Purchasing Power Parity.
\nIn 2017, Google’s Open Source Survey results showed that incomplete or missing documentation was one of the most common problems encountered in open source, observed by 93% of respondents. The Season of Docs program aims to give technical writers an opportunity to contribute to open source projects in a more structured way while learning about open source code. Participating organizations gain the chance to improve their processes for documenting their projects while working with a technical writer. Check out the FAQ section of the Season of Docs website for more detailed information.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Mar 2019 01:17:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"WPTavern: WordCamp Nordic Hosts Successful Kids Workshop\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87893\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wptavern.com/wordcamp-nordic-hosts-successful-kids-workshop\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2631:\"WordCamp Nordic hosted a successful kids workshop over the weekend where participants learned how to start publishing with WordPress. The event was held during Contributor Day at the same venue, tucked into a comfortable corner with soft chairs and ample floor space for the kids to stretch out.
\nPetya Raykovska led the workshop and participants followed along with the help of a large screen for demonstrating basic publishing-related tasks. The kids learned how to use the editor, add text and images, create galleries, and customize their sites by selecting a theme. Each participant left the workshop with their own WordPress site hosted at WordPress.com.
\n“It’s like an exercise in creativity, showing them how to use a tool to express themselves on the web,” Raykovska said.
\n\nTeaching kids how to use WordPress is far easier than teaching adults how to use it for the first time, because they don’t have preconceived notions about how the editor should behave. Raykovska said the group at WordCamp Nordic had no issues using Gutenberg.
\n“It doesn’t matter for them what editor they use,” Raykovska said. “They are very intuitive; they go along with anything that comes their way.”
\nShe also reported that many of the kids from past kids workshop events have kept their blogs going and maintain strong relationships with the volunteers who helped them get started.
\nEach kids workshop is a new opportunity for organizers to test and refine different methods for teaching kids how to use WordPress. As these workshops become more common at WordCamps around the globe, it would be exciting to see them grow to become large scale events where more experienced kids can present on what they are learning and doing with WordPress.
\nIf you are interested in running a kids workshop at another WordCamp, Raykovska has created an organizer kit for training the next generation of WordPress users and developers. It includes all the tasks and requirements for organizing this type of event, sample content, and a workshop script that organizers can follow.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Mar 2019 19:09:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"WordPress.org blog: WordPress 5.1.1 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6736\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4066:\"WordPress 5.1.1 is now available! This security and maintenance release introduces 14 fixes and enhancements, including changes designed to help hosts prepare users for the minimum PHP version bump coming in 5.2.
\n\n\n\nThis release also includes a pair of security fixes that handle how comments are filtered and then stored in the database. With a maliciously crafted comment, a WordPress post was vulnerable to cross-site scripting.
\n\n\n\nWordPress versions 5.1 and earlier are affected by these bugs, which are fixed in version 5.1.1. Updated versions of WordPress 5.0 and earlier are also available for any users who have not yet updated to 5.1.
\n\n\n\nProps to Simon Scannell of RIPS Technologies who discovered this flaw independent of some work that was being done by members of the core security team. Thank you to all of the reporters for privately disclosing the vulnerabilities, which gave us time to fix them before WordPress sites could be attacked.
\n\n\n\nOther highlights of this release include:
\n\n\n\nYou can browse the full list of changes on Trac.
\n\n\n\nWordPress 5.1.1 was a short-cycle maintenance release. Version 5.1.2 is expected to follow a similar two week release cadence.
\n\n\n\nYou can download WordPress 5.1.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.
\n\n\n\nIn addition to the security researcher mentioned above, thank you to everyone who contributed to WordPress 5.1.1:
\n\n\n\nAaron Jorbin, Alex Concha, Andrea Fercia, Andy Fragen, Anton Vanyukov, Ben Bidner, bulletdigital, David Binovec, Dion Hulse, Felix Arntz, Garrett Hyder, Gary Pendergast, Ian Dunn, Jake Spurlock, Jb Audras, Jeremy Felt, Johan Falk, Jonathan Desrosiers, Luke Carbis, Mike Schroder, Milan Dinić, Mukesh Panchal, Paul Biron, Peter Wilson, Sergey Biryukov, and Weston Ruter.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Mar 2019 03:34:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Luke Carbis\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: WordPress Explores Proposal for New Block Directory to Host Single Block Plugins\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87864\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://wptavern.com/wordpress-explores-proposal-for-new-block-directory-to-host-single-block-plugins\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5749:\"WordPress core contributor Alex Shiels has published a proposal for a WordPress.org block directory that would host JavaScript-based, single block plugins. The directory would make blocks searchable and installable from within the Gutenberg editor. Building a directory for discovering blocks and seamlessly installing them is one of the nine projects that Matt Mullenweg identified as a priority for 2019.
\nBlock collections have become one of the most popular ways for distributing a group of related blocks but this method can cause bloat. Users currently cannot search for individual blocks by name and plugin names and descriptions are not always a good indication of what the blocks do.
\nShiels proposed the new directory be limited to single block plugins, frontend JavaScript blocks with no UI outside of the editor. It would be a separate section inside the Plugins Directory, optimized for users to find blocks by name and description. Developers would be required to use a block.json file with metadata as outlined in the Block Registration RFC, which provides a technical specification for block type registration.
\nThe most controversial part of the proposal is having blocks installable from within the Gutenberg editor. The long term goal is to make that process as seamless as possible. Block collections and blocks that do not meet the requirements of the single block directory would still be available via the normal plugin installation process. This could be confusing for users who do not know that blocks can be found in two separate directories.
\n“The Gutenberg editor should NOT be a plugin installation source,” Matt Cromwell commented on the proposal. “That just seems ripe for scope-creep. That’s not its purpose or function. Let it be an editor, layout builder, content manager, etc. Moving into searching an external library and installing plugins is the definition of losing site of the purpose of a ‘product.\'”
\nCromwell suggested a centralized block manager as an alternative that would offer a better experience for searching and installing blocks. He also echoed other participants’ opinions on the importance of including dynamic blocks in the directory, instead of limiting it to “JavaScript only” blocks.
\n“A centralized Block Manager like has already been suggested is a far better user-experience for searching and installing blocks than doing that in the Gutenberg editor. I like the idea of single-block plugins being the only option in the Directory. But make sure Dynamic Blocks that depend on other existing plugins or outside functionality are able to be added to that very important Directory as well. I really don’t see a benefit to limiting this Directory so much.”
\nWordPress developer Jamie Schmid also expressed hesitation about pursuing a solution that puts block installation inside the editor, as it may discourage users from thinking about their block usage across the entire site.
\n“I am not convinced that making blocks searchable and installable from within the editor is the best solution,” Schmid said. “This, along with page level block controls and style overrides, is encouraging a very short-sighted, page-level solution to an issue that is very likely a global site (or content or even business) issue. I’d love to instead see a central view for all installed blocks – similar to how plugins are, but more organized by type/function/etc and with a visual alongside. This will encourage making decisions at the site level, encouraging some bigger-picture reflection. And same to being able to apply access controls to the installation of new blocks.”
\nThe proposal would place the single block plugin search interface inside the block inserter in the Gutenberg editor. This would enable users to quickly search for and install a block if they don’t see one they need among the existing blocks.
\nRiad Benguella, Gutenberg’s technical lead for phase 2, encouraged participants in the discussion to think about blocks as pieces of content that do not rely on the post editor but can be configured anywhere inside WordPress.
\n“It is important to think of blocks as its own unit that have a meaning on its own, and that can be used in different contexts,” Benguella said. “A block is a piece of content (static or dynamic) that can be configured and rendered anywhere.” This includes blocks found both inside and outside post_content, content in a full site editor, inside the WordPress admin, a headless application, or even another CMS.
\n“We should be ambitious and think about all these contexts (the final picture), but at the same time we should be pragmatic and iterate to achieve this goal,” Benguella said.
\nThe discussion regarding the new block directory and block plugin architecture continues across WordPress contributor teams. Shiels said the proposal was meant as a starting place and contributors are still in the preliminary stage of exploring ideas.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Mar 2019 01:32:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"BuddyPress: Join the Worldwide BuddyPress table during the first Contributor Day of the 11th WordCamp Paris\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=303465\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://buddypress.org/2019/03/wordcamp-paris-contributor-day/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3364:\"To start a new decade of WordCamps in Paris (France), the Parisian organizing team has scheduled their first Contributor Day on April 24th, 2019.
\n\n\n\n![\"The](\"https://buddypress.org/wp-content/uploads/1/2019/03/i-contribute.png\")
The « I contribute » badgeAs a member of this team, I‘m very excited and as one of the BuddyPress core developers I’m very proud to announce I will run a BuddyPress contributor table !
\n\n\n\nThe WordCamp Paris Contributor Day will start at 8:00am UTC and will end at 4:00pm UTC.
\n\n\n\nIf you’re in Paris on April 24th : you can get your free ticket to have a sit at our table. We’ll work on resolving issues, testing patches, improving the documentation and the french translation and why not on enhancements we can imagine using the BuddyPress REST API (It’s arriving in BuddyPress 5.0.0 !).
\n\n\n\n\n\n\n\n\n\n\n\nBuddyPress is created by a worldwide network of friendly folks
John James Jacoby
Then I thought what about trying to extend our BuddyPress table to a Worldwide BuddyPress Contributor Time ? @boonebgorges & @johnjamesjacoby will try to be around in our Slack channel to help us, to review the code and commit our changes.
\n\n\n\nIf you’re not in Paris on April 24th : you can participate from where you are, you simply need to hang around into our #BuddyPress Slack channel. If you’re not familiar with Slack, please read this short documentation about it.
\n\n\n\nLet’s contribute to BuddyPress together ![\"♥\"](\"https://s.w.org/images/core/emoji/11.2.0/72x72/2665.png\")
Il existe une version française de cet article.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Mar 2019 01:10:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"imath\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"Matt: A Meditation on the Open Web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=49220\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"https://ma.tt/2019/03/a-meditation-on-the-open-web/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 08 Mar 2019 23:28:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"HeroPress: How WordPress Changed My Life\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=2703\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:132:\"https://heropress.com/essays/how-wordpress-changed-my-life/#utm_source=rss&utm_medium=rss&utm_campaign=how-wordpress-changed-my-life\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:35846:\"![\"Pull](\"https://s20094.pcdn.co/wp-content/uploads/2020/03/030619-min-1024x512.jpg\")
هذا المقال متاح باللغة العربية
\nI’m about to get real! Vulnerable! Transparent! & guess what…I don’t give a fuck! So buckle up boys…you’re about to go for a ride!
\nJune 2014 when I decided to leave my life I’ve lived with my husband for thirteen years, left everything behind. My community I always knew, my friends, my way of life, I just dropped everything!
\nThe only thing I took with me was my idea box and my two kids to started our new life in Chandler Arizona. When I moved, I lived with my mom till I figured it out. At the time I was in school for my Computer Science degree at Austin Peay State University. I figured I have only one year, so why not finish, get a good paying job and my mom was ok with us living in her house. It was difficult and the most challenging experiences as my mom had her own health challenge and having her newly divorced 29 year old daughter with two kids in her house was not easy for her. I was so broken. I was broken spiritually. I was broken mentally and this affected my overall physical health. And still had to find the strength to be strong in front of my kids. I did not have a job. I had never worked a day in my life as my husband did not allow it.
\n\nSo here I was, 29 years old, two kids, divorced, no degree, no work experience…yet I had to find a way to not only support myself but my kids as well.
While living with my mom, the atmosphere got a little tense. As I mentioned above, my mom went through a lot, she had her own struggles, her own journey, and I happened to be a part of her narrative. With the loss of the man she loved so dearly, and her health declining, she as well had her own capacity of what she can handle, and having me in the house with the kids was getting burdensome. I tried to do my part with buying food in bulk as there was nine of us in a five bedroom house. But sometimes, my idea of “doing my part” does not match the other, and issues may arise.
\nOne day my mom approached me with the Cox internet bill and asked me to pay for it. Honestly, I probably could have afford the bill under $100.00 dollars, but the inconsistent deposit of child support from my ex at that time, I was not able to commit to paying for anything. That is why I would buy food from Costco in bulk, etc. But, that was the turning point for my mom to pull the plug and say,
\n“I don’t want you in my house anymore.”
\nSo the plan to finish school within a year went out the door!
\nI came home one day I and found my stuff in a baskets in front of the garage. I reversed the car from my moms driveway and went in search of an apartment I could afford. At the time, my ex was depositing a total of $1,000 dollars in the joint account for our kids. I had to find an apartment that was under $1,000 dollars plus cover the cost of gas and food. To my surprise I found an apartment called CrossWinds Apartments for $550 a month on Arizona Ave and Pecos rd.
\nOn Aug. 2014 I moved in my first apartment with my two kids.
\nSo here I was 29 years old, no job yet, the idea of finishing school went out the door, and I have to find a way to make it.
\nBreath…just breath…(sometimes breathing doesn’t work. I mean…I feel like I was gasping for air in order to breath!)
\n\nMy kids where very sad. I was confused. I had no idea what to do and where to go and I needed a job.
After reaching out my friend, Deedra Hill Abboud who helped me with revamping my resume based on past experiences, I started applying to every job I could find. And just a side note, Deedra Hill Abboud not only helped with my resume which I was clueless on how to put together, but also helped me with my mindset, reminded me to be grateful even though I felt so defeated, and I was at my lowest point in my life. But, I had no luck with my job hunt and I was ready to settle for anything! I was hired as a nanny on Aug 29, 2014. I moved that month into a new apartment, never lived on my own before, never payed for bills (like what the fuck are those yo), and was able to find a job by the end of the month that payed me $300.00 a week. I was so happy. Like you have noooo idea! I was so happy.
\nMy family visited sporadically. But, on October 2014, my sister Eman, who’s known for Eman B. Fendi, came over to visit. I had no couch, no bed, no furniture for a while. We had a long conversation about life, and everything in between. During the conversation, I pulled out my idea box and shared with her a card game I had created when I used to tutor Muslim kids back in Clarksville TN. She informed me about Score, a non-profit organization that provides free business mentorship all over the USA. She said, “reach out to them. They will help you with your idea.”
\nI’m like…OMG! I was soooo excited! I went to Peixoto coffee in Chandler AZ…for internet…I could not afford internet at the time. I checked out Score website and they had an event I attended on November 2014. I was so nervous and so scared. As I did not know what to really do with my idea. All I know is I had an idea, I was passionate about it, and had the drive to do something about it! The event host asked everyone in the room to stand up and introduce themselves. Everyone had their fancy title and so much amazing experience to represent themselves, and here I am trying to make something out of myself I have never done before. In all my insecurities, self doubt, and internal contradictions, my intro goes as follows…
\n“Hi! My name is Amena Mabrouk and I have a card game idea that helps kids learn the name and position of Salah(prayer). I am here because I have no idea what to do with my idea.”
\nAfter the session was over a man walked towards me by the name of Doug Whitney. He was a certified Score mentor helping clients who want to start or grow their businesses. He approached me and said,
\n“Hi! My name is Doug Whitney. I think I can help you with your idea. Here’s my business card.”
\nWOW! I was thrilled! I booked an appointment with him that day and I continued to meet with my business mentor weekly for two years. The journey was lonely. As I was so focused on work, my kids, and my idea, I started to miss being apart of a community.
\n\nDuring the two years I was meeting with my business mentor, Whitney said to me, “You need to start building a website. I recommend you start building your website on WordPress.”
“I’m like, WordPress. Ok! I will start tonight. Like what is it? I press words? “
\nHa…ha…Just kidding! I figured you lasted this long reading my blog, we’re practically related at this point….might as well add a little humor…lol
\nSo please continue on…
\nSo I went to Peixoto coffee, opened my computer, went to wordpress.org, created an account and started to build my website. This was my first time building a website. I googled everything and lots of youtube videos. And man, I got stuck. I was frustrated. I was so disappointed especially when you see all the pretty websites out-there, I was a little discouraged to continue. In the process of trying to figure out this WordPress thing, I also learned about co-working spaces which I became obsessed with!
\nDid you know there all over the valley! OMG!
\nI found out about one near my home called GangPlank in Chandler Arizona. I started working out of GangPlank and fell in love with the community there. This was the first time in two years to finally feel a sense of community after my divorce. I worked there consistently and an amazing woman by the name of Anne Watson Barber. During our conversation, I informed her about my dilemma with my WordPress website. She automatically, without hesitation, offered to help me without any question. I was so so excited! Thrilled! You have no idea!
\nI consistently met up with Anne Watson Barber at GangPlank for a while. In all honesty, without this WordPress thing, I would have never looked for a place where people work out of, which led me to meeting Anne Watson Barber and many other amazing people. But that was the beginning. As not only did I get a sense of community I was missing in my life at GangPlank, I was making legit friends who selflessly are willing to help out no matter what! WOW!
\nCan we just stop for a moment and talk about it!
\nThroughout our meetings my friend Anne informed me about Meetup groups for WordPress.
\nI started to google Meetup groups around the valley for WordPress. I went to all of them! Some WordPress Meetup where one hour and thirty minutes way! I loved every bit of it! Disclaimer, most of it was over my head, but I still went, made new friends, and continued building my WordPress website.
\nHow WordPress Changed My Life, well the story speaks for itself. Choosing to build my site on WordPress was the catalyst from the beginning that opened many doors I was not aware of. I continued to build my site for a few years, and then moved on to a different venture.
\n\nBut, without WordPress which lead to the WordPress community, I would not have learned how to build an online presence, to fearlessly ask questions when I’m stuck, to be around people who are willing selflessly help out, even-though I needed the information repeated over and over again for me to understand it.
Without the WordPress community, I would not have learned to be ok with failure that’s free of judgment, as we are all trying to make it. Without the WordPress community, I would not have learned to be ok with the idea of shared information – because your success is my success. Without the WordPress community, I would not have learned how to be tolerant when feeling defeated and to continue with the little courage I had to figuring it out. It really did change my life.
\nAfter venturing off with other things, the universe has it’s way of reminding me of where I belong. I was informed about volunteering at WordCamp Phoenix 2019 by a good friend, Justin Nealey at GoDaddy. So I used my volunteer and sick time to take off from work to be apart of the event. I was blown away! I never knew what WordPress really meant to its people. I did not understand the heart of the WordPress project, and how important it is in the way it impacts the community. When I started with WordPress, it was about building my website for my startup business. But this time, I had a glimpse of it’s magnitude in the world and I am so thrilled to be apart of it on a whole new level!
\nDuring my time at WordCamp Phoenix 2019 , I meet amazing people and had the time of my life! This event lead to the opportunity to take photos/video during Contributor Day + Organizing WordPress Panels at Galvanize Phoenix. This further opened doors to meeting Topher DeRosia who approached me and inspired me to write this essay for his website called HeroPress; to meeting Adam Warner | Field Marketing Manager for GoDaddy Pro; to the amazing conversation with Aaron Campbell |WordPress Core/Ecosystem; and so many amazing humans who came into my life because of it!
\nCurrently, I work at GoDaddy Hosting Support. I love my job and I’m making a comeback into my WordPress community here in the valley. I am working closely with Matthew Clancy to record and edit the Advanced WordPress Developer Meetup and other upcoming events as well. I am so excited for the future!
\nOh, and in case you’re wondering about my Salah(Prayer) card idea…that’s another blog post, another joy ride boys! In the meantime, let’s be friends! Let’s connect! Twitter @AmenaMabrouk
\n\n
\n
أنا على وشك أن اصبح صادقة! و قوية و صريحة ! هل تعلم… انا لا اكترث نهائيا! .. أنتم على وشك الذهاب فى نزهه! فى يونيو 2014 عندما قررت أن أترك حياتي التى عشتها مع زوجي لمدة ثلاثة عشر عاما ، تركت كل شيء خلفى. مجتمعي ألذى عرفته ،أصدقائي ، طريقه معيشتى، فقد تركت كل شيء! الشيء الوحيد الذي أخذته معي كان صندوق أفكارى وأطفالي الاثنين لكى نبدأ حياتنا الجديدة في تشاندلر أريزونا. عندما انتقلت ، عشت مع أمي حتى أكتشفت الأمر. ويوم ان كنت في المدرسة لكى أحصل على درجتى العلميه فى علوم الكمبيوتر في جامعة أوستن بيي ستيت. كان لدى سنة واحدة فقط لانهى دراستى، فلماذا لا انهيها ، وأحصل على وظيفة جيدة الأجر ، وكانت أمي طيبه معنا في منزلها. كان ذلك صعبا ومن اكثر التجارب تحدياً …فقد كانت أمي تواجه تحديهاالخاص من الناحيه الصحيه ، ولديها ابنتها المطلقة حديثا والبالغه من العمر 29 عاما مع طفلين في منزلها لم يكن ذلك سهلا بالنسبه البها. كنت محطمه بشكل كبير . فقد تحطمت روحيا وعقليًا وأثر ذلك على حالتى الصحيه بشكل عام. وكان يجب ان أكون قويه أمام أطفالي. ولم أكن أعمل. فلم أعمل ابدا ولم يسمح زوجي بذلك. ﻟذا ، والان ، انا ابلغ 29 ﻋﺎﻣﺎً ، وأم لطفلين ومطلقه وليست لدى درجه علميه ولا خبره مهنيه ورغما عن كل ذلك كان يتوجب على ان ابحث عن وسيله ليس فقط لاعاله نفسى و لكن لاعاله أطفالى أيضا ً. أثناء الاقامه مع والدتى ، أصبحت الحياه متوترةً شيئا ما . فكما ذكرت ، فقد مرت أمي بالكثير ، ولديها صراعاتها ورحلتها الخاصة ، وقد أصبحت انا جزءا من قصتها. ومع خسارتها بفقدان الرجل الذي أحبته كثيرا ، وصحتها المتدهوره، فهى أيضا لها قدراتها الخاصة على تحمل ما تتعامل معه ، وأصبح وجودى في المنزل مع اطفالى عبئا ثقيلا بالنسبه اليها. وقد حاولت أن أقوم بدوري بشراء الطعام بكميات كبيرة فقد كنا تسعة أشخاص في منزل مكون من خمس غرف نوم. لكن أحيانا ، لا تتطابق مع وجهه نظرى عن “القيام بدوري” مع الأخرىن ، وأحيانا تحدث بعض المشكلات. ففي أحد الأيام اتصلت والدتى وطلبت منى دفع فاتوره الإنترنت . بصراحة ، قد استطيع دفع فاتورة أقل من 100.00 دولار ، ولكن النفقه الغير عادله لاطفالى من طليقى في ذلك الوقت ، لم تمكننى من الالتزام بدفع أي شيء. وذلك هو السبب في أنني أشتري الطعام من كوستكو بكميات كبيرة ، وهكذا. ولكن ، كانت تلك نقطة التحول بالنسبة لأمي فقد قالت لى ، “أنا لا أريدك في منزلى بعد الآن”. لذا فإن خطتى لإنهاء المدرسة في عام واحد اختفت ! وعدت إلى المنزل في يوم ما لاجد أغراضي قد وضعت في سلات أمام الجراج. فغيرت اتجاه السيارة وذهبت في البحث عن شقة أستطيع تحمل نفقتها. في ذلك الوقت ، كان زوجى السابق يودع 1000 دولار في الحساب المشترك لأطفالنا. كان علي أن أجد شقة أقل من 1000 دولار بالإضافة إلى تغطية تكلفة البنزين والطعام . ولدهشتي وجدت شقة تسمى شقق كروس ويندز مقابل 550 دولار شهريا فى أريزونا افي وبيكوس . في أغسطس 2014 ، انتقلت للعيش فى شقتى الأولى مع أطفالى. كنت في التاسعة والعشرين من عمري ، ولم يكن لدى وظيفة بعد ، وتلاشت فكرة إلانتهاء من المدرسة ، ولا بد لي من إيجاد طريقة للتغلب على ظروفى . اتنفس … فقط اتنفس … (فاحيانا لا أستطيع. أعني … أشعر وكأنني كنت أبحث عن الهواء حتى اتنفس!) وكان أطفالي فى حاله حزن شديده. وكنت مشوشه. لم يكن عندى أدنى فكرة عما يجب أن أفعله وأين أذهب فأنا أحتاج إلى وظيفة. بعد أن وصلت إلى صديقتي ، ديدرا هيل ابود التى ساعدتني في ان اجدد السيرة الذاتية الخاصه بى بناءا على خبراتى السابقة ، بدأت أتقدم بطلب لكل وظيفة أعثر عليها. وكملاحظة جانبية ، فإن ديدرا هيل ابود لم تساعدنى في عمل سيرتي الذاتية والتى لم أكن أعرف طريقه تنظيمها فقط ، ولكن أيضا ساعدتني في طريقه تفكيري ، وذكّرتني بأن أكون شاكره حتى مع شعوري بالهزيمه ، وقد كنت في أدنى نقطة من مراحل حياتي. ولكن ، لم أكن محظوظه في البحث عن عمل ، وكنت على استعدادأن أقبل بأى شىء! ولكن في أكتوبر 2014 ، جاءت شقيقتي إيمان ، التي كانت شهرتها إيمان بى فندي ، لزيارتى. لم يكن لدي مقعد ، ولا سرير ، ولا أثاث لفتره. وتحدثنا طويلا عن الحياة ، وكل شيء بيننا. خلال المحادثة ، حدثتها عن فكرتي وشاركت معها لعبة بطاقة ابتدعتها عندما كنت أعلم الأطفال المسلمين مرة أخرى في كلاركسفيل تينيسي. وفى 29 أغسطس 2014 تم تعيينى كمربية. وانتقلت في ذلك الشهر إلى شقة جديدة ، لم أحيا أبدا فى شقه خاصه بى من قبل ، ولم أقم بدفع أيه فواتير (كما يفعل الاخرون ) ، وأستطعت العثور على وظيفة فى نهاية الشهر وكان راتبها 300.00 دولار في الأسبوع. وكنت سعيدة جدا بدرجه لا يمكن أن تتخيلوها. كنت سعيدة جدا. وكانت عائلتي تزورنى فى اوقات متفرقه. أخبرتني عن “سكور” ، وهي منظمة غير ربحية تقوم بتقديم إرشادًات مهنيه مجانيًة في جميع أنحاء الولايات المتحدة الأمريكية. قالت ، “تواصلى معهم. سيقومون بمساعدتك في فكرتك. و انا “يا اللهي!” فقد كنت متحمسة للغايه! ذهبت إلى مفهى بيكسوتو في تشاندلر أيه زى … للولوج الى الإنترنت … فلم أكن أستطيع تحمل تكلفة الإنترنت في ذلك الوقت. وتفقدت موقع سكور على الإنترنت وكان لديهم حدث قمت بحضوره في نوفمبر 2014. كنت متوترة وخائفه جدًا. لاننى لم أكن أعرف ماذا أفعل بفكرتي. كل ما أعرفه هو أن لدي فكرة ، وكنت متحمسة لها ، ولدى الدافع لعمل أى شيء لتلك الفكره! طلب مضيف الحدث من جميع الحضور الوقوف وتقديم أنفسهم. الجميع كان لهم لقب ممتاز وتجربة رائعة جدا لتقديم أنفسهم ، وعندئذ حاولت ان اقدم شيئا عن نفسى لم اقم به من قبل. بكل ما لدى من عدم الاحساس بالامان ، وعدم الثقة بالنفس ، والتناقضات الداخلية ، وقمت بتقديم نفسى كالتالى … “مرحبا! اسمي أمينة مبروك ولدي فكرة لعبة بطاقة تساعد الأطفال على ان يتعلموا اسم ومكان (الصلاة). أننى هنا لأنني لا أعرف ماأفعله بفكرتي “. بعد الجلسة ، كان هناك رجل يتجه نحوي يسمى” دوج ويتني “. وهو معلمًا معتمدًا في سكور ، وهو يساعد العملاء الراغبون في البدء فى أعمالهم أو تنمية أعمالهم. اقترب مني قائلا: “مرحبا! أنا اسمي دوج ويتني. أظن أنني أستطيع أن أساعدك في فكرتك.هذا هو الكارت المهنى الخاص بى . وااو ! فقد شعرت بسعادة كبيره! وقمت بحجز موعدًا معه في ذلك اليوم ، واستمريت فى مقابلة المشرف المهنى الخاص بى اسبوعيا و لمدة عامين. كنت أشعر بالوحدة فى رحلتى . فقد كنت أركز على العمل ، أطفالي وفكرتي ، بدأت أفتقد كونى جزء من المجتمع. خلال السنتين اللتين كنت التقى فيهما مع المشرف المهنى ، قال لي ويتني: “يجب عليكى ان تبدأى في بناء موقع إلكتروني. أنصحك بإنشاء موقع الويب الخاص بك على وورد بريس . ” أنى أحب وورد بريس . حسنا! سأبدأ الليلة. و انا كمن يقول “ما هذا؟ اقوم بالضغط علي الكلمات؟” ها ها اني امزح فحسب! لقد اكتشفت انك استغرقت هذا الوقت في قراءة مدونتي, حيث ترتبط عمليًا في هذه المرحلة … .كما يضفى قليلا من المزاح … أكمل ارجوك … ثم ذهبت إلى قهوة بيكسوتو ، وفتحت جهاز الكمبيوتر الخاص بي ، ثم ولجت إلى wordpress.org ، أنشأت حسابًا وبدأت إنشىء موقع الويب الخاص بي. كانت هذه المرة الأولى التي أنشئ فيها موقعًا على الويب. وبحثت فى جوجل عن كل شيء وكثيرا من الفيديوهات على يوتيوب. اتدري, لقد تعلقت بما ابحث فيه. فقد كنت محبطة. واحسست بخيبة أمل كبيرة وخاصة عندما رأيت المواقع الجميلة هناك ، كنت متردده قليلاً فى الاستمرار. ففي محاولة معرفة هذا الوورد بريس ، تعلمت أيضًا ماهى مساحات العمل المشترك التي صرت مهووسة بها! هل تعلم أنهم هنا في جميع أنحاء المدينه! يا الله ! لقد اكتشفت أن أحدا هنهم قريبا من منزلى جانج بلانك في تشاندلر أريزونا. بدأت العمل من خلال جانج بلانك وأحببت ذلك المجتمع. كانت تلك هي المرة الأولى منذ عامين أشعر بالتواصل الاجتماعى بعد الطلاق. عملت هناك باستمرار وقابلت سيدة رائعه اسمها أن واتسون باربر ومن خلال أحاديثنا ، أخبرتها عن مشكلتى مع موقع الوورد بريس
\nوبدون تردد و بتلقائيه عرضت على مساعدتى بدون أى سؤال. كنت متحمسة جدا! ليس لديك فكره عن السعادة الكبيرة التى احسست بها! كنت ألتقي باستمرار مع آن واتسون باربر في جانج بلانك كثيرا. وبأمانة ، بدون الوورد بريس ، ماكنت بحثت عن مكان يعمل فيه الناس معا ، والذى قابلنى بآن واتسون باربر والكثير من الأشخاص الرائعين . لكن ذلك كان البداية. فلم احصل فقط على شعور التواصل الاجتماعى والذي كنت افتقده في حياتي في جانج بلانك ، بل قمت بعمل صداقات مع اشخاص رائعين ممن هم مستعدين لتقديم المساعدة مهما حدث ! هل يمكن ان نتوقف لحظه ونتحدث عن ذلك.! فمن خلال اجتماعاتنا ، أخبرتنى صديقتي “آن” عن مجموعات Meetup في وورد بريس. بدأت أبحث فى جوجل عن مجموعات الميت اب من حولى للوورد بريس. ذهبت الى كل منهم! بعض من WordPress Meetup تكون ساعة وواحد وثلاثون دقيقة ولقد احببت كل هذا ! ولكني استمريت فى تكوين أصدقاء جدد ، واستمريت في بناء موقعي على وورد بريس. كيف غيرت وورد برس حياتي ، تتحدث القصة عن نفسها. فاختيارى لبناء موقعي على وورد بريس كان هو الحافز منذ البداية والذي فتح لى الكثير من الأبواب التي لم أكن على علم بوجودها. واصلت بناء موقعي لسنوات عديده ، ثم انتقلت إلى مشروع آخر. ولكن ، بدون الوورد بريس والذى عرفنى على مجتمع الوورد بريس ، لم أكن لاتعلم كيفية بناء وجود لى على الإنترنت ، لكى أطرح الأسئلة بلا خوف عندما أعجز عن عمل الاشياء ، وأن يكون حولى أشخاص على استعداد للمساعده بلا أنانيه ، وبالرغم من أنى أحتاج إلى تكرار المعلومات كثيرا لكى افهمها.
\nفبدون مجتمع الوورد بريس ، لم أكن لاتعلم أن أتقبل الفشل والذى يخلو من من النقد ، حيث أننا جميعا نحاول أن نحقق مانريد. وبدون مجتمع الوورد بريس ، لم أكن لاتعلم فكرة مشاركه المعلومات – حيث أن نجاحك هو نجاحي. بدون مجتمع وورد بريس ، لم أكن لأتحمل ألشعور بالهزيمة وان استمر ولو بقليل من الشجاعة التى امتلكها لتحقيق ما أريد. لقد غير الوورد بريس حياتى حقا. بعد المغامرة بأشياء أخرى ، و للكون طريقتة فى تذكيري بما أنتمي إليه. أبلغت عن التطوع. ففي 15 – 17 من فبراير 2019 ابلغنى صديقى جاستن نيلى بالتطوع فى وورلد كامب فينكس #WCPHX ، في جو دادى. لذا استخدمت تطوعي وأوقات المرض للإبتعاد لاكون جزءا من هذا الحدث. لقد كنت b! لم أكن أعرف أبداً ماذا تعنى الوورد بريس لاصحابها. لم أفهم قلب مشروع الوورد بريس ، ومدى أهميته في طريقة تأثيرة على المجتمع. عندما بدأت مع الوورد بريس ، فقد كان من أجل بناء موقعي على الويب لنشاطي المبدئى. لكن في هذه المرة ، تلقيت نظره خاطفة عن أهميتها في العالم ، وأننى سعيدة بأن أكون جزءا منها على مستوى جديد! وأثناء تواجدى فى وورد كامب فينكس من 15 – 17 فبراير 2019 قابلت اشخاصا رائعين وكان هذا من اسعد اوقات حياتى! وقد اتاح لى هذا الحدث الفرصه لالتقاط الصور والفيديوهات فى يوم المشاركة و تنظيم أجتماعات المناقشة الخاصه بوورد بريس فى جالفانيز فينكس. وفتح ذلك مزيدا من الأبواب لمقابلة توفر دى روسيا الذي اقترح وألهمني أن أكتب هذه المدونة لموقعه الإلكتروني والذي أطلق عليه أسم هيرو بريس ؛ ولمقابلة آدم وارنر مدير التسويق الميداني لـ جو دادى ؛ ولمحادثة رائعة مع آرون كامبل | WordPress Core / Ecosystem؛ والكثير من الاشخاص الرائعين الذين ظهروا فى حياتي بسبب ذلك! والان اناأعمل في جو دادى هوستنج سابورت. فأنا أحب عملي وأقاتل فى مجتمع الوورد بريس هنا في المدينه. إنني أعمل قريبه من ماثيو كلانسي لتسجيل وتحرير برنامج وورد بريس المتقدم وتطوير الاجتماعات وغيرذلك من الأحداث القادمة. أننى متحمسة جدا للمستقبل! ، وأذا ما كنت تتساءل عن فكرتى لبطاقه الصلاة … فهذه مدوّنة أخرى ، و سعادة أخرى. في نفس الوقت ، دعنا نكن أصدقاء! دعنا نتواصل! على تويتر AmenaMabrouk
\nThe post How WordPress Changed My Life appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 08 Mar 2019 01:30:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Amena Mabrouk\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"WPTavern: WPWeekly Episode 348 – RIP Alex, Facebook Moderators, and Shorter Release Cycles\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=87851&preview=true&preview_id=87851\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"https://wptavern.com/wpweekly-episode-348-rip-alex-facebook-moderators-and-shorter-release-cycles\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2067:\"In this episode, John James Jacoby and I review feedback from last week’s show, share a few more memories of Alex Mills, and discuss an article that describes what it’s like to be a content moderator for Facebook. We also share our opinions on the idea of WordPress having shorter release cycles.
\nThe Drive Remembers Alex Mills
\nThe Secret Lives of Facebook Moderators
\n\nPressNomics 6 Tickets are on sale
\nFreemius Patches Severe Vulnerability in Library Used by Popular WordPress Plugins
\nWordPress Contributors Propose Shorter, Time-based Release Cycles
\n\nNext Episode: Wednesday, March 13th 3:00 P.M. Eastern
\nSubscribe to WordPress Weekly via Itunes
\nSubscribe to WordPress Weekly via RSS
\nSubscribe to WordPress Weekly via Stitcher Radio
\nSubscribe to WordPress Weekly via Google Play
\nListen To Episode #348:
\n
The inaugural WordCamp Nordic will be live streamed for free on March 8, from the Paasitorni Congress Center in Helsinki. The conference starts at 9 AM. Those watching remotely can tune into both tracks via the following links:
\nTrack 1
\nhttps://2019.nordic.wordcamp.org/live-congress-hall/
Track 2
\nhttps://2019.nordic.wordcamp.org/live-sirkus/
The WordCamp’s organizers published the direct links, so there is no need to sign up for a livestream ticket. Session topics include Gutenberg development, environmentally friendly WordPress development, preparing for PHP 7.2, Gutenberg Cloud, WooCommerce, blog marketing, multilingual websites, and more. Check out the full schedule for a list of all the sessions.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 07 Mar 2019 22:09:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:18;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"Gary: Authentication in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"https://pento.net/?p=4591\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://pento.net/2019/03/06/authentication-in-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2315:\"WebAuthn is now a W3C recommendation, bringing us one step closer to not having to use passwords anymore. If you’re not familiar with WebAuthn, here’s a little demo (if you don’t own a security key, it’ll probably work best on an Android phone with a fingerprint reader).
\n\n\n\nThat I needed to add a disclaimer for the demo indicates the state of WebAuthn authenticator support. It’s nice when it works, but it’s clearly still in progress, and that progress varies. WebAuthn also doesn’t cover how the authenticator device works, that falls under the proposed CTAP standard. They work together to form the FIDO2 Project. Currently, the most reliable option is to purchase a security key, but quality varies wildly, and needing to carry around an extra dongle just for logging in to sites is no fun.
\n\n\n\nAnything that replaces passwords needs to provide some extra benefit, without losing the strengths of the password model:
\n\n\n\nMagic login links are an interesting step in this direction. The WordPress mobile apps added magic login support for WordPress.com accounts a while ago, I’d love to see this working on all WordPress sites.
\n\n\n\nA WebAuthn-based model would be a wonderful future step, once the entire user experience is more polished.
\n\n\n\nThe password-less future hasn’t quite arrived yet, but we’re getting closer.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 06 Mar 2019 02:13:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Gary\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"WPTavern: Global WordPress Translation Day Set for May 11, 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87768\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wptavern.com/global-wordpress-translation-day-set-for-may-11-2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2290:\"One of the the most important factors in WordPress’ growth is the software’s availability in 186 languages. Its vibrant community of translation volunteers, known as the Polyglots team, continually update the translations to ensure access for millions of non-English speakers around the world. In 2016, the team began hosting their own events dedicated to educational sessions and topics that affect the translation community, along with coordinated translation sprints.
\nThe 4th edition of the Global WordPress Translation Day (GWTD) has been set for Saturday, May 11, 2019. It is a 24-hour virtual and in-person event that brings together new and experienced translators. The most recent event was held in 2017 with 71 local events in 29 countries. More than 1,300 people RSVP’d for local events and volunteers around the world translated 93,179 strings in core, themes, and plugins. The event was also successful at growing the local translation communities, adding 217 new translators to the project.
\nIt’s hard to overstate the importance of events like this that support and grow WordPress’ vital translation community. This colorful chart shows the percentage of users running the software in different locales. WordPress has a diverse global user base, thanks in large part to the efforts of volunteer translators.
\nIf you want to get involved in the next Global WordPress Translation Day, mark your calendar for May 11, 2019. For more information, check out the #GWTD4 tag on the Polyglots blog and join in on the #polyglots-events Slack channel.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 01 Mar 2019 23:53:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"WPTavern: Freemius Patches Severe Vulnerability in Library Used by Popular WordPress Plugins\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87723\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"https://wptavern.com/freemius-patches-severe-vulnerability-in-library-used-by-popular-wordpress-plugins\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5480:\"Freemius, a monetization, analytics, and marketing library for WordPress plugin and theme developers, patched an authenticated option update vulnerability in its wordpress-sdk four days ago. The library is included with many popular plugins, such as NextGEN Gallery (1,000,000+ installs), 404 – 301 (100,000+ installs), WP Security Audit Log (80,000+ installs), and FooGallery (100,000 installs+). Freemius CEO Vova Feldman said he would classify it as “a severe vulnerability.”
\nFeldman had planned to wait to publish anything about the vulnerability until more plugin authors had updated, but the security team at PluginVulnerabilities.com published a detailed explanation of the vulnerability within 24 hours of plugin developers getting notified about the patch:
\n\nThe vulnerability, an authenticated option update vulnerability, would allow anyone with access to a WordPress account to take complete control of the website. That is a type of vulnerability that hackers will try to exploit if there is significant usage of a plugin. Anyone that allows untrusted individuals access to WordPress accounts and is using a plugin with this library is at a pretty significant risk if they haven’t updated the plugin to a version that fixes this or deactivated the plugin.
Plugin developers using the library have already been notified by Freemius, the team at pluginvulnerabilities.com, and will soon be contacted by the WordPress.org plugin team. A full list of the plugins impacted by this vulnerability is not available yet, but Freemius has a page on its website showcasing 96 WordPress.org plugins and nine themes that use it.
\n“More than 60% of the developers who are using our SDK have already upgraded to the patched version,” Feldman said. As of today, Feldman said he has not received any reports of the vulnerability having been exploited.
\nFeldman published a summary of his company’s actions on the security issue and described how Freemius is working to mitigate exposure and try to give users more time to update. The company requested two things from developers using its wordpress-sdk library:
\nIt is in a company’s best interest to keep the details of a product’s security issue under wraps for as long as possible, but that may leave some users exposed when the vulnerability has already been published on the web. Any user who sees an update for a plugin using Freemius is advised to act on that update immediately, regardless of whatever generic note appears in the changelog.
\nAs a company providing a security service, PluginVulnerabilities.com had different priorities in publishing details about the vulnerability, according to a representative who identified himself as John:
\n\nIn this case where we are not the discoverers. The biggest issue is that vulnerability looks to have already been being exploited when we came across it, so hiding the situation from the public seems highly irresponsible. Our customers pay us to warn them about vulnerabilities in their plugin, so we would need to warn them right away once we became aware of this. If we only warned our customers that obviously raises some serious questions since others in WordPress community would be left in the dark.
In cases like this, where developers are including a third-party library in their plugins, it can take longer for users to receive an update that fixes the vulnerability, since the need for a patch has to be communicated to multiple parties. The situation is similar to the recent vulnerability that Bootstrap patched two weeks ago. Bootstrap announced the vulnerability in the same week it was reported and fixed, instead of trying to delay disclosure, even though thousands of products across the web use the Bootstrap framework.
\nWordPress.org doesn’t currently have a mechanism to flag certain plugin updates as security updates, but if a security update is severe enough, the plugin team can push updates out faster with cooperation from plugin authors. That route has not yet been pursued in this case, but we will continue monitoring the situation. In the meantime, if you are using a plugin that includes Freemius and the author has not updated, you may want to consider turning the plugin off temporarily until a patch is available.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 01 Mar 2019 19:47:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WordPress.org blog: The Month in WordPress: February 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6652\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2019/03/the-month-in-wordpress-february-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7523:\"A new version of WordPress, significant security enhancements, important discussions, and much more – read on to find out what has been going on in the WordPress community for the month of February.
\n\n\n\nNear the end of the month, WordPress 5.1 was released, featuring significant stability and performance enhancements as well as the first of the Site Health mechanisms that are in active development. Most prominent is the new warning for sites running long-outdated versions of PHP.
You can check out the Field Guide for this release for a detailed look at all the new features and improvements. The next release is already in development with plans to improve the Site Health features, PHP compatibility, and a number of other things.
Want to get involved in testing or building WordPress Core? You can install the WordPress Beta Tester plugin, follow the Core team blog, and join the #core channel in the Making WordPress Slack group.
\n\n\n\nThe block editor that is now a part of WordPress core started out as a project named Gutenberg with the lofty goal of creating a whole new site-building experience for all WordPress users. The first phase of Gutenberg resulted in the block editor that was included in WordPress 5.0, but development didn’t stop there – phase 2 of the project is well underway.
This month, one of the initial goals for this phase was reached with all of the core WordPress widgets being converted to blocks – this will go a long way to allowing full sites to be built using blocks, rather than simply post or page content.
Want to get involved in developing Gutenberg? Check out the GitHub repository and join the #core-editor channel in the Making WordPress Slack group.
\n\n\n\nAs Gutenberg development continues, the Mobile team has been working hard to integrate the new block editor into the WordPress mobile apps. Near the end of February, the team shipped a complete integration in the beta versions of the apps – this a significant milestone and a big step towards unifying the mobile and desktop editing experiences.
Both the iOS and Android apps are open for beta testers, so if you would like to experience the block editor on mobile today, then join the beta program.
Want to get involved in developing the WordPress mobile apps? Follow the Mobile team blog, and join the #mobile channel in the Making WordPress Slack group.
One of the goals for 2019 that Matt Mullenweg (@matt) announced in his State of the Word address last year was to form a team who would work to manage the ever-increasing number of tickets in Trac, the bug tracker that WordPress Core employs.
\n\n\n\nThis team, known as the Triage Team, has been announced. Their work will involve coordinating with component maintainers, release leads, project leadership, contributors, and other WordPress related projects with issue trackers outside of Trac to ensure that everyone is empowered to focus on contributing.
\n\n\n\nThe team was formed based on nominations of volunteers to take part and will be led by Jonathan Desrosiers (@desrosj). The other members of the team are Chris Christoff (@chriscct7), Tammie Lister (@karmatosed), Sergey Biryukov (@sergey), and Sheri Bigelow (@designsimply) – all of whom have a strong track record of contributing to WordPress, have exhibited good triaging practices, and are overall good community members.
\n\n\n\nHave a story that we should include in the next “Month in WordPress” post? Please submit it here.
Creating a block for navigation menus is one of the nine projects Matt Mullenweg identified as a priority for 2019, and the future of WordPress menus is starting to take shape. Designers working on the new Navigation Menu block have published a prototype this week with detailed notes on how users will interact with the block.
\nThe proposed solution would automatically generate a menu and users would able to delete menu items using the keyboard or block settings ellipsis menu. Individual menu items can be moved right or left and more advanced options for reordering or nesting would be hidden behind the block inspector.
\nAdding a menu item opens a search bar that would give quick access to all the content in the site. From here users can create a new page or use advanced mode to bulk add more pages. The designs aim to hide most of the more complex tasks behind the block inspector.
\nReading through the list of interactions this design is expected to cover, it’s clear that navigation menus are one of the most challenging interfaces to bring into the block editor. One of the principles the designs are based on is that “The editing state of the block itself should mimic as closely as possible the front-end output.” However, it’s difficult to fully visualize how this will work. Navigation menus are most likely to be used in the header and/or footer of a website, but it’s not yet clear how themes will reveal a navigation area to Gutenberg.
\nThere are still many questions to be answered and the design team is seeking feedback on the prototype. Comments are open on the post and feedback on more specific interactions can be left on the relevant GitHub tickets or in Figma. The tickets related to the navigation block discussion are listed in the proposal. The design team is currently working on usability testing and aims to have a final design by the end of March.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 01 Mar 2019 04:55:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:23;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"WPTavern: WPWeekly Episode 347 – Chair Buying, Pressing Issues, and Block Management\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=87718&preview=true&preview_id=87718\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"https://wptavern.com/wpweekly-episode-347-chair-buying-pressing-issues-and-block-management\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2347:\"In this episode, John James Jacoby and I start off by discussing the office chair purchasing process. I recently needed to buy a new chair and was surprised by some of the features that were highlighted.
\nWe talked about block managers and some of the pitfalls that will need to be overcome. For example, what should WordPress do if a user disables a block that’s already used in a post?
\nWe wrap up the show by sharing some of the most pressing issues people are having with WordPress.
\nYoast CEO Responds to #YoastCon Twitter Controversy, Calls for Change in the SEO Industry
\nWordPress 5.1 Improves Editor Performance, Encourages Users to Update Outdated PHP Versions
\nBlock Management Features Proposed for WordPress 5.2
\n5.2 Proposed Scope and Release Schedule
\nUI/UX Changes for the Site Health Check Plugin
\nJeffrey Zeldman Promoted to Automattic Employee
\nThe Most Pressing Issues People Have with WordPress These Days
\nNext Episode: Wednesday, March 6th 3:00 P.M. Eastern
\nSubscribe to WordPress Weekly via Itunes
\nSubscribe to WordPress Weekly via RSS
\nSubscribe to WordPress Weekly via Stitcher Radio
\nSubscribe to WordPress Weekly via Google Play
\nListen To Episode #347:
\n
WordPress release cycles may soon take a more predictable cadence, as contributors are considering moving to a time-based approach. The discussion began during a recent core dev chat in mid-February when Gutenberg phase 2 lead Riad Benguella proposed the project move to shorter, automated release cycles.
\nThe Gutenberg team has successfully been releasing a new version of the plugin every two weeks on schedule and any features that aren’t ready are postponed to the next releases automatically. Benguella contends that this type of release schedule has the potential to bring several benefits to WordPress:
\nShortening major releases may prove more challenging for WordPress, which is at a much larger scale than the Gutenberg plugin. The plugin also has the added advantage of being able to manage releases and development on GitHub.
\n“I think there are a lot of infrastructure problems that need to be solved for WordPress before we could move to a fast, automated release cycle,” Gary Pendergast said.
\n“Having a major release once a month is achievable, it’s something I’d like us to get to, but the release process is too manual to have multiple releases running at the same time at the moment.”
\nJonathan Desrosiers drafted a proposal that summarizes this discussion and outlines some of the manual tasks required for getting a major release out the door. These include time-consuming tasks like Trac gardening, creating a Field Guide, blog posts for the betas, RCs, and official release, documentation updates, videos, dev notes, and other items that are often completed by volunteers.
\nThe 3-4 month release cycles that WordPress had from versions 3.9 – 4.7 allowed for all of the administrative overhead outlined above to be completed in a reasonable amount of time, but the general consensus is that some of these tasks could be more simplified and/or automated.
\nDesrosiers highlighted several benefits of moving to a shorter major release cycle, including less drastic change for users that might ultimately result in more users being comfortable enabling automatic updates for major releases. Detriments to shortening the release cycle are the increased burden it puts on volunteers as well as theme and plugin developers who need to push compatibility releases. It would also introduce more backporting work for security releases.
\nSeveral contributors have left feedback on the post with insight gleaned from other projects’ release scheduling. Jeremy Felt reviewed Firefox’s release owner table that assigns leadership and dates for several releases in advance.
\n“I think getting to a shorter release cycle in general will involve scheduling multiple releases and assigning their release leads in advance,” Felt said. “So far most of our scheduling is done as soon as the last release has been shipped.”
\nJoe McGill examined VS Code’s development process and found several similarities to the process he thinks WordPress could adopt in the future:
\nSeveral of these points echo feedback from other contributors who have identified documentation integrated into development and automated testing as ways to speed up major release cycles.
\n“If we don’t have the infrastructure and tooling to support a 1 month cycle, then I think we could attempt a 2 month cycle with a goal towards moving to shorter cycles,” McGill said.
\nThe Gutenberg plugin’s relentless pace of iteration and predictable release cycles have opened up a world of new ideas for improving the process for WordPress core. Discussion around moving the project to shorter, time-based release cycles is still in the preliminary stages. No major changes have been agreed upon yet, but the process of exploring different ideas has put the spotlight on tasks that could afford to be tightened up in the release process. This falls in line with WordPress’ 2019 theme of “tightening up.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 28 Feb 2019 18:21:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"Post Status: Branching out: An interview with Peter Suhm\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=55639\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://poststatus.com/branching-out-an-interview-with-peter-suhm/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7073:\"In Peter’s words, “the most basic way to think of WP Pusher is that it replaces FTP with a flow where updates come directly from GitHub/Bitbucket” through the WordPress core auto-updater.
\nYou may not know Peter built the first version of WP Pusher in a shopping mall in Thailand while traveling the globe for four years. Originally from Copenhagen, today Peter is settled down in Glasgow and has just launched Branch, a Docker-based build and deployment tool for WordPress developers that goes quite a bit further than WP Pusher. Branch is a continuous integration service for WordPress that adds “the ‘build’ and ‘test’ steps” before deployment.
\nDK: You’ve launched Branch with a manifesto that declares “WordPress developers are developers too” before outlining the well-known lack of modern tools for WordPress development. Why do you think that has been such a long-lamented situation and was there something unique in your experience that drove you to do something about it?
\nPS: One of the things that makes WordPress really special is its low barrier of entry. The 5-minute install and all of that. The WordPress community proudly consists of a large percentage of amateurs and hobbyists. A lot of people have their first experience with programming because of WordPress, which is great and something WordPress should be really proud of. Most development frameworks exist to make the developer more productive, but I think WordPress has another purpose. The purpose of WordPress is to democratize publishing (which is something user facing), not to be an awesome tool for developers. There are obviously some political decisions behind this lack as well. Religiously supporting outdated versions of PHP is just one of them. Not having any sort of dependency management, so everyone has to reinvent the wheel on each project is another one.
\nEvery WordPress developer is asking the same questions. “How do I manage my dependencies?” or “how do I migrate changes to the database?” These are questions people literally ask me because I sell WordPress developer tools. Personally, I didn’t get into programming because of WordPress. I have been doing PHP development since my early teens, and my first job was as a Ruby on Rails junior developer. “Growing up” as a developer, I was raised very strictly! My co-workers would write failing unit tests for me, and I’d have to implement the code. This made me pretty religious about best practices, testing etc. After RoR I discovered Laravel in 2013 and helped build the Laravel community in Copenhagen. However, during high school, I had built quite a few different projects using WordPress for myself and my clients. Once in a while, I’d have to update these old WordPress sites, which always involved installing an FTP client. This was rough after five years of continuous deployment using Git and automated tests. I hate FTP with a passion. It’s an error-prone and outdated way to deploy your code.
\nInspired by some of the tooling I knew from RoR and Laravel, I set out to build a better way to deploy WordPress code. After a lot of experimentation, I landed on WP Pusher. However, WP Pusher only moves the code. It doesn’t run your build scripts or your unit tests. It just blindly moves your code from a Git repository to WordPress. I was intentionally ignoring this problem for a while, being kind of intimidated by it I guess. However, people kept asking me the questions I described earlier, so I started experimenting again and believe I found a really cool solution with Branch. Branch is built on top of Docker, so everything you can imagine doing inside of Docker containers will eventually be available within Branch. A major part of building Branch is to make this great, but highly technical, stack available to WordPress developers.
\n![\"\"](\"https://cdn.poststatus.com/wp-content/uploads/2019/02/branch_screen.png\")
The Branch Dashboard showing the configuration options for a theme’s build steps.
DK: Does Branch build on or incorporate WP Pusher, or are these totally separate technologies? As SaaS businesses, will they remain separate or merge? I imagine some of your agency customers for WP Pusher might want to move up to Branch, if they don’t lose anything in the process.
\nPS: The best way to understand Branch, and why it’s different from WP Pusher, is to imagine it as two separate parts: The build + test part (continuous integration) and the deployment part (continuous deployment). The deployment part of Branch very much builds upon WP Pusher. The build part is what’s new. It’s the missing link between developing on your local machine and shipping to production.
\nOne of the things that excite me the most about Branch is that it’s a hosted SaaS, compared to WP Pusher which is “just” a WordPress plugin. That allows me to add a much more advanced feature set and ship much faster. With a SaaS, you are in control of the environment in which the software runs. That gives you a lot more flexibility and opportunity. I want WP Pusher to stay around for everyone to keep using. However, I want to make Branch so good that everyone wants to switch eventually. But WP Pusher will stay around. That’s for sure.
\nDK: What did you learn from life as a digital nomad? Have you given it up for good now, or do you plan to do more traveling?
\nPS: That’s a good question, I should probably spend some more time thinking about! I came into the “nomadic” lifestyle sort of by accident. It wasn’t very purposeful. I think on a personal level the number one lesson has been how important for me it is to have a base. Traveling for a long time, you become very aware of your roots. You spend a lot of time thinking about the good and the bad parts of being back home. I think ideally it allows you to go “home” and have a better idea of which parts of settled life you like, and which ones you’d rather be without.
\nOn a business level, WP Pusher was born on the road and has a very different nature than most businesses. From day one it’s been a premise that I wasn’t always around 24/7. It’s never been a problem, because it’s never been an expectation. I’ve never had to change anything about WP Pusher to allow me to travel, because I was already traveling when I built it. Now I’m pretty settled, and I live with my fiancé and only travel for smaller trips. I’ll never stop traveling, hopefully, but I don’t think I’ll ever live on the road again! ![](\"https://cdn.poststatus.com/wp-content/uploads/2015/10/cropped-logo-blue-192x192.png\"){kind=logo}
Gatsby WordPress Themes is a new collaborative project led by Zac Gordon with help from Jason Bahl, Rich Tabor, Muhammad Muhsin, and Alexandra Spalato. The group is working together to port popular themes for use with Gatsby, the React-based static site generator that uses GraphQL for its data layer.
\nKnown for its performance and ease of deployment, Gatsby has captured developers’ attention and was one of the rising stars of the React ecosystem throughout 2018. Using WordPress as a headless CMS, developers can pull data into Gatsby and enjoy the scalability, speed, and security that comes with serving static files.
\nAlthough static site generators have been around for awhile, the current Gatsby craze seems to be rooted in the fact that the project uses React, Webpack, and modern JavaScript and CSS.
\n“WordPress devs love Gatsby because it lets them throw away the entire old school PHP based WordPress theming system and built sites with React and GraphQL,” Gordon said.
\n“Gatsby devs are finding a new interest in WordPress because by default you have to edit Gatsby content in Markdown. WordPress gives a much richer editing experience.”
\nJason Bahl, creator of the WPGraphQL project, is a technical advisor for the Gatsby WP Themes project. He was inspired to collaborate with the team because he thinks Gatsby has a lot of benefits for WordPress sites.
\n“The end result of a Gatsby site is a static site with no live Database connection,” Bahl said. “Just HTML and JavaScript files, so performance is better than even the most highly cached WordPress sites, and security is better because there’s no live database connection to be compromised.
\n“Also, Gatsby is fully React. With Gutenberg in core, WordPress developers are writing a LOT more React. Using Gatsby as the presentation layer for a site allows for components to be re-used across the admin and the theme, where now developers need to create React components for Gutenberg and PHP template partials for the ‘regular’ theme rendering.”
\nRegular WordPress theme are not immediately compatible with Gatsby, since the entire theme has to be built with React, but developers can use the same styles.
\n“We are taking a distinctly different direction than the WordPress themes on the Gatsby themes repo currently,” Gordon said. “We are going to base all of our themes on the WP GraphQL plugin. The default Gatsby themes now work on a wrapper on top of the REST API and don’t have live GraphQL endpoints, so they are limited.”
\nThe Gatsby WordPress Themes project will offer a combination of free and commercial Gatsby themes. Gordon is partnering with theme shops that are open to his team doing the heavy lifting of porting popular themes over to Gatsby.
\n“The first two theme partners are Rich Tabor of CoBlocks and ThemeBeans, who is licensing us his super clean and Gutenberg perfect ‘Tabor’ premium theme,” Gordon said. “Then we have Leland Fiegel, a fellow DC WP chap and long time friend, from Themetry. They specialize in themes on WordPress.com, which means they are also battle tested. They have licensed us their great business theme Belmont.”
\nGordon said the first versions of the Gatsby themes are targeted towards business and brochure sites that might have a couple pages laid out in Gutenberg and possibly a news/blog section and contact page.
\n“Since headless sites don’t work with a lot of plugins by default, the V1 of all the themes will be super opinionated and focused (but 100% extendable),” Gordon said.
\n“The final set of themes are from the WordPress default themes collection. We will have a detailed article showing how we ported the Twenty Nineteen theme over to a Gatsby theme and that will be the first of the default themes we do.”
\nAlthough this initiative is aimed at simpler WordPress sites, creating and maintaining a Gatsby site isn’t necessarily going to be well-suited to beginners.
\n“As far as the target audience, I think any WordPress site that doesn’t have super fast moving content – like the average marketing site or documentation site is perfect for Gatsby,” Bahl said.
\n“Gatsby does have a ‘Build’ step, where it collects ALL the data needed for the entire site, then outputs the content in the static Gatsby site. So even changing a typo on a post would require the ENTIRE SITE to rebuild, which can take anywhere from a few seconds to several minutes, which may not be acceptable for sites that need content live FAST (like a newspaper).
\n“But for your average WordPress site, waiting two minutes for your changes to be live in production is acceptable. Many heavily cached WordPress sites already experience a delay in content being live anyway.”
\nGordon said he doesn’t believe Gatsby is the right fit for all WordPress sites but for certain projects it “can be a really cool approach both in terms of development experience and gains in speed and security.”
\nThe group is aiming to have its first themes released for WordCamp Miami in mid-March and plans to release more as they make new partnerships and see an actual demand. Gordon is actively looking for more theme shops to bring on board.
\n“Zac will be primarily maintaining the Gatsby themes, though I’ll help where I’m needed,” ThemeBeans founder Rich Tabor said. “We’re still in the very initial stages of development.
\n“Overall, it’s a super interesting idea. Static site generators are increasing in popularity and Gatsby is pretty much leading the pack in terms of performance and ease-of-use — both of which WordPress is not particularly well-known for (but is making strides to improve).”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Feb 2019 19:50:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"HeroPress: Know That You Are Not Alone\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=2692\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:128:\"https://heropress.com/essays/know-that-you-are-not-alone/#utm_source=rss&utm_medium=rss&utm_campaign=know-that-you-are-not-alone\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9625:\"![\"Pull](\"https://s20094.pcdn.co/wp-content/uploads/2019/02/022719-min-1024x512.jpg\")
I remember when I was about 10 years and my mom got our first ever computer. She went to the store and got a bunch of CD’s which I was hyped about because I knew some of them were games. She gave me a yellow box that had “Microsoft FrontPage” on the front and said, “Here, learn this”. She saw my confused face and said “It shows you how to build websites. The web is huge right now. If you have this skill, one day you can make a lot of money.” I did go through the course and was pretty good at HTML and CSS but never stuck with it.
\n\nBesides, no one else I knew was doing it and what do moms know anyway?
\nEverything. They know everything.
This was my first taste of coding. But it definitely wasn’t the last.
\n2016 was a bad year. I was still living in my hometown Philly, constantly working overtime at my low paying job, constantly stressed, trying to prove myself to a company that only viewed me as a number. That combined with the two hour commute both ways daily and I eventually burned myself out severely. I was so depressed that I would go to sleep crying and then wake back up crying again willing myself to get out of bed so that I could go to work. Eventually, I saw a therapist who diagnosed me with depression and she recommended that I take a break from work to recover. I was out of work for three months still recovering when my job called not to check on me, but to see when I was coming back. I ended up quitting over the phone, and never looked back.
\nBut I knew I needed to find out what I wanted to do career-wise. I decided to start teaching myself HTML and CSS again to see what I could do with that skill. I took the CodeAcademy courses and was surprised at how much I remembered.
\n\nI eventually found someone who wanted me to do maintenance on their site for really cheap. I was excited because in just a couple of months I landed a client! But it was also a HUGE mistake.
He was constantly nagging me daily on fixing his site, and every time I would fix it he would find something else wrong. Worse part is that went on for months without me collecting any extra money from him. I didn’t have him sign a contract (BIG Mistake) and he would contact me at various hours which I always responded right away because I felt I had to (Another mistake). Eventually, it got to be too much and I had to cut him off completely. I learned quite a bit about the business of web development and knew I needed to do more research before jumping head first into this again.
\nFast forward to December 2017, I got offered an IT Management job in DC and moved within a couple of weeks with only $50 in my pocket which no place to live. But I made it work. I stayed in a hostel for two weeks while I found an apartment. My mom helped with getting the funds for my apartment and without her support, I don’t know think I would be here now. I stopped my web stuff for a while so I can focus on my transition. I’m not gonna lie, as much as I was happy to move here, I was also very lonely. The folks at my job were older and they were all family people, and I knew no one out here. But the biggest challenge was trying to run a whole IT department by myself and the upper-management C-Suite folks not having a clue about tech or why it costs so much. It also didn’t help that there were folks that had a huge dislike of IT and therefore transferred that dislike to me. I knew about a month into this job that this wasn’t going to be the path that I was going an needed to do something else.
\nI searched online for a web course that would help me learn front-end development and eventually I came across Skillcrush. They were offering a course to teach WordPress development and all you needed to know was HTML and CSS. They offered the course for $150 a month for 3 months. After researching and seeing how many companies were using WordPress and the value in it I decided to take the plunge and take the course. I started in May and completed it in August.
\n\nWhile taking the course I joined their Slack and met a group of amazing women, some who were alumni and found success from freelancing building websites with WordPress. They shared advice and tips on how to find clients and freelance and how they made the transition.
I took all the knowledge I saw and absorbed it like a sponge. Then in September, I took the plunge and quit my job.
\nNow, this was reckless of me. While I did have some savings to keep me afloat for a minute I never planned this out. If you’re going to freelance I highly recommend you don’t go this route. I started looking everywhere I could to get gigs. Upwork was the most successful platform especially for finding WordPress gigs. I was able to find a few successful gigs and luckily got to work with a web agency which gave me a steady stream of income for a while. I learned how to do contracts, set rates and expectations and through these methods and more was able to secure quality clients that I still work with today. One client referred me to others who needed work, which brought in even more income. While I was doing this I also decided to join Twitter and found a community of other black folks who were also starting their tech journey. I was able to help others and well as ask for advice when I needed it. Finally, I no longer felt alone.
\nBut then in February, the agency jobs started to slow down. I could have gone a little longer without a proper job but I decided to go back into the workforce because I wanted to build back up my savings faster and also invest in other parts of my business. So I decided to get back into the job world and got a contract job with the federal government. The job was good and I did so well that after 2 months they offered me a full-time position. I still work at this job to this day.
\nAs for my WordPress websites, I still do work for existing clients if they really need it. In addition, I run a blog called #WordPressWednesday (now named #WordPressWisdom) where I share tips and tricks on all things WordPress. But my journey isn’t over. I recently got accepted into Flatiron Software Development Bootcamp where I will be diving into more backend development. I also have a lot of other things coming which I can’t share just yet. It took a lot of work to get to this point.
\n\nI don’t think I would have ever gotten to this point without the support of the tech community on Twitter and most notably the Digital Empire community that I’m a part of.
Having a place to share resources, tips and jokes daily have kept me motivated and going for the past year.
\nWordPress for me has been a life skill that has brought wealth. It has given me the ability to generate a whole other means of income as well and give resources to other people who are looking for a place to start in the coding world. But it wasn’t an easy journey to get this point. And if you feel stuck like I was, know that there are people here for you. Start your journey today. Get on Twitter and introduce yourself to the community. Ask for help. And most importantly, know that you are not alone.
\nThe post Know That You Are Not Alone appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Feb 2019 12:00:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Sarah Williams\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:28;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: Block Editor Now in Beta for WordPress Mobile Apps\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87647\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wptavern.com/block-editor-now-in-beta-for-wordpress-mobile-apps\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2369:\"The new Gutenberg block editor that arrived in WordPress 5.0 is now in beta testing on the mobile apps. The editor will be available in version 11.9, which is planned to be released to the public on March 11.
\n“For this first version, our main focus was to build a pleasant writing experience with support for the most basic types of content,” WordPress mobile engineer Jorge Bernal said.
\n“Our data showed that 90%+ of the posts created on the mobile apps consisted of basic text and images, so we decided to focus on supporting the Paragraph, Image, and Heading blocks on this version.”
\nThe interface looks similar to using Gutenberg on desktop, but it has been pared back to allow for only the most commonly used blocks and access to simple block settings.
\n![\"Block](\"https://i2.wp.com/cldup.com/p1TdZhszqp.gif?resize=606%2C454&ssl=1\")
The block editor in the Android app feels noticeably slower on mobile than the previous editor. It’s not yet an improvement on the existing mobile editor but it’s still in beta. Even though it’s still rough around the edges, the posting interface is more consistent with what users experience on the desktop. During this transition time, users will retain the ability to use either editor, since the Gutenberg implementation just provides the basics for now.
\nAfter version 11.9 rolls out to the apps, users can choose if they want to use the block editor. The app detects which editor a post was created with and will automatically open it when a user attempts to edit a post. Users can manually switch back to the old editor for posts that have blocks by selecting “Switch to Classic Editor” under the ellipses menu. New posts will still use the Classic Editor by default but users can change the default to the block editor by going to Me > App Settings and enabling the “Use Block Editor” option.
\nAfter 11.9 is released the team plans to work on UX improvements and bug fixes before moving on to add support for the most common blocks and use cases.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Feb 2019 01:00:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: Gumroad Plugin for WordPress Adds Gutenberg Block for Embedding Products\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87606\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"https://wptavern.com/gumroad-plugin-for-wordpress-adds-gutenberg-block-for-embedding-products\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2290:\"Gumroad has updated its WordPress plugin to include a Gutenberg block for embedding a product in any page or post. The online platform enables creators, artists, educators, writers, and anyone else to sell their products without having to manage their own e-commerce setup. Gumroad’s WordPress plugin has been available for several years and is now compatible with the new Gutenberg editor.
\n\n\n\n\n— Gumroad (@gumroad) February 22, 2019
Re-introducing: Gumroad for WordPress.
• automatically includes our JS if we detect a link to a Gumroad product
• support for Gutenberg blocks
Get it now: https://t.co/DW87xf1f8K pic.twitter.com/wRHy0pI5I0
I tested the block and it works as advertised. It would be nice if the block also provided an optional button style, instead of just a plain link on the frontend.
\n\n\n\nGumroad founder and CEO Sahil Lavingia recently published a post titled “Reflecting on My Failure to Build a Billion-Dollar Company” about his journey building Gumroad. The post gained a lot of attention due to Lavingia’s honest and inspiring account of the failures and painful changes he experienced throughout the company’s history. Last year he decided to embrace transparency and began publishing the company’s monthly financials. The post also included a nod to WordPress with Gumroad’s plans to go open source.
\n\n\n\n“Soon, we’re also planning to open-source the whole product, WordPress-style,” Lavingia said. “Anyone will be able to deploy their own version of Gumroad, make the changes they want, and sell the content they want, without us being the middleman.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 26 Feb 2019 16:23:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"WPTavern: Block Management Features Proposed for WordPress 5.2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87478\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wptavern.com/block-management-features-proposed-for-wordpress-5-2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7394:\"WordPress 5.1 has been downloaded more than 3.6 million times since its release last week and work on 5.2 is now underway. The upcoming release will be led by Matt Mullenweg with Josepha Haden acting as Release Coordinator. Gary Pendergast posted a proposed scope and schedule that would have 5.2 arriving April 23, 2019.
\nOne of the proposed features is block management, the ability for users to hide or turn off blocks that they are not using. An avalanche of blocks is pouring into the WordPress ecosystem, especially with the push to convert core widgets to blocks. Users’ expectations will soon become firmly rooted in the concept of the block interface as widgets slowly become a relic of the past. It’s also quite common for users to install block collections that introduce a dozen or more new blocks when they really only have use for a handful of blocks.
\nSeveral standalone plugins already provide block management features, such as Gutenberg Manager and Disable Gutenberg Blocks. They all have different UI’s and approaches to letting users turn off blocks. For example, Gutenberg Manager uses a tabbed interface with checkboxes for disabling core blocks. The Disable Gutenberg Blocks plugin offers an admin screen that is similar to plugin management:
\nA few block collections have also implemented their own block management features, including Advanced Gutenberg Blocks and CoBlocks. Advanced Gutenberg Blocks adds a screen under its own top level menu for disabling blocks.
\nCoBlocks recently introduced a block management feature that is one of the more elegant implementations currently available. It adds the block management interface inline with the editor in a modal window, instead of relegating it to its own admin page. It also offers the ability to turn entire categories on/off.
\n\nAfter CoBlocks announced its block management feature, Nick Hamze contended that this should be replicated for WordPress core. His comments received a bit of pushback from Gutenberg technical lead Riad Benguella who sees it as a feature for more advanced users.
\n\n\n\nYeah, nice plugin. It feels like something for advanced WordPress users / developers / agencies… and not something that should be baked in initially but happy to discuss.
\n— Riad Benguella (@riadbenguella) February 15, 2019
“The ability to disable blocks seems pretty basic,” Hamze responded. “Rich didn’t make this feature for fun. Regular users (not advanced ones or developers) asked for this. He made it to solve a problem that real users are having. You are telling me that more regular users will use the Amazon Kindle Embed Block (that is being baking into 5.1) than would like the ability to turn off blocks they don’t want to use.”
\nLast week when I spoke to Benguella about the possibility of block management capabilities being included in core sometime in the future, he said it wasn’t an immediate priority for the project.
\n“Block management is not an immediate focus in the Gutenberg roadmap and is considered plugin territory, but we keep close attention to the work done in the community and adapt in case user research and suggestions that bring value for the majority of users,” Benguella said. “My personal opinion for the moment is that, these are advanced features not required by every user of WordPress.
\n“That said, it’s important to enable plugin developers to implement more block management features, and one important piece of the puzzle here is the work we’re doing right now to improve the block registration and discovery both using REST APIs, PHP helpers and JavaScript APIs.”
\nThe project’s priorities seem to have changed since that time, as block management is now a strong consideration for WordPress 5.2. Thousands of users have already installed a plugin that includes these kinds of capabilities, a good indication that there is a demand for this. As everything in the plugin ecosystem gradually moves towards blocks, it will be easy for users to get inundated by the many blocks available in the editor. Plugins are currently answering users’ needs with many different UI’s for turning blocks on/off. It’s clear that WordPress core needs to lead the way by providing a standard UI for block management.
\nIn recent #core-editor chats Benguella said he has some concerns regarding the short time frame for the newly proposed block management feature, but is starting initial explorations of what the first iteration may look like in WordPress 5.2.
\n“So in addition to the currently shipped enhancements and the work done on the widget blocks, there has been a bunch of requests and feedback suggesting the need for a block management solution and block directory work,” Benguella said. “This is actually proposed for 5.2 and something we need to start thinking about and exploring the existing possibilities.”
\nPendergast referenced CoBlocks’ implementation in his 5.2 scope and schedule post as an example of how plugin developers have approached block management.
\n“We weren’t the first by far, but I’d argue it’s clearly the best experience,” CoBlocks author Rich Tabor said. “I built it because folks have been asking for just that, and I wanted to deliver a much better experience than asking them to go to a WP admin page elsewhere. I’d love to see something like the Block Manager in core and am available to help out in any way I can.”
\nOther proposed features for WordPress 5.2 include the Site Health Check plugin, PHP error protection, and package signing for updates. The first beta is expected March 14, 2019, and RC 1 is slated for April 10, 2019.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 25 Feb 2019 17:22:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:113:\"WPTavern: Ecwid E-Commerce Plugin Adds Gutenberg Support, Focuses on Small Businesses to Compete with WooCommerce\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87223\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:123:\"https://wptavern.com/ecwid-e-commerce-plugin-adds-gutenberg-support-focuses-on-small-businesses-to-compete-with-woocommerce\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5542:\"Ecwid’s e-commerce plugin for WordPress is now fully integrated with the Gutenberg editor. The cloud-based store builder, pronounced “eck-wid,” is short for e-commerce widgets, but the service has fully embraced blocks in its latest releases.
\nThe new default Storefront block comes pre-installed and embeds the entire Ecwid store on a page, including product listing, filters, navigation, and checkout. It provides a quick way for a new seller to get everything working without having to do anything besides add the plugin. Inside the block sidebar, the seller can tweak the storefront’s appearance, including thumbnails, page layout, colors, and other settings. The short screencast below shows the block in action and part of it was featured during Matt Mullenweg’s State of the Word address in December 2018.
\n\nEcwid also has a new Single Product block with a buy now button. It enables sellers to select a product and display it as a card with an image, title, and buy now button. This is convenient for using inside a blog post without having to open the whole storefront.
\nThe team behind Ecwid is working on adding more Gutenberg blocks, despite having only a small fraction of their customers using WordPress. The company has more than 1.5 million customers running stores in 175 countries, but only 1.3% (20,000) are using WordPress. Even with so few active installations of the company’s WordPress plugin, Ecwid has its sights set on competing with WooCommerce, the most dominant player in this spacee. Last year at WordCamp Moscow, Ecwid Product Manager Matvey Kuritsyn gave a presentation titled “Why does anyone need a WooCommerce alternative?” Much of the company’s strategy is outlined in the slides from that presentation.
\n“We are focusing on small businesses and resolving their problems — where WooCommerce is weak,” Ecwid Marketing Manager Kseniya Pinkova said. She identified a few ways that Ecwid is working to differentiate itself from competitors:
\nThis level of security, support, and maintenance is only available for WooCommerce via a managed solution like WordPress.com or Liquid Web, but sellers may still struggle with setup and customization due to the vast number of options and integrations available. Ecwid is focusing on its strengths as a SaaS-only solution to target small businesses in the WordPress space, instead of trying to replicate all the features that the dominant plugins already have.
\nThe company started in 2009 and has a distributed team of 160 people who work in development, IT, operations, support, content, and business development.
\n“The WordPress plugin is technically a separate application (because Ecwid is a cloud solution, SaaS), and it appeared in 2009 as well,” Pinkova said. “But everything is interconnected — when a new featured is released in Ecwid, WordPress plugin users see it appear in their stores as well and can use it even without updating their WordPress plugin. For example, we rolled out new in-house Product Filters last week and they are now available for all Ecwid users, including those using WordPress. Some other features touch the WordPress plugin code — for example, some SEO enhancements involve both robust cloud part (API) and changes on the plugin side. The Gutenberg block is a good example of a third kind of Ecwid feature — it mostly resides in the plugin and it’s great to see how it improves the experience of our WordPress user base segment specifically.”
\nEcwid’s roadmap for 2019 includes tighter integration with Facebook and Instagram, an in-house multilingual catalog, and marketing features to help small businesses find their customers. Because the WordPress plugin essentially hooks up the cloud-based solution, many of the features and improvements on Ecwid’s general roadmap for all platforms will be automatically available whenever they roll out.
\n“Regarding our WordPress plugin, the main thing for us is Gutenberg,” Pinkova said. “We’re very excited about it, we’re looking forward to new features Gutenberg is going to provide, and working on our plugin to make sure we’re making those available and easy-to-use for Ecwid sellers.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 22 Feb 2019 19:57:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"WPTavern: WordPress 5.1 Improves Editor Performance, Encourages Users to Update Outdated PHP Versions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87494\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:111:\"https://wptavern.com/wordpress-5-1-improves-editor-performance-encourages-users-to-update-outdated-php-versions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2420:\"![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/02/betty-carter.jpg?ssl=1\")
WordPress 5.1 “Betty” was released today, honoring American jazz singer Betty Carter. This is the first major release since Gutenberg came into core. As part of WordPress’ 2019 “tighten up” theme, this release was focused on improving performance in the editor and helping users update outdated versions of PHP.
\nWordPress 5.0 had been downloaded more than 35 million times prior to 5.1’s release. Users who have adopted the block editor will notice that it is much more responsive and writing posts should feel smoother. WordPress 5.1 includes the performance improvements from Gutenberg 4.8 – faster page initialization time, improved typing performance, and optimization of various background processes.
\nThis release introduces new features from the Site Health project. WordPress will now detect if a site is running on an insecure, outdated version of PHP and display a notice in the dashboard with information about how to update PHP. It also includes checks for PHP version compatibility with plugins. WordPress 5.1+ will prevent users from installing plugins that require newer versions of PHP than they have running.
\nThis release also introduces a medley of miscellaneous improvements under the hood for developers, including (but not limited to) the following:
\nWordPress 5.1 was led by Matt Mullenweg with help from Gary Pendergast and 561 contributors. Approximately 41% (231 people) were new contributors to the project.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 22 Feb 2019 00:29:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"WordPress.org blog: WordPress 5.1 “Betty”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6589\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://wordpress.org/news/2019/02/betty/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:43199:\"\n\n\n\n\n\n\n\nVersion 5.1 of WordPress, named “Betty” in honour of acclaimed jazz vocalist Betty Carter, is available for download or update in your WordPress dashboard.
\n\n\n\nFollowing WordPress 5.0 — a major release which introduced the new block editor — 5.1 focuses on polish, in particular by improving the overall performance of the editor. In addition, this release paves the way for a better, faster, and more secure WordPress with some essential tools for site administrators and developers.
\n\n\n\n\n\n\n\nWith security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.
\n\n\n\nWhen you install new plugins, WordPress’s Site Health features will check them against the version of PHP you’re running. If the plugin requires a version that won’t work with your site, WordPress will keep you from installing that plugin.
\n\n\n\n\n\n\n\nIntroduced in WordPress 5.0, the new block editor continues to improve. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother.
\n\n\n\nExpect more performance improvements in the next couple of releases.
\n\n\n\n\n\n\n\n5.1 introduces a new database table to store metadata associated with sites and allows for the storage of arbitrary site data relevant in a multisite / network context.
\n\n\n\nThe Cron API has been updated with new functions to assist with returning data and includes new filters for modifying cron storage. Other changes in behavior affect cron spawning on servers running FastCGI and PHP-FPM versions 7.0.16 and above.
\n\n\n\nWordPress 5.1 features a new JavaScript build option, following the large reorganisation of code that started in the 5.0 release.
\n\n\n\nMiscellaneous improvements include:
\n\n\n\n![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/03/github-commit-organization.png?ssl=1\")
![](\"https://i0.wp.com/wptavern.com/wp-content/uploads/2019/03/Screen-Shot-2019-03-14-at-9.23.29-PM.png?ssl=1\")
![](\"https://i2.wp.com/wptavern.com/wp-content/uploads/2019/03/dark-mode.png?ssl=1\")
![](\"https://i0.wp.com/wptavern.com/wp-content/uploads/2019/03/Screen-Shot-2019-03-12-at-6.13.26-PM.png?ssl=1\")
![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/03/wordcamp-nordic-kids-camp.jpg?ssl=1\")
![](\"https://i0.wp.com/wptavern.com/wp-content/uploads/2019/03/inserter-with-search-results-from-block-dir.jpg?ssl=1\")
![](\"https://i0.wp.com/wptavern.com/wp-content/uploads/2019/03/WordPress-Translation-Day4.jpeg?ssl=1\"){kind=spacer}
![](\"https://i0.wp.com/wptavern.com/wp-content/uploads/2019/03/Screen-Shot-2019-03-01-at-3.17.50-PM.png?ssl=1\")
![](\"https://i2.wp.com/wptavern.com/wp-content/uploads/2019/02/navigation-menu-prototype.png?ssl=1\")
![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/02/navigation-menu-block-advanced.png?ssl=1\")
![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/02/navigation-block-add-new-item.png?ssl=1\")
![](\"https://i2.wp.com/wptavern.com/wp-content/uploads/2019/02/disable-gutenberg-blocks.jpg?ssl=1\")
![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/02/advanced-gutenberg-blocks-disable-blocks.jpg?ssl=1\")
WP_DEBUG_LOG constantwp_unique_post_slug(), WP_User_Query, and count_users()human_readable_duration functionLIKE support for meta keys when using WP_Meta_Query…and more!
\n\n\n\nThis release was led by Matt Mullenweg, along with Gary Pendergast as Senior Code Reshuffler and Poet. They received wonderful assistance from the following 561 contributors for this release, 231 of whom were making their first ever contribution! Pull up some Betty Carter on your music service of choice, and check out some of their profiles:
\n\n\n0x6f0, 1265578519, 1naveengiri, 360zen, aardrian, Aaron Jorbin, Abdullah Ramzan, Abhay Vishwakarma, Abhijit Rakas, Achal Jain, achbed, Adam Silverstein, Ajit Bohra, Alain Schlesser, aldavigdis, alejandroxlopez, Alex, Alex Concha, Alex Shiels, Alexander Botteram, Alexandru Vornicescu, alexgso, allancole, Allen Snook, Alvaro Gois dos Santos, Ana Cirujano, Anantajit JG, Andrea Fercia, Andrea Gandino, Andrea Middleton, andrei0x309, andreiglingeanu, Andrew Duthie, Andrew Lima, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrey Savchenko, Andrés Maneiro, Andy Fragen, Andy Meerwaldt, Angelika Reisiger, Antal Tettinger, antipole, Anton Timmermans, Anton Vanyukov, Antonio Villegas, antonioeatgoat, Anwer AR, Arun, Ashar Irfan, ashokrd2013, Ayesh Karunaratne, Ayub Adiputra, Barry Ceelen, Behzod Saidov, Ben Byrne, benhuberman, Benoit Chantre, benvaassen, Bhargav Mehta, bikecrazyy, Birgir Erlendsson, BjornW, Blair jersyer, Blobfolio, bobbingwide, boblinthorst, Boone Gorges, Boro Sitnikovski, Brad Parbs, Bradley Taylor, bramheijmink, Brandon Kraft, Brandon Payton, Brent Swisher, Brian Richards, bridgetwillard, Brooke., bruceallen, bulletdigital, Burhan Nasir, Bytes.co, Caleb Burks, Calin Don, campusboy, carolinegeven, ccismaru, chasewg, Chetan Prajapati, Chouby, ChriCo, chriscct7, Christopher Spires, claudiu, Clifford Paulick, Code Clinic, codegrau, coleh, conner_bw, Corey McKrill, croce, Csaba (LittleBigThings), Cyrus Collier, Daniel Bachhuber, Daniel James, Daniel Koskinen, Daniel Richards, Daniele Scasciafratte, danimalbrown, Danny Cooper, Danny de Haan, Darko A7, Darren Ethier, Dave Pullig, David A. Kennedy, David Anderson, David Binovec, David Cramer, David Herrera, David Lingren, David Shanske, David Stone, dekervit, Denis Yanchevskiy, Dennis Snell, designsimply, dfangstrom, Dhanendran, Dharmesh Patel, Dhaval kasavala, Dhruvin, DiedeExterkate, Dilip Bheda, dingo-d, Dion Hulse, dipeshkakadiya, Dominik Schilling, Donncha O Caoimh, dontstealmyfish, Drew Jaynes, Drivingralle, dschalk, dsifford, eamax, eArtboard, edo888, ElectricFeet, Ella Van Durpe, Emil Dotsev, Eric Andrew Lewis, Eric Daams, Erich Munz, Erick Hitter, ericmeyer, etoledom, Evan Solomon, Evangelos Athanasiadis, Faisal Alvi, Felipe Elia, Felix Arntz, Fernando Claussen, flipkeijzer, Florian TIAR, FPCSJames, Frank Klein, fuchsws, fullyint, Gabriel Maldonado, Gareth, Garrett Hyder, Gary Jones, Gennady Kovshenin, Gerhard Potgieter, Girish Panchal, GM_Alex, gnif, graymouser, greg, Grzegorz Ziółkowski, Guido, GutenDev, Hafiz Rahman, Hai@LiteSpeed, Hans-Christiaan Braun, Hardeep Asrani, Hardik Amipara, Harsh Patel, haruharuharuby, Heather Burns, Helen Hou-Sandi, Henry Wright, Herre Groen, Hitendra Chopda, Ian Belanger, Ian Dunn, ibantxillo, Ignacio Cruz Moreno, Igor, Igor Benic, imath, ionvv, Irene Strikkers, isabel104, ishitaka, Ivan Mudrik, J.D. Grimes, Jack Reichert, Jacob Peattie, Jake Spurlock, James Nylen, janak Kaneriya, janalwin, Janki Moradiya, janthiel, Jason Caldwell, javorszky, Jaydip Rami, Jayman Pandya, Jb Audras, Jeff Farthing, Jeffrey de Wit, Jeffrey Paul, Jennifer M. Dodd, Jenny, Jeremey, Jeremy Felt, Jeremy Herve, Jeremy Pry, Jeremy Scott, Jesper V Nielsen, Jesse Friedman, Jimmy Comack, Jip Moors, Jiri Hon, JJJ, joanrho, Job, Joe Bailey-Roberts, Joe Dolson, Joe Hoyle, Joe McGill, Joel James , Joen Asmussen, Johan Falk, John Blackbourn, John Godley, johnalarcon, johnpgreen, johnschulz, Jonathan Champ, Jonathan Desrosiers, joneiseman, Jonny Harris, Joost de Valk, Jorge Costa, Joseph Scott, JoshuaWold, Joy, jpurdy647, jrdelarosa, jryancard, Juhi Patel, Julia Amosova, juliemoynat, Juliette Reinders Folmer, Junaid Ahmed, Justin Sainton, Justin Sternberg, Justin Tadlock, K.Adam White, kapteinbluf, keesiemeijer, Kelly Dwan, kelvink, khaihong, Kiran Potphode, Kite, Kjell Reigstad, kkarpieszuk, kmeze, Knut Sparhell, konainm, Konstantin Obenland, Konstantinos Xenos, kristastevens, krutidugade, laghee, Laken Hafner, Lance Willett, laurelfulford, lbenicio, Leander Iversen, leemon, lenasterg, lisannekluitmans, lizkarkoski, Luca Grandicelli, LucasRolff, luciano-croce, Luke Carbis, Luminus, Mário Valney, maartenleenders, macbookandrew, Maja Benke, Mako, mallorydxw-old, Manuel Augustin, manuel_84, Marc Nilius, marcelo2605, Marco Martins, marco.marsala, Marcus Kazmierczak, marcwieland95, Marius L. J., mariusvw, Mariyan Belchev, Mark Jaquith, Mathieu Sarrasin, mathieuhays, Matt Cromwell, Matt Gibbs, Matt Martz, Matthew Boynes, Matthew Riley MacPherson, mattyrob, mcmwebsol, Mel Choyce, mensmaximus, mermel, metalandcoffee, Micah Wood, Michael Nelson, Michiel Heijmans, Migrated to @sebastienserre, Miguel Fonseca, Miguel Torres, mihaiiceyro, mihdan, Mike Gillihan, Mike Jolley, Mike Schroder, Milan Dinić, Milan Ivanovic, Milana Cap, Milind More, mirkoschubert, Monika Rao, Monique Dubbelman, moto hachi ( mt8.biz ), mrmadhat, Muhammad Kashif, Mukesh Panchal, MultiformeIngegno, Muntasir Mahmud, munyagu, MyThemeShop, mzorz, nadim0988, nandorsky, Naoki Ohashi, Naoko Takano, nataliashitova, Nate Allen, Nathan Johnson, ndavison, Ned Zimmerman, Nextendweb, Nick Diego, Nick Halsey, Nick Momrik, Nick the Geek, Nicolas Figueira, Nicolas GUILLAUME, Nicolle Helgers, Nidhi Jain, Niels Lange, Nikhil Chavan, Nilambar Sharma, Noam Eppel, notnownikki, odyssey, Omar Reiss, Omkar Bhagat, Ov3rfly, Paal Joachim Romdahl, palmiak, panchen, parbaugh, Parham Ghaffarian, Pascal Birchler, Pascal Casier, Paul Bearne, Paul Biron, Paul Paradise, Paul Schreiber, Perdaan, Peter Putzer, Peter Wilson, Petter Walbø Johnsgård, Pierre Saïkali, Pieter Daalder, Piyush Patel, poena, Pramod Jodhani, Prashant Baldha, Pratik K. Yadav, Pratik K. Yadav, precies, Presskopp, Presslabs, PressTigers, programmin, Punit Patel, Purnendu Dash, Qucheng, Rachel Baker, Rachel Cherry, Rachel Peter, Rafsun Chowdhury, Rahul Prajapati, Raja Mohammed, Ramanan, Rami Yushuvaev, Ramiz Manked, ramonopoly, RavanH, redcastor, remyvv, rensw90, rhetorical, Riad Benguella, Rian Rietveld, Richard Tape, Ricky Lee Whittemore, Rinku Y, Rishi Shah, Robbie, robdxw, Robert Anderson, Robin Cornett, Robin van der Vliet, Ryan McCue, Ryan Paul, Ryan Welcher, ryotsun, Sébastien SERRE, Saša, sagarnasit, Sami Ahmed Siddiqui, Sami Keijonen, Samuel Wood (Otto), sarah semark, Sayed Taqui, Scott Lee, Scott Reilly, Sean Hayes, Sebastian Kurzynoswki, Sebastian Pisula, Sergey Biryukov, Shamim Hasan, Shane Eckert, Sharaz Shahid, Shashwat Mittal, Shawn Hooper, sherwood, Shital Marakana, Shiva Poudel, Simon Prosser, Sjardo, skoldin, slilley, slushman, Sonja Leix, sonjanyc, Soren Wrede, spartank, spyderbytes, Stanimir Stoyanov, Stanko Metodiev, stazdotio, Stephen Edgar, Stephen Harris, stevenlinx, Storm Rockwell, Stoyan Kostadinov, strategio, Subrata Sarkar, Sultan Nasir Uddin, swift, Takahashi Fumiki, Takayuki Miyauchi, Tammie Lister, Taylor Lovett, teddytime, Terri Ann, terwdan, tharsheblows, ThemeZee, Thomas Patrick Levy, Thomas Vitale, thomaswm, Thorsten Frommen, Thrijith Thankachan, Tiago Hillebrandt, tigertech, Tim Havinga, Tim Hengeveld, Timmy Crawford, Timothy Jacobs, titodevera, Tkama, Tobias Zimpel, Tom J Nowell, TomHarrigan, Tommy Ferry, tonybogdanov, Tor-Bjorn Fjellner, TorontoDigits, Toshihiro Kanai, Towhidul Islam, transl8or, Ulrich, upadalavipul, Usman Khalid, Utsav tilava, uttam007, Vaishali Panchal, Valérie Galassi, valchovski, vishaldodiya, vnsavage, voneff, vortfu, warmlaundry, wbrubaker, Weston Ruter, Will Kwon, William Earnhardt, williampatton, wpzinc, xhezairi, Yahil Madakiya, Yoav Farhi, Yui, YuriV, Zane Matthew, and zebulan.\n\n\n\nFinally, thanks to all the community translators who worked on WordPress 5.1. Their efforts bring WordPress 5.1 fully translated to 34 languages at release time, with more on the way.
\n\n\n\nIf you want to follow along or help out, check out Make WordPress and our core development blog.
\n\n\n\nThanks for choosing WordPress!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Feb 2019 22:48:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:34;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WPTavern: WPWeekly Episode 346 – Cancer Sucks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=87497&preview=true&preview_id=87497\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://wptavern.com/wpweekly-episode-346-cancer-sucks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1211:\"In this episode, John James Jacoby and I reflect on Alex Mill’s latest blog post where he announced that he’s ending his battle with Leukemia. We highlight some of the impacts he’s had on people’s lives and the contributions he’s made to open-source software.
\nNext Episode: Wednesday, February 27th 3:00 P.M. Eastern
\nSubscribe to WordPress Weekly via Itunes
\nSubscribe to WordPress Weekly via RSS
\nSubscribe to WordPress Weekly via Stitcher Radio
\nSubscribe to WordPress Weekly via Google Play
\nListen To Episode #346:
\n
Gutenberg development continues ploughing ahead with new blocks and steady improvements to performance and accessibility. Version 5.1 was released this week with new Search, Calendar, and Tag Cloud blocks. All widgets have now been ported over to blocks, a major Phase 2 milestone. The next phase of that project will explore how the widgets screen will change in response to core widgets becoming blocks.
\nVersion 5.1 also brings more polishes to existing blocks, introducing micro-animations for a smoother experience when hovering over menus or accessing the sidebar in the editor.
\n![\"New](\"https://i2.wp.com/cldup.com/XkGFmONOUH.gif?resize=627%2C408&ssl=1\")
This release includes dozens of small stylistic improvements to blocks for a more consistent display, improvements to CSS specificity of styles, more options for the Quote block styling, improvements to using the editor on mobile devices, and lots of bug fixes. Documentation is also progressing with a new tutorial for working with editor notices, expanded JavaScript build tools documentation, and enhanced block edit/save documentation and code examples.
\nGutenberg phase 2 technical lead Riad Benguella also included a table of benchmarks, showing the editor’s performance improvements since it was first released in WordPress 5.0. Each release of the plugin since then has significantly cut the loading time, and this is a noteworthy improvement to continue tracking.
\nThese benchmarks compare performance for a post with approximately 36,000 words and 1,000 blocks. This isn’t an average post but large amounts of content help to reveal performance issues.
\nGutenberg 5.1 had 51 contributors. For more details, check out the full list of enhancements and fixes in the release post.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Feb 2019 20:12:57 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"WPTavern: The State of CSS 2019 Survey is Now Open\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87339\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://wptavern.com/the-state-of-css-2019-survey-is-now-open\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2663:\"The makers of the annual State of JavaScript survey have launched a new survey for developers who work with CSS. In September 2018, Sacha Greif and his collaborators sent out the State of JS survey for the third year running but dropped the CSS libraries category in favor of keeping it from getting too long. The new State of CSS survey takes up this category and expands upon it.
\nThe success of the State of JS survey has brought valuable information to the industry for developers, employers, startups, project maintainers, and even those who are just beginning their coding journey and wondering which frameworks are worth learning. The 2018 State of JS survey received more than 20,000 responses. Results showed that React was once again the most popular front-end framework and Vue.js received the highest satisfaction rating. The detailed results are influential in helping framework maintainers know how the development community perceives their projects.
\n\n\n\nI think Vue got the highest satisfaction rating among frameworks in State of JS this year (91.2%) – thanks to our users, and we aim to do even better! Hope we can change the mind of the 568 people who don’t want to use it again ;) https://t.co/7MrM8Y4ekq
\n— Evan You (@youyuxi) November 19, 2018
The new survey for CSS developers was created to help identify the latest trends in the rapidly changing CSS landscape. It includes the following topics:
\nThe State of CSS Survey is powered by Typeform and all questions are optional. It is quick to scroll through and can take as little as 10 minutes to complete. Participants can leave their email to be notified when results are published.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Feb 2019 04:35:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"WPTavern: New Wapuu Dashboard Pet Plugin Displays WordPress Site Health\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87379\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/new-wapuu-dashboard-pet-plugin-displays-wordpress-site-health\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3333:\"Wapuu Dashboard Pet is a new plugin from Kayleigh Thorpe and the team at WordPress hosting company 34SP.com. It is essentially a WordPress Tamagotchi, or digital pet, that resides in your dashboard and monitors the health of the site.
\nThe plugin checks to make sure WordPress has been updated (plugins, themes, and core) and backups have run. Wapuu’s appearance will change based on these factors. Thorpe used her illustration skills to create the images, which indicate if wapuu is feeling dead, happy, sad, sick, or very sick. The threshold for a dead wapuu is 10+ updates. The example below is a “very sick” wapuu on a site with five or more updates pending.
\nAfter updating, the happy and healthy wapuu is displayed, as shown below.
\nThe Wapuu Dashboard Pet is featured at the bottom of every page in the admin. It also comes with an option to enable weekly email notifications that will only send if wapuu is feeling sick (has one or more updates available). This feature can help site administrators who don’t log into their dashboards very often, resulting in more updated and secure WordPress sites.
\nThe plugin is currently very effective in its simplicity but there are a lot of interesting features that its authors could add. It could be set up to check for PHP and MySQL versions, similar to what the Health Check plugin offers. It would also be useful if wapuu could detect whether or not any of the necessary updates are security-related, which might inspire administrators to act faster on the emails. There may be other useful applications for forks of this plugin, such as a wapuu that helps bloggers stay on track with their monthly posting goals.
\nWhen wapuu is feeling unwell, the image displayed is a pathetic-looking creature that appears to have been left out in the rain. Wapuu-conscious site admins will not be able to look at that image in the dashboard without feeling the need to improve wapuu’s condition. These visual indicators of site health may be just the type of prompt necessary for admins who have become desensitized to WordPress’ many update notifications.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Feb 2019 19:33:57 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"BuddyPress: BuddyPress 4.2.0 Maintenance and Security Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=302991\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://buddypress.org/2019/02/buddypress-4-2-0-maintenance-and-security-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1196:\"BuddyPress 4.2.0 is now available. This is a security and maintenance release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.
\n\n\n\nThe 4.2.0 release addresses two security issues:
\n\n\n\nThese vulnerabilities were reported privately to the BuddyPress team, in accordance with WordPress’s security policies. Our thanks to the reporters for practicing coordinated disclosure.
\n\n\n\nBuddyPress 4.2.0 also fixes 4 bugs. For complete details, visit the 4.2.0 changelog.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Feb 2019 16:00:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Boone Gorges\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"WPTavern: Yoast CEO Responds to #YoastCon Twitter Controversy, Calls for Change in the SEO Industry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87389\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/yoast-ceo-responds-to-yoastcon-twitter-controversy-calls-for-change-in-the-seo-industry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7233:\"Yoast CEO Marieke van de Rakt published a post yesterday, addressing the controversy that dominated the #YoastCon hashtag on Twitter in the days leading up the the event. Several parties from the SEO industry began circulating old tweets, along unsavory videos depicting Joost de Valk partying with promotional models. de Valk issued a public apology on Twitter before YoastCon officially kicked off.
\n\n\n\nI think and act differently now, though I know that doesn\'t change the past. If anyone felt harmed by this: I\'m truly sorry.
\n— Joost de Valk (@jdevalk) February 6, 2019
In her post, titled “Let’s create a more female-friendly world!”, van de Rakt characterized the incident as an attack and cited examples of how Yoast is actively working to improve the position of women:
\n\nWe were all hurt. We really don’t understand why the company Yoast is being attacked, why the #yoastcon is being used for something the person Joost did 10 years ago. Our company and our company culture is nothing like the tweets imply.
van de Rakt also referenced a post from Gisele Navarro, a woman who has been working in the SEO industry for 10 years.
\n“I totally agree with Gisele that the SEO industry was not welcoming to women ten years ago,” van de Rakt said. “And although some things may have changed, I still think that the SEO industry has a long way to go. I also think that the problem is much bigger than the SEO industry.”
\nAfter the tweets and videos began circulating on the #YoastCon hashtag, the @yoast Twitter account was quietly scrubbed of potentially offensive tweets. The total tweet count for the account was 44.1K on January 31, 2019.
\nOn February 8, 2019, the account’s total tweets were slashed to 10.7K. Approximately 33,000 tweets have been deleted in the wake of this controversy.
\nSome of the tweets were still available via the Internet Archive Wayback Machine during the height of the controversy and screenshots were shared widely.
\n\n\n\nNo seriously, fucking don’t try and excuse behaviour like this. (9/41) pic.twitter.com/DoK1zOl3p2
\n— Tom Rayner (@tjprayner) February 7, 2019
One recipient of the tweets, Lisa Barone, dismissed them as “friends being stupid,” but de Valk’s wife, Marieke van de Rakt, admitted in her recent post that the tweets and videos were hurtful to her. Since the tweets were public, many onlookers said they felt uncomfortable reading these types of interactions within a professional context.
\nNavarro’s post described how the tweets made her feel as an outside onlooker working in the male-dominated SEO industry:
\n\nI don’t know the story behind the ‘friendly and consensual sexual banter’ (as someone called it) of those tweets so I’ve got zero context on how the conversations led to Joost saying things like:
\n‘I bet you’d look good, even when pregnant ;-)’
\n‘Ahem, why are you not naked indeed?’
\n‘Nothing beats a yummy young mummy :)’
\nWhen I read those tweets, that was all I could think of – Decades of obscenities been pushed on me by men who thought that was normal, acceptable behavior.
\nI thought about how much it would have crushed me back then if someone I respected were to have said something like that to me. I wondered if I would still be part of the SEO community had that happened.
\nI imagined how would I have felt if before or after that tweet, I were to have been an attendee at SEOktoberfest surrounded by Playboy escorts who touched themselves looking at the camera while I was having a beer in a corner, trying to network my way to a job interview at an agency I loved.
After the tweets and videos began to get attention on the #YoastCon hashtag, many in the SEO industry dismissed the content as an attack orchestrated by trolls who they alleged are also guilty of harassment. Several spoke out against David Cohen in particular, who had originally started the controversy by unearthing the old content, describing him as the person behind other troll accounts known for sending harassing tweets.
\nRegardless of how the old content came to light on Twitter, both Joost de Valk and Yoast CEO Marieke van de Rakt have admitted that the tweets and videos are indefensible and not representative of their company’s current push to empower women.
\nNavarro’s post calls readers to look at the tweets and videos from the perspective of someone working in the SEO industry, wondering if they should attend conferences after seeing leaders and role models behaving this way:
\n\nTo those of you who are defending the SEO personality that is Joost: remove the so-called SEO trolls and #YoastCon from the picture, go through the tweets and ask yourself how would YOU feel if someone you look up to says those things to you on a public forum. Would you feel comfortable attending a conference knowing this person would be there? Would you want him to be your boss? Would you feel safe around this person? Would you have anybody to talk to about what happened and how you felt? Would you even bring it up?
The #YoastCon Twitter controversy has had the positive effect of highlighting behavior and public communication styles that need to be addressed in order to create a more welcoming and diverse SEO industry. In spite of the recent challenges, van de Rakt said she is hopeful that her company can continue working towards creating “an atmosphere at conferences that is friendly for all people, regardless of their gender.” On this Navarro and van de Rakt both agree – the conditions for women working in the SEO industry are ripe for improvement.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Feb 2019 05:22:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"WPTavern: Alex Mills Ends His Battle With Leukemia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87400\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://wptavern.com/alex-mills-ends-his-battle-with-leukemia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5232:\"Today, we are reminded that life is fleeting and that plugins, themes, and WordPress itself is built and maintained by humans. Alex (Viper007Bond) Mills announced that he is ending his fight with Leukemia.
\n\n\n\n\n\n\n\nDue to liver inflammation and GvHD, the liver is too damaged to continue with treatment and there are no further options. I don’t want to spend the rest of my time in the hospital so I am choosing to remain at home where I can be comfortable with family and friends.
Alex Mills
Mills is encouraging members of the WordPress community to fork and maintain his open-source plugins. Mills thanked his co-workers, members of the WordPress community, and his car friends for enriching his life. It’s a somber read knowing it’s coming from a person who is still alive but knows that their time is near.
\n\n\n\n\n\n\n\nI want to thank everyone who has given me moral support through these difficult times. It has meant a lot hearing all of the love and support pour in from my friends and colleagues from around the world. I have been so grateful for all of the opportunities that have been given to me in my life, professionally and personally.
Automatticians have really helped me grow professionally by giving me an amazing career for the past nine years. My car friends have helped me grow socially and provided me so many good memories and life experiences. The people that I have gotten to know in the WordPress community have been very supportive as well. I am amazed by how many friends I have made and how much they have been there for me. They all have enriched my life and helped me grow as a person.
Alex Mills
Mills is the author of the Regenerate Thumbnails plugin, has been a long-standing member of the WordPress community, and is the founder of FinalGear, a forum community fan site devoted to Top Gear. The community may have played a role in bringing the show to the US.
\n\n\n\nMembers of the FinalGear community are weighing in on the news.
\n\n\n\n\n\n\n\nFinalGear has been a big part of my life for just over 13 years now, that’s damn near half of my life. It’s an incredible community that we’ve built up over the years, spawned from Viper’s work.
I’m really thankful that I stumbled across the community all that time ago and was able to get to know him, even having the pleasure of spending a weekend with him at the Ringmeet in 2015. Thanks to him, petrolheads who would otherwise probably never have met are regularly traveling the world together and he’ll always be there.
Fuck. Cancer.
Matt2000
\n\n\n\nA huge number of us owe Alex a massive ‘thank you’ for the FG Community. I speak from the heart when I say I have made lifelong friends from across the globe and enjoyed trips and experiences that I couldn’t have dreamed of 10 years ago. None of that would have happened had I not been searching for an obscure piece of music from a TG episode and stumbled into this place.
MWF
Some of you may remember the Viper’s Video Quicktags plugin created more than 10 years ago. It was essentially the precursor to native oEmbed support that arrived in WordPress in 2016.
\n\n\n\nIf you have benefited from Mill’s code, work, or have been positively impacted by him in any way, please let him know by commenting on this blog post. Mills is in a unique position to see, read, and hear how much of an impact he’s had on so many people throughout his life and we’re in a unique position to tell him.
\n\n\n\nAlex, thank you for your contributions to open-source, for being an early member of the WPTavern forum, and a supporter of the site. Throughout all of these years, I pronounced your nickname as Viperbond007 instead of Viper007Bond. It rolled off the tongue easier heh. I wish I could have gotten a ride in that sweet Viper you picked up a few years ago. Getting that Viper is something that I know was a lifelong dream of yours.
\n\n\n\nPlease enjoy the time you have left with as little pain as possible and I’ll meet you on the other side. Please leave the light on for me.
Bootstrap has released versions 4.3.1 and 3.4.1 to patch an XSS vulnerability (CVE-2019-8331) that was reported to the Bootstrap Drupal project by a developer and then responsibly disclosed to the Bootstrap development team. The vulnerability specifically affects usage of the tooltip and popover features:
\n\nEarlier this week a developer reported an XSS issue similar to the data-target vulnerability that was fixed in v4.1.2 and v3.4.0: the data-template attribute for our tooltip and popover plugins lacked proper XSS sanitization of the HTML that can be passed into the attribute’s value.
The fix includes a new JavaScript sanitizer that allows only whitelisted HTML elements in the data attribute. Developers can modify Bootstrap’s sanitization implementation or customize their own function. In addition to patching the vulnerability, Bootstrap has published new sanitizer documentation for versions 4.3 and 3.4.
\nAccording to data from BuiltWith, Bootstrap is used by approximately 16% of the internet. It is also used widely in WordPress plugins and themes. There are hundreds of listings in the WordPress.org Plugin Directory that implement Bootstrap in one way or another. Many of them have not been updated for months or even longer than a year. It’s tough to say which ones may be affected by this vulnerability, as it depends on how the plugin author has implemented Bootstrap and, in some cases, what the users have decided to output to the frontend. If you have a plugin or theme that uses Bootstrap, it may be worth getting in touch with the author to see if a security update will be necessary.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 19 Feb 2019 19:54:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"WordPress.org blog: WordPress 5.1 RC2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6585\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/2019/02/wordpress-5-1-rc2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3060:\"The second release candidate for WordPress 5.1 is now available!
\n\n\n\nWordPress 5.1 will be released on Thursday, February 21, but we need your help to get there—if you haven’t tried 5.1 yet, now is the time!
\n\n\n\nThere are two ways to test the WordPress 5.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).
\n\n\n\nFor details about what to expect in WordPress 5.1, please see the first release candidate post.
\n\n\n\nThis release includes the final About page design. It also contains fixes for:
\n\n\n\nPlease test your plugins and themes against WordPress 5.1 and update the Tested up to version in the readme to 5.1. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.
\n\n\n\nThe WordPress 5.1 Field Guide has also been published, which goes into the details of the major changes.
\n\n\n\n\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages!
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nWordPress Five Point One:
It’s so slick, shiny, and new.
Lands in a few days!
Topher may be best known for HeroPress, which has published autobiographical essays from members of the WordPress community every month since March 2015. He took some time to reflect on HeroPress and recount his own path to WordPress, the long and winding road of freelancing, and his role as a developer evangelist for BigCommerce.
\nDK: How did you first got into programming, the web, and WordPress?
\nTD: Getting into programming is a long slow story. Someone mentioned the other day how they learned HTML through View Source, and I did that as well, but then it occurred to me that I learned how to do that through WordPerfect’s “View Codes.” Same idea, different platform.
\nThe college that I went to had a VAX/VMS computer network for the whole campus. Dumb terminals with either green or orange letters hooked up to a computer that was probably five feet tall, eight feet long, and about four feet wide. It could do email so that we could send an Electronic Message all the way across campus! It was incredible. Then I was told we were going to be connected to The Internet. I remember where I was standing, and who I was talking to when I said the words “What’s the Internet?”
\nA year later we got a World Wide Web client installed, called Lynx. It took me a while to figure out why it was better than Gopher, but then I loved it. One day a friend said, “Hey, look what I made!” and he had made his own web page. I was floored. He said, “You should do it too!” I said “No, I could never figure that out” to which he responded, “Sure, let me show you.” That right there summarizes how I’ve tried to treat new people in my profession.
\nHe showed me how HTML worked, and I learned every single HTML tag in about an hour. There were only about 30 tags, and the H tags were six of them.
\nWithin a year people were paying me to build web pages. (Here’s a screenshot of my first paid web gig.)
\nI did plain HTML for a number of years. Server Side Includes came and went. In 1997 someone asked me to build a site with PHP/FI 2.0, so I went home from work, went to devshed.com and looked up an article on how to do that, thus starting my career as a PHP developer.
\nA couple of years later “cascading style sheets” looked like they were here to stay and I picked those up and became a “full stack developer” though no-one used that phrase back then. I was a Webmaster.
\nWhen WordPress was first released, I was working at a University, teaching a class on the side for fun. It was Intro to Web Development. Each student had to do a project, so I decided to take one on as well. I built a blogging system to compete with WordPress. To my knowledge, one other person used it, ever. But I used it for about ten years. I didn’t really like WordPress back then because it really WAS “just for blogging.” Trying to make it do other things was hard.
\nBut then came WordPress 3.0 with Custom Post Types, and everything changed. WordPress morphed into a real CMS with that one version.
\nIn 2010 I went freelance (on purpose!) about the same time 3.0 came out, and I immediately started using it, and haven’t really used anything else since.
\nDK: I’m curious, how did you come by the nickname “Topher?” Is there a good story there?
\nTD: When I was three, my Aunt was babysitting, and she asked me if I knew what my middle name was. I knew my first name was Chris, last name DeRosia, and full name Christopher DeRosia, so I assumed Topher was my middle name. She laughed and wrote it on the fridge notebook and called my Grandma etc. I still have the paper she wrote it on. People called me Topher very occasionally until college when there were four Chris’ on my dorm floor. We each picked something, and I’ve been 100% Topher ever since. When I was young and vain, I considered making it a mononym, but… such a nerd.
\nDK: What have you learned from HeroPress over time? Did it surprise you in any way, what people had to say? What do you think about people and groups on the “fringe” of the WordPress community today? Who/what are we (North Americans) least attentive to/aware of?
\nTD: I read your question about what I’ve learned from HeroPress over time and then sat in my chair for a good ten minutes just thinking about everything. HeroPress has become so pervasive in my personal relationships with people that it’s hard for me to separate these days. I never thought I would be such close friends with people so far away. People I laugh with, cry with, talk long into the night, have days-long conversations on Twitter.
\nMost times when I approach someone about being a contributor I have some idea of their background, so while surprises happen they’re not usually too big. One time that really blew my mind though was at WCUS in Philly. A speaker looked like a good candidate, and so without knowing anything about her, I approached her in the hall and introduced myself. I asked if I could tell her about my project, HeroPress, and she agreed. About 20 seconds into my pitch she started sobbing. Deeply and loudly. I was literally speechless. As it turns out she had a story that needed to be told, a story that started with a family leaving her country of origin when she was very young, and all the things that happened to her after that. I cried then with her, and I’m crying a little bit now as I write it. I will always say that HeroPress has affected me personally more than anyone else in the world.
\nI’ve learned that people are diverse, so I can’t say anyone is like X or wants Y because of my perception of where they live. Some poor people want money. Some don’t. Some people want freedom. Some never think about it. It doesn’t matter where they live or what they have; I can never assume about them.
\nI have noticed that wealthier people tend to forget they’re wealthy and take it for granted. They usually don’t feel wealthy. One WordPress person might say “I’m a little short on cash this year, I’ll only go to one WordCamp.” Another WordPress person might say “I wish attending WordCamp didn’t cost two years salary.” Or perhaps “I wish people I don’t know didn’t think I was a terrorist, so I could go learn.” I feel so flippant sometimes. I want to learn something, so I spend $100 on an online class. My friend wants to learn the same thing, and $100 is six months salary. Even in wealthy nations like America, where our poorest are among the richest internationally, WordCamp is a couple of months rent, or gas, or electricity.
\nI could write for a long time, but it has been impressed upon me the difference in life choices between the haves and the have nots.
\nDK: How do you look at your freelance career now? What kind of work did you do? And how did that path lead to Sandhills, Modern Tribe, and now BigCommerce?
\nTD: I started freelancing in college, though I didn’t know that’s what it was called, or even that people actually did it for a living. I was just picking up odd jobs. After I graduated, rather than get a Real Job, I just kept taking contracts. A few months after graduation I took a three-month contract with Kellogg’s and built their first intranet web site. Netscape 3 was the hotness at the time.
\nAfter that, I took a real job at a hosting company of sorts, and I was there until 2000 when I took a job at my old university running their radio station websites for ten years. I never quit freelancing on the side though. Always there was someone emailing me saying “Hey, my brother’s wife’s uncle’s nephew says you do internet. Can you help?” Or worse “Hi there, someone told me you know web stuff, my username and password are *****. Can you help?”
\nOver Christmas break in 2009, my wife and I were talking, and I realized I had spent all of every evening working on side work for two years solid. I was spending eight hours a day at work making $25/hr (granted, with benefits etc.) and three hours every evening making $65/hr. We reasoned that if I got that day job out of the way and managed four billable hours a day, we’d be in about the same position. Except I wouldn’t be at the office eight hours a day (nine if you include driving) and I’d get my evenings back. What’s not to like? So in February 2010, I was done.
\nPeople often ask me “How do you know when it’s time to freelance?” The answer is, start now, on the side. When you’re making enough that the day job is getting in the way, fire it.
\nAs for what kind of work I did, there’s some irony. Before 2010 I did all custom PHP/MySQL/HTML/CSS stuff. 2010 is when WordPress 3.0 came out and changed everything. I did only WordPress after that. So the metric I had based my freelance career on changed as soon as I started full time. But it worked out.
\nI wasn’t very good with WordPress when I started, but I was a very good PHP dev, so I quickly learned how to mess with custom post types. Most implementors didn’t know how but needed them, so I did a lot of work for other WordPress devs. I would say the majority of my freelance work since 2010 has been building doodads for other WordPress developers, as opposed to building websites.
\nSomewhere around 2011, a client talked me into joining their startup. I become CTO, and it was sort of a Real Job. Then we took investment and became a really Real Job. Varsity News Network is still going today. While there I built a monolithic plugin that did everything I could think of — it was ridiculous. It was my first plugin, and it showed. It was decently secure and whatnot, but I didn’t fully understand hooks and filters, and the whole thing was a bit of a mess. But who doesn’t look at their code from eight years ago and cringe?
\nI didn’t really enjoy my time there, and my partner knew it, so in the summer of 2013 he took me out to breakfast and fired me. It was awkward because that meant I didn’t have a job or insurance anymore, but he was right, I didn’t want to be there. It also meant I had to go tell my wife that we were out of work.
\nThere were some upsides, however. My partner went to bat for me with the board and got me my stock options, without having to work six more months to vest them. Also, there was a New Thing in the WordPress world: agencies. I’d been hearing about one called 10up, and I knew there were others. By this time I knew some people in the WordPress world, and I felt pretty confident I could get a job fast. I emailed a friend at 10up, and he said, “You need to talk to Jake.” So a few minutes later I was talking Jake at 10up. He gave me some advice and gave me a test to take to see if I’d fit in there. I’m going to skip ahead here, because the next few months are an interesting story in and of themselves, and it would make this tome even more epic.
\nLong story short, I started a trial with X-Team in November of 2013 and went full time in January. I worked there until the fall of 2013 when Dave Rosen, the owner of X-Team/XWP approached me about starting HeroPress. HeroPress took about four months to fail, and during that time several people approached me and said “If this doesn’t work out, come see me,” which was a very nice safety net.
\nOf course, it did fail. I went and saw Pippin Williamson and worked for him writing docs for about a year and a half. In the spring of 2016, I wasn’t very happy writing docs. Pippin was great, the company was great, but I just didn’t fit well. I heard Peter Chester from Modern Tribe talk about how they work, and getting back to coding sounded like just the thing to me. I worked there for about five months. Some miscommunication during hiring put me in a position I was ill-suited for, and it wasn’t good for either of us.
\nAfter that, I joined with Tanner Moushey for about a year to spin up a WordPress agency. In typical startup fashion it was a lot of hard work and not quite enough pay for either of us, so we ended that at the beginning of 2018, and I had to decide what I wanted to do next.
\nI freelanced for about six months. What I really wanted was a community job — something where I did a lot of shaking hands and kissing babies.
\nThen at 11:33 PM on June 11th, my friend Luke sent me this in Slack:
\n![\"\"](\"https://cdn.poststatus.com/wp-content/uploads/2019/02/topher-sms.png\")
This may come as a surprise to you, but I WAS interested. A week later they made an offer, and I accepted. I started at BigCommerce on my birthday, 17 July.
\nDK: So do you get to do a lot of shaking hands and kissing babies as a WordPress Developer Evangelist?
\nTD: A lot of shaking hands, not too many babies yet, which is sad, I love babies. ![\"?\"](\"https://s.w.org/images/core/emoji/11/72x72/1f642.png\")
I’ve been tasked with going to twenty WordCamps in 2019, and I travel in person to at least one Meetup per month. On top of that, I spend a ton of time talking with people on Slack, Twitter, Hangouts, etc.
DK: Tell us about the good news of headless eCommerce.
\nTD: The joys of headless eCommerce are many.
\nDK: Is BigCommerce unique in the WordPress space?
\nTD: Depends on how you define it. There are other eCommerce plugins, and there are other SaaS plugins. There’s even a Shopify plugin that works over API just like BigCommerce. That said, Shopify’s API handles two requests per second out of the box, whereas BigCommerce’s does 400 per second. I think if you want to look at the purely SaaS angle, plugins like OptinMonster and Kraken.io started the movement. I think larger companies like BigCommerce are going to help turn the tide toward heavy SaaSification (that’s a @Mor10 term).
DK: Are developers or site owners hesitant to move inventory to an API-first service where pricing is based on fixed API call limits? Or is this what the future of WordPress looks like, as a Digital Experience Platform?
\nTD: We haven’t seen that with the developers who use our platform most. The most traffic we’ve ever gotten is a small fraction of what our theoretical limits are on the API, so there hasn’t been any concern there. Mostly what we’ve seen is excitement about being able to break out of our built-in Stencil framework and build without limits, while keeping the core power of the eCommerce platform. (Here’s a simple example.) There’s a simple form where you can put in your weight and skill level, and it will tell you your surfboard volume. In WordPress, that’s ridiculously simple, but in Stencil, on BigCommerce it would be really hard. Putting WordPress on the front end of BigCommerce gives the benefits of both platforms.
\nSomething that has really surprised me is the excitement of agencies that have been working in Stencil on BigCommerce for years. Most of them also do WordPress sites, and they are thrilled at the possibilities. I know of more than one agency that is giving up all other eCommerce options (like Magento or Shopify) to go exclusively BigCommerce on WordPress. It’s very exciting.
\nDK: What do you do when you’re not working to relax or to decompress when you’re off work?
\nTD: I typically spend time with my family watching TV or playing games. I do have a personal vice; I play a few video games. I don’t consider myself a gamer, but there are a few I like, and I’ll occasionally take a few hours in the evening and play.
Last week Amazon launched Alexa Skill Blueprints that allow anyone to publish new skills to the Alexa Skills Store without having to have any coding knowledge. The blueprints are templates that provide a starting point where users can create a new skill by filling in the blanks and then publish it to the store for US customers.
\nThis first round of blueprints is targeted at content creators, bloggers, and organizations. It includes blueprints for personal trainers, flashcards, facts, quizzes, and a fable blueprint for storytellers. There are also new blueprints available called University and Spiritual Talks for live and recorded audio content from institutions and organizations.
\nAmazon has also created a blueprint specifically for WordPress blogs. It works in connection with the Amazon AI Plugin for WordPress to read blogs aloud on Alexa-enabled devices. Setup is not trivial but it is much easier for users than having to create their own blueprints from scratch.
\nAccording to Amazon’s announcement, the new WordPress blog blueprint converts posts into speech and creates an audio RSS feed:
\n\nThe Amazon AI Plugin for WordPress is a sample application that enables WordPress bloggers to easily convert their blog posts into speech by leveraging Text-to-Speech (TTS) and translation tools provided by Amazon. Bloggers can generate an audio feed (RSS feed) for text-based blog content, and simply add this to the new Blog blueprint to create and publish their own Alexa skill.
If you want to get this working for your WordPress blog, the first step is to install the official Amazon AI Plugin for WordPress. Follow the instructions on the Blog skill blueprint page. The plugin will generate an RSS feed that you will enter into your skill content section. It also needs to be configured with the AWS access key, secret key, and AWS region. There are options available for specifying a post type, enable logging, audio player settings, the ability to exclude certain tags from generating audio, translations, audio excerpts, and more.
\nAfter setting up the plugin, you can complete the blueprint by customizing the welcome messages, naming the skill, and publishing it to the Alexa Skills Store, as demonstrated in the video below. Anyone with an Alexa-enabled device can then have Alexa read your RSS feed to them.
\n\nAmazon also introduced a new blueprint for creating flash briefing skills, which include short-form content in the form of an audio feed. This format lends itself well to local weather reports, news and sports updates, and other information that can be quickly communicated via an audio update. This may be another option that WordPress news site owners may want to consider. The flash briefing skills page has instructions for creating one and there is also an unofficial WordPress plugin called WP Alexa Flash Briefing that has its own Alexa skill already set up.
\nIf you want to go one step further and manage your WordPress blog with Alexa, the unofficial Blog Helper skill will enable you to log new drafts and moderate comments. It’s available on GitHub.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 Feb 2019 21:46:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"WPTavern: Matt Mullenweg Publishes TED Talk on the Future of Work, Prepares to Launch New Distributed.blog Website\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87306\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:124:\"https://wptavern.com/matt-mullenweg-publishes-ted-talk-on-the-future-of-work-prepares-to-launch-new-distributed-blog-website\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3617:\"Matt Mullenweg is teasing out a new website at distributed.blog with the tagline “The future of work is here.” It’s not clear yet whether subscribers to the mystery blog will be on board for blog posts, a new podcast, or a book promotion, but the site has piqued curiosity.
\n\n\n\nThis should be fun… (take 2 with working form) https://t.co/RpAfb8jvg5
\n— Matt Mullenweg (@photomatt) February 14, 2019
Mullenweg recently recorded a talk for TED’s new video series, The Way We Work. Over the past 14 years since founding Automattic, he has become an expert and an industry advocate for distributed work, having grown the company to more than 800 employees. In the video he said he prefers the term “distributed” over “remote,” as remote implies there are some people who are central and some who are not.
\n\n\n\nWhen I first started working as a developer from home in 2008, many of my friends and family didn’t believe I had “a real job.” People would often say things like, “Remind me what it is that you do at home all day…?” Sometimes I would even receive honest questions from incredulous friends, asking, “Why don’t you go find a real job?” The culture of remote and distributed work is still not widely understood 11 years later but it is slowly improving.
\n“I think a distributed work force is the most effective way to build a company,” Mullenweg said. “The key is that you have to approach it consciously. I believe that talent and intelligence are equally distributed throughout the world but opportunity is not.” Large tech companies, along with more traditional style companies, still struggle to get on board with this way of working.
\nMullenweg’s TED talk explains a few advantages of distributed work. He also anticipates responses from managers in traditional work environments, who might say, “Sure, that may work for all you fancy tech folks but not for us.” Mullenweg outlines a few tips for getting started, such as documenting everything, increasing communication online, and experimenting with collaboration tools.
\nAutomattic was the first WordPress company to operate a completely distributed workforce. Many other product companies, hosts, and agencies have followed suit. Remote and distributed teams have now become so common in the WordPress ecosystem that many who have experienced this way of working can never return to their old way of life.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 14 Feb 2019 19:02:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: WPBrigade Patches Critical Vulnerability in Simple Social Buttons Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87279\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"https://wptavern.com/wpbrigade-patches-critical-vulnerability-in-simple-social-buttons-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1750:\"WPBrigade, the developers behind the Simple Social Buttons plugin, have patched a critical privilege escalation vulnerability. The security issue was discovered by the team at WebARX. Developer and researcher Luka Šikić summarized the vulnerability in a post published this week:
\n\nImproper application design flow, chained with lack of permission check resulted in privilege escalation and unauthorized actions in WordPress installation allowing non-admin users, even subscriber user type to modify WordPress installation options from the wp_options table.
Simple Social Buttons is a plugin that makes it easy for users to add social buttons to posts, pages, archives, and, popups, fly-ins, and custom post types. More than 40,000 users have the free version of the plugin active on their sites. A commercial version is also available through the developer’s website.
\nThe plugin’s authors released version 2.0.22 the day after WebARX disclosed the vulnerability, but some site owners and agencies may not have heard about the security issue. Not everyone checks for updates automatically or even once per month. WPBrigade has not yet alerted users to the vulnerability on their blog or Twitter account. The only mention is in the plugin’s changelog, which states: “Enhancement: Fix security issue.” Users who see an update notice in their dashboards are advised to update immediately.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 14 Feb 2019 06:04:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"WPTavern: WPWeekly Episode 345 – The Relationship Between Corporate Cash and Open Source Software\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=87276&preview=true&preview_id=87276\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"https://wptavern.com/wpweekly-episode-345-the-relationship-between-corporate-cash-and-open-source-software\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2844:\"In this episode, John James Jacoby and I discuss a thought-provoking post published by Morten Rand-Hendriksen that takes a deep look at equity in open source software. Morten suggests that the mantra of decisions are made by those who show up be changed to decisions are made by those who can afford to show up.
\nWe talk about the relationship and influence money from businesses can have on open source software, especially if they’re employing someone to contribute to that project full-time. We discuss the pros and cons of financial contributions and whether or not WordPress could fall victim to progressing only at the whims of corporate sponsors.
\nNear the end of the show, John provides an overview of what’s new in Sugar Calendar 2.0.
\nPetersenMediaGroup is Relaunched
\nhttps://www.petersenmediagroup.com/
\n\nGutenberg 5.0 Adds New RSS Block, Amazon Kindle Embed Block, and FocalPointPicker Component
\nGutenberg Blocks Design Library Offers Pre-Built Page Designs Using Existing Core Blocks
\nGoogle+ is shutting down in April with some APIs shutting down in March
\nSugar Calendar 2.0 Beta Released
\nThe Dark Mode plugin developed by Daniel James is no longer a featured plugin.
\nNext Episode: Wednesday, February 20th 3:00 P.M. Eastern
\nSubscribe to WordPress Weekly via Itunes
\nSubscribe to WordPress Weekly via RSS
\nSubscribe to WordPress Weekly via Stitcher Radio
\nSubscribe to WordPress Weekly via Google Play
\nListen To Episode #345:
\n
Ultimate Blocks, one of the many Gutenberg block collections that have sprouted up, launched before WordPress 5.0 with eight blocks. The collection has since doubled in size, adding features like accordions, social sharing buttons, tabbed content, a progress bar, and star-ratings. Many block collections are loosely organized around serving a specific user demographic. This one is aimed at bloggers and marketers.
\n\n\n\nUltimate Blocks’ latest release includes Reviews, a new Gutenberg block that is unique to this plugin. It allows users to easily add rows of review criteria and will automatically calculate the cumulative star rating. Users can also edit the title of the review, author name, review summary, and call-to-action button.
\n\n\n\nOne of the most interesting features of the plugin is that it is schema-enabled, which means that the reviews use a standard schema for structured data that can be easily read by applications like Google, Microsoft, Pinterest, and others. For example, when Google finds a schema-enabled review, it can display it as a rich review snippet with stars and other summary info. These snippets may appear in search results or in Google Knowledge Cards.
\n\n\n\nIt’s important to clarify that this block is for the site owner to write their own reviews. It’s not a block that adds a frontend form for visitors to leave reviews. It’s more useful for site owners who want a nice way to display their own reviews for books, movies, restaurants, or any other type of information.
\n\n\n\nAfter testing the plugin, I was impressed by how the star rating calculations all work live inside Gutenberg while setting up the block. The back and frontend styles also match fairly well. The Reviews block is generic enough to be used for virtually any type of review a user wants to display. It would even more useful if the author expanded it to support frontend review submissions, which would allow users to create their own community review sites.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Feb 2019 20:34:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"WPTavern: Speaker Applications Now Open for 2nd Annual JavaScript for WordPress Conference, July 11-13, 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=87220\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:117:\"https://wptavern.com/speaker-applications-now-open-for-2nd-annual-javascript-for-wordpress-conference-july-11-13-2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2477:\"Last year Zac Gordon organized a free virtual JavaScript for WordPress conference and the event drew 1,200 live attendees. With attendance numbers higher than most WordPress conferences and hundreds more views on the videos published afterwards, Gordon considered it a success and committed to organize another event this year.
\nThe next edition is set for July 11-13, 2019, and has been expanded to feature three free days of talks, workshops, and contribution focused on JavaScript and WordPress. The goal for the event’s contributor day is to improve Gutenberg documentation. Applications for speakers and sponsors are now open and attendees can reserve their seats by signing up on the event’s website.
\n“The conference aims to cover intermediate and advanced topics (not so much beginner),” Gordon said. “Most of the talks are about latest trends of how JS and WP can be used together. Accessibility is really important, as is diversity in speakers. I’d love to have more folks share about cool things they do at work.” He said topics like headless WP, Gatsby, React, state management, Gutenberg, and blockchain are a few examples that seem to be popular in this space right now. Testing and internationalization are two topics that still need speakers.
\nGordon teaches both beginner and more advanced courses on JavaScript and Gutenberg development, giving him a unique window into the landscape of JavaScript education. After Gutenberg made its way into core, Gordon said folks “finally have a tangible reason to learn JavaScript.”
\n“Also, I think folks are finding it easier than first thought,” he said. “A lot of folks have taken my Gutenberg Development Course with zero React or tooling experience and that served as a good introduction to it all.
\n“At first Matt said, ‘Learn JavaScript Deeply.’ But at the last WCUS he said, ‘Learn Blocks Deeply.’ Luckily, I think it is becoming easier to learn what we need to know with JS and React and tools to get by.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Feb 2019 03:39:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Sun, 17 Mar 2019 21:55:48 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Sun, 17 Mar 2019 21:45:09 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";s:16:\"content-encoding\";s:2:\"br\";}}s:5:\"build\";s:14:\"20130911073210\";}','no'),(134,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1552902949','no'),(135,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1552859749','no'),(136,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1552902949','no'),(137,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b','','no'),(138,'_site_transient_timeout_poptags_40cd750bba9870f18aada2478b24840a','1552870587','no'),(139,'_site_transient_poptags_40cd750bba9870f18aada2478b24840a','O:8:\"stdClass\":100:{s:6:\"widget\";a:3:{s:4:\"name\";s:6:\"widget\";s:4:\"slug\";s:6:\"widget\";s:5:\"count\";i:4566;}s:11:\"woocommerce\";a:3:{s:4:\"name\";s:11:\"woocommerce\";s:4:\"slug\";s:11:\"woocommerce\";s:5:\"count\";i:3336;}s:4:\"post\";a:3:{s:4:\"name\";s:4:\"post\";s:4:\"slug\";s:4:\"post\";s:5:\"count\";i:2613;}s:5:\"admin\";a:3:{s:4:\"name\";s:5:\"admin\";s:4:\"slug\";s:5:\"admin\";s:5:\"count\";i:2477;}s:5:\"posts\";a:3:{s:4:\"name\";s:5:\"posts\";s:4:\"slug\";s:5:\"posts\";s:5:\"count\";i:1910;}s:9:\"shortcode\";a:3:{s:4:\"name\";s:9:\"shortcode\";s:4:\"slug\";s:9:\"shortcode\";s:5:\"count\";i:1719;}s:8:\"comments\";a:3:{s:4:\"name\";s:8:\"comments\";s:4:\"slug\";s:8:\"comments\";s:5:\"count\";i:1713;}s:7:\"twitter\";a:3:{s:4:\"name\";s:7:\"twitter\";s:4:\"slug\";s:7:\"twitter\";s:5:\"count\";i:1466;}s:6:\"images\";a:3:{s:4:\"name\";s:6:\"images\";s:4:\"slug\";s:6:\"images\";s:5:\"count\";i:1430;}s:8:\"facebook\";a:3:{s:4:\"name\";s:8:\"facebook\";s:4:\"slug\";s:8:\"facebook\";s:5:\"count\";i:1425;}s:6:\"google\";a:3:{s:4:\"name\";s:6:\"google\";s:4:\"slug\";s:6:\"google\";s:5:\"count\";i:1423;}s:5:\"image\";a:3:{s:4:\"name\";s:5:\"image\";s:4:\"slug\";s:5:\"image\";s:5:\"count\";i:1355;}s:7:\"sidebar\";a:3:{s:4:\"name\";s:7:\"sidebar\";s:4:\"slug\";s:7:\"sidebar\";s:5:\"count\";i:1291;}s:3:\"seo\";a:3:{s:4:\"name\";s:3:\"seo\";s:4:\"slug\";s:3:\"seo\";s:5:\"count\";i:1287;}s:7:\"gallery\";a:3:{s:4:\"name\";s:7:\"gallery\";s:4:\"slug\";s:7:\"gallery\";s:5:\"count\";i:1136;}s:4:\"page\";a:3:{s:4:\"name\";s:4:\"page\";s:4:\"slug\";s:4:\"page\";s:5:\"count\";i:1091;}s:5:\"email\";a:3:{s:4:\"name\";s:5:\"email\";s:4:\"slug\";s:5:\"email\";s:5:\"count\";i:1089;}s:6:\"social\";a:3:{s:4:\"name\";s:6:\"social\";s:4:\"slug\";s:6:\"social\";s:5:\"count\";i:1049;}s:9:\"ecommerce\";a:3:{s:4:\"name\";s:9:\"ecommerce\";s:4:\"slug\";s:9:\"ecommerce\";s:5:\"count\";i:985;}s:5:\"login\";a:3:{s:4:\"name\";s:5:\"login\";s:4:\"slug\";s:5:\"login\";s:5:\"count\";i:919;}s:5:\"links\";a:3:{s:4:\"name\";s:5:\"links\";s:4:\"slug\";s:5:\"links\";s:5:\"count\";i:850;}s:7:\"widgets\";a:3:{s:4:\"name\";s:7:\"widgets\";s:4:\"slug\";s:7:\"widgets\";s:5:\"count\";i:836;}s:5:\"video\";a:3:{s:4:\"name\";s:5:\"video\";s:4:\"slug\";s:5:\"video\";s:5:\"count\";i:823;}s:8:\"security\";a:3:{s:4:\"name\";s:8:\"security\";s:4:\"slug\";s:8:\"security\";s:5:\"count\";i:771;}s:7:\"content\";a:3:{s:4:\"name\";s:7:\"content\";s:4:\"slug\";s:7:\"content\";s:5:\"count\";i:723;}s:4:\"spam\";a:3:{s:4:\"name\";s:4:\"spam\";s:4:\"slug\";s:4:\"spam\";s:5:\"count\";i:719;}s:10:\"buddypress\";a:3:{s:4:\"name\";s:10:\"buddypress\";s:4:\"slug\";s:10:\"buddypress\";s:5:\"count\";i:717;}s:6:\"slider\";a:3:{s:4:\"name\";s:6:\"slider\";s:4:\"slug\";s:6:\"slider\";s:5:\"count\";i:703;}s:3:\"rss\";a:3:{s:4:\"name\";s:3:\"rss\";s:4:\"slug\";s:3:\"rss\";s:5:\"count\";i:696;}s:10:\"e-commerce\";a:3:{s:4:\"name\";s:10:\"e-commerce\";s:4:\"slug\";s:10:\"e-commerce\";s:5:\"count\";i:693;}s:9:\"analytics\";a:3:{s:4:\"name\";s:9:\"analytics\";s:4:\"slug\";s:9:\"analytics\";s:5:\"count\";i:679;}s:5:\"pages\";a:3:{s:4:\"name\";s:5:\"pages\";s:4:\"slug\";s:5:\"pages\";s:5:\"count\";i:677;}s:5:\"media\";a:3:{s:4:\"name\";s:5:\"media\";s:4:\"slug\";s:5:\"media\";s:5:\"count\";i:661;}s:6:\"jquery\";a:3:{s:4:\"name\";s:6:\"jquery\";s:4:\"slug\";s:6:\"jquery\";s:5:\"count\";i:649;}s:6:\"search\";a:3:{s:4:\"name\";s:6:\"search\";s:4:\"slug\";s:6:\"search\";s:5:\"count\";i:646;}s:4:\"form\";a:3:{s:4:\"name\";s:4:\"form\";s:4:\"slug\";s:4:\"form\";s:5:\"count\";i:645;}s:4:\"feed\";a:3:{s:4:\"name\";s:4:\"feed\";s:4:\"slug\";s:4:\"feed\";s:5:\"count\";i:627;}s:4:\"ajax\";a:3:{s:4:\"name\";s:4:\"ajax\";s:4:\"slug\";s:4:\"ajax\";s:5:\"count\";i:617;}s:4:\"menu\";a:3:{s:4:\"name\";s:4:\"menu\";s:4:\"slug\";s:4:\"menu\";s:5:\"count\";i:615;}s:8:\"category\";a:3:{s:4:\"name\";s:8:\"category\";s:4:\"slug\";s:8:\"category\";s:5:\"count\";i:612;}s:5:\"embed\";a:3:{s:4:\"name\";s:5:\"embed\";s:4:\"slug\";s:5:\"embed\";s:5:\"count\";i:583;}s:10:\"javascript\";a:3:{s:4:\"name\";s:10:\"javascript\";s:4:\"slug\";s:10:\"javascript\";s:5:\"count\";i:569;}s:6:\"editor\";a:3:{s:4:\"name\";s:6:\"editor\";s:4:\"slug\";s:6:\"editor\";s:5:\"count\";i:565;}s:4:\"link\";a:3:{s:4:\"name\";s:4:\"link\";s:4:\"slug\";s:4:\"link\";s:5:\"count\";i:557;}s:3:\"css\";a:3:{s:4:\"name\";s:3:\"css\";s:4:\"slug\";s:3:\"css\";s:5:\"count\";i:556;}s:7:\"youtube\";a:3:{s:4:\"name\";s:7:\"youtube\";s:4:\"slug\";s:7:\"youtube\";s:5:\"count\";i:548;}s:5:\"share\";a:3:{s:4:\"name\";s:5:\"share\";s:4:\"slug\";s:5:\"share\";s:5:\"count\";i:533;}s:12:\"contact-form\";a:3:{s:4:\"name\";s:12:\"contact form\";s:4:\"slug\";s:12:\"contact-form\";s:5:\"count\";i:532;}s:5:\"theme\";a:3:{s:4:\"name\";s:5:\"theme\";s:4:\"slug\";s:5:\"theme\";s:5:\"count\";i:528;}s:7:\"comment\";a:3:{s:4:\"name\";s:7:\"comment\";s:4:\"slug\";s:7:\"comment\";s:5:\"count\";i:525;}s:10:\"responsive\";a:3:{s:4:\"name\";s:10:\"responsive\";s:4:\"slug\";s:10:\"responsive\";s:5:\"count\";i:519;}s:9:\"dashboard\";a:3:{s:4:\"name\";s:9:\"dashboard\";s:4:\"slug\";s:9:\"dashboard\";s:5:\"count\";i:511;}s:6:\"custom\";a:3:{s:4:\"name\";s:6:\"custom\";s:4:\"slug\";s:6:\"custom\";s:5:\"count\";i:502;}s:9:\"affiliate\";a:3:{s:4:\"name\";s:9:\"affiliate\";s:4:\"slug\";s:9:\"affiliate\";s:5:\"count\";i:496;}s:3:\"ads\";a:3:{s:4:\"name\";s:3:\"ads\";s:4:\"slug\";s:3:\"ads\";s:5:\"count\";i:495;}s:10:\"categories\";a:3:{s:4:\"name\";s:10:\"categories\";s:4:\"slug\";s:10:\"categories\";s:5:\"count\";i:493;}s:4:\"tags\";a:3:{s:4:\"name\";s:4:\"tags\";s:4:\"slug\";s:4:\"tags\";s:5:\"count\";i:472;}s:6:\"button\";a:3:{s:4:\"name\";s:6:\"button\";s:4:\"slug\";s:6:\"button\";s:5:\"count\";i:471;}s:4:\"user\";a:3:{s:4:\"name\";s:4:\"user\";s:4:\"slug\";s:4:\"user\";s:5:\"count\";i:469;}s:7:\"contact\";a:3:{s:4:\"name\";s:7:\"contact\";s:4:\"slug\";s:7:\"contact\";s:5:\"count\";i:462;}s:7:\"payment\";a:3:{s:4:\"name\";s:7:\"payment\";s:4:\"slug\";s:7:\"payment\";s:5:\"count\";i:462;}s:3:\"api\";a:3:{s:4:\"name\";s:3:\"api\";s:4:\"slug\";s:3:\"api\";s:5:\"count\";i:460;}s:6:\"mobile\";a:3:{s:4:\"name\";s:6:\"mobile\";s:4:\"slug\";s:6:\"mobile\";s:5:\"count\";i:455;}s:5:\"users\";a:3:{s:4:\"name\";s:5:\"users\";s:4:\"slug\";s:5:\"users\";s:5:\"count\";i:441;}s:5:\"photo\";a:3:{s:4:\"name\";s:5:\"photo\";s:4:\"slug\";s:5:\"photo\";s:5:\"count\";i:429;}s:6:\"events\";a:3:{s:4:\"name\";s:6:\"events\";s:4:\"slug\";s:6:\"events\";s:5:\"count\";i:425;}s:9:\"slideshow\";a:3:{s:4:\"name\";s:9:\"slideshow\";s:4:\"slug\";s:9:\"slideshow\";s:5:\"count\";i:418;}s:6:\"photos\";a:3:{s:4:\"name\";s:6:\"photos\";s:4:\"slug\";s:6:\"photos\";s:5:\"count\";i:417;}s:5:\"stats\";a:3:{s:4:\"name\";s:5:\"stats\";s:4:\"slug\";s:5:\"stats\";s:5:\"count\";i:416;}s:15:\"payment-gateway\";a:3:{s:4:\"name\";s:15:\"payment gateway\";s:4:\"slug\";s:15:\"payment-gateway\";s:5:\"count\";i:403;}s:10:\"navigation\";a:3:{s:4:\"name\";s:10:\"navigation\";s:4:\"slug\";s:10:\"navigation\";s:5:\"count\";i:403;}s:10:\"statistics\";a:3:{s:4:\"name\";s:10:\"statistics\";s:4:\"slug\";s:10:\"statistics\";s:5:\"count\";i:393;}s:9:\"marketing\";a:3:{s:4:\"name\";s:9:\"marketing\";s:4:\"slug\";s:9:\"marketing\";s:5:\"count\";i:387;}s:8:\"calendar\";a:3:{s:4:\"name\";s:8:\"calendar\";s:4:\"slug\";s:8:\"calendar\";s:5:\"count\";i:385;}s:5:\"popup\";a:3:{s:4:\"name\";s:5:\"popup\";s:4:\"slug\";s:5:\"popup\";s:5:\"count\";i:384;}s:4:\"chat\";a:3:{s:4:\"name\";s:4:\"chat\";s:4:\"slug\";s:4:\"chat\";s:5:\"count\";i:380;}s:4:\"news\";a:3:{s:4:\"name\";s:4:\"news\";s:4:\"slug\";s:4:\"news\";s:5:\"count\";i:378;}s:10:\"shortcodes\";a:3:{s:4:\"name\";s:10:\"shortcodes\";s:4:\"slug\";s:10:\"shortcodes\";s:5:\"count\";i:377;}s:10:\"newsletter\";a:3:{s:4:\"name\";s:10:\"newsletter\";s:4:\"slug\";s:10:\"newsletter\";s:5:\"count\";i:370;}s:12:\"social-media\";a:3:{s:4:\"name\";s:12:\"social media\";s:4:\"slug\";s:12:\"social-media\";s:5:\"count\";i:368;}s:7:\"plugins\";a:3:{s:4:\"name\";s:7:\"plugins\";s:4:\"slug\";s:7:\"plugins\";s:5:\"count\";i:360;}s:4:\"code\";a:3:{s:4:\"name\";s:4:\"code\";s:4:\"slug\";s:4:\"code\";s:5:\"count\";i:356;}s:9:\"multisite\";a:3:{s:4:\"name\";s:9:\"multisite\";s:4:\"slug\";s:9:\"multisite\";s:5:\"count\";i:353;}s:3:\"url\";a:3:{s:4:\"name\";s:3:\"url\";s:4:\"slug\";s:3:\"url\";s:5:\"count\";i:352;}s:5:\"forms\";a:3:{s:4:\"name\";s:5:\"forms\";s:4:\"slug\";s:5:\"forms\";s:5:\"count\";i:348;}s:4:\"meta\";a:3:{s:4:\"name\";s:4:\"meta\";s:4:\"slug\";s:4:\"meta\";s:5:\"count\";i:345;}s:8:\"redirect\";a:3:{s:4:\"name\";s:8:\"redirect\";s:4:\"slug\";s:8:\"redirect\";s:5:\"count\";i:343;}s:4:\"list\";a:3:{s:4:\"name\";s:4:\"list\";s:4:\"slug\";s:4:\"list\";s:5:\"count\";i:342;}s:14:\"contact-form-7\";a:3:{s:4:\"name\";s:14:\"contact form 7\";s:4:\"slug\";s:14:\"contact-form-7\";s:5:\"count\";i:328;}s:11:\"performance\";a:3:{s:4:\"name\";s:11:\"performance\";s:4:\"slug\";s:11:\"performance\";s:5:\"count\";i:324;}s:11:\"advertising\";a:3:{s:4:\"name\";s:11:\"advertising\";s:4:\"slug\";s:11:\"advertising\";s:5:\"count\";i:320;}s:12:\"notification\";a:3:{s:4:\"name\";s:12:\"notification\";s:4:\"slug\";s:12:\"notification\";s:5:\"count\";i:319;}s:16:\"custom-post-type\";a:3:{s:4:\"name\";s:16:\"custom post type\";s:4:\"slug\";s:16:\"custom-post-type\";s:5:\"count\";i:316;}s:6:\"simple\";a:3:{s:4:\"name\";s:6:\"simple\";s:4:\"slug\";s:6:\"simple\";s:5:\"count\";i:313;}s:16:\"google-analytics\";a:3:{s:4:\"name\";s:16:\"google analytics\";s:4:\"slug\";s:16:\"google-analytics\";s:5:\"count\";i:313;}s:8:\"tracking\";a:3:{s:4:\"name\";s:8:\"tracking\";s:4:\"slug\";s:8:\"tracking\";s:5:\"count\";i:309;}s:7:\"adsense\";a:3:{s:4:\"name\";s:7:\"adsense\";s:4:\"slug\";s:7:\"adsense\";s:5:\"count\";i:308;}s:6:\"author\";a:3:{s:4:\"name\";s:6:\"author\";s:4:\"slug\";s:6:\"author\";s:5:\"count\";i:307;}s:4:\"html\";a:3:{s:4:\"name\";s:4:\"html\";s:4:\"slug\";s:4:\"html\";s:5:\"count\";i:307;}s:3:\"tag\";a:3:{s:4:\"name\";s:3:\"tag\";s:4:\"slug\";s:3:\"tag\";s:5:\"count\";i:304;}}','no'),(141,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1552859840;s:7:\"checked\";a:3:{s:19:\"akismet/akismet.php\";s:5:\"4.1.1\";s:38:\"fv-wordpress-flowplayer/flowplayer.php\";s:10:\"7.3.12.727\";s:9:\"hello.php\";s:5:\"1.7.1\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:3:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:5:\"4.1.1\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.1.1.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:59:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272\";s:2:\"1x\";s:59:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:61:\"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904\";}s:11:\"banners_rtl\";a:0:{}}s:38:\"fv-wordpress-flowplayer/flowplayer.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:37:\"w.org/plugins/fv-wordpress-flowplayer\";s:4:\"slug\";s:23:\"fv-wordpress-flowplayer\";s:6:\"plugin\";s:38:\"fv-wordpress-flowplayer/flowplayer.php\";s:11:\"new_version\";s:10:\"7.3.12.727\";s:3:\"url\";s:54:\"https://wordpress.org/plugins/fv-wordpress-flowplayer/\";s:7:\"package\";s:66:\"https://downloads.wordpress.org/plugin/fv-wordpress-flowplayer.zip\";s:5:\"icons\";a:3:{s:2:\"2x\";s:76:\"https://ps.w.org/fv-wordpress-flowplayer/assets/icon-256x256.png?rev=1085518\";s:2:\"1x\";s:68:\"https://ps.w.org/fv-wordpress-flowplayer/assets/icon.svg?rev=1085604\";s:3:\"svg\";s:68:\"https://ps.w.org/fv-wordpress-flowplayer/assets/icon.svg?rev=1085604\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:78:\"https://ps.w.org/fv-wordpress-flowplayer/assets/banner-772x250.png?rev=1668464\";}s:11:\"banners_rtl\";a:0:{}}s:9:\"hello.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:3:\"1.6\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/plugin/hello-dolly.1.6.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:63:\"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=969907\";s:2:\"1x\";s:63:\"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=969907\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:65:\"https://ps.w.org/hello-dolly/assets/banner-772x250.png?rev=478342\";}s:11:\"banners_rtl\";a:0:{}}}}','no'),(143,'recently_activated','a:0:{}','yes'),(144,'widget_widget_fvplayer','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(145,'fv_player_email_lists','a:1:{i:1;a:6:{s:10:\"first_name\";b:1;s:9:\"last_name\";b:0;s:11:\"integration\";b:0;s:5:\"title\";s:21:\"Subscribe to list one\";s:11:\"description\";s:39:\"Two good reasons to subscribe right now\";s:8:\"disabled\";b:0;}}','yes'),(146,'_transient_timeout_plugin_slugs','1552946257','no'),(147,'_transient_plugin_slugs','a:3:{i:0;s:19:\"akismet/akismet.php\";i:1;s:38:\"fv-wordpress-flowplayer/flowplayer.php\";i:2;s:9:\"hello.php\";}','no'),(148,'fv_player_mailchimp_lists','a:0:{}','yes'),(151,'fv_flowplayer_checker_queue','a:0:{}','yes'),(152,'theme_mods_twentyseventeen','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(153,'_transient_is_multi_author','0','yes'); /*!40000 ALTER TABLE `wpwh_options` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwh_postmeta` -- DROP TABLE IF EXISTS `wpwh_postmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwh_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=29 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwh_postmeta` -- LOCK TABLES `wpwh_postmeta` WRITE; /*!40000 ALTER TABLE `wpwh_postmeta` DISABLE KEYS */; INSERT INTO `wpwh_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default'),(3,5,'_wp_attached_file','2019/03/espresso.jpg'),(4,5,'_wp_attachment_metadata','a:5:{s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:4:\"file\";s:20:\"2019/03/espresso.jpg\";s:5:\"sizes\";a:5:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:20:\"espresso-150x150.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:6:\"medium\";a:4:{s:4:\"file\";s:20:\"espresso-300x180.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:180;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:12:\"medium_large\";a:4:{s:4:\"file\";s:20:\"espresso-768x461.jpg\";s:5:\"width\";i:768;s:6:\"height\";i:461;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:5:\"large\";a:4:{s:4:\"file\";s:21:\"espresso-1024x614.jpg\";s:5:\"width\";i:1024;s:6:\"height\";i:614;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:32:\"twentyseventeen-thumbnail-avatar\";a:4:{s:4:\"file\";s:20:\"espresso-100x100.jpg\";s:5:\"width\";i:100;s:6:\"height\";i:100;s:9:\"mime-type\";s:10:\"image/jpeg\";}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'),(5,5,'_starter_content_theme','twentyseventeen'),(6,5,'_customize_draft_post_name','espresso'),(7,6,'_wp_attached_file','2019/03/sandwich.jpg'),(8,6,'_wp_attachment_metadata','a:5:{s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:4:\"file\";s:20:\"2019/03/sandwich.jpg\";s:5:\"sizes\";a:5:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:20:\"sandwich-150x150.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:6:\"medium\";a:4:{s:4:\"file\";s:20:\"sandwich-300x180.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:180;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:12:\"medium_large\";a:4:{s:4:\"file\";s:20:\"sandwich-768x461.jpg\";s:5:\"width\";i:768;s:6:\"height\";i:461;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:5:\"large\";a:4:{s:4:\"file\";s:21:\"sandwich-1024x614.jpg\";s:5:\"width\";i:1024;s:6:\"height\";i:614;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:32:\"twentyseventeen-thumbnail-avatar\";a:4:{s:4:\"file\";s:20:\"sandwich-100x100.jpg\";s:5:\"width\";i:100;s:6:\"height\";i:100;s:9:\"mime-type\";s:10:\"image/jpeg\";}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'),(9,6,'_starter_content_theme','twentyseventeen'),(10,6,'_customize_draft_post_name','sandwich'),(11,7,'_wp_attached_file','2019/03/coffee.jpg'),(12,7,'_wp_attachment_metadata','a:5:{s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:4:\"file\";s:18:\"2019/03/coffee.jpg\";s:5:\"sizes\";a:5:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:18:\"coffee-150x150.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:6:\"medium\";a:4:{s:4:\"file\";s:18:\"coffee-300x180.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:180;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:12:\"medium_large\";a:4:{s:4:\"file\";s:18:\"coffee-768x461.jpg\";s:5:\"width\";i:768;s:6:\"height\";i:461;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:5:\"large\";a:4:{s:4:\"file\";s:19:\"coffee-1024x614.jpg\";s:5:\"width\";i:1024;s:6:\"height\";i:614;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:32:\"twentyseventeen-thumbnail-avatar\";a:4:{s:4:\"file\";s:18:\"coffee-100x100.jpg\";s:5:\"width\";i:100;s:6:\"height\";i:100;s:9:\"mime-type\";s:10:\"image/jpeg\";}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'),(13,7,'_starter_content_theme','twentyseventeen'),(14,7,'_customize_draft_post_name','coffee'),(15,8,'_customize_draft_post_name','home'),(16,8,'_customize_changeset_uuid','dbf8f58f-37da-4ba0-86f7-a6e435ab3572'),(17,9,'_thumbnail_id','6'),(18,9,'_customize_draft_post_name','about'),(19,9,'_customize_changeset_uuid','dbf8f58f-37da-4ba0-86f7-a6e435ab3572'),(20,10,'_thumbnail_id','5'),(21,10,'_customize_draft_post_name','contact'),(22,10,'_customize_changeset_uuid','dbf8f58f-37da-4ba0-86f7-a6e435ab3572'),(23,11,'_thumbnail_id','7'),(24,11,'_customize_draft_post_name','blog'),(25,11,'_customize_changeset_uuid','dbf8f58f-37da-4ba0-86f7-a6e435ab3572'),(26,12,'_thumbnail_id','5'),(27,12,'_customize_draft_post_name','a-homepage-section'),(28,12,'_customize_changeset_uuid','dbf8f58f-37da-4ba0-86f7-a6e435ab3572'); /*!40000 ALTER TABLE `wpwh_postmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwh_posts` -- DROP TABLE IF EXISTS `wpwh_posts`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwh_posts` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_author` bigint(20) unsigned NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_title` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_excerpt` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'publish', `comment_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', `ping_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', `post_password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `post_name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `to_ping` text COLLATE utf8mb4_unicode_ci NOT NULL, `pinged` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `guid` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT '0', `post_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`ID`), KEY `post_name` (`post_name`(191)), KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), KEY `post_parent` (`post_parent`), KEY `post_author` (`post_author`) ) ENGINE=MyISAM AUTO_INCREMENT=14 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwh_posts` -- LOCK TABLES `wpwh_posts` WRITE; /*!40000 ALTER TABLE `wpwh_posts` DISABLE KEYS */; INSERT INTO `wpwh_posts` VALUES (1,1,'2019-03-17 21:29:19','2019-03-17 21:29:19','\nWelcome to WordPress. This is your first post. Edit or delete it, then start writing!
\n','Hello world!','','publish','open','open','','hello-world','','','2019-03-17 21:29:19','2019-03-17 21:29:19','',0,'https://steelseriesfans.com/wp/?p=1',0,'post','',1),(2,1,'2019-03-17 21:29:19','2019-03-17 21:29:19','\nThis is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:
\n\n\n\n\n\n\n\nHi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)
...or something like this:
\n\n\n\n\n\n\n\nThe XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.
As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!
\n','Sample Page','','publish','closed','open','','sample-page','','','2019-03-17 21:29:19','2019-03-17 21:29:19','',0,'https://steelseriesfans.com/wp/?page_id=2',0,'page','',0),(3,1,'2019-03-17 21:29:19','2019-03-17 21:29:19','Our website address is: https://steelseriesfans.com/wp.
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Visitor comments may be checked through an automated spam detection service.
![](\"https://i0.wp.com/wptavern.com/wp-content/uploads/2019/02/Screen-Shot-2019-02-21-at-1.33.43-PM.png?ssl=1\")
![](\"https://i0.wp.com/wptavern.com/wp-content/uploads/2019/02/Screen-Shot-2019-02-20-at-6.30.27-PM.png?ssl=1\")
![](\"https://i0.wp.com/wptavern.com/wp-content/uploads/2019/02/Screen-Shot-2019-02-20-at-12.19.12-PM.png?ssl=1\")
![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/02/Screen-Shot-2019-02-20-at-12.30.11-PM.png?ssl=1\")
![](\"https://i2.wp.com/wptavern.com/wp-content/uploads/2019/02/Screen-Shot-2019-02-19-at-2.26.36-PM.png?ssl=1\")
![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/02/Screen-Shot-2019-02-19-at-2.25.49-PM.png?ssl=1\")
![](\"https://i1.wp.com/wptavern.com/wp-content/uploads/2019/02/amazon-plugin-for-wp.png?ssl=1\")
![](\"https://i2.wp.com/wptavern.com/wp-content/uploads/2019/02/JS-for-WP-conf-2019.jpg?ssl=1\")
![a screenshot of my first paid web gig](\"https://topher1kenobe.com/wp-content/uploads/2015/02/cornerstone_college_website_lynx.png\"){kind=link}