Closed (fixed)
Project:
Virtual Sites
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Apr 2012 at 21:30 UTC
Updated:
7 Mar 2015 at 14:34 UTC
Jump to comment: Most recent
Comments
Comment #1
mikeaja commentedSorry, just realised issue 1 is fixed in DEV and works fine as far as I can see.
Issue 2 still exists, but I'm not sure if this is simply something unfixable (because the domain is part of the condition). If so, you are welcome to close this as fixed.
Thanks for this great extension. Amazed not more using this. Makes multisite much easier. I didn't even need to create a manual symlink. Once the domain alias was put in the hosting control panel, it worked with that domain as condition. Nice.
Comment #2
djg_tram commentedYes, as soon as this is sorted out, it would need to be released into a new stable version.
The statistics are always flawed because they only show sites that actively use the new update mechanism but yes, those are my thoughts as well. I used fokke's D6 version with great pleasure and this is exactly why I ported it to D7: I needed it on new sites as well. Fortunately, I never had problems with my ISPs, they always offered everything that's needed for real multi-site setup but I only use that when I need seemingly unrelated sites to be built on the same codebase. Whenever I need only virtually different sites, different representations of the same site (like, for instance, the mobile device version), VS was always the best solution.
So, as to your remaining problem, could you be a bit more specific? I regularly use it especially with mobile sites where the domain is in the form of m.example.com. There doesn't seem to be any problem with the display (I suppose you mean the browser URL display). Where do you see something going wrong?
Comment #3
mikeaja commentedSorry, my explanation was not great.
I just meant in the Site Information, within config.
If I set the condition to a different domain, then the Virtual Site 'Site Information' will still show the settings (frontpage, etc) for the main domain.
I guess this is difficult to change because the new domain only exists as a condition.
Comment #4
djg_tram commentedDo we speak about admin/config/system/site-information? I have the m. subdomain there on my sites. Strange.
Comment #5
mikeaja commentedyes, that's it.
In case my setup is different, in my condition it is a completely different domain, not a subdomain.
I will try removing it and setting up again, in case I didn't do this when updating to DEV.
Comment #6
djg_tram commentedThe setup might well be different. I always use the ISPs domain-subdomain services to set up the different names.
Anyway, the Site information page is not in any way directly manipulated by VS, it simply shows whatever Drupal thinks the current base URL is.
Comment #7
adamps commentedTidying up - the main problem seems to be fixed in dev.
The secondary problem - yes I see the same thing. It's not really something this module has any control of, and it only affects the admin, so I think we just have to live with it.