Buy

Maintenance

Maintenance package

Experimental: Maintenance can fail and can cause damage on live servers. Always try it on a test system first to see whether and how it works before you use it on real websites. WebDonkey makes backups before it writes anything, but they do not replace your own test. In the app the page carries a red Experimental badge for this.

The Maintenance page (full name Website maintenance) sits in the sidebar under Remote. This is where you look after customer websites on your servers: create staging sites and local test copies, take changes from them over to live one object at a time, take extensions over, and have every website checked on a schedule (updates, vulnerabilities, files, appearance, flows), up to a monthly PDF report and a status page.

Anyone can use Fetch locally, Free included. Everything else belongs to the Maintenance package, an add-on that needs a coupled WebDonkey Premium license. What works in which plan is listed under Plans.

Page layout

On the left are your saved remote connections, on the right the tabs:

  • Websites: the looked-after websites of the chosen connection as cards, with the quota above them (Websites)
  • Fetch locally: bring a project folder and its database to this Mac (Fetch locally)
  • Reports: the monthly reports of all websites (Reports)
  • Status page: an HTML page with the state of your websites (Status page)
  • Settings: check times, the Wordfence key and the sender of the PDF reports (Settings)

Clicking a website card opens the website with the tabs Deploy, Updates, Security, Visual, Flows and Report. Deploy has the sections Environments, Changes, Extensions, History and Backups. In narrow windows, tabs and sections turn into a pick list.

What you can do here

Safety rules

Taking something over to a live site must never do anything wrong. So these rules are built into every run, not just printed as advice:

  • Live is only read while a staging site or copy is created. No step of the creation writes to the live folder or the live database.
  • Backup first: before every write, WebDonkey backs up the database and the files concerned and checks the backup. If it fails, nothing is written.
  • Detect, never assume: before every write, WebDonkey reads system, version and the installation's fingerprint again. If anything differs, it stops.
  • One action at a time: only one action runs per installation, across devices too.
  • Three-way comparison: only fields that changed in the source are taken over. If the target changed the same field itself, that is a conflict and stays locked until you decide.
  • Undo: every takeover can be taken back. The full backup is only the last resort.
  • Flow tests against live never order, pay, register or send a form. They stop before the buy button.
  • Confirmation: on a server with a red colour mark and for versions with the Preview badge you type the live domain before anything is written to live.

Systems and versions

System Deploy Checks, backups and fetching locally only
Shopware 6 6.6.1 to 6.7 6.4, 6.5 and 6.6.0 (no more security updates, no test server)
WordPress 6.0 to 7.1, single site Multisite
WooCommerce 8.0 to 11
Magento 2 Open Source 2.4.4 to 2.4.9 Adobe Commerce, Magento 1
Standard site files only
Laravel, Symfony, Drupal, TYPO3, unknown systems no deploy checks; fetching locally only without a database on the server

Newer or unknown versions, pre-release and development versions, and projects in a Deployer layout (current link to releases) get no staging and no takeover. When you add a website, WebDonkey shows its status: Tested, Preview (built but not fully tested yet: before every write to live you confirm once more) or Locked with the reason.

Limits

  • Checks run in WebDonkey on your Mac while it is on and WebDonkey is open. Whatever was missed runs at the next start.
  • Long steps on the server (staging, takeovers) keep running there when you close the window. The card shows the state when you come back.
  • A staging site always lives on the same server as the live site.
  • Deletions in staging or a copy are shown but never taken over.
  • Updates are only shown, never run on the live site.

Open the page: Maintenance.

Websites Maintenance package

The Websites tab shows the looked-after websites of the connection you chose on the left. A looked-after website is an installation on a server that WebDonkey knows: with system, version, fingerprint and live address. Only then are staging, takeovers and checks available. Adding websites needs the Maintenance package.

