Machete is a simple suite of tools that solves common WordPress annoyances using as few resources as possible. Machete doesn’t cover every single use case, but there is a huge amount of sites that would require less plugins if they used Machete.
All Machete tools have two things in common: they solve problems faced by many web developers and they do it using as few server resources as possible.
So far, Machete includes the following tools:
WordPress places a lot of code inside the
<head> tag just to keep backward compatibility or to enable optional features. You can disable most of it and save some time from each page request while making your installation safer.
Cookies & GDPR Warning
We know you hate cookie warning bars. Well, this is the least hateable cookie bar you’ll find. It is really light, doesn’t affect your PageSpeed score and plays well with static cache plugins.
Analytics and custom code
You don’t need a zillion plugins to perform easy tasks like inserting a verification meta tag (Google Search Console, Bing, Pinterest), a json-ld snippet or a custom stylesheet (Google Fonts, Print Styles, accessibility tweaks…).
The Google Analytics and Google Tag Manager tracking codes are PageSpeed optimized, GPDR friendly.
The maintenance mode that ships with WordPress is just a basic lock-down that is activated whenever you do a major update. With machete Maintenance Mode you can hide your unfinished page from visitors and search engines, give your clients a secure temporary access and lock your site without affecting your SEO.
Post & Page cloner
Adds a „duplicate“ link to post, page and most post types lists. Also adds „copy to new draft“ function to the post editor.
Social Sharing Buttons
Social sharing done the Machete way. The icons are made as a custom webfont embedded in a minified CSS file that only weighs 5.8KB. The sharing actions use each platform’s native share URL.
WooCommerce was designed to work for every possible use case, but that often leads to unexpected behavior. These simple fixes can improve the WooCommerce user experience by making it behave as clients expect.
- Upload the plugin files to the
/wp-content/plugins/machetedirectory, or install the plugin through the WordPress plugins screen directly
- Activate the plugin through the ‘Plugins’ screen in WordPress
- Configure each tool using the corresponding link on the Machete side menu
Doesn’t plugin X do that better?
Yes, but Machete does it well enough and is probably much lighter.
Is there any set-it-and-forget-it alternative to Machete?
Machete is meant to be used as a development suite. If you are looking for a simpler solution to cut out WordPress bloat, you should have a look at WordPress WPO Tweaks & Optimizations by Fernando Tellado.
Why does WordFence show a warning when I save my options?
Machete caches some of its options to files located in
wp-content\uploads\machete\to speed up loading. This is completely safe, but it’s not a normal WordPress behaviour and it might make plugins like WordFence raise a warning. Just whitelist the action, save again and you’ll be fine.
Why doesn’t Machete have an option to disable Gutenberg?
Like it or not, the WordPress Block Editor (codenamed Gutenberg) is here to stay. Instead of disabling Gutenberg, you should be focusing on updating you workflow to use it. If you need to disable Gutenberg during the transition, you should use the official Classic Editor plugin.
Þátttakendur & höfundar
“Machete” er opinn hugbúnaður. Eftirfarandi aðilar hafa lagt sitt af mörkum við smíði þessarar viðbótar.Höfundar
- Checked for compatibility with WordPress 6.1
- Added option to disable WooCommerce SKUs
- Added option to disable WooCommerce duplicate SKU check
- Fix: Corrected WooCommerce Settings bug
Fix: Corrected the bug that prevented the obsolete tracking code warning to be dismissed.
- Checked for compatibility with WordPress 6.0
- Cleanup module: Added option to disable WordPress search functions
- Cookies module: Complete rework to comply with GDPR. New styles and scripts.
- Tracking & code: Added Analytics 4 and Google Tag Manager support
- New WooCommerce module!
- Import/export module removed
- Powertools: Removed option to save with keyboard
- Tracking & code: Removed option to track CF7 forms
- Checked for compatibility with WordPress 5.5
- Changes to improve render on RTL languages
- Typo and grammar fixes, general proofreading of the English language (kudos @noplanman)
- Updated language files
- Tweak: prevented LastPass from loading on code fields (kudos @noplanman)
- Fixed: Fix HTML layout errors (kudos @noplanman)
- Style changes to adhere to WP Coding Style
- Fixed: social share links didn’t work on pages (kudos @davizoco for the heads up)
- Fixed: content of the individual post was returned empty if the social share module was active but no position was selected
- Fixed: Bundled translations weren’t being loaded
- Version push to include a file left out in the 3.4 commit (sorry)
- Complete rework of the social share module
- Added shortcode for the social share buttons
- Updated WhatsApp share URL
- Updated the option to remove the medium_large thumbnail size
- New share JS without jQuery
- New custom code editor interface (with tabs!)
- Refactored the import/export module
- Minor WordPress Coding standards fixes
- Fixed social share title that disappears if no placeholder
- Minor CSS fix
- New: remove generator tag from RSS feeds
- Fixed social share WhatsApp URL
- Updated description wp_generator also removes WooCommerce generator tag
- New Social Sharing Buttons module
- Lots of tiny changes to adhere to WordPress Coding standards
- Minor Gutenberg compatibility fixes
- Fixed the position of the admin notices on Machete admin pages
- Fixed WP-CLI Warnings (finally). Props to @angelfplaza and @oterox
- Improved Clone Module to make it work better with Gutenberg and complex page builders
- Fix: In some cases the clone module didn’t copy the featured image.
- Fix: In some cases the clone module could break the post metas.
- Maintenance URL whitelist made more restrictive by request. Only ‘wp-login.php’ and ‘wp-admin’ accepted now
- Changed the admin stylesheet handle to prevent HUGE SVG icons on update
- Urgent fix: Fixes typo that prevented the maintenance page from working properly.
- Improved the compliance of the code with the WordPress Coding Standards
- Made some interface changes. The redundant tab menu is gone, navigation is now made using the admin sidebar menu.
- Dropped the use of PHP sessions in the maintenance page. It uses session cookies now.
- New: New ‘Clone item’ button on the back-end admin bar to make the admin bar compatible with the Gutenberg interface.
- New: Added option to PowerTools to enable upload of SVG images
- Fix: Fixed ampersand escaping error in the code editor
- Fix: Typo in the Disabled REST API notice (props @carloslongarela)
- Fix: PHP 5.4 empty() syntax error. Do you realize Machete only supports PHP 5.6+? (props @luisrull and @Selupress)
- Added option to reduce Thumbnail JPEG quality
- Fix to allow HTML in the cookie warning text
- Added option to PowerTools to disable RSS feeds
- PowerTools fix
- Fixed a stupid PHP 5.4 bug (props @cheteronda)
Machete 3.1 is a completely new beast. Almost all the code has been rewritten, taking great care not to break existing sites. That is the reason version 3.0 wasn’t pushed to the WordPress directory, everything had to be tested thoroughly first.
- Added Contact Form 7 tracking to the Analytics & Code module
- Updated machete PowerTools
- Added option to Machete PowerTools to disable RSS feeds
- Refactor of Optimization module. Code is now lighter and faster.
- Added native WordPress code editor to the custom code module
- Added new designs for the cookie bar warning
- Deleted old icons
- Added option to remove Contact Form 7 refill scripts
- Fixed option to remove jquery-migrate to reduce compatibility issues
- New module structure, modules are lighter and more isolated now.
- New import-export module to backup and restore machete settings
- Huge code refactor
- Huge module cleanup
- Fix module management issues in about tab
- Fixed false ‘error saving to database’ notice