Explore the world of essential plugins
Sep 01, 2023 pm 09:01 PMThe core of WordPress is packed with features, tools, and utilities, many of which help make WordPress the world’s number one content management system.
Most WordPress features are well known, such as custom post types, action and filter hooks, and the visual editor, but some of them are not necessarily as “well known” as others. In this article, we’ll discuss one of WordPress’s lesser-known (but very useful) features: must-use plugins.
What are the necessary plug-ins?
It’s not surprising that the must-use plugin feature is overlooked, since it was introduced in WPMU (WordPress Multi-User), and WPMU wasn’t integrated into WordPress Core until WordPress 3.0. At the time, a folder called mu-plugins
provided network administrators with the ability to activate plugins on every blog in the network. After merging in WordPress 3.0, the "mu-plugins" directory remains, with its name (according to the Codex) reinterpreted meaning "must-use plugins".
Main functions of must-use plug-ins
Must-have plug-ins each have their own advantages and disadvantages, let’s take a look:
They are always on: Essentially, must-use plugins are plugins that must be used and automatically loaded in your WordPress website (or web).
You cannot disable them: Even if you are an administrator, you cannot disable or remove plug-ins that must be used. However, you can delete them from the mu-plugins
directory (which, by the way, is under wp-content
). You can't install new plugins there either - you have to manually upload them to the directory.
They are loaded before normal plugins: mu-plugins
Plugins in the directory are loaded before plugins in the plugins
directory. Interestingly, the plugins that must be used are loaded in alphabetical order.
You can't use activation/deactivation hooks: This one is self-explanatory - since plugins that must be used are automatically activated and cannot be deactivated or uninstalled, you can't use activate or deactivate for them Use a hook.
They won’t update: mu-plugins
Plugins in the directory will not update automatically, and WordPress will not notify you of new versions. This means you mustmanually keep them up to date.
You must use PHP files: WordPress will not look at folders in the mu-plugins
directory - you must place PHP files in the root of that directory. No worries, though: you can create a proxy PHP file and then require
the main file in the plugins folder.
Ideas on where they could be used
Must-have plugins have many uses, whether they are clever, creative or just to save the world. Let’s take a look at some examples I can think of – if you have an idea, don’t forget to share it with us!
Must-use plug-ins for use on multi-site networks
Multisite networking is the reason the mu-plugins
directory exists, so I put this idea above the others.
While it may be a better idea to just use the Network Activation feature, if you need more features, there are must-have plugins. There are various differences between network-activated plugins and plugins that must be used (explained in this very old blog post), some of which may apply to your network.
Must-use plug-ins for use on the client website
If you grant (or must) access a customer's admin account, they may tend to use settings, theme options, plugins, and any other pages they have access to. When they try to deactivate (or worse, remove) certain plugins, they may be tempted to call you on a Saturday night and admit their guilt - or blame you for not maintaining the site.
If you move all plugin folders to the mu-plugins
directory and create a PHP file that requires the main files for these plugins, your client will not be able to deactivate these plugins. But be warned: you won't get automatic updates!
Using must-use plugins for site-specific plugins
This is my favorite must-have plugin use.
If your website requires some key functionality, the right thing to do is to create a website-specific plugin. Since you can't tolerate accidental deactivation of a site-specific plugin, you'd better move it to the mu-plugins
directory so even you can't disable it. And since you are a developer and you don't use the plugin anywhere else, there won't be any plugin updates.
in conclusion
In this article, I want to introduce you to one of the most underrated (and often unknown) features of WordPress. I was really shocked when I discovered the plugin I had to use, and I hope you are too. We definitely have must-have plugins in more areas than I can think of, but these alone can make a huge difference to your WordPress site.
Do you agree that the necessary plug-ins are useful? Can you think of more use cases for must-have plugins? Leave a comment below and let us know what you think. If you liked this article, don’t forget to share it with your friends!
The above is the detailed content of Explore the world of essential plugins. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

