In most cases, the WordPress plug-in works well on almost all hosts. However, the plug-in may duplicate the functions provided by the management host (hinder work), or reduce performance. The plug-in contains security vulnerabilities or is considered a medium of spam. As a result, many hosts (and most WordPress hosting companies) have a list of disallowed plug-ins. That is, there is a list of plug-ins that are completely blocked or seriously not recommended. If you know which plug-ins to avoid from the beginning, you don’t need to fix complex websites. Or fight the host on this issue. In addition, you don’t have to face the problem of finding and using plug-ins to replace plug-ins or required functions that are already in use by the web host.
It is not possible to include all WordPress hosts in the list of management hosts in this post. However, if there is a list of disallowed plug-ins, we will include as many top ranked and most popular companies as possible. For example, SiteGround and cloudway provide optimized hosting for WordPress, but do not publish a list of disallowed plug-ins. The following hosts are included in this list: You can press the Kingstar pagely WP engine host of the flywheel, gate Blue Host Dadi. Note: not allowed does not mean bad. Before migrating to the plug-in itself, I want to make it clear that this is not a bad plug-in. Usually not, which means that the host may conflict with the services provided or duplicate within the managed ecosystem. If there is no list of disallowed plug-ins on the host, the operations performed by these plug-ins are good choices. Not allowed only in the context of these hosts.
The least frequently allowed plug-ins and plug-in types usually have all categories of disallowed plug-ins (backup, cache, etc.). There are also many specific plug-ins that are not allowed on most hosts. Let’s take a look at some of the plug-ins and plug-in types that continue to appear in this list. Note: the list of plug-ins and hosts that do not allow this plug-in are incomplete. The idea is to provide how often plug-ins are blocked. We have done as much as possible to ensure that it is as complete as possible. Backup plug-ins typically include backups in managed schedules. The backup plug-in may consume a lot of resources, so it may slow down the website (or switch to offline), and disk space may be consumed by large files. In addition, some backup plug-ins do not know how to find the site root path that may vary from host to host.
These backup plug-ins are often the least allowed. Backupbuddy: flywheel, kinsta, pagely not allowed backupwordpress: flywheel, pagely, WP engine not allowed backup: flywheel, kinsta, pagely not allowed simple backup: BlueHost, Hostgator, pagely not allowed replacement? You should be able to a backup of the host instead of creating another backup using the WordPress plug-in. Alternatively, use a backup plug-in stored offsite (executed on vaultpress). During the backup process, site performance may degrade, but at least it will not affect storage. Many management hosts include regular backups as part of the management pack.
Similar to the caching and performance plug-in backup plug-ins, most hosts handle caching at the server level, so there is no need for caching or performance plug-ins. If you think the caching plug-in is only helpful for performance, so using it, will you be better than one? under these circumstances,
No- Plug ins may interfere with server-side caching. This can seriously degrade website performance. Here are some cache \/ performance plug-ins that are not normally allowed: W3 total cache: flywheel, goddy, pressable, WP engine does not allow WP fastest cache: goddy does not allow, clickable WP super cache: flywheel, goddy, pressable, WP engine does not allow replacement?
You may not need a dedicated caching plug-in, but if you have a plug-in to use for other functions, you can turn off caching. For example, WP rocket and W3 total cache can handle important tasks that you don’t want to miss. It can be used for analysis, image management and CDN integration. However, it may be better to use a dedicated plug-in than a post disallowed plug-in. This type of related post plug-in will automatically allocate related posts by relying on a large number of MySQL queries every time the page is loaded. This may damage the database and slow down the website. Managed word press hosting is about the best performance and strictly controlled environment, so this kind of database adjustment often means that there is no space for external plug-ins.
The following are related plug-ins that are often not allowed by the host: Context related posts: flywheel, goddy and WP engines are not allowed to forward SEO Boosters: BlueHost, goddy, Hostgator and WP engines are not allowed to send similar posts: are flywheel and WP engines not allowed to be replaced? It is recommended to use external services, such as contextly, jetpack related posts or word press related posts, rather than these related post plug-ins. The security plug-in is managed by WordPress and can provide the configuration required for security. Now you can find a security plug-in that adds another layer of protection. However, you may overuse the server and inflate the site’s database, slowing down the site. The host may not allow these plug-ins, but may frown.
In many cases, the following security plug-ins are not recommended for hosts: Cleantalk: flywheel causes frustration HC custom WP admin URL: BlueHost, Hostgator does not allow ithemes security: does flywheel have frustration replacement? Good safety best practice is on the way here. Ensure that plug-ins and themes are up-to-date, and strengthen operations such as passwords. If you need help, please read the article on how to perform WordPress security audit. Statistics plugins some hosts do not work on specific statistics plugins. If you send too many requests to the database, it will prevent site caching and reduce performance. Part of the managed hosting program usually provides excellent analysis at the server level, and such plug-ins are just interference. The following are the most disallowed statistical plug-ins:
Livestats: BlueHost, Hostgator do not allow statpress: BlueHost, goddy, Hostgator, pagely do not allow more disallowed plug-ins and plug-in types. These plug-ins will continue to appear in the list of disallowed plug-ins. Database manager: BlueHost, goddy, Hostgator, pagely disallowed link checker: BlueHost, flywheel, goddy, Hostgator, pagely, pressable, WP engine disallows mailit and send email from admin
Email plug-ins (including): pressable is not allowed, and most of them are not recommended. Database management plug-in wpdbspringclean: plug-ins not allowed by BlueHost, Hostgator and pagely. This section lists the plug-ins not allowed by each host. Some sections contain a simple list, while others divide the list into categories. Jump in.
Sometimes write the full name of the plug-in, and sometimes write the URL plug-in, such as W3 total cache (opposite to W3 total cache). If listed in this way https:\/\/wordpress.org\/plugins\/ You can add a string at the end and move it directly to the plug-in. Insert of flywheel is not allowed. The following insert or insert type is not allowed for flywheel: Most backup plug-ins: for example, backupbuddy, backupwordpress, and backwpup. Most cache and performance plug-ins: for example, batcache, nitropack, W3 total cache and WP super cache. For example, many link checker plug-ins, including broken link checker. Related post plug-ins: for example, context sensitive posts and similar posts. Security plug-ins (not recommended): for example, cleantalk and ithemes security. The following are some points to know about plug-ins that are not allowed or recommended in flywheel:
Plug ins and themes using ioncube are not compatible with flywheel sites running PHP 7.4 or later Modify htaccess or WP config. Write to a PHP file or XMLRPC. Plug ins that require access to PHP (except jetpack) do not work. Not allowed to click the plug-in backup plug-in: not recommended. If the support team finds a problem, it will be deleted. If the customer support team finds a problem with the backup plug-in, disable and delete it. Better WordPress (BWP) reduced link checker plug-ins: broken link checker cache plug-ins: nginx helper, W3 total cache, WP fastest cache and WP super cache. Email plug-ins: for example, mailit and send email from admin. Hummingbird performance plug-in is not recommended. Plugins not allowed by BlueHost male BlueHost has a long list of disallowed plugins, which are not classified in any way other than alphabetical order. Isrug https:\/\/wordpress.org\/plugins\/ Remember, you can add it to the end and find the link directly. Administrator opposes broken link checker DBC backup dynamic related posts EZPZ one click backup file commander perge so boost Google XML Sitemaps with multisite support gosquared livestats HC custom WP admin URL suppress ALF simple backup simple word printing backup statpress overload statpress visitor statistics super slider Toolkit tracking statistics twitter mixer visitor statistics part VM backup VSF simple stats WordPress gzip compressed WP cache WP full backup WP database optimizer wpdbspringclean wpengine migration WP time machine GoDaddy disallowed plug-ins malebackup plug-ins: 6scan backup, EZP one click backup, The codetree backup and wponlinebackup cache plug-ins: W3 total cache, WP cachecom, WP fast cache, WP fast CA
Che, WP file cache and WP super cache performance plug-ins: Adsense click fraud monitoring, break link checker, Google sitemap generator and Google XML sitemap with musupport, and function replication plug-ins provided by goddy: 6scan protection, administrator, portable phpMyAdmin WordPress gzip compress and WP phpMyAdmin plug-ins with known security problems: note, infinite WP client, NextGen Gallery, mailpool, pipdig power pack, slice pop, toolpack, WP copysafe web, WP copysafe PDF, WP database backup, WP live support and plug-ins for real-time search and replacement of relevant posts: context related posts, fuzzy- SEO ALRP, like posts, WordPress phost posts, then other featured Posts plugin and then other related posts plugin statistical plug-ins: Jr refer, refer WP, stats, WP postview, WP power stats, WP stats and WP slimstat unnecessary plug-ins or plug-ins that do not work on GoDaddy websites: Hello Dolly, P3 profiler, sgcachepress, beta tester, synthers WP engine snapshot and wpengine common Hostgator disallowed plug-ins malehostgator’s long list of disallowed plug-ins is not classified in any way other than alphabetical order. Administrator automatic text imprinting backup broken link checker cache image against DBC backup dynamic related post EZPZ one click backup file commander firefighter forwarding – start Google XML Sitemaps with multi support gosquared livestats HC custom WP admin URL junior news tower imprinting no modification of portable phpMyAdmin report materials SA post simple backup simple statistics simple text imprint backup snapshot backup statistics statpress – reload statpress visitor statistics super slider toolkit total archive by Fotan full backup tracking statistics twitter brende visitor statistics part VM backup VSF simple stats problem press release backup WordPress gzip compression WP cache WP full backup WP database optimizer wpdb Springclean wpengine migration WP engine snapshot wpengine snapshot WP S3 backup WP time machine and other functions post plug-ins kingsta does not allow plug-ins male backup plug-ins: multi function WP migration, backupbuddy, backwpup, duplicator pro, snapshot, updraftplus Wpdb backup and wpdb backup production cache plug-in: cache enabler and Litespeed cache performance plug-in: improved word press minify, jch optimization, database optimization after revision deletion, P3 profiler and image optimization and video conversion plug-in based on word press gzip compression server: not allowed. Social media plug-ins: plug-ins not allowed on Facebook instant articles and Google amp pages of pageflog and Facebook open graph, Google + and twitter card tags. More views: allow PHP to run, dynamic parts, EXE
