[ad_1] WooCommerce has shipped version 5.5.2 as a follow-up to the forced security update that patched a SQL Injection vulnerability last week. The vulnerability impacted versions 3.3 to 5.5 of the WooCommerce plugin, as well as versions 2.5 to 5.5 of the WooCommerce Blocks feature plugin. The team created a patch for more than 90 releases, which was sent as a forced security update from WordPress.org, due to the potential severity of impact for millions of WooCommerce installations. Shortly after the automatic update rolled out, many store owners started reporting serious performance issues on both WordPress.org and GitHub. Some users reported database crashes after receiving the automatic security patch in 5.5.1. One user reported a painfully slow, endless query that was “crippling to our operations,” with similar reports on GitHub of this same query “causing the entire server to go down.” Those with a large number of products in their databases were impacted more frequently. “We run a fairly big DB – 17k products,” one user said. “This has been a nightmare.” Store owners affected by this issue had resorted to downgrading to the previous releases at WooCommerce’s recommendation. They shared temporary workarounds to disable the query while WooCommerce investigated the issue. The problem was reported so frequently that it became a high priority for the team to fix. A week ago, WooCommerce developer Adrian Duffell reported back that they had determined the cause was twofold: A slow SQL query used to retrieve the products that are low in stock. This SQL has been in WooCommerce for a number of releases. A REST API request, which executes this SQL query, is called more frequently in WooCommerce 5.5 than in previous versions. A combination of these factors was causing the degraded server performance when users updated to WooCommerce 5.5. A fix was released in WooCommerce Admin 2.4.4 three days ago, and the fix was also added to core today in 5.5.2. Users who had put workarounds in place are advised to remove them after updating to the latest release. Like this: Like Loading… [ad_2] Source link
Continue readingTag Archives: Issues
Major Revamp Coming to GitHub Issues – WP Tavern
[ad_1] This week GitHub unveiled new features that will be included in a total revamp of GitHub Issues, including project tables that are similar to spreadsheets, custom fields, a keyboard driven command palette, improved task lists, and issue forms. The new project table view is an alternative to project boards, allowing users to filter, sort, and group issues and pull requests. Project managers can customize the table with custom fields and saved views. GitHub is also making it easier to manage issues that include subtasks. Users can now add lists and the issue will automatically track the status with a progress indicator. Issues forms are now in beta for public repositories. Many open source projects currently use Markdown issue templates and encourage contributors to provide more details by removing the placeholder text and replacing it with their own. Maintainers can now set up YAML configured forms with required fields and instructions to better guide the process. The revamped Issues feature is being updated to provide a bridge between the planning tools and the problems the tools were created to solve. Mario Rodriguez, Head of Product for GitHub Enterprise, explained why they are evolving GitHub Issues in the beta announcement: As teams and projects grow, the way you work evolves. Tools that hard-code a specific methodology are too rigid and complex to flex to whatever the moment demands. Often, we find ourselves creating a spreadsheet or pulling out a notepad, just to have the freedom to think. But then our planning is disconnected from where the work happens and quickly goes stale. The WordPress project hasn’t yet moved away from Trac but most of Gutenberg development happens on GitHub. It’s also the most popular repository hosting site for WordPress theme and plugin authors. Contributors to these projects may soon see some of these features in action for personal accounts and organizations that opt into the beta. The new GitHub Issues is expected to be out of beta later this year. GitHub plans to bundle it for free, along with the new project planning capabilities, with its Free, Pro, Team, and Enterprise plans. Like this: Like Loading… [ad_2] Source link
Continue reading