Add a website

  1. Click Add website. The button is off when every website of your quota is in use.
  2. Choose the Connection and the Project folder on the server (Choose…). Pick the folder of the whole project, not only the public folder. If the chosen folder looks like a public folder, WebDonkey suggests the project above it (Use parent folder). WebDonkey reads what lives there and changes nothing.
  3. The detection shows system and version with the status Tested, Preview or Locked, and below it PHP-CLI, Database, Database server, Free space, Missing tools and Layout. Warnings follow, for example when the database could not be reached from the server. Detect again reads once more.
  4. Document root (relative to the project folder): detected or chosen by you.
  5. Name and Live address (with http:// or https://).
  6. Add website.

With a live address, WebDonkey also adds an entry to the Monitor, in the project “Wartung”. It measures reachability for the report and the status page.

The detection keeps a fingerprint of the installation. Every writing action checks it again. If a different installation lives in the folder by now, the action stops and writes nothing.

The cards

Each card shows name and live address, and after the first check also updates and vulnerabilities (for example Up to date or No known vulnerabilities). Archived and Over the quota appear as badges. Clicking the name opens the website, All websites takes you back.

The website

At the top are system and version, with the Preview badge where it applies. The tabs:

  • Deploy: Environments (cards for Live, Staging and Local copy with address, folder, status and base state), Changes, Extensions, History and Backups. Standard sites have Files in place of changes, extensions and history. Systems without deploy show only environments and backups.
  • Updates, Security, Visual, Flows, Report: the checks of this website.

If the version is locked, it says Locked for this version: checks, backups and fetching locally only.

Quota

At the top of the tab you see … of … websites active with a bar. Active websites count; one website is one live target.

  • Archive frees the place. Reports and history stay readable. Reactivate brings the website back when the quota has a free place.
  • If there are more active websites than the quota allows (for example after moving to a smaller package), the most recently added ones are locked and the oldest stay active. Nothing is deleted. On a locked website, what is there stays visible and everything else is locked.

Delete

Only an archived website can be deleted. Delete “…”? removes it with its history, reports and saved states from this Mac. Nothing on the server is touched: deploy backups and a staging site stay there.

Staging Maintenance package

A staging site is a copy of the live site on the same server: its own folder, its own database, its own address. Personal data in it is replaced, mails and payments are defused, access is protected. You change and test there, then take the changes over to live one by one. It lives in Deploy › Environments on the Staging card. Staging needs the Maintenance package.

Prepare

In your hosting panel, create first:

  • a folder, new or empty, next to the live folder, never inside or above it
  • an empty database
  • an address of its own, such as staging.example.com. The live address is not allowed.

If the database user may create databases, WebDonkey offers Create database.

Create staging

  1. On the card, click Create staging….
  2. Fill in Staging folder on the server (Choose staging folder), Document root, Staging address, Database host (as the server sees it, often localhost), Port, Database name, User, Password and, if you like, Allowed IP addresses (optional). The password is stored encrypted on this Mac.
  3. Check: WebDonkey checks before it writes anything: Live installation unchanged, System supports staging, Staging address differs from live, Tools on the server, Database access works, Database exists, Database empty, Database is not the live database, Address reaches the folder, Enough space on the server, Rules for replacing personal data fit and Live database readable and dumpable. For the address, WebDonkey puts a test file into the folder, requests it through the staging address and removes it again. Anything that does not fit is shown with its reason; then Check again. If the live database cannot be read, set its access under Database access as when you fetch locally; WebDonkey then uses it here too.
  4. With All checks passed you see the tables the rules do not know and choose Empty, Replace personal data (pseudonymise) or Keep unchanged per table, plus Leave out orders if you want.
  5. Create staging.

The job runs on the server: Locking the website, Checking folder, database and address, Backing up, Copying files on the server, Exporting the database with personal data replaced, Importing into the staging database, Defusing (mails, payments, tasks, access), Checking the defusing, Proving that personal data are replaced, Recording the base state and Switching the staging live. You can close the window; the state updates when you come back. Cancel stops after the current step.

Options for Shopware 6

For Shopware 6 (6.6 and 6.7) the dialog shows these additional options:

  • Admin users in the staging: when it opens, WebDonkey loads the admin users of the live shop and lists them with tick boxes (username, name, email, the Admin badge, inactive). Default: all ticked. Only the ticked accounts come into the staging and log in there with their live password. The others are deleted in the copy, together with their roles and settings. Tick all restores the default. At least one account must stay ticked, otherwise the staging does not start. If the list cannot be loaded, all accounts come along; Load again tries once more. A refresh uses the same selection.
  • Addresses: the shop address, the sales channel domains and the media and CDN addresses that point to a host of the live shop are switched to the staging address. Images and files in the staging therefore come from the staging.
  • Licences: licence domain and shop secret of the store connection stay as in live. This way the store licences of your extensions keep working in the staging, and no second domain is needed at Shopware. WebDonkey never changes the licence domain, because Shopware would then delete the secret and the store logins. Whether using it in a staging falls under the terms of Shopware and the extension vendors is for you to check.
  • Send mails in the staging: off by default (recommended). The staging then sends no mail at all, neither from orders and forms nor from scheduled tasks or the queue. If you switch it on, the staging sends through the live shop's mail server. With personal data replaced, customer addresses are made up, but admin addresses are real. The mail settings of the live shop stay unchanged.

What never happens

  • Live is only read. The database is read with a consistent dump, the files are copied. No step writes to the live folder or the live database. WebDonkey still backs up the live database first.
  • Finished first, visible second. The copy is built in a work folder next to the target and only becomes visible once it is defused and checked. If a step fails, WebDonkey removes everything the job created.
  • Personal data is replaced (pseudonymised) during the export, not afterwards. Customers' names, email addresses, postal addresses, phone numbers and IP addresses are replaced or cleared; sessions, carts, payment tokens and logs are emptied. Record IDs, order contents and the accounts of administrators and shop managers remain. As proof, WebDonkey checks that no customer email address from live turns up in the staging site; otherwise it stays invisible.
  • Defusing: mails off, scheduled tasks and queues off, payment providers in test mode or without keys, access data of external services cleared (licence domain and shop secret of the store connection stay), apps and webhooks silenced, search index and Redis separated, search engines kept out. Every point is checked on its own. If one cannot be confirmed, the staging site stays invisible.
  • If links in the copy point out of the staging folder, WebDonkey stops, so the staging site cannot write into live or a shared folder.

Access

The staging site sits behind access protection: Basic Auth where the server allows it, otherwise a maintenance mode of the system that only lets the allowed IP addresses through. Access shows the Basic Auth user and password, Copy password puts it on the clipboard.

Refresh

Refresh… rebuilds the staging site from live. First WebDonkey compares the staging site with its base state and tells you how many changes have not been taken over to live and will be lost. Tick Back up the staging and replace it with a fresh copy of live. and click Refresh staging. The old staging site is backed up first.

Delete

Delete… empties the staging folder and the staging database on the server, but only if both carry the marker of this staging site. Live is not touched. If deleting fails, Remove from WebDonkey only removes the staging site from the list only. Deleting also works without the Maintenance package.

If WebDonkey was quit during a job, the card says at which step it stopped. Clean up removes what it left on the server.

Limits

  • Staging is available for Shopware 6, WordPress, WooCommerce and Magento 2 in the supported versions, not for Multisite, Deployer layouts or locked versions.
  • You create folder, database and address yourself in the hosting panel.
  • A website has at most one staging site.

Local test copy Maintenance package

The local test copy brings a looked-after website to this Mac: files and database, personal data replaced (pseudonymised), the configuration adapted to this Mac. Unlike Fetch locally, the copy belongs to the website and has a base state. That is why changes made in it can later be taken over to staging or live one by one. The test copy needs the Maintenance package.

Create the copy

  1. Open the website, Deploy › Environments, and on the Local copy card click Create local test copy.
  2. Fetch media files: uploads and product images can be large. Without them the copy runs, images are missing.
  3. If you like, Check tables: tables the rules do not know but which look like personal data. Per table choose Empty, Replace personal data (pseudonymise) or Keep unchanged, plus Leave out orders. Without the check such tables are emptied.
  4. If needed, Advanced › Database access, as when you fetch locally.
  5. Create copy. The same pre-check as for fetching locally runs first: on green the copy starts, on yellow after one more click, on red not at all.

The progress shows Read the project, Dump the database on the server, Download the dump, Download the files, Unpack the files, Create the local database, Import the dump, Make the copy safe, Add the site and Record the base state. Personal data is replaced on the server before the dump leaves it. If the server returns a dump that is not replaced, WebDonkey imports nothing.

Afterwards the card shows the copy's .test address with Open and Open in editor. The copy is also a normal site.

What the copy is like

  • Database access to the local database, mails to Mailpit, scheduled tasks off, access data of external services cleared.
  • Addresses rewritten to .test, in serialised data too, Redis and search service off.
  • Customers' names, email addresses, postal addresses, phone numbers and IP addresses are replaced (pseudonymised); sessions, carts, payment tokens and logs are empty. Record IDs, order contents and the accounts of administrators and shop managers remain.
  • The base state records what the live site looked like when it was fetched. That is how the comparison knows what you changed in the copy.

The copy also enables taking over extensions, the visual comparison Live/Local and flow tests against Local.

Remove

Remove deletes the site, its local database and its folder on this Mac. The live website is not touched.

Limits

  • A website has at most one local test copy.
  • If the website's version is locked for deploy, use Fetch locally instead.
  • Locally you need MySQL or MariaDB and Mailpit, ideally also the server's PHP version (under Services).

Take over changes Maintenance package

In the Changes section (website › Deploy) you compare a staging site or a local test copy with live and take over single objects: a product, a page, a menu. Only the fields that changed in the source are written. This is available for Shopware 6, WordPress, WooCommerce and Magento 2 and needs the Maintenance package.

Compare

  1. From: Staging or Local copy. Into: Live or Staging.
  2. Compare. WebDonkey checks both installations, reads source and target and fetches the changed objects.
  3. The list is grouped by kind of object. Search objects and Show filter it: To take over, All, New, Changed, Conflicts, Already the same, Locked, Deleted in the source.
  4. Clicking an object opens Fields of … in the side panel: Source and Target per field, plus Depends on.

Every row has a status: new, changed, already the same, conflict, locked (with the reason) or deleted in the source.

How the comparison decides

When a staging site or copy is created, WebDonkey records a base state: at that moment both sides are equal. Later it compares three values per field, base, source and target:

Source Target Result
as the base anything nothing to do
changed as the base can be taken over
changed same as the source already the same
changed changed differently conflict

You resolve a conflict in the side panel: Keep the value in the target or Force the source value. Forcing overwrites the target's change and needs a confirmation of its own per field. Undecide resets it.

  • Only changed fields are written, never whole objects.
  • Volatile fields such as stock, sales, ratings and counters, and environment fields such as addresses, domains and access data, are neither compared nor written. A new object gets the stock from the source.
  • If an object needs new objects, they come along (comes along). If a dependency is missing in the target or is locked itself, the object is locked.
  • If both sides created an object with the same key separately, that is a conflict, not a new object.
  • Deletions in the source are shown but never taken over.
  • On WordPress and WooCommerce, new objects in staging and copies get IDs far above those of the live site, so they keep their ID when taken over. If the ID has been used on live in the meantime, the object is locked.
  • On Magento, new CMS pages and CMS blocks get the next free ID on live when they are taken over. WebDonkey rewrites the references to them. If an object refers to an ID through a directive WebDonkey does not know, it is locked; refer to the object by its identifier instead.

Take over

  1. Tick the objects; the group's tick chooses all takeable objects of one kind.
  2. Take over … objects…
  3. The summary Take over changes lists objects and fields, what comes along, forced values and the rough duration. First a full backup of the target's database is made; without it nothing is written. On a server with a red colour mark (Production server) or the Preview badge you type the live domain.
  4. Take over.

The first time a website goes to live, the notice Pushing to live for the first time comes first: it says what is about to happen and that the backup is on the same server and does not replace a backup stored somewhere else. Only with the tick I am allowed to change this website and I check the plan myself. does Continue lead to the summary. The notice comes once per website.

The takeover locks the target against other actions, backs it up, writes and reads back, stores the state before for undo, copies files such as media along, and then checks the pages. It runs on the server; closing the window does not stop it.

The result shows how many objects were taken over, how the affected pages answer afterwards and whether anything reads back differently after writing. If a visual comparison is set up, See before and after shows the pages before and after the takeover. Undo takes the takeover back (Undo).

Safety rules

  • Contents are only taken over between equal versions: the same system version and the same versions of the extensions involved. Otherwise update first or take the extension over.
  • Before writing, WebDonkey reads the target's system, version and fingerprint again.
  • Exactly the plan you confirmed is run. In the target WebDonkey checks every precondition again; if anything changed since the comparison, nothing is written. Where the system allows transactions, nothing is ever half written.
  • Only one action runs on an installation at a time, across devices and apps too.

What is taken over

System Objects
Shopware 6 products with variants, translations, prices, media, properties, visibilities and categories; manufacturers, properties, snippets, shopping experiences, categories, landing pages, media, mail templates, theme configuration
WordPress posts, pages and custom post types with meta, terms and featured image; media, categories, tags and custom taxonomies, menus, customizer, widgets, selected settings such as title and tagline
WooCommerce in addition products (simple and variable), product categories and product attributes
Magento 2 CMS pages, CMS blocks, selected configuration values

Never taken over are, for example, customers, orders, carts, users, comments, coupons, subscriptions, payment and shipping methods, rules, flows and system settings outside the selection. For Magento, products and categories are not included yet. Standard sites are transferred file by file.

History and undo Maintenance package

The History section (website › Deploy) lists every takeover and every undo with direction, number of objects and status: taken over, stopped, undone, planned or running. read-back differs marks a takeover where something read back differently after writing. Backup before names the deploy backup made beforehand.

Take a takeover back

  1. Click Undo in the row (also right in the result of a takeover).
  2. The summary Undo takeover says how many objects get their values back and how many created objects are removed. As with a takeover, a backup comes first, and with a red colour mark or Preview you type the live domain.
  3. Undo.

How undo works

Before every write, WebDonkey stores the previous state of every field it changes on this Mac. Undo is a new takeover with exactly that state and the same preconditions:

  • A field only gets its old value back if the target still holds the value the takeover wrote. If someone changed it since, that is a conflict.
  • Objects the takeover created are removed. If they are in use in the target by now, WebDonkey writes nothing; if such an object has to go, the backup is the way.
  • Objects that cannot be checked stay as they are and are named.

Undo is the first way back, restoring a backup the last. A backup puts the whole database back, with everything that is new since.

Planned, stopped, interrupted

  • If a takeover is still running on the server, Resume brings it back into the window. A planned takeover that never ran is removed with Drop.
  • If WebDonkey was quit while a takeover started, check the target; the backup is then the way back.
  • If the state before is missing because it could not be stored, undo is not possible. Then the backup helps.

Without the Maintenance package

Undo stays possible after the package has run out. Safety comes before the license.

For standard sites, the undo of the last file transfer is in the Files section.

Take over extensions Maintenance package

In the Extensions section (website › Deploy) you take plugins, themes and modules over from a staging site or a local test copy. This is the safe way to update: update in staging or the copy, test and compare, then take over. It works for Shopware 6, WordPress, WooCommerce and Magento 2 and needs the Maintenance package.

Compare

Choose From and To: from staging or the local copy into live, or from the local copy into staging. The table shows Extension, Source, Target and Status:

  • New: only in the source
  • Newer: a newer version in the source
  • Same version, Older in the source, Only in the target
  • Not possible here: managed by Composer (deploy it via Composer then), a single-file plugin, or versions that cannot be compared

Not compatible and Compatibility unknown name the reason, such as the system version, PHP, WooCommerce or a missing parent theme. Compare again reads both sides once more.

Take over

  1. Click Take over… in the row.
  2. The dialog shows the version in the target (old to new), the target and the system's steps. For Magento it says the shop is in maintenance mode for a few minutes. For WordPress, Activate after taking it over decides whether the extension's activation code runs; without it the extension stays inactive.
  3. If it goes to live on a server with a red colour mark or with the Preview badge, you type the domain. If it is the website's first takeover to live, the notice Pushing to live for the first time comes first, once, with the tick I am allowed to change this website and I check the plan myself. and Continue.
  4. Take over.

What happens:

  1. Checking the installation…: system, version and fingerprint.
  2. Backing up the database and the folder…: the whole database and the extension's folder in the target, checked. Without a backup nothing is changed.
  3. Copying the new version next to the target…
  4. Swapping the folders. The old version moves out of the web root into WebDonkey's folder on the server, so old code does not stay reachable over HTTP.
  5. The system's step:
    • Shopware 6: plugin:refresh, install or update, clear the cache, compile the theme if the plugin has a storefront part.
    • WordPress and WooCommerce: swap the folder; WooCommerce updates its database if needed.
    • Magento 2: maintenance mode, setup:upgrade in safe mode, flush the cache; in production mode also compile and deploy static content.
  6. Checking the website…: if the website does not answer with success, WebDonkey tells you.

When something goes wrong

  • If the system's step fails, WebDonkey swaps the old folder back. The step may already have changed the database, though: Restore database backup… undoes that.
  • Magento then stays in maintenance mode until database and code fit again. After restoring, end it with End maintenance mode.
  • If the old state could not be fully restored, the details name the folders; manual work is needed then.

Leftovers of earlier takeovers

If folders of earlier runs still lie next to the extensions (Old version, Prepared copy, Failed new version), WebDonkey lists them under Leftovers of earlier takeovers. Clean up… moves old versions out of the web root into WebDonkey's folder and deletes prepared and failed copies.

Limits

  • No downgrades: if the target has a newer version, it keeps it.
  • Shopware: only plugins in custom/plugins, none managed by Composer.
  • The folder swap happens on the server; an extension from the local copy is uploaded first.

Deploy backups Maintenance package

Before WebDonkey writes to a looked-after website, it backs up the database and the files concerned on the server. You find these Deploy backups in the Backups section (website › Deploy) and in Remote backups as a section of their own, Deploy backups, apart from your manual and scheduled backups.

When backups are made

Occasion Entry
Creating staging (live database) Before staging
Refreshing staging (staging database and files) Before refreshing staging
Taking changes over or undoing them Before takeover
Taking over an extension (database and the extension's folder) Before extension
Restoring a backup (the state before) Before restore

Every backup is checked: the dump has to be complete, readable and not empty. If the server lacks space or the check fails, nothing is written.

Retention

  • The backups live on the server in WebDonkey's folder, not in the web root.
  • The newest 10 per website stay. The backup of the last takeover that was not undone always stays (Kept).
  • Also copy to this Mac puts every backup here as well.
  • If you archive or delete the website in WebDonkey, the backups stay on the server.

Every entry names the occasion, the environment (Live or Staging), the place (on the server, on this Mac), the database and the number of paths. A local copy is not backed up here; it is a site on this Mac.

Restore

To take back only one takeover, use Undo in the History first. Restoring puts back everything the backup holds.

  1. Click Restore… on the entry.
  2. Restore deploy backup reads the backup and counts what is new in the database since: orders, customers, reviews and comments. That is lost, as are all other changes since (products, content, settings).
  3. Confirm I understand that this data is lost.
  4. Restore.

Before restoring, WebDonkey backs up the current state as a deploy backup of its own. Files from the backup overwrite the files there; files added since stay. If putting the database back fails, it returns to how it was. If that fails too, the state before is in the backup Before restore.

Access data comes from the website's configuration; you do not need to enter anything.

Without the Maintenance package

Viewing and restoring backups also works without the package. Safety comes before the license.

Transfer files Maintenance package

Standard sites have no database. For them Deploy has the Files section: it transfers files between the project folder of a local site and the live folder. Only the plan you confirm runs, and every file is backed up before it is replaced or deleted. Transferring needs the Maintenance package.

Set up

  1. Local site: Choose a site. If you already fetched the website, the copy is at the top of the list. If there is no site, create one under Sites or fetch the website locally first.
  2. Live folder shows the folder on the server.
  3. Also leave out: folders or files, comma-separated, such as uploads, var/log. Some entries are always left out; they are listed below.
  4. Save. Change adjusts it later.

Transfer

  1. Choose the direction Local → Live or Live → Local and click Preview.
  2. The preview groups New, Changed, Renamed, Conflicts, Delete, Only in the target and Not transferable. Tick what should go (All, None).
    • Conflicts: changed or different on both sides. Ticked, the source version replaces the one in the target.
    • Delete: deleted in the source since the last transfer. Ticked entries are only deleted after a second yes.
    • Only in the target: never transferred. Kept unless ticked.
    • Not transferable: resolve these by hand.
    • Files changed only in the target stay as they are.
  3. Transfer… shows the summary: files, volume, deletions and conflicts taken over. On a server with a red colour mark or the Preview badge you type the live domain.
  4. Transfer. If deletions are due, Delete … entries on live? asks once more (Yes, delete).

If a preview would delete more than half of the target, WebDonkey asks Delete most of the target?. Usually the folder is wrong then.

On the first transfer of a pairing, files that differ on both sides are listed as conflicts; earlier deletions cannot be recognised.

Undo

Before anything is replaced or deleted, WebDonkey backs up the old version on this Mac (14 days). Under Last transfer, Undo… reverts the whole run: every file goes back to its backed-up version, new files are removed again. A file changed since then is left alone and reported. Undo also works without the Maintenance package.

Limits

  • Standard sites only. Shopware, WordPress, WooCommerce and Magento take contents over through Changes.
  • Lists are shortened to 5,000 entries. With every transfer ticked, the ones not shown go as well.
  • If a run is cancelled, what was transferred stays; the next transfer continues from there.

Updates Maintenance package

A website's Updates tab shows what is installed on the live site and what is newer. Updates are only shown here, never run on the live site. The safe way: update in staging or the local copy, compare visually, then take the extension over. Updates need the Maintenance package.

Check

The check runs at its check time (daily by default) while WebDonkey is open. Check now starts it right away and also matches the vulnerabilities. At the top you see Last checked … and the number of updates or Everything up to date.

The list is grouped: Core, Plugins, Themes, Apps, Modules, Composer packages and npm packages. Each entry shows the installed and the available version, the level Major, Minor or Patch, where useful Newest in this line: …, and inactive or development. Only with update hides what is current, Open details leads to the source.

Notes in a row: No update source, Unknown to the source, Updates come from the vendor, Query failed.

Where the versions come from

WebDonkey reads what is installed on the server, plus composer.lock and package-lock.json. It asks for new versions from your Mac:

Source For
wordpress.org WordPress core, plugins and themes
Update check of the site (vendor) premium plugins: what WordPress stored on the site
Shopware releases Shopware core
Shopware’s store check store plugins: Shopware's own check in the shop
Mage-OS mirror Magento
Packagist Composer packages
npm registry npm packages

Limits

  • For Magento, the version number does not show hotfixes and quality patches. Check Adobe's security bulletins as well.
  • Without database access, active states and the site's own update check are missing.
  • Checks only run while your Mac is on and WebDonkey is open. Whatever was missed runs at the next start.

The number of updates also shows on the website's card and in the report.

Security Maintenance package

A website's Security tab has two parts: Vulnerabilities of the installed versions and Files, the checksums of the files on the live server. Both need the Maintenance package.

Vulnerabilities

WebDonkey matches the installed versions on your Mac against public advisory databases: Packagist, OSV, npm, the Shopware releases and, for WordPress, Wordfence. The match runs at its check time (daily by default) and with Check now in the Updates tab.

Each finding shows the severity (Critical, High, Medium, Low, Unrated), fixed in … and Details. development dependency marks packages only used for development. If the Shopware security plugin is active, core vulnerabilities say Possibly fixed by the Shopware security plugin. The bell reports new open vulnerabilities as New vulnerabilities.

Wordfence key for WordPress

WebDonkey only matches WordPress core, plugins and themes with your own Wordfence Intelligence key. It is free with a wordfence.com account (Integrations). Without it, the Vulnerabilities part shows the field Wordfence Intelligence key: paste it and Save key. The same field is on the Settings tab of the Maintenance page, where you can also Remove the key. It is stored encrypted on this Mac and only sent to wordfence.com. Wordfence allows one download every 30 minutes.

Files

WebDonkey builds checksums of the files on the live server and compares them with the base at the check time (daily by default). The first check takes the base. Check now starts right away.

The result is OK, Changes, Suspicious or Failed, broken down into:

  • New executable files in upload folders and Changed executable files in upload folders: upload folders are not hashed; there WebDonkey reports executable files such as .php.
  • Differ from the official checksums, Not part of the official files, Official files missing: for WordPress core and plugins from wordpress.org.
  • New files, Changed files, Deleted files compared with the base.

The bell reports new findings as Maintenance: files.

Accept as new base turns the state of the last check into the base. Only do this when you know where the changes came from. Differences from the official checksums stay visible. After a takeover through Deploy, WebDonkey updates the base of the files concerned itself (Updated after a deploy).

Limits

  • The file check finds no skimmer in the database. Card skimmers in shops often hide in database fields such as configuration or CMS blocks.
  • For Magento, the version number does not show hotfixes; check Adobe's security bulletins as well.
  • Without a Wordfence key there is no match for WordPress itself, only a note.
  • In very full upload folders WebDonkey checks the first 5,000 executable files.

Visual comparisons Maintenance package

The Visual tab takes screenshots of chosen pages in several widths and compares them pixel by pixel. That shows whether an update, a takeover or something on the server changed the look. Visual comparisons need the Maintenance package.

Prepare

The screenshots are taken by your Google Chrome through a small browser module (puppeteer-core, axe-core and pixelmatch from npm, in fixed versions). If it is missing, the tab shows Browser module missing with Install. WebDonkey installs it once.

Set up pages

  1. Set up pages.
  2. Addresses: the Home page and up to ten more, as a path below the live address (/kontakt) or as a whole address of the live site. From the sitemap suggests addresses, Add address adds one.
  3. Widths: 375, 768, 1280 and 1920 pixels, in any combination.
  4. Areas to mask: one CSS selector per line, such as a clock or a changing teaser. It is painted black on every screenshot.
  5. Changed from (% of the pixels): below this share a page counts as unchanged, 0 to 10. 0 means every pixel counts.

Animations are switched off and common cookie banners hidden. Every page is taken twice; what already differs between both takes (sliders, adverts) is left out automatically.

Comparisons

  • Live earlier/now: against the base, by itself at the check time (weekly by default). The first comparison of live becomes the base.
  • Live/Staging and Live/Local: the same pages on staging or the local copy, once they exist.
  • Before/after taking over: with every takeover to live, by itself, once pages are set up.

Every run shows … of … changed. In the view you pick Width and View: Side by side, Fade or Difference. The status per image is Unchanged, Changed, Errors or Failed. Take as new base turns the latest live screenshots into the base.

Limits

  • Images of different Chrome versions are not compared. After a Chrome update, WebDonkey suggests taking the latest live screenshots as the new base.
  • Staging and the copy are captured at the same paths as live.
  • The website needs a live address.
  • The scheduled comparison only runs while your Mac is on and WebDonkey is open.

Flow tests Maintenance package

The Flows tab clicks through a website like a visitor: log in, search, fill the cart, go to the checkout. If a step does not go as expected, you see where and why. Flow tests need the Maintenance package.

Create a flow

  1. New flow from template… and pick a template:
    • Start page: for every system
    • Login and Search: for Shopware 6, WooCommerce, Magento 2 and WordPress
    • Cart and Checkout up to the buy button: for the shops
    • Empty flow: you build the steps yourself
  2. Name, Run against (Live, Staging or Local) and Schedule (On demand, Daily, Weekly, Monthly).
  3. Test login: User or e-mail and Password of a test account. Steps use it with {{login.user}} and {{login.password}}. It is stored encrypted on this Mac.
  4. Steps (1 to 50): Open page, Click, Fill in, Choose, Expect text, Expect address, Wait for element and Screenshot (optionally Whole page). Clicks and fields are found by CSS selectors. Add step appends one, Move up and Move down reorder, Remove step deletes one.
  5. Save.

Flows run in Google Chrome with a small browser engine (puppeteer-core). If it is missing, install it with Install engine.

Run

Run starts a flow right away; scheduled flows run on their schedule. Under Runs every run is listed with its target and status: Passed, Stopped, Failed or Not run. A run shows its steps, times and pictures. If a scheduled flow fails, the bell reports Flow test failed.

What never happens against live

Against the live site a flow stops before the buy button. WebDonkey never orders, pays, registers or sends a form there:

  • Ordering, paying, registering, contact forms and guest checkout steps are refused, in the flow and by the browser itself.
  • A login against the live site happens at most once an hour.
  • If a run halts at such a step, its status is Stopped.

Complete flows up to the order belong on the staging site or the local test copy.

Limits

  • Scheduled flows only run while your Mac is on and WebDonkey is open.
  • The templates use the system's standard storefront. With customised themes, check the selectors.

Report and monthly reports Maintenance package

For every looked-after website, WebDonkey sums up a month: reachability, SSL, backups, updates, vulnerabilities, changed files, takeovers and Lighthouse. You save the report as a PDF, with your own sender if you like, and send it to your client. Reports need the Maintenance package.

A website's Report tab

Choose the Month. The tiles show:

  • Reachability with a bar per day: Measured on … of … days · … outages
  • SSL certificate: … days left
  • Backups: successful, failed and those before deploys
  • Open updates and the version changes in the month
  • Vulnerabilities, Changed files
  • Pushes: applied, undone, failed
  • Lighthouse performance: Desktop and Mobile

Whatever was not measured honestly says not measured. Above the tiles it says where the figures come from: Frozen on the first of the following month, Computed from what is still stored or Figures so far, the month is not over yet. Save PDF stores the report as a file.

The Reports tab

The Reports tab of the Maintenance page lists the monthly reports of all websites, archived ones included. On the first of each month WebDonkey freezes the month before; if the Mac was off, it catches up at the next start. You save the PDF per month.

The PDF

The Maintenance report opens with a verdict (Good, Needs attention, Critical) and the key figures. Then follow reachability with day bars and outages, the SSL certificate, backups (scheduled, manual, before deploy), updates, vulnerabilities, file checksums, pushes and Lighthouse (performance, accessibility, best practices, SEO, desktop and mobile, with the trend). For the current month it says these are the figures so far.

You set your own sender, that is company name, contact line and logo, on the Settings tab of the Maintenance page or under Settings › Reports. Name and logo then appear on the cover, name and contact line in the footer of every page, if you like with the small line Created with WebDonkey.

Where the figures come from

  • Reachability and SSL are measured by the Monitor through the entry made when the website was added. Without a monitor entry it says This website has no monitor entry.
  • Lighthouse values are taken from that monitor entry's Lighthouse runs and kept for the report.
  • Backups come from Remote backups, deploy backups included.
  • Updates, vulnerabilities, files and pushes come from the website's checks and history.

Measuring only happens while your Mac is on and WebDonkey is open. Gaps stay gaps.

Status page Maintenance package

The Status page tab creates one HTML file with the state of the chosen websites and a bar per day of the last 90 days. No script, no outside request, no tracking. You save it as a file or upload it to a server, for example as a status page for your clients. The status page needs the Maintenance package.

Set up

  1. Heading of the page.
  2. Websites on the page: choose at least one active website.
  3. Show the address under each name if the addresses should be visible.
  4. Folder on a server: Connection and Choose folder. The page lands there as index.html and replaces the previous one in one step.
  5. If you like, Link to legal notice (optional) and Link to privacy policy (optional), each starting with https:// or http://. They then appear at the bottom of the page as Legal notice and Privacy. If you publish the status page as a page of its own, add a link to your legal notice.
  6. Save keeps the settings.

Create

  • Export as file… saves the page on this Mac.
  • Upload puts it into the chosen folder on the server.

At the top the page says All websites are reachable, Some websites are not reachable or No current measurement, per website Reachable, Not reachable or Not measured with the share over 90 days, and at the bottom when it was made.

Limits

  • The values come from the Monitor. Days without a measurement count as not measured.
  • The page shows the state at the moment it was made. For a new state, export or upload it again.

Settings Maintenance package

The Settings tab of the Maintenance page holds what applies to all looked-after websites: how often WebDonkey checks, your Wordfence key and the sender of the PDF reports. Changing them needs the Maintenance package. Without the package, what is set stays visible, and a stored Wordfence key can still be removed.

Check times

The Check times table has one row per website and one column per check: Updates, Vulnerabilities, Files and Visual. In each cell you choose Daily, Weekly, Monthly or Off. The top row All websites sets a column for all of them at once; if the websites differ, it reads Different. Hover over a choice to see the last check (Last check: …).

  • New websites check updates, vulnerabilities and files daily.
  • Visual only exists once you have set up pages on the website; then it runs weekly. Until then the column shows a dash.
  • Websites Over the quota of the package cannot be set here.
  • Checks run while this Mac is on and WebDonkey is open. A check missed while it was off follows after the next start.
  • Flow tests have their own times on the Flows tab of a website. The monthly report is created at the start of every month.

Wordfence Intelligence

WebDonkey matches WordPress core, plugins and themes only with your own Wordfence Intelligence key. It is free with an account at wordfence.com (Integrations). Paste it into Wordfence Intelligence key and click Save key. It then reads A key is stored, and Remove deletes it again. It is stored encrypted on this Mac and only sent to wordfence.com.

Wordfence requires a link and its copyright notice with every finding. WebDonkey shows both with each finding; if you pass findings on, keep both with them. More under Security.

Sender of PDF reports

Enter your Company name, a Contact line and your Logo (PNG, JPEG or SVG, at most 1 MB). Behind the logo decides whether a light plate sits behind it, and Show “Created with WebDonkey” shows or hides the small line in the footer. The preview shows the sender on the dark page of the report. Without a name the report carries the WebDonkey logo.

It is the same sender as under Settings › Reports and in the PDF reports of the SEO package.

Plans and the Maintenance package Maintenance package

The Maintenance package is an add-on like the SEO package: you buy it on its own and assign it to a license in your account. It needs a coupled WebDonkey Premium license and is not part of Premium. Fetching a project locally, on the other hand, works in every plan.

What works in which plan

Feature Free Premium Premium + Maintenance
Open the page, Fetch locally: add and test a connection, choose folders, fetch project folder and database, add the site yes yes yes
Make the copy safe: local database, mails to Mailpit, scheduled tasks off, access data of external services cleared yes yes yes
Make the copy run: addresses on .test, Redis and search service off no yes yes
Replace personal data while fetching (pseudonymise) no no yes
Add looked-after websites no no yes
Staging, local test copy, taking over changes and extensions, transferring files no no yes
Updates, vulnerabilities, checksums, visual comparisons, flow tests, reports, status page no no yes
Viewing, viewing and restoring backups, undo, deleting staging, archiving yes yes yes

The last row always applies: if the package runs out, you can still look, restore backups, take takeovers back, delete a staging site and archive websites. Safety comes before the license.

Billing

The Maintenance package is experimental and can only be booked monthly. Cancel it when you no longer need it. Prices are on webdonkey.io/pricing.

Quota

The package comes for 10, 30 or 100 websites. Each add-on pack brings 10 more. Active looked-after websites count; archived ones do not. What happens with too many websites is explained under Websites.

Without the package

  • In the sidebar, Maintenance carries the package's mark. The page still opens, because Fetch locally is free.
  • Above the other tabs it says Maintenance package not active: new websites, deploy and checks are locked. with View in shop.
  • Scheduled checks and monthly reports do not run.

Unlocking it

  1. Buy the package in the shop.
  2. Assign it in your account to a license with Premium. Until then WebDonkey shows Package bought but not yet assigned to a licence with Assign in account.
  3. WebDonkey unlocks it at the next license check; in Settings, Check now triggers it immediately.

If the Premium license ends, the package stops working too. Which products your license includes is shown under License, with status and validity per product.

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy