EDITS.WS

Author: Sarah Gooding

  • Finding Freedom and Opportunity With WordPress: How Wolf Bishop Overcame Prison and Addiction to Launch a Career

    In 2005, Timothy “Wolf” Bishop was serving time in an Iowa prison for charges related to a gambling addiction.

    “When I was 25, I made a bet that I could not cover,” Bishop said. “I had gambled with a local thug on a local semi-pro baseball game between the Burlington Bees and the Clinton Lumberkings. I bet on the Bees, who lost the game without even scoring.

    “I did not have the $10,000 I had bet. When I told the man I owed this, he was less than happy. He put a gun to my head and told me that if I did not have his cash in one week, he would put a bullet in my brain. I had the money three days later.”

    It was the crimes Bishop committed to cover that debt that got him sent to prison. Now an experienced professional, entrepreneur, and educator, who has spoken at numerous WordCamps, he credits WordPress for changing the trajectory of his life and helping him find a place of stability.

    “It saved my life,” Bishop said. “I am not being over-dramatic when I say that. If it was not for WordPress, I would either still be in prison or dead.”

    During the time Bishop was incarcerated in Rockwell City, the Iowa Department of Corrections began allowing limited internet access to inmates, and he was fortunate enough to be in one of the select prisons. Writing a personal blog was one of the allowed activities, so Bishop went on the hunt for a blogging platform to use. He had already tried many of them, as he had been into open source software since the mid-90’s.

    “As I was also fighting to overcome my gambling addiction, I had the idea of starting a blog about my experience as a sort of self-therapy,” he said. “I tried TypePad first, but did not like it. Less than a month later, I discovered WordPress thanks to a correctional officer who had a blog of her own.”

    Wolf Bishop in prison in 2005, Rockwell City, IA

    The officer had maintained a blog for the past several months and recommended to Bishop that WordPress would be the easiest and best for his needs. This was in the summer of 2005, just a few months after WordPress 1.5 was released with a new “Pages” feature, a better templating system, and the Kubrick default theme.

    “I was at a point in my life when I knew that I needed to change, and drastically, or I was going to be in prison for the rest of my life, or worse….dead,” Bishop said. “I know that sounds over dramatic, but I swear it is true. I hoped that by blogging about my battle with addiction, I could better overcome it.”

    His first blog launched in September 2005, and he posted weekly for just over one year.

    “Prison is a place where hope is in low supply,” Bishop said. “You have to watch your back every minute of every day. Before WordPress, I got in a ton of trouble in prison. I spent a lot of time in the hole. I had nothing to focus my time or energy on, so I fought and walked around with a giant chip on my shoulder.”

    At one point he realized that he needed to change if he wanted to survive, get out of prison, and stay out of prison, but he was struggling with how to make this happen. Bishop attended Gamblers Anonymous (GA) but described himself as a somewhat shy person and found it difficult to open up to other people in the group.

    “You cannot effect change until you open up,” he said. “So when I found WordPress I was able to remain somewhat anonymous, and that made it easier to open up. I could write about my struggles and my feelings. I had some place safe to vent my fears and frustrations and anger. I had a safe space to process childhood trauma and self-destructive thought patterns.”

    In January 2007, Bishop was released from prison and went into a work release program. These kinds of programs have employment requirements and have been shown to lower the recidivism rates among prisons.

    “It was then that I discovered how difficult it is to overcome the stigma of being a felon,” he said. “No matter how much I wanted to do better and succeed, it proved to be more challenging than I expected. Within three months I was sent back to prison for a parole violation after losing my minimum wage job.”

    Bishop, who describes himself as “a pretty intense mix,” of being bi-polar and living with ADHD on the Autism spectrum, found it difficult in prison to manage the mental and emotional health issues that led him to a gambling addiction. Mental health resources for prisoners can be scarce, but blogging helped him find a way through.

    “I guess you could just call it personal talk therapy,” he said. “By writing about the experiences I had, being in prison, and how I was feeling, I was able to address my demons and work through the thought patterns that kept leading to destructive behaviors. I guess you could say it was more like a publicly accessible journal.”

    Launching a WordPress Career Fresh Out of Prison

    What Bishop learned in the work release program in 2007 about the challenges inmates face after prison became even more clear when he was finally released in 2010. Even though he had fully completed his sentence and was not on supervision, the challenges remained.

    “Every GOOD job I applied for shot me down the second they learned I was an ex-con,” Bishop said. “From 2010 until 2015, I struggled to get a job that would pay the bills. I worked dead end fast food and temp jobs.”

    In 2015, he and his wife were homeless with three small children living in a tent in Texas. It was this year that he was given the opportunity that launched his career in WordPress. He was offered a support role at InMotion Hosting.

    “They took a chance on me and they paid for us to move to Virginia Beach,” Bishop said. “At first, we still lived in a tent and then a hotel. From there it was an upward trajectory and my career has continued to grow.”

    Wolf Bishop speaking at WordCamp Atlanta in 2018

    In the years following, Bishop has worked in various support roles and branched out into launching his own development and hosting companies. He is now on his fourth WordPress business, WP Octane, which follows two that failed and two that he successfully built and sold. WP Octane started in 2016 under the name WP Top Hat, and was geared towards being a 1-stop WordPress shop.

    “The idea was to have a company that provided everything a business needed for its online presence,” Bishop said. “But trying to provide managed hosting, ongoing care, content management, marketing, SEO, and several other services proved to be more than I could handle on my on.”

    In 2019, just before the pandemic hit, he decided to convert to just a managed WordPress host with ongoing care plans included, and changed the name to WP Octane. For the next two years his small startup struggled to thrive during the pandemic, although he did see some growth.

    “Finally, in early 2022, WP Octane became profitable for the very first time,” Bishop said. “Since then we have continued to grow, albeit slowly.”

    In late 2022, after investing more into infrastructure, WP Octane pivoted again to offer low cost shared WordPress hosting that serves a middle of the road between shared and managed.

    “We limit tenancy of all servers to a fraction of what most shared hosts have,” Bishop said. “We introduced features that allow us to outperform most shared hosts and come pretty close to matching performance of a managed WordPress host. We have virtually eliminated many of the typical pitfalls of shared hosting like the dreaded noisy neighbor syndrome.”

    WP Octane still offers fully managed plans with ongoing care included as they did previously, but the new shared platform has taken off better than Bishop expected and is now the company’s primary focus.

    Empowering Inmates and Ex-Convicts for Success with WordPress Skills

    Bishop is also now invested in giving back through a new effort to launch a prison program that will teach inmates the skills they need to use WordPress. The program is still in its early stages and has gotten preliminary approval from the Missouri Department of Corrections, which is local to where he now lives on 63 acres in the Ozarks. He is working on completing the curriculum, a requirement before it can be fully approved. The target for that phase is early August so it can go to a committee for approval at a September meeting.

    “It is this struggle that led me to start this project,” he said. “I want to give inmates that truly want to turn their lives around a skill that can enable them to do just that. If they learn how to work with WordPress, whether it be design, development, SEO, or any other area, they can avoid some of the challenges I faced.”

    Bishop said inmates equipped with WordPress skills will not be at the mercy of employers who are unwilling to give them a chance, because they have a skill they can use independently. If they go the route of custom development, most clients do not ask for a background check.

    “When participants complete the program and eventually get out of prison, they will have a portfolio that they can show to potential clients and even employers,” Bishop said. “It is my hope that it will increase their chances of success.”

    This is a first of its kind program that is still awaiting final approval. In the beginning he is aiming to launch it in the Missouri prison system but said he would love to take it nationwide some day.

    Bishop is also working on a related project – a website that lists employment opportunities with WordPress companies that are willing to give ex-offenders a chance. The project is still in the early planning stages as he talks with employers to encourage them to join this movement. His experience with this community has led him to believe that WordPress will be a beacon of hope and opportunity for anyone who wants to make something on the web.

    “WordPress helped me overcome addiction,” Bishop said. “It taught me the value of community and that if you are willing to put in the work, you do not have to rely on others to ‘let’ you succeed. WordPress lets you make success a choice.”

  • Gutenberg 16.0 Introduces Page Management in the Site Editor

    Gutenberg 16.0 was released today with page management now available inside the Site Editor. This is the first step towards a more unified experience of editing both content and design.

    Users can now create new pages and view page details in the sidebar, an experience that is very similar to editing a page in the block editor except it keeps the process inside the flow of design editing.

    video credit: Gutenberg 16.0 release post

    “This means you can practically build out a website without leaving the Site Editor, which speeds up the site creation process, makes it easier to see what the final result will look like, and reduces the overall cognitive load of switching between editors,” Automattic-sponsored core contributor Nick Diego said.

    This update to the Site Editor will be available in the upcoming WordPress 6.3 release, along with the Details block, which has been stabilized in Gutenberg 16.0 and is no longer under the Experimental flag. The implementation was scaled back to be more simple by including the summary as part of the block itself.

    The Command Center, created to be an extensible quick search for jumping to other pages or templates inside the editor, has come out of the experimental stage as well in Gutenberg 16.0. This is another major feature coming to core in the next release, and its API is also now public, opening the possibility for developers to create custom commands.

    A few other user-facing highlights in this release of the plugin include the following:

    Check out the release post for more details on all the enhancements, bug fixes, and tooling, accessibility, and performance updates included in Gutenberg 16.0.

  • WooCommerce Stripe Gateway Plugin Patches Security Vulnerability in 7.4.1

    Patchstack is reporting an Insecure Direct Object References (IDOR) vulnerability in WooCommerce Stripe Gateway, the most popular WooCommerce Stripe payment plugin with more than 900,000 active users. It was discovered by Patchstack researcher Rafie Muhammad on April 17, 2023, and patched by WooCommerce on May 30, 2023, in version 7.4.1.

    The security advisory describes the vulnerability as follows:

    This vulnerability allows any unauthenticated user to view any WooCommnerce order’s PII data including email, user’s name, and full address. The described vulnerability was fixed in version 7.4.1 with some backported fixed version and assigned CVE-2023-34000.

    It was assigned a high severity CVSS 3.1 score of 7.5 and added to the Patchstack database on June 13.

    The vulnerability affects versions 7.4.0 and below. Although the patch from WooCommerce has been available for two weeks, more than 55% of the plugin’s user base is running on versions older than 7.4 and it’s not clear how many 7.4.x users are on the latest version.

    The WooCommerce Stripe Gateway plugin’s changelog for version 7.4.1 includes two short notes and doesn’t elaborate on the severity of the security update:

    • Fix – Add Order Key Validation.
    • Fix – Add sanitization and escaping some outputs.

    Patchstack’s security advisory includes more technical details about underlying vulnerabilities fixed in this update. It is not yet known to have been exploited but store owners are encouraged to update to the latest 7.4.1 version as soon as possible.

  • WordPress Accessibility Day Secures Nonprofit Status for Annual Event, Calls for Speakers and Sponsors

    WordPress Accessibility Day, an independent 24-hour virtual conference, will return in 2023 – this time under an official non-profit status.

    The first edition of the event was hosted in 2020 by the WordPress core Accessibility Team. They wanted to manage it independently of the WordPress Foundation in order to reserve the option to do things like pay speakers for their time and expertise. The most recent 2022 event ran its finances through  WP Accessibility Day Board President Amber Hinds’ company, Equalize Digital, to expedite the process of getting started.

    The success of last year’s event, which drew 1,604 attendees from 52 countries, thanks to 28 sponsors and a 32-person volunteer crew, inspired organizers to keep pushing to make the organization a nonprofit.

    Through a fiscal sponsorship partnership with Knowbility, an Austin-based digital accessibility advocate and services provider, WP Accessibility Day has secured 501(c)(3) nonprofit status.

    “When I helped found this event in 2020, I already knew that our biggest challenge would be ensuring that the event wasn’t dependent on a single person to survive,” WP Accessibility Day Board Secretary Joe Dolson said. “Setting up as a non-profit and partnering with a larger organization helps us reach our goal of creating an event with a life of its own. Knowbility’s dedication to accessibility education makes them a great match for our mission.”

    This arrangement makes sponsorships and donations to the WP Accessibility Day event tax-deductible in the United States. Past sponsors include Cloudways, Gravity Forms, WP Engine, Yoast, GoDaddy Pro, Weglot, among other WordPress companies.

    The next WP Accessibility Day event is scheduled for September 27-28, 2023, and will feature a single-track that runs for 24 hours. It will also include live captioning and sign language interpreters. Organizers plan to publish the sessions following the event with transcripts and updated captions.

    Speaker and sponsor applications are already open, and speakers will be compensated with a $300 stipend per session. The deadline to submit an application as a speaker has been extended to June 18, 2023. Attendance is free via livestream.

  • WordPress.org Enables Commercial and Community Filters on Plugin and Theme Directories

    During the 2022 State of the Word, Matt Mullenweg announced a plan to add new “Community” and “Commercial” taxonomies for the theme and plugin directories that would help users more quickly ascertain the purpose of the extensions they are considering. Shortly after the announcement, instructions were published for theme and plugin authors to opt into the new taxonomies.

    The new filters are now enabled on both the theme and plugin directories, giving users the ability to quickly sort between free community extensions and those with commercial upgrades. Anything with a “pro version” should be designated as Commercial. These usually come with some upsells for more features than are offered in the free version. So far, the number of themes identified as commercial vastly exceed the number of community themes.

    In the Plugin directory, extensions designated as free are nearly equal those designated as commercial. Many of the most widely used plugins have already been identified as commercial, including Yoast SEO, Jetpack, Akismet, Elementor, WooCommerce, All-in-One WP Migration, and more. Examples of community plugins include the WordPress Importer, Classic Editor, Classic Widgets, Gutenberg, Performance Lab, and Debug Bar.

    In both directories it appears only a small percentage of authors have designated their extensions using the commercial or community taxonomies. At this time, use of the taxonomies is not required. This gave rise to some questions in the comments of the announcement.

    “Would a better classification system would be to just have either no label for the majority, and then something closer to ‘includes paid upgrades’ that just implies they also offer additional services on top of their free (and often fully functional) version?” WordPress developer Kevin Batdorf said.

    “All plugins are open source regardless of whether they sell something, and that doesn’t make those developers any less passionate about open-source. Nor does it imply non-commercial plugins have any less features, or that the level of dedication to support is any less dedicated.”

    Batdorf also asked if use of the taxonomies would be a requirement in the future, because, at the moment, their low usage could give some plugins an advantage under these new classifications.

    “Should it also be a requirement?” he said. “Otherwise this also seems like something to be gamed for visibility. Do Community or Commercial (or neither) plugins show higher install growth? I guarantee you people are tracking this already.”

    WordPress’ Meta team is seeking feedback on the current implementation. Automattic-sponsored contributor Steve Dufresne said “work is continuously underway to improve the browsing experience and refine the visual aspects of the Theme and Plugin Directory as part of the site redesign.” The new filters will be incorporated into the upcoming redesign changes that have been slowly rolling out across WordPress.org.

    These filters will also be making their way into the admin theme and plugin browsers, so users can access them from wherever they search for extensions. In the meantime, users and theme and plugin developers can leave feedback via Meta Trac on the specific tickets outlined in the announcement, as the team continues to iterate on the project.

  • WordCampers Demand Changes to Q&A Format

    Q&A segments at a live event are a valuable point of connection where attendees have the opportunity to gain the undivided attention of the speaker or panelist and get answers to important questions. Inevitably, people who abuse the format can lower the quality of the experience for everyone. A Twitter thread addressing this chronic problem is gaining momentum today following the conclusion of WordCamp Europe 2023.

    “One problem is that they often add very little value – although they’re supposed to achieve the opposite,” WordPress Core Committer Felix Arntz said. “Unfortunately, those who ‘ask’ are often telling stories, promoting themselves or their business, [or] mansplaining the speaker.

    “Sometimes they’re not even asking any question at the end which is ridiculous. If that is you, you may not even notice it, but you are seriously wasting people’s time, potentially harming the speaker, and preventing folks from actually learning something.”

    Arntz suggested that those asking questions longer than a minute should forego the Q&A time and ask the speaker informally at a later opportunity if it is relevant.

    “Just to clarify, while some of the issues apply especially to sessions with more exposure, like a Matt Q&A, they all also apply to any other session,” he said.

    “While these problems mostly occur due to individual folks in the audience, I think the WordCamp organization needs to take action to improve the situation as it’s been happening for years.”

    Arntz proposed a number of actionable ideas, including submitting questions to a central platform where they can be upvoted by community members, discarding lengthy questions, and providing mandatory training or documentation for emcees on how to handle problematic Q&A situations. He also noted that having questions in writing can assist non-native English speakers in understanding other non-native speakers.

    Arntz also contends that Q&A should be optional, depending on the speaker’s preference. This may also have the added effect of creating a more inclusive environment for speakers.

    “Particularly for new speakers, it can cause lots of distress or anxiety, especially because, as mentioned before, it very often isn’t questions but any of the aforementioned problems,” he said.

    “All of this can be another blocker for folks from underrepresented groups to even apply to speak, which came up in the session on women & non-binary folx of WordPress.

    “Making Q&A optional is a great and simple way to at least improve the latter issue while working on addressing all the other problems. It’s literally just a decision to make, so I urge the community and organizing teams to make it.”

    Arntz’s thread has received positive feedback and support, and other WCEU attendees have joined in with suggestions for improving the Q&A format.

    “Many other open source conferences use apps that do more with Q&A, rating speakers, and even helping attendees schedule networking,” GoDaddy Developer Advocate Courtney Robertson said. “The favorited events export to iCal/gCal.”

    Raymon Mens, a first-time-attendee at WCEU, said he was “negatively surprised by the Q&A part” for every session. “I would have preferred some more time for the speaker to go more in depth and not have a long Q&A that doesn’t add a lot.”

    Jon Ang, an organizer for WordCamp Asia, said he is taking Arntz’s feedback into consideration for their next event, and future global leads for WCEU said they are also discussing these ideas for next year.

    “At WordCamp San Francisco 2011 there was a Q&A session with Barry and it used a P2,” WordPress core committer Aaron Jorbin said. “For the off topic questions, others often chimed in. I think an MC with knowledge of the subject matter asking questions off this would be perfect.”

    Changes will likely originate from WordCamp organizers who can recognize the existing problems with the current Q&A format and depart from tradition with a better way of bringing quality questions to speakers who wish to entertain them. Getting Q&A right may also become a stronger priority as WordPress’ community team evolves the WordCamp format to promote adoption, training, and networking. Based on the feedback on Arntz’s Twitter thread, it’s past time to update the Q&A format and WordCampers are eager to see it happen.

  • WordPress Turns 20

    WordPress is 20 years old today, an estimable milestone for open source software running on the web. Parties are happening all over the world – in Geneva, Los Angeles, Istanbul, Bangkok, Lahore, Jakarta, Mumbai – in over 150 different locations.

    The software has been downloaded more than 2.8 billion times but the most impressive stat is the project’s staggering 112,000 contributors, past and present, who have improved and energized WordPress with their passion, talent, and hard work.

    None of the global collaboration we enjoy today would exist without the inspiration and leadership of co-founders Matt Mullenweg and Mike Little. They worked in a distributed way from day one, having never met when they started WordPress. This way of working created the foundation for a global contributor base that now supports 43% of the world’s websites.

    WordPress has had a profound impact on the lives of millions of users, giving them a voice on the web and the tools to launch businesses, create jobs, and bring ideas to life. The #WP20 hashtag is replete with stories of how WordPress and its community have given people a place of belonging and launched them into successful endeavors.

    Does WordPress have 20 more years in its future? Two of the biggest challenges ahead are capturing the hearts of the next generation of builders and maintainers, and preserving the open web where WordPress has thrived. The project’s 2022 annual survey showed that the respondent demographic is aging. The percentage of respondents under age 40 has decreased every year, as WordPress enters its third decade.

    Ensuring that WordPress remains resilient and relevant to future generations has required some courageous leadership decisions, like introducing the block editor, and may bring some significant shifts down the road, as we enter a new era of AI-powered innovation.

    Major milestones are are a good time to acknowledge the efforts that made all of this possible. Thank you, dedicated contributors, for lending WordPress a little bit of your fire and a lot of your patience, nurturing, and support. The code under the hood may look very different from the early days in 2003, but WordPress is still that same scrappy, irrepressible force of good on the web that users can count on for years to come.

  • WordPress and Drupal Co-Founders Discuss Open Source, AI, and the Future of the Web

    WordPress is celebrating its 20th anniversary tomorrow and recently its co-founders, Matt Mullenweg and Mike Little, joined Drupal founder Dries Buytaert together on stage at a private event for the first time on May 17. They discussed how their lives were influenced by open source and how they built their projects around the freedoms it guarantees.

    Founders of both projects expounded on the benefits of open source collaboration, and Buytaert characterized their continued improvements as an example of the flywheel effect, accumulating small wins that compound over time. They discussed the early history of WordPress and how something as seemingly insignificant as a comment on a blog can be the first step towards building a better future for the web.

    Mullenweg acknowledged that it may not be possible to reach everyone with open source philosophy so “at the end of the day you have to make the best user experience.” This has been WordPress’ path over the past 20 years, working in tandem with the power of its open source license and the freedoms that has enabled for the community.

    “I consider all proprietary software to be an evolutionary dead end,” Mullenweg said. They discussed how AI is changing the developer experience. Mullenweg is optimistic about AI working with open source and reiterated what he said recently on Post Status’ Slack:

    Open source and AI are the two mega trends of the next twenty years, and the reason they are complimentary is that GPT4 hasn’t read Shopify’s code. It’s read Drupal’s code and WordPress’ code, and all 55,000 plugins and everything else, so it can write it. If you ask it to write a website, it’s going to write it in an open source thing. It’s not going to write it in these propriety things. From an evolutionary point of view, if you go far enough into the future, someday we’ll see even our proprietary competitors – the Wix’s and Squarespace and Shopify’s of the world, actually running on open source software.

    That’s part of our vision with Gutenberg as well as why we made it an even more permissive license than the GPL. We dual-licensed it under the MPL so it could even be embedded in commercial applications, because I really think it’s so important that I want it to be in even commercial applications.

    Check out the video embedded below to hear this historic conversation between some of the pioneers of open source publishing on the web.

  • WordPress 6.2 Core Performance Analysis Finds Improving Template Loading for Classic Themes Could Make a Major Impact

    WordPress’ Performance Team has published a summary of a core performance analysis they completed in order to identify and prioritize areas for improvement. As part of this process, contributors created a methodology with a standard set of tools that can be used to collect and share profiling data for various components of the application.

    The team tested a classic theme (Twenty Twenty-One) and a block theme (Twenty Twenty-Three) configured with the Theme Unit Test data. They tested out of the box functionality, in addition to different scenarios such as a homepage displaying the latest posts, a basic text-only page, a page with a large set of images and default blocks, and a homepage and a basic page with translation.

    These tests uncovered numerous performance issues which the team has documented with related trac tickets and detailed in the summary of the findings. The first priority identified for improvement is template loading for classic themes.

    Although WordPress contributors are blazing forward on the project’s roadmap for the block editor, with most of the headline release features focused on site editing, block theme adoption is not where one might expect it to be more than four years after Gutenberg landed in core.

    “A majority of websites still use the classic theme architecture, so improvements made here could have the largest horizontal impact,” 10-up sponsored WordPress Core Committer Joe McGill said in the summary.

    McGill referenced data collected in April 2023 for the HTTPArchive which uses a query based on a new HTTP Archive custom metric to detect block theme adoption. Based on this information, improving template loading and rendering for classic themes should remain a high priority. Most of the WordPress-powered web is still running on classic themes.

    The summary highlights the improvements for template loading that would make the most impact:

    In the classic theme tested, the most expensive process is related to locating and rendering template parts. This starts with get_template_part(), includes the process of locating the template part files with locate_template(), and rendering the content for each template part. This whole process accounted for approximately 30–60% of the entire server response in the test results, with much of that time spent handling filesystem checks (e.g., file_exists() is responsible for 4–9% of all time measured and can likely be optimized with a cache), rendering widget blocks, etc. Given many of these filesystem checks aren’t likely to produce different outcomes often between requests, there are likely opportunities to find substantial improvements here.

    These improvements are the first of five priorities the Performance Team identified as the result of analysis. The second recommendation is to improve translation loading, as more than 56% of all WordPress websites are using translations.

    The other three priorities include improvements for block-powered sites, with the first two ringing up as the most costly operations in terms of performance:

    • Improve handling of block registration from metadata
    • Improve resolving block templates
    • Improve rendering of block widgets

    “These efforts will likely require additional research and architectural design before engineering begins,” McGill said. “All other items identified could be worked on directly through individual Trac tickets as capacity allows.”

    The Performance Team is considering making the tooling for performance profiling more broadly available so other contributors can extend their work. In the future, they may also consider contacting hosting companies to get them to run analysis on their infrastructure and examine additional use cases, such as PHP versions, Object Caching configuration, and more. Once the methodology used for this analysis is nailed down, future efforts to improve performance may become more frequent and easier to produce.

  • MariaDB Health Checks Plugin Now Available on WordPress.org

    A new MariaDB Health Checks plugin is now available on WordPress.org, thanks to the efforts of contributors involved in the 2023 CloudFest Hackathon which took place in Germany. MariaDB is a popular open source database used by those looking to further scale their websites, as it is generally faster than MySQL with better support for a concurrent number of connections.

    “At the moment it appears WordPress is dominating the PHP world, so this seemed to be the perfect target,” MariaDB Foundation Chief Contributions Officer Andrew Hutchings said about creating the plugin at the hackathon.

    “The MariaDB Foundation loves WordPress (I’m writing this post in WordPress right now) so it seemed like a logical project.”

    The plugin helps users debug their MariaDB databases by displaying important information, such as logs, locale, connections, character set and collation, and options. It also shows a graph of the number of queries and the execution time over the last 24 hours.

    The plugin also integrates with WordPress’ Site Health feature with two checks: an end-of-life check and a check for whether Histograms have been run. Histograms are an optimizer that can help improve MariaDB performance, and the plugin enables calculation of histograms to run on WordPress tables with the click of a button under the plugin’s Tools menu.

    “There are a few features now and it is a good framework to add more features to in future,” Hutchings said. “This is a community project and is open to suggestions and pull requests. This is a project that we at the MariaDB Foundation want to support in the future.”

    MariaDB Health Checks is developed on GitHub where developers can follow the plugin’s progress, contribute to new features, and report bugs.