Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#13 2010-02-20 17:36:46
- ajw-art
- Member
- Registered: 2010-02-10
- Posts: 33
Re: Help with the older multi-site method.
The error paths don’t correspond to the config.php file path, which is why I’m so confused. Here’s the structure of the error message:
Warning: include(/home/myaccount/public_html/sites/subdomain/textpattern/lib/constants.php) [function.include]: failed to open stream: No such file or directory in home/myaccount/public_html/sites/subdomain/index.php on line 36
When index.php should be pulling the files from the main installation’s folders, as I set in config.php:
$txpcfg[‘txpath’] = ‘/home/myaccount/public_html/textpattern’;
Offline
Re: Help with the older multi-site method.
You need to edit the public-side index.php as well. The changes will be very similar to what you did with the admin-side index.php.
Code is topiary
Offline
#15 2010-02-20 18:29:25
- ajw-art
- Member
- Registered: 2010-02-10
- Posts: 33
Re: Help with the older multi-site method.
All right, progress! I’m now able to log into the admin side for the subdomain without error messages.
But.
The CSS/jquery references in the source code aren’t being found for either the admin or public sides. I’m getting 500 internal server errors when I click the links to them. I tried hard-coding the location of the admin side css into the @import rule in the /textpattern/textpattern.css stylesheet, but no go. I can’t find the part of either index.php that’s referencing these files, so I don’t know what I should be changing. The instructions did say to delete everything but the following files after setting up the subdomain:
airweek2006/index.php
airweek2006/textpattern/index.php
airweek2006/textpattern/css.php
airweek2006/textpattern/config.php
airweek2006/textpattern/textpattern.css
airweek2006/textpattern/textpattern,js
airweek2006/textpattern/txp_img/*.*
airweek2006/files/*.* (if it exists).
Here’s a link to the public side of the site in question so you can see what I mean.
Thanks for all of your help so far.
Last edited by ajw-art (2010-02-20 18:30:13)
Offline
Re: Help with the older multi-site method.
Take a look at the public-side css.php — you’ll have to make the same change in this one too.
Are you sure this is worth the effort? You’ll have to preserve all these mods every time you upgrade.
Code is topiary
Offline
#17 2010-02-20 21:08:15
- ajw-art
- Member
- Registered: 2010-02-10
- Posts: 33
Re: Help with the older multi-site method.
It might not be at this point. It’s turning out to be a lot more complicated than I’d hoped it would be; multi site would be nice as it would avoid a bunch of redundant files and make upgrading easier, but if I’m going to have to go through all of this for each of the sites that will eventually be created, I’ll be tearing my hair out.
At least I know that multi-site doesn’t work on shared hosts. It’ll save me trouble in the future.
Thanks for all of the help. I think I’ll just bite the bullet and do a separate install for each site.
Offline
Re: Help with the older multi-site method.
ajw-art wrote:
At least I know that multi-site doesn’t work on shared hosts. It’ll save me trouble in the future.
Not on shared hosting with crippling restrictions. Plenty of shared hosts support multi-site.
Code is topiary
Offline
#19 2010-02-21 01:46:24
- ajw-art
- Member
- Registered: 2010-02-10
- Posts: 33
Re: Help with the older multi-site method.
Any shared host suggestions for the future?
Offline
Re: Help with the older multi-site method.
There’s a lot of “it depends” with that question. And it’s a topic that comes up pretty often, so best not to drift this thread into the swamp of specific recommendations. There’s even a page on TextBook, though it hasn’t been updated much since it was created. I have found webhostingtalk.com worth perusing.
Code is topiary
Offline