Fuse Hub AI

FuseHub Site

FuseHub Site is FuseHub’s own WordPress plugin. FuseHub installs it on the sites people build with FuseHub. It is not listed on wordpress.org; a plugin by that name there is not FuseHub’s.

What it does on your site

Its features follow what whoever built your site with FuseHub set up. It has no settings screen of its own.

  • Comments off. Visitors cannot leave comments, existing comments are kept but not shown, comment feeds are off, and WordPress’s Comments screen is hidden. Posts are closed to new comments.
  • Hover titles off. On your public pages, the small box of text that appears when the pointer rests on something, such as a link or an image, does not appear. The titles stay in your pages for search engines and screen readers.
  • If your site uses the Perfmatters plugin, its own “Disable Comments” setting follows FuseHub’s comments switch.
  • Your business details for search engines. If your site uses the Rank Math SEO plugin and Rank Math describes your business as a business (not as a person), FuseHub Site adds the area you serve and the services you offer to that description, and, on your services page if your site has one, a list of those services. It takes them from the business details FuseHub saved for your site. Search engines read these details; visitors do not see them.
  • A weekly clean-up of old revisions. WordPress keeps earlier saved versions, called revisions, of your pages, posts and other items, such as templates saved in WordPress’s site editor. Where FuseHub switched the clean-up on, WordPress keeps the newest 10 revisions of each (fewer if your site was already set to keep fewer; another plugin or your theme can set more) and deletes older ones each time it saves a new revision, and once a week FuseHub Site deletes any older ones still left, at most 500 each time. The copies WordPress saves by itself while someone is editing (autosaves) are left alone. A deleted revision is gone from your site. When FuseHub’s optimization pass switches the clean-up on, it first takes a backup of your site’s database, on the computer of whoever built your site with FuseHub; FuseHub takes no backup before the later deletions.

How it stays up to date

  • FuseHub’s updates come through WordPress’s normal updater, from updates.fusehub.ai.
  • Every update is signed by FuseHub: a signature is a mark that only FuseHub’s own signing key can make. While FuseHub Site is active, before WordPress unpacks an update it offers for it, FuseHub Site checks the signature with FuseHub’s key, which is built into the plugin, and checks that the file is exactly the one FuseHub signed. If anything does not match, it refuses the update, so someone who took over the update server could not use it to install their own code. FuseHub Site normally stays as it was; in rare cases, on a host where WordPress cannot check on itself, WordPress’s own recovery may put back an older copy of the plugin.
  • That check covers the updates WordPress itself offers for FuseHub Site, whether installed automatically or with “update now” on the Plugins screen, and nothing else. A FuseHub Site zip you upload yourself (“Upload Plugin”, even “Replace current with uploaded”), or a copy put on the server another way, is not checked: take FuseHub Site’s updates only through WordPress’s updates, and do not install a zip that reaches you by email or download.
  • FuseHub offers each new version first to a few sites it picks: its own, and sites it looks after for its clients. It offers it to other sites only from the seventh day after the day it signed it (days counted in UTC, the world’s standard clock), and only after checking that at least one of those sites runs it.
  • Where automatic updates are on for FuseHub Site, once a new version is offered to your site, WordPress installs it by itself the next time its scheduled update check runs, usually within a day, and emails your site’s admin address afterwards.
  • The notes of the version your site runs are under “View details” on the Plugins screen.
  • On the Plugins screen, people who can update plugins also see “FuseHub update check:” followed by a short value (or “no update code”), which whoever looks after your site can read back to FuseHub to confirm it has your site right. Beside it, “early-release site” means a new version is offered to your site before other sites, and “held by FuseHub” means FuseHub is holding your site back from new versions.
  • On a site with a local address, such as mysite.local, it asks for no updates.

Turning updates off, or removing it

  • To stop automatic updates: on the Plugins screen, under FuseHub Site, click “Disable auto-updates”. WordPress still shows you an update when there is one, and you can install it yourself with “update now”.
  • To stop everything it does, including every request to FuseHub: deactivate it. To remove it: delete it.
  • To stop only the weekly clean-up and keep the rest of FuseHub Site: delete the scheduled event named fusehub_site_weekly_cleanup, with a plugin that lists WordPress’s scheduled events, or ask whoever built your site with FuseHub. FuseHub Site itself never schedules it.
  • Once it is off or removed, comments and hover titles go back to how WordPress and your theme show them, except that posts closed to comments stay closed until someone reopens them. If you use Perfmatters, its own Disable Comments setting applies again, and FuseHub may have switched it on: check it in Perfmatters’ settings. Your business details go back to what Rank Math gives search engines on its own. The weekly clean-up stops, and WordPress keeps revisions as your site’s own setting says; revisions already deleted stay deleted, and the clean-up’s weekly entry stays in WordPress’s schedule and does nothing while the plugin is off, so if you switch FuseHub Site on again, the clean-up starts again. The plugin’s saved switches, the business details FuseHub saved for it, the update code FuseHub stored in your site (see fusehub.ai/site-plugin/privacy), and small markers on the posts it closed, stay in your database and do nothing without it.