The main reasons why WordPress causes the surge in server CPU usage include plug-in problems, inefficient database query, poor quality of theme code, or surge in traffic. 1. First, confirm whether it is a high load caused by WordPress through top, htop or control panel tools; 2. Enter troubleshooting mode to gradually enable plug-ins to troubleshoot performance bottlenecks, use QueryMonitor to analyze the plug-in execution and delete or replace inefficient plug-ins; 3. Install cache plug-ins, clean up redundant data, analyze slow query logs to optimize the database; 4. Check whether the topic has problems such as overloading content, complex queries, or lack of caching mechanisms. It is recommended to use standard topic tests to compare and optimize the code logic. Follow the above steps to check and solve the location and solve the problem one by one.

Miniving JavaScript files can improve WordPress website loading speed by removing blanks, comments, and useless code. 1. Use cache plug-ins that support merge compression, such as W3TotalCache, enable and select compression mode in the "Minify" option; 2. Use a dedicated compression plug-in such as FastVelocityMinify to provide more granular control; 3. Manually compress JS files and upload them through FTP, suitable for users familiar with development tools. Note that some themes or plug-in scripts may conflict with the compression function, and you need to thoroughly test the website functions after activation.

Methods to optimize WordPress sites that do not rely on plug-ins include: 1. Use lightweight themes, such as Astra or GeneratePress, to avoid pile-up themes; 2. Manually compress and merge CSS and JS files to reduce HTTP requests; 3. Optimize images before uploading, use WebP format and control file size; 4. Configure.htaccess to enable browser cache, and connect to CDN to improve static resource loading speed; 5. Limit article revisions and regularly clean database redundant data.

TransientsAPI is a built-in tool in WordPress for temporarily storing automatic expiration data. Its core functions are set_transient, get_transient and delete_transient. Compared with OptionsAPI, transients supports setting time of survival (TTL), which is suitable for scenarios such as cache API request results and complex computing data. When using it, you need to pay attention to the uniqueness of key naming and namespace, cache "lazy deletion" mechanism, and the issue that may not last in the object cache environment. Typical application scenarios include reducing external request frequency, controlling code execution rhythm, and improving page loading performance.

The most effective way to prevent comment spam is to automatically identify and intercept it through programmatic means. 1. Use verification code mechanisms (such as Googler CAPTCHA or hCaptcha) to effectively distinguish between humans and robots, especially suitable for public websites; 2. Set hidden fields (Honeypot technology), and use robots to automatically fill in features to identify spam comments without affecting user experience; 3. Check the blacklist of comment content keywords, filter spam information through sensitive word matching, and pay attention to avoid misjudgment; 4. Judge the frequency and source IP of comments, limit the number of submissions per unit time and establish a blacklist; 5. Use third-party anti-spam services (such as Akismet, Cloudflare) to improve identification accuracy. Can be based on the website

When developing Gutenberg blocks, the correct method of enqueue assets includes: 1. Use register_block_type to specify the paths of editor_script, editor_style and style; 2. Register resources through wp_register_script and wp_register_style in functions.php or plug-in, and set the correct dependencies and versions; 3. Configure the build tool to output the appropriate module format and ensure that the path is consistent; 4. Control the loading logic of the front-end style through add_theme_support or enqueue_block_assets to ensure that the loading logic of the front-end style is ensured.

To add custom user fields, you need to select the extension method according to the platform and pay attention to data verification and permission control. Common practices include: 1. Use additional tables or key-value pairs of the database to store information; 2. Add input boxes to the front end and integrate with the back end; 3. Constrain format checks and access permissions for sensitive data; 4. Update interfaces and templates to support new field display and editing, while taking into account mobile adaptation and user experience.

robots.txt is crucial to the SEO of WordPress websites, and can guide search engines to crawl behavior, avoid duplicate content and improve efficiency. 1. Block system paths such as /wp-admin/ and /wp-includes/, but avoid accidentally blocking the /uploads/ directory; 2. Add Sitemap paths such as Sitemap: https://yourdomain.com/sitemap.xml to help search engines quickly discover site maps; 3. Limit /page/ and URLs with parameters to reduce crawler waste, but be careful not to block important archive pages; 4. Avoid common mistakes such as accidentally blocking the entire site, cache plug-in affecting updates, and ignoring the matching of mobile terminals and subdomains.
