Jump to content

Recommended Posts

Posted

Well you just override the current page. If there are children involved you have to define those children before switching the page object. Otherwise children are empty.

Posted

Perhaps a screenshot would help with annotations which page should display what and how they are related. Also the complete code of your template would help.

Also: perhaps start a new thread, because this is pretty specific and this thread is getting longer and longer ;).

  • 4 weeks later...
Posted

Hi Forum,

I'm having a hard time to get the original module (Apeisa's one) to work with 2.5.

I did setup a bunch of 12 landingpages (each with a little bit different content but sharing the same template). I added their domains to the module settings as well as to $config->httpHosts array. 10 of my 12 domains were working fine, but 2 didn't - they redirected to the root. I triple checked everything but didn't find out what was wrong.

Unfortunately during this debug process I must have added a domain twice to the module settings. This made PW throw a 404 on the admin and on the frontend side for all domains making the admin inaccessible.

I've temporarily made it back into the admin by renaming the module to multisite-old.module. But I can't figure out how to "reset" the module settings to its former or a fresh state (replacing multisite.module with a new file from Github doesn't work) nor how to get all of my 12 domains work.

Any help is appreciated.

Thanks

  • 1 month later...
Posted

Anyone? I've tried forwarding the domain but that doesnt work (well in terms of the multi-site working). What would the DNS changes be?

Posted

Make sure domain B points to the same server (A record or CNAME) as domain A. And on the serverside you have to make sure that domain B it pointing to the same directory as domain A.

  • Like 1
Posted

OK cool. Is there any way of doing this without root access? I'm using Apache, any good links for how to set up server side? Thanks!

Posted

Depends on your server configuration. The domainname you can alter yourself by changing the DNS. The server part you should pickup with your hosting company. If you run an unmanaged server, it (again) depends on which OS you use. A quick search on Google should help you out.

Posted

still struggling a bit on this, is there any docs?

This is my DNS, the host has informed me its pointing the to the same directory as horton-stephens.com when incoming on hortonsshortuns.com (as i dont have root access :(

www.hortonsshortuns.com & hortonsshortuns.com set in module settings and www.hortonsshortuns.com page name for the new site. But still getting the homepage of the other site, should apache be sending to /www.hortonsshortuns.com not / ??

* A     80.87.143.6 * CNAME     www.horton-stephens....   @ MX 10   mx0.123-reg.co.uk.   @ MX 20   mx1.123-reg.co.uk. @ A     80.87.143.6   www A     80.87.143.6
Posted

No, no. Apache has nothing to do with this module. The module only identifies the page name, does some path voodoo and that's it. No further server side configuration needed.

Your mistake is that you added several different domain names in the module's configuration. So basically it has to be configured like that:

- Homepage

-- sub page 1

-- sub page 2

[...]

-- sub site (with page name "hortonsshortuns.com")

--- sub site sub page 1

--- sub site sub page 2

--- sub site sub page 3

[...]

And in your module's config you only define "hortonsshortuns.com" as another domain. The www stuff should be configured with htaccess, but never ever put several domain variations in the module's config. This has to go wrong.

  • Like 2
Posted

Still struggling. changed the the config to hortonsshortuns.com only and changed the title and path of the subpage to hortonsshortuns.com could there be anything else wrong with my settings above as im still only getting the home of the main site? Thanks for you help

Posted

Hard to say... You type in hortonsshortuns.com (without www) and then you get redirected to horton-stephens.com, not to some 404 page? Do you have one (404) and are you sure you are on the homepage? You haven't changed your .htaccess I assume?

Posted

I've not changed the .htaccess just added the above in the DNS and on the server. You don't go to a 404 (though there is one obvisouly) but just land on the home for horton-stephens.com

Posted

Sorry, just trying to get an idea of what's going on here.

So far it sounds like your domains are configured correctly, or at least they work (mostly) as expected. The fact that hortonsshortuns.com is identical in content to www.hortonsshortuns.com and both versions work is a problem (for this module and from SEO point of view) but as long as you use the version that you've configured this module to use, it's not really the issue right now.

Anyway, this makes me think that there could be something wrong with the Multisite module config or the page it's trying to point the user to. If you're using Soma's variation of Multisite, I don't really know anything about that (never used it), but:

It might be helpful if you could post here literally how you've configured the module (every config setting and value exactly as they are on your site, either as text or screenshots)? Also, just to rule out any inconsistencies, please double-check (or triple-check, or whatever) that the related page branch is correctly named (name field, not title) and placed in the page tree below the root page, something like this:

- Home
    - whatever
    - whatever
    - hortonsshortuns.com
    - whatever
    - whatever
    - ... and so on

Looks like this has been way more difficult than it should've been, but hopefully we'll get this sorted :)

  • Like 1
Posted

Looks ok but have no idea. Everybody seems to have problems with it except me. :)

I only used multisite on where all pages are multisites, there's no default home. But I think it doesn't matter.

What happens if you enter the direct url to the domain folder

http://domain.com/hortonsshortuns.com

What happens if you output 

echo "subdomain: " . $modules->Multisite->subdomain;

in your template?

Maybe you can debug the module and try to locate where it's failing?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...