domain

Hallojs.

Sitter med ett problem som jag inte lyckas lösa mer än på det teoretiska planet, men vill slänga ut frågan här i gruppen för att se ifall någon sitter på lösningen.

Min setup är Drupal 7-installation med en massa noder. Dessa noder ska spridas till två sajter. På Site1 ska alla Article-noder inte går att accessa förutom via Views (de ska visas på framsidan i en listning, men du ska inte kunna komma åt dem på site1.com/node/1).

På Site2 (med en egen domän) så ska alla noder går att visa, både i listningar och som egna nod-visningar).

Olá a todos,

Alguém tem projectos com o domain access e está a ter problemas em fazer login?

Basicamente o que estou a experenciar é o seguinte:
- Utilizador faz login
- Os cookies são enviados correctamente.
- No watchdog fica registada a entrada do user (login)
- Utilizador não fica logado no site, é quase como se fizesse logout automaticamente.

Isto em vários browsers e dispositivos.

Se desligar o modulo domain já se consegue fazer login.

Estou a usar PHP 5.6.2 (php-fpm), nginx 1.6.2 e memcache. (mesmo desligando o memcache obtenho os mesmos resultados).

I'm thinking about technologies and options for a new multisite, edu multidomain project. Basic idea: people buy subscriptions to create custom domain sites.

Instead of pure sites for each domain, I'm thinking of using OG and some workflows for each domain. How capable is OG for custom full domain sites? Not just subdomains, 123.mysite.com but mysite123.com and mysite345.com all under the main code OG code base?

Hi,

we're in the process of moving our main site to Drupal and was intending on using multisite. We've already move one smaller site over doing just that, and will be moving another over soon.

Now our manager really likes the idea of sharing content across all sites, which I was guessing would mean using the Domain Module.

How hard is it, or more specifically, what would be the process of moving sites that each have their own database to use Domain Access, since what i understand is, it uses one database for all sites.

My rule is that when a user is updated, the email domain must contain @domain1.com, @domain2.com, etc in order to become upgraded from Provider to GoldProvider. I've been trying to use the function AND without success. Can somebody tell me where and how do I need to add the additional domains?

thanks,

{ "rules_provider_upgrade_to_gold" : {
"LABEL" : "Provider upgrade to Gold Provider role after update",
"PLUGIN" : "reaction rule",
"REQUIRES" : [ "rules" ],
"ON" : [ "user_update" ],
"IF" : [

Is it possible to integrate some domain registration service into aegir?
I found this module which may help. http://drupal.org/project/registrar_api

Usecase:

1)Client comes to the site, searches for domain name, If available adds the domain name to cart via ubercart module
2)Client will browse for hosting packages, selects one and adds to cart
3)proceeds to checkout
4)drupal site will be created at chosen domain name and email will be sent with access details

At the risk of self-promotion, I thought I'd share this. In the project I just completed (http://www.thestrong.org), I had to decide whether to use Domain Access or a Multisite installation. I started implementing the Domain Access module, but then changed my mind.

I wrote up the reasons why I abandoned Domain access here.

I'm curious if people agree with my complaints about the Domain Access module, or had a different experience?

Im finding sites online that run on Drupal but display a bit of inconsistancy. If you go to http://domain.com than the site works fine. However if I visit http://www.domain.com, than I get the "site offline" message. I had a similar problem with something like that using Wordpress so Im curious in what is affecting things in that adverse way.

From what I have seen, most people correct this with a band-aid by just setting a redirect on canonical names. Would this be a problem with Drupal or a problem with the domain registrar and how the DNS is set up?

I have a multi-site installation like

• example.com/drupal (default)
• site1.example.com
• site2.example.com
• site3.example.com

example.org → site3.example.com

Now, I have an additional domain example.org, which shall be used for site3.example.com. So, when a user enters example.org, he shall be redirected(?) internally(!) to site3.example.com. So, the user shall not see any redirection and he shall not be able to see, that the site is available at site3.example.com, too.

site3.example.com → example.org

Hej!

Jag har byggt en plattform i .NET för att hantera CMS-kunder på en central administration men med olika domäner kopplade till den. Nu är det så att jag undrar om det finns möjlighet att göra samma sak i Drupal och därmed också få med alla utvecklade, smidiga och bra moduler som finns. Det jag har i åtanke är:

• En databas och delade tabeller (inte en databas med 1000-tals tabeller som växer i takt med antalet domäner/kunder som kopplas till)