Emails from WordPress

  • After each automatic update, WordPress emails your site’s admin address, listing FuseHub Site with its old and new version.
  • If FuseHub Site refuses an automatic update at install, WordPress emails once for that version to say the update failed. Your site normally keeps the version it had. An update list that does not check out when WordPress checks for updates is simply ignored: nothing is offered, and no email is sent. An update you install yourself with “update now” sends no email either.
  • These emails suggest the wordpress.org forums. For FuseHub Site, use the help below instead.

When updates stop

  • If FuseHub stops publishing updates, your site is offered nothing new within about a year and keeps working with the version it has.
  • Each copy stops asking FuseHub for updates three years after it was built, unless it has been updated to a newer copy first.
  • If your site cannot reach wordpress.org, WordPress does not ask FuseHub Site for updates either, so it gets none.

What it sends

Nothing that names your site. The details are at fusehub.ai/site-plugin/privacy.

Requirements

WordPress 7.1 or newer, and PHP 8.2 or newer. On an older PHP it shows a notice and does nothing else, which includes asking for updates. To take updates it also needs a 64-bit PHP, and a host where WordPress writes its own files directly; without them it takes no updates and keeps the version it has. It also refuses an update that needs a newer WordPress or PHP than your site runs.

Licence

GPL-2.0-or-later.

Help

contact@fusehub.ai. Please do not ask about FuseHub Site on the wordpress.org forums; it is not listed there.

If you build sites with FuseHub

These are the terms for FuseHub Site on the WordPress sites you build with FuseHub.

Automatic updates. FuseHub switches automatic updates on for FuseHub Site the first time a site’s optimization pass runs. You, or the site’s owner, can switch them off on the Plugins screen, and FuseHub does not switch them on again. While they are on, WordPress installs FuseHub’s updates for FuseHub Site by itself and emails the site’s admin address after each one. FuseHub decides what goes into each update and when it is offered. While FuseHub Site is active, an update WordPress offers for it installs only if FuseHub signed it; a FuseHub Site zip uploaded by hand, or copied onto the server another way, is not checked. The plugin’s requests do not tell FuseHub which of your sites has taken an update: look at each site’s Plugins screen.

The weekly clean-up deletes old revisions. A site’s optimization pass first takes a backup of the site’s whole database and keeps it on your computer, and only if that backup checks out does it switch on FuseHub Site’s weekly clean-up. The clean-up runs once straight away, then every week wherever the site is, and deletes old revisions (earlier saved versions) of the site’s pages, posts and other items, keeping the newest 10 of each (or as many as the site already keeps, if fewer); while it is on, WordPress also deletes older ones each time it saves a new revision. The copies WordPress saves by itself while someone is editing (autosaves) are left alone. Each backup holds every revision the site had when it was taken, whichever run later deletes it. A revision saved after the last of these backups is in none of them, and FuseHub takes no backup before the later weekly runs, nor when WordPress deletes revisions as a page is saved, so once such a revision is deleted it may be in no backup but the site’s own, if it has any. FuseHub keeps the latest five of these backups for each site and deletes older ones as it takes new ones, and restoring one puts the site’s whole database back as it was when it was taken. FuseHub’s Undo of an optimization run switches off a clean-up that run switched on, and does not put deleted revisions back. On a site already moved live, deleting the scheduled event fusehub_site_weekly_cleanup stops only the clean-up; deactivating FuseHub Site stops it while the plugin is off, and it starts again if the plugin is switched on again while that event remains. If the clean-up is switched on any other way than by the optimization pass, for example through FuseHub’s assistant, no backup is taken first.

After you hand a site over, or stop using FuseHub. FuseHub Site keeps working on the site and keeps taking FuseHub’s updates: nothing in it depends on a FuseHub account, or on your copy of FuseHub running. Its weekly clean-up keeps running too. FuseHub cannot see a handover happen, so tell the site’s owner about FuseHub Site when you hand the site over; FuseHub offers a handover note for that. If FuseHub stops publishing updates, each site is offered nothing new within about a year and keeps the version it has, and each copy of FuseHub Site stops asking for updates three years after it was built. The site’s owner can switch automatic updates off, or deactivate or delete FuseHub Site, at any time on the Plugins screen.

What stays on your computer. FuseHub keeps, on your computer, what it recorded about the sites you built with it, among them each site’s update code and the database backups above, which hold everything that was in the site’s database. FuseHub deletes the oldest of the backups it takes by itself as it takes new ones; nothing deletes the rest, or the update codes, when you stop using FuseHub.

FuseHub Site is free software under the GNU General Public License, version 2 or later. What it sends is at fusehub.ai/site-plugin/privacy.