CMS Made Simple Forums

ive looked all around and not found the answer to this question
maybe becouse no ones thought of it or maybecouse its just not a good idea
anywhoo just thought id throw it out there and see if anyone knows the answer

i have a single install of cmsms running on my godaddy shares hosting account
and i have 4 domains pertaining the same site

1 main
3 extras pointing to the root of the account
they are aliases aliased to the ROOT so when i go to the aliased domain it pulls the site just fine with the domain i entered in the address bar like i typed it only with a slash at the end

now since the cmsms config file shows the root domain name to be my primary doman all links point to http://primarydomain.com/index.php?page somethin somehitn and clicking a page takes me to the origional domain name
as it should..

so the question is this

if i take this code
$config['root_url'] = 'http://phxwv.com'; <-- what can i put here to reflect the domain name that was entered with??? like a server command to put the domain name in that person arrived with
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')

or is there any way say to make the pages just display without the domain name

like in html making links like this  about.html ---- as opposed to ---- http://domainname.com/about.html
so that whatever the domain name the links would work and not change the domain that u entered the site with//
is that poss in cmsms?

some how.. i know i sounds shady but the intent is so that when someone goes to the site thru a secondary domai is doenst seem like a redirect domain name... and doesnt seem like a redirect to the search engines either.. like seperate site u know?

Currently there's no option to do that.

It's on roadmap for versions after 2.0

As now {meta} tag creates info on header but can be turned of by {meta showbase="false"} If another base href tag is created with some custom tag (do not know enough to do it) I assume you could carry domain information and give that depending what domain was entered from. This needs relative paths to images etc. so maybe config.php needs to be edited.

I quess you could get some idea something like this http://wiki.cmsmadesimple.org/index.php ... content_id

but I could be wrong.

br, K

yea but can a user defined tag go in config.php?

and where in the files would i attempt to change such a line?

maybe im walking down the wrong street here

True multi-host support is not planned for 2.0..... I should change the roadmap.  we've decided that it is 'out of scope' for cms made simple, because implementing it the way people would want (with the users and permissions split out per domain, and the files split out per domain, and, and, and..... ) would take the 'simple' out of 'cms made simple.'.

Now we may do some funky modifications such that you can have multiple domains all pointing at one install of cms made simple, and maybe specify a different start page for each domain..... but that is as far as we would go.  and there's no guarantees on that.

calguy1000 wrote: True multi-host support is not planned for 2.0..... I should change the roadmap.  we've decided that it is 'out of scope' for cms made simple, because implementing it the way people would want (with the users and permissions split out per domain, and the files split out per domain, and, and, and..... ) would take the 'simple' out of 'cms made simple.'.

Now we may do some funky modifications such that you can have multiple domains all pointing at one install of cms made simple, and maybe specify a different start page for each domain..... but that is as far as we would go.  and there's no guarantees on that.

i think what a *few* people are looking for is a system that they can use in a 'hosted services' environment (ala blogger). one install for MANY 'users', but i agree, it's NOT simple, it's too much to do to satisfy such a small audience, would likely require server root access to set up and administer (something most do not have and would not be 'simple' to support), etc......


