Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#1 2025-01-25 17:50:05

albatros69
Member
Registered: 2021-06-17
Posts: 25

Migrate from a mono- to a multi-site instance

Dear all,

I’ve a mono-site textpattern instance (v4.8.7 if that matters). As I’m now extending the number of txp websites, I’ve prepared a new multi-site instance (v4.8.8). Everything is ready but I’m now wondering what is the best strategy to migrate the data from the old site to the new one.
The old is quite large and transferring all the stuff manually would be tedious.

Any hints before I’ll start?
Any hurdle I should expect because of the peculiarities of the situation?

Regards,

Offline

#2 2025-01-26 18:52:36

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 9,143
Website GitHub Mastodon Twitter

Re: Migrate from a mono- to a multi-site instance

SSH would be the most efficient way.

I posted a how to tutorial on txp tips some years ago.


Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.

Offline

#3 2025-01-29 20:00:37

albatros69
Member
Registered: 2021-06-17
Posts: 25

Re: Migrate from a mono- to a multi-site instance

Hello,

colak wrote #338918:

I posted a how to tutorial on txp tips some years ago.

Thanks for the tips: that would have been exactly how I would have proceed, if the origin and destination textpatterns were similar.
The new instance being a multi-site one doesn’t matter, does it?

Regards,

Offline

#4 2025-01-30 00:28:10

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 11,642
Website GitHub

Re: Migrate from a mono- to a multi-site instance

albatros69 wrote #338961:

The new instance being a multi-site one doesn’t matter, does it?

Not really. The principle is the same. The main difference besides a slightly different directory structure is that the symlinks allow you to share a codebase, with a bunch of different databases, one per site.

You can migrate data from one database to another and copy the site files around (export and import themes etc). As long as you remember to change any txp_prefs that point to paths or URLs in each database to match the domain/directory structure of that instance, it all should work fine.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#5 2025-01-30 09:17:53

jakob
Admin
From: Germany
Registered: 2005-01-20
Posts: 4,827
Website GitHub

Re: Migrate from a mono- to a multi-site instance

Please note, if you re-arrange your site manually and don’t go through the setup installer, you’ll need to add some additional config variables in your site’s config.php to define paths and the admin url. See these lines in config.php on your site’s future “private” directory.

EDIT: Reading your post again, it sounds like you used the installer and are now porting the /files and /images manually. In that case you probably already set those via the installer.

My guess is that there’ll be negligible/no update difficulties between 4.8.7 and 4.8.8. At least, there is no update script between 4.8.4 and 4.8.8 in the /textpattern/update/ directory.


TXP Builders – finely-crafted code, design and txp

Offline

Board footer

Powered by FluxBB