I have my drupal installation over several alias domains, thus domain1.com domain2.com domain3.com are completely the same and I want to gain access to drupal with any of those domains. So I have only one settings.php within /sites/default where i have only one domain (the good one), so I can access the site with this name, but not with other domains. I want them all to bring to the same installation. What's wrong?
After installing drupal and creating a new admin account, I am not able to login to the site. If the correct username and password is used, I am directed to the same login page again. If the wrong username/password is used I am redirected to another login page, with wrong username/passsword highlighted in red.
After an extensive search of the drupal site, I tried the following:
Today I installed Drupal in my Linux server. It is amazing. Atlast I found the ultimate CMS after trying 4-5 other programs. Thank you very much Drupal Team!
If anybody is working on Tamil translation, please let me know. I would like to contribute in this translation. Anyhow I am preparing myself to start the translation. I have no experience with the gettext or similar tools . Let me see how it works.
Thanks
I have just installed Drupal 4.6.3 on a server where I am using LDAP authentication, so I want to use the ldap_integration module. I have it working fine, as long as the user logs in with the 'user@server' format. But if I un-check the option in the settings to not require that format, I cannot get it to work. I'm using OpenLDAP on RHEL 3. What should be used in the pattern and replacement fields if you are configuring to not use the user@server format of login? All of my users will have the same dn, so I really do not want to require that format.
I have just installed Drupal (4.5.5, latest version available on Debian via apt-get), and then followed the instructions to install the Tinymce module. However, when I go to a create (or edit) content page, it is blank - completely white.
I'm guessing the Tinymce module needs Drupal v. 4.6.x (as the module version is numbered 4.6.0), and it doesn't work with 4.5.5, but wanted to confirm that is the problem before I manually install 4.6.x on my machine.