Skip to main content

Drupal Clean URL with GoDaddy

GoDaddy shared hosting allows multiple domains hosting where each domain can be hosted within its own folder in the document root. I install Drupal in a separate folder for each domain, even for the main domain. GoDaddy supports URL redirect and each domain can be redirected to its on folder. However, Drupal may get confused with the RewriteBase for clean URL rewriting.

Drupal handles URL rewriting for clean URL automatically. In fact, Drupal will try to enable it by default. On the other hand, there is no issue with GoDaddy regarding the Drupal URL rewriting. However, Drupal need to know the RewriteBase when a domain is NOT pointing to the document root folder. The RewriteBase is not necessarily the Drupal installation folder. This can be tricky because GoDaddy URL redirect may be set in two places.

In GoDaddy a domain can be redirected to a folder, even for the main domain. A http://xyz.com can be redirected to http://xyz.com/xyz which is my preferred configuration. The /xyz is a folder in my document root folder, which is now the root folder for http://xyz.com. Thus, my Drupal RewriteBase must be /.

The Drupal RewriteBase is set in .htaccess file in the Drupal installation folder somewhere near to the following line:

# If your site is running in a VirtualDocumentRoot at http://example.com/ ,
# uncomment the following line:
RewriteBase /

Also in GoDaddy, any URL can be redirected to any other URL. If Drupal is installed in a sub-folder of a domain which is already in a folder of its own such as http://abc.com/abc/jkl then I need to deal with three things:


  1. Redirect domain abc.com to folder /abc in the GoDaddy hosted domain settings.  
  2. Redirect http://abc.com/jkl to http://abc.com/abc/jkl in URL redirect settings.
  3. Set RewriteBase to /jkl in the Drupal .htaccess file.


GoDaddy URL redirect will alter the .htaccess file in the document root.




Comments

Post a Comment

Popular posts from this blog

Setting Up PyScripter for Quantum GIS

PyScripter is a general purpose Python Integrated Development Environment (IDE). Quantum GIS (QGIS) is a desktop GIS application that can be extended with Python plugins. Both are open source softwares. We intend to use PyScripter as an IDE to build QGIS Python plugin. We are using PyScripter 2.4.1.0 and QGIS 1.6.0 in Windows. PyScripter does not come with Python. On the other hand, QGIS is built in with Python. Thus, we will setup up PyScripter to use the build in Python in QGIS. We assume both PyScripter and QGIS are already installed. Preparing PyScripter batch file We assume that QGIS is installed in C:\OSGeo4W\ folder and PyScripter is installed in C:\Program Files\PyScripter\ . 1. Copy qgis.bat in C:\OSGeo4W\ bin to pyscripter.bat 2. Edit pyscripter.bat to remove the last line that read something like this start "Quantum GIS" /B "%OSGEO4W_ROOT%"\apps\qgis\bin\qgis.exe %* and replace it with this in one line Start "PyScripter" /B "C:\Progr...
8 comments
Read more

Access Control

Access control is about controlling user flow within your application. Do not mistaken access control with security which is a bigger subject in itself. Access control begins by authenticating user and limit his or her activity in your application. An activity is something like creating, updating or deleting a content. There are always finite number of activities that can be done in a given application. Each user can be assigned to a set of activities that he or she is allowed to do. Access control is usually tied to session management. However, you do not need session management to have access control. When a user log in, a session is created so that the user is remembered for the subsequent access. Otherwise the user has to keep on providing his or her credential for each access. We can also keep a list of activities that the user is allowed to do in the session record. Some applications let the session alive indefinitely and some applications time out user after a duration of inacti...
Post a Comment
Read more

Separation of Front-end and Back-end Concerns

Separation of concerns is the cornerstone of MVC framework. Model, view and controller are three broad concerns of web-based software development. On its early days MVC was implemented on server side. The server renders views for clients. Nowadays, most clients render views themselves. Even the terminology of client-server has already morphed into front-end and back-end . The need for back-end to handle views is diminishing. View concerns have became increasingly complex with two big sub-concerns of aesthetic and dynamics. Front-end evolves into bigger MVC concerns of itself. While back-end evolves into larger modeling concerns. Now, front-end and back-end are two separate concerns. Front-end and back-end are handled by two different teams of software developers with different specialties. Back-end evolves into something like "dinner can be served even without plates, forks and spoons, without table and chairs, and without a dinning room." Front-end is serving the withouts....
Post a Comment
Read more