I need to set up Drupal 6 as a multilanguage site.
1 installation, several language versions = several domains, i.e.
English at englishsite.com
French at frenchsite.com
German at germansite.com.
I've found a Tutorial that suggest that you need access to server's http.conf - this is quite unlikely on shared hosting.
Is it really neccesary?
Maybe You can set it up with .htaccess or any other way.
Namely: what should I do to have such a configuration working ?
(after setting Language negotiation to Domain name only on .../admin/settings/language/configure)
According to what I've found this could resolved in at least 2 ways.
Admin interface
Make the domains point to the Drupal directory in the hosting account admin interface (what is equivalent to http.conf edit suggestion from the tutorial)
Symbolic links
Replace the domain-specific directories with symbolic links to the Drupal directory (in Unix-based systems), i.e.
ln -s <drupalDirectory> <domainDirectoryName>
Related
I would like to use Drupal 7 to support two domains with same code, themes, modules and even database and content, completely transparent to the end-user.
So, user of exmaple1.com would see only exmaple1.com and user of example2.com would see only example2.com (not be redirected to example1.com). To complicate matters, I already have example1.com legacy, which cannot change.
Closest I have come -
1) using apache virtual host to proxy requests for both domains to same drupal htdcos directory.
2) setup sites for each domain as per https://drupal.org/node/53705.
a) Modify the base URL within settings.php file under example2.com directory
But, still, users of example2.com are redirected to example1.com(?!). In fact, I looked into my default settings.php file and found the baseURL field is commented out. A directory search for my sites base URL returned no results, suggesting it is set somewhere in the database? WHERE? I looked into tables like url_alias - no records. Can this is set to some variable that reads the HTTP request for the base URL and not be hard-coded as it seems to be?
I have already reviewed solutions that "fix" the base_URL in settings.php, apache virtual host, doing HTTP redirect/rewrite in .htaccess, pathauto modules, backup/migrate and also multi-site.
It seems that you read an old documentation for multisites on (2). For Drupal 7 check https://drupal.org/documentation/install/multi-site.
But you need to set up Symlinks (Symbolic links) to achieve that. I don't think you need a multisite here if both sites use the same files and database.
Try the useful link below for Drupal 7 multisite install,
http://mydons.com/drupal-7-multisite-install-steps-in-windows/
http://mydons.com/drupal-7-multisite-install-steps-in-linux/
I have a rather general but very important question. I have built a main website and an eShop for a client. The main website is in Wordpress and I have to find a platform for the eShop, but let's say it's also a Wordpress theme.
Can I install 2 wordpress sites in my hosting server? So for example, the first one will be www.company.com/website and the other being www.company.com/shop.
Yes you can: Installing Multiple Blogs « WordPress Codex.
While all the previous answers are technically correcct - they will have you doing twice the work that is actually needed for your desired outcome (as in two installs, two upgrades, two sets of security checks, two databases, two admin panels... you get the idea - two times the work, all unnecessary).
Since Wordpress 3.0, the WordpressMU features have been integrated into the core. This allows you to run multiple Wordprsss 'sites' from a single install.
Sites can be served from their different domain, sub-domains, or in your case different sub-directories within the same domain and server.
Full information on how to achieve this is available from Wordpress Codex:
Create A Network
Just install one wordpress app in your root directory and create the other directory and install it there, there should be no problem.
Keep in mind that if you are routing around a port 80 blockade (aka using a different port to host your site) then Multi-site WILL NOT WORK. In such an instance multiple WP installations seem to be the ticket.
You can choose a directory relative to your root domain when installing wordpress on your site.
I am trying to develop a bilingual site based on WordPress (bilingual sites in Quebec are a necessary reality). The problem is I find automated translators (i.e. Google Translate) do not get the context right.
I noticed during a WordPress install (with Fantastico) I can select the folder where WordPress would live. Would it possible to have set up like:
public_html
|-index.html
|-english_site
|-wordpress install for english
|-french_site
|-wordpress install for french
Is it feasable to have both WordPress installs hook into the same database and media uploads? Or is there a better way to avoid automated translators?
I'd definitely recommend, WPML plugin for handling multilingual sites.
One admin area, every bit of content can have multiple hand crafted translations. Including pages, posts, menus etc. Plugins also get translated if they contain the relevant translation files.
Also supports sub domains, so you could do french.yourdomain.com or yourdomain.com (english / default).
Just notice that if you install any multilingual plugin, you should NOT have multiple WordPress instances. Multilingual plugins use a single WP install to serve several languages.
The language-directories structure that you see in the URL is a virtual thing. You shouldn't have real directories on the server. WordPress should be installed in the root path, not in a language directory.
If you're looking to serve languages from different domains (or subdomains), have a look at this FAQ for how to setup on your DNS and Apache.
When naming a sites folder in Drupal using a multi-site setup, can I name the site "mydomain" or does it have to be in the format of the domain name like "mydomain.com".
Is there a way to do this using symbolic link in linux?
thanks
Drupal matches the domain name requested via HTTP with the folder name inside sites. If it does not match anything it will fall back to "default". So you need to name the folder mydomain.com.
You can definitely use a symbolic link from mydomain.com -> mydomain provided your Apache (or other HTTPd) is configured to resolve symlinks.
Drupal 6 looks for a file named settings.php in a folder named sites/mydomain.com, or similar. The exact rules are listed in default.settings.php. If your host supports symbolic links, you could make mydomain.com into a link: the syntax is ln -s /path/to/real/files/mydomain mydomain.com
Drupal 7 is much nicer about how it handles multisite installs- it's possible to tell drupal where the settings.php file is for each domain. There's a patch that backports this feature here: http://drupal.org/node/231298
I have a new client that I am converting over to Drupal from Wordpress. We have two domains with the same name but different TLDs i.e. .com & .org. We have decided to start by setting up the site first under the .com so we have a live site to play with during the development.
So we currently have a wordpress site running on the .org and drupal (on a new host) running on the .com domain.
So two questions:
Can and How do you configure Drupal to work for both the .com and the .org ?
Can and How do you change the base domain drupal is configured with after the site is live ?
If you aren't using Drupal's multisite system (that is, the site information is being put into sites/default instead of sites/example.org or sites/example.com), this is really easy: do nothing. There is no step 2. Drupal will handle any domain thrown at it: just use your web server's name-based handling to determine which domains to accept.
If you are using Drupal's multisite system, it's a little harder:
Rename the sites folder (so from sites/example.com to sites/example.org).
Drupal's files table hardcodes the files directory it uses, so you're going to need to change all the paths in it. Run UPDATE files SET filepath = REPLACE(filepath,'example.org','example.com') on the database.
The other place to change the path is under Site Configuration -> File system.
The final place you're going to need to change paths is going to be on the settings page for your theme if you decided to use a custom logo or favicon.
Once you've changed all the paths, rebuild the cache under Site Configuration -> Performance.
This should cover most cases. Check with the third-party modules you're using to see if they also hardcode filepaths. If the modules are using the API correctly, they should've been handled in steps 2 and 3.
Because of all the hardcoded file paths, I highly recommend not using multisite unless you really need to. If you are only running one site in a Drupal install, just stick the site in sites/default.