what i think WOULD be "simple" (comparatively speaking), considerably easier to implement, and be of value to MORE people is a way to have one install serve up pages for multiple sites (domains)... one install for a *single* user or client's multiple sites..

  -- all domains are simply 'parked' on top of one another, determine which 'site' to serve based on the hostname in the http request...  would easily work in shared environments.

  -- each 'site' would have their own page hierarchy (perhaps a new 'super top level' menu item called 'site' that each site's pages go under)... all pages for all sites shown on the same listcontent page... no separating them by 'site' other than this. (see below for permissions idea)

  -- each site could be served from their respective domain's root level (the 'site' level is not part of the url path); if cmsms is in a subdirectory, then all sites must use the same path in their url (no complicated rewrite rules needed to deal with different paths).

  -- a new content type to duplicate the same page on a different 'site' with ability to override template, alias, and a few other page settings...

  -- groups are modified so that a group only includes permissions on a single 'site' (then to add a user to more than one site, you simply add them to multiple groups). users of course only 'see' in the administration area what they have permissions to modify, just like it is now. if a user only has permissions on one site, than that's the only pages they will see... if they have permissions to content in multiple sites, than they will see those pages for all the sites when they listcontent.

  -- no messing around with separating the database, uploads directory, global content blocks, plugins, udt, templates, modules, etc...  on a "per site" basis... as we're dealing with a SINGLE entity's multiple sites, that level of separation is not necessary.

  -- if 'multisite' is not enabled, then cmsms operates and looks like it does now from the user's perspective.

I've mentioned it before, but just not on this thread.... 'everybody's idea of multi-site' is different... and to incorporate even 1/2 of the intersection of the ideas would result in a jumble, that would not be easily maintainable, wouldn't satisfy anybody. and would still take the 'simple' out of cms made simple.

To this end.... we've decided to keep the 'simple' in cms made simple, and IF we do anything related to multisite it would be that multiple domains could point at the same cms installation, and MAYBE depending upon the domain a different home page could be specified.  That would be it.

no 'groups' split out, no 'permissions' split out, 'modules, udt's, gcb's, templates' or other things split out.  No 'copying pages' amongst sties, or any of that....

See what I mean..... everybody's idea on this is different..... nobody can be 100% satisfied.... it would not be easy to accomplish, and it could potentially introduce alot of complexity and instability into the application that is not needed.

Modules can be written to allow 'mirroring' of various content items, of user accounts, of modules, or entire sites.... this is all possible.... this is where people's focus should lie.  I encourage you to bug your developers to write addon modules to accomplish some or all of this stuff (just not me).

well you are absolutely right and to tell you the truth, i like cmsms the way it is , simple, managable, and to the point, i think you guys have done  spectacular job with this..

and to anyone else reading this who wants to do what im wanting to do or similar..

I HAVE A SOLUTION!

YEAH ME!

So here it is

get your self a hosting account that lets you host multiple sites on one account

go daddy has deluxe plan
web air has unlimited sites on all plans

simply this <-- and this is so simple i cant believe i didnt think of this right away

step 1: install cmsms, design your site <-- if you havent allready
step 2: copy and paste the install to all of your other site folders
step 3: make all changes from 1 install (like a smart person would)

oh and edit config.php a little for paths and main URl
database info should stay the same

theoretically this should work great......i think......well ill find out!....i hope

chotaboy wrote: well you are absolutely right and to tell you the truth, i like cmsms the way it is , simple, managable, and to the point, i think you guys have done  spectacular job with this..

and to anyone else reading this who wants to do what im wanting to do or similar..

I HAVE A SOLUTION!

YEAH ME!

So here it is

get your self a hosting account that lets you host multiple sites on one account

go daddy has deluxe plan
web air has unlimited sites on all plans

simply this <-- and this is so simple i cant believe i didnt think of this right away

step 1: install cmsms, design your site <-- if you havent allready
step 2: copy and paste the install to all of your other site folders
step 3: make all changes from 1 install (like a smart person would)

oh and edit config.php a little for paths and main URl
database info should stay the same

theoretically this should work great......i think......well ill find out!....i hope

hello chotaboy
You can be be more specific, give a exemple the config  etc.
thsnks

@chotaboy

It's not a really multi site solution and  btw.

chotaboy wrote: step 2: copy and paste the install to all of your other site folders

... there's the sitepusher module to do that.

Well my case might be a little different but it deales with your problem....

and gives perhaps people with similar cases a solution....

I have a Page that contains several "sub"-sites but this is not visible to the visitor....

(language and location)

The Structur is as follows:

1      English
1.1    Hamburg
1.1.1 Start Page    en_HH_home
1.2    Budapest
1.2.1 Start Page    en_BP_home

2      German
2.1    Hamburg    de_HH_home
2.1.1 Start Page
2.2    Budapest
2.2.1 Start Page    de_BP_home

A little complicated, but you'll see what its for...

The domain xxx goes now to the german site of Hamburg

The domain yyy goes now to the german site of Budapest

So this is what I did.

I changed the config.php so that the root seen from the webserver is xxx/yyy depending on the 3. and 4. letter in the page alias (HH oder BP).......

I wrote a .htaccess file so that the xxx goes to de_HH_home and the yyy goes to de_BP_home...


Look here...

xxx: www DOT 360werbung DOT de
yyy: www DOT 360com DOT info

sweet i gotta get me that module

and hey it was a theoretical solution

not A solution

just tryin to help lol

I've recently had a brainstorm to solve the 'updating multiple sites' problem.

if I tweaked sitepusher to only push 'certain stuff' (actually others have mentioned this already).... like... not to push the database, not to push the uploads directory, etc.  that'd take care of 90% of the problem, as only the 'core' stuff would be pushed...

Next comes the problem when there are database upgrades necessary.  Well, this may be done easily by issuing some wget type urls that a) login to the admin of the remote site, b) access install/upgrade.php and give it the required parameters....

but it's just a thought at this moment.

Already by several times, say, they will take the roodmap the multisites, but so far there still, is not going to implement (for reasons not yet understood) take advantage of it, or we will create between all system multisites like to be.

It's now removed from the roadmap.