- Home
- MediaWiki
For wikis that are too large to leave alone.
A wiki that has not been updated for years becomes slow and vulnerable. RBCK brings it to a current version, without losing pages, files or users.
What we do
From an outdated wiki to one that lasts for years again.
Upgrades in stages
An old wiki cannot jump to the latest version in one go. We go through the intermediate versions and test every step on a copy.
Migration
To our servers in the Netherlands or to another host. Database, images and settings move across in full.
Recovery after a hack
We find out what happened, remove what does not belong and close the gap. Only then does the site reopen.
Extensions and skins
Checking existing extensions and replacing them where needed, and writing new ones: a custom design, a dashboard or an integration.
Semantic MediaWiki
Lists, maps and search pages that are rebuilt for every visitor are often why a wiki is slow. We make them fast.
Maintenance afterwards
Updates, backups and monitoring for a fixed amount per month, so the wiki does not fall behind again.
Who it is for
Does this sound familiar?
Many wikis and large sites were set up with care and then grew for years. Until the day nobody dares to touch them any more.
That is the moment to sort it out properly.
- The colleague or volunteer who set it up has left.
- The software has not been updated in years.
- The site gets slower as more is added.
- Your host is closing down, or the bill keeps rising.
Tick what applies to you.
How it went in practice
Atlasmuseum: from MediaWiki 1.26 of 2015 to 1.39.
The wiki went from 1.26 to 1.39 in three intermediate steps. PHP and the database moved along. Each of the 52 extensions was checked against the new version.
| Component | Was | Is now |
|---|---|---|
| MediaWiki | 1.26 (2015) | 1.39 |
| PHP | 7.4 | 8.3 |
| MySQL | 5.7 | 8.0 |
In their own words
«Robert Blok, expert en sites Web complexes»
Process
Look first. Then a price.
- 01
Check
We look at your site, wiki or application: which version, how secure and how fast. That costs nothing.
- 02
Proposal
You get in writing what needs to happen and what it costs. One fixed price.
- 03
Delivery
We work on a copy. The new version only goes live once everything is right.
- 04
Maintenance
After that we keep it up to date, for a fixed amount per month.
Frequently asked questions
What organisations ask us about their wiki.
Can a ten-year-old wiki still be upgraded?
Yes. It just cannot be done in one go. The Atlasmuseum wiki ran on MediaWiki 1.26 from 2015 and was brought to 1.39 via 1.31 and 1.35. Every step was tested on a copy first.
Will pages, images or users be lost?
No. Everything comes along: pages with their full history, files, users and permissions. Before the switch we compare the copy with the original.
Our wiki has been hacked. What now?
Send the address and what you have seen. We first look at how far the damage goes. Then we clean the site, update the software and only reopen it once the gap is closed.
We have our own extensions. Can they come along?
Usually, yes. We check every extension against the new version. What is no longer maintained, we replace or rewrite.
Does the wiki have to move to your servers?
No. We can also upgrade the wiki at your current host. Maintenance with fixed agreements on backups and availability is done on our own servers in the Netherlands.
What does an upgrade cost?
That depends on the version, the size and the number of extensions. After a free check you get one fixed price. Extra work is only charged when you ask for it.
Curious about the state of your software?
Send the address of your site, wiki or application. Within one working day you will hear what stands out and what we would tackle. Free, and without obligation.