Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#1 2024-12-07 13:00:58

gaekwad
Server grease monkey
From: People's Republic of Cornwall
Registered: 2005-11-19
Posts: 4,296
GitHub

Multisite scaffold and corresponding files

I’ve not yet used multisite in anger, so please forgive this newbie question.

Should the files in /sites/site1/public/ match those in / byte for byte, or are there expected / intended differences?

Last edited by gaekwad (2024-12-07 13:01:13)

Offline

#2 2024-12-07 13:05:51

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

Re: Multisite scaffold and corresponding files

I think index.php is different to take account of the extra path stuff but the rest should be the same, if memory serves.

We may even have unified the index.php files. Can’t remember exactly. The general idea is to only need one set in the next version.


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

#3 2024-12-07 13:15:07

gaekwad
Server grease monkey
From: People's Republic of Cornwall
Registered: 2005-11-19
Posts: 4,296
GitHub

Re: Multisite scaffold and corresponding files

Thanks, Bloke. I’ve made a start on a sync script to keep multisite stuff in line with core files (see recent commits), and there are some differences with the index.php over and above what I anticipated – so I’m glad I checked!

Offline

#4 2024-12-07 13:44:31

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

Re: Multisite scaffold and corresponding files

Nice one. I expect the multi-site index.php to be more fully featured and thus the one that we eventually adopt so if the differences aren’t vast, it might be possible to merge the code to make a definitive file with the necessary bits from both. That would certainly make things simpler for sync purposes until we change the directory structure in Txp 5 to unify admin access.


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 2024-12-07 13:53:46

etc
Developer
Registered: 2010-11-11
Posts: 5,257
Website GitHub

Re: Multisite scaffold and corresponding files

Bloke wrote #338442:

We may even have unified the index.php files.

Currently, site index.php just (more or less) includes the ‘main’ index.php:

include txpath.'/../index.php';

So they are definitely different atm.

Offline

#6 2024-12-07 13:58:28

gaekwad
Server grease monkey
From: People's Republic of Cornwall
Registered: 2005-11-19
Posts: 4,296
GitHub

Re: Multisite scaffold and corresponding files

Thanks Bloke, thanks etc.

I’ll leave it as-is for now.

Offline

#7 2024-12-07 14:04:35

etc
Developer
Registered: 2010-11-11
Posts: 5,257
Website GitHub

Re: Multisite scaffold and corresponding files

And why do we need a copy of textpattern.js for each site? CSP? Or is the ‘main’ URL totally inaccessible in multisite setup? Noob me too.

Offline

#8 2024-12-07 14:27:45

gaekwad
Server grease monkey
From: People's Republic of Cornwall
Registered: 2005-11-19
Posts: 4,296
GitHub

Re: Multisite scaffold and corresponding files

etc wrote #338447:

And why do we need a copy of textpattern.js for each site? CSP? Or is the ‘main’ URL totally inaccessible in multisite setup? Noob me too.

cf. github.com/textpattern/textpattern/issues/1962

Offline

Board footer

Powered by FluxBB