.htaccess code conflicting, anyone advise?
-
Metal Beryl
- Forum Members

- Posts: 69
- Joined: Wed Apr 18, 2007 9:57 am
.htaccess code conflicting, anyone advise?
I have two folders on my cgi server, each with a cms made simple website in. I am using the following .htaccess rewrite rule to direct my two urls to their folder.
RewriteEngine On
RewriteCond %{HTTP_HOST} ^www.website1.co.uk$ [nc]
RewriteCond %{REQUEST_URI} !^/website1/*
RewriteRule (.*) /website1/$1 [L]
RewriteBase /website1/
RewriteCond %{REQUEST_FILENAME} !-d [NC]
RewriteCond %{REQUEST_FILENAME} !-f [NC]
RewriteRule ^(.+)$ index.php?page=$1 [QSA]
RewriteCond %{HTTP_HOST} ^www.website2.co.uk$ [nc]
RewriteCond %{REQUEST_URI} !^/website2/*
RewriteRule (.*) /website2/$1 [L]
RewriteBase /website2/
RewriteCond %{REQUEST_FILENAME} !-d [NC]
RewriteCond %{REQUEST_FILENAME} !-f [NC]
RewriteRule ^(.+)$ index.php?page=$1 [QSA]
You can view the two websites here...
www.rapidreality.co.uk and www.designrealitygraphics.co.uk
As you will see the rapidreality site loads in but the links don't work and the designrealitygraphics loads in but the images don't appear.
Jane
RewriteEngine On
RewriteCond %{HTTP_HOST} ^www.website1.co.uk$ [nc]
RewriteCond %{REQUEST_URI} !^/website1/*
RewriteRule (.*) /website1/$1 [L]
RewriteBase /website1/
RewriteCond %{REQUEST_FILENAME} !-d [NC]
RewriteCond %{REQUEST_FILENAME} !-f [NC]
RewriteRule ^(.+)$ index.php?page=$1 [QSA]
RewriteCond %{HTTP_HOST} ^www.website2.co.uk$ [nc]
RewriteCond %{REQUEST_URI} !^/website2/*
RewriteRule (.*) /website2/$1 [L]
RewriteBase /website2/
RewriteCond %{REQUEST_FILENAME} !-d [NC]
RewriteCond %{REQUEST_FILENAME} !-f [NC]
RewriteRule ^(.+)$ index.php?page=$1 [QSA]
You can view the two websites here...
www.rapidreality.co.uk and www.designrealitygraphics.co.uk
As you will see the rapidreality site loads in but the links don't work and the designrealitygraphics loads in but the images don't appear.
Jane
-
Pierre M.
Re: .htaccess code conflicting, anyone advise?
Hello,
I think your virtualhosting is bad, at the webserver level, before PHP and CMSms. Because you shouldn't need any "RewriteCond %{HTTP_HOST}" inside a given virtualhost.
You should have 2 distinct virtualhosts, each with its own root www folder. Hence each with its independant CMSms install (and .htaccess).
Pierre M.
I think your virtualhosting is bad, at the webserver level, before PHP and CMSms. Because you shouldn't need any "RewriteCond %{HTTP_HOST}" inside a given virtualhost.
You should have 2 distinct virtualhosts, each with its own root www folder. Hence each with its independant CMSms install (and .htaccess).
Pierre M.
-
Metal Beryl
- Forum Members

- Posts: 69
- Joined: Wed Apr 18, 2007 9:57 am
Re: .htaccess code conflicting, anyone advise?
Hmmm not quite sure what you mean? Will both CMSms work on here or should I move one to another cgi server?
Jane
Jane
-
Pierre M.
Re: .htaccess code conflicting, anyone advise?
Hello Jane,
Let's simplify : CGI is more complex. Let'us talk about standard HTML pages.
How do you separate requests to www.domain1.com and requests to www.domain2.net ?
Put otherwise : if you want www.domain1.com/staticpage1.html and www.domain2.net/staticpage2.html where do you put the files staticpage1.html and staticpage2.html ?
Pierre M.
Let's simplify : CGI is more complex. Let'us talk about standard HTML pages.
How do you separate requests to www.domain1.com and requests to www.domain2.net ?
Put otherwise : if you want www.domain1.com/staticpage1.html and www.domain2.net/staticpage2.html where do you put the files staticpage1.html and staticpage2.html ?
Pierre M.
-
Metal Beryl
- Forum Members

- Posts: 69
- Joined: Wed Apr 18, 2007 9:57 am
Re: .htaccess code conflicting, anyone advise?
Web hosting is with www.plus.net. They have static pages hosted on one server and have a seperate server for the cgi. You cant have php in the same place as the html. You have to point your domain to either the www or the cgi server.
Jane
Jane
-
Pierre M.
Re: .htaccess code conflicting, anyone advise?
Humm... they say : "some accounts come with an optional .co.uk domain. You can choose whether or not to take advantage of this optional extra when you sign up for your account". I suppose this is what we are speaking about.
You shouldn't care if they have separate servers for static pages, images and PHP. This is their job under the cover.
What matters about a hosting offer is one domain name linked to some web(file) space. domain.co.uk and extra.co.uk should have their own independant technical lives (even if commercialy linked).
Make what you want with domain.co.uk it shouldn't change anything for extra.co.uk.
And make what you want with extra.co.uk it shouldn't change anything for domain.co.uk.
Put otherwise :
Make what you want with astonmartin.co.uk it shouldn't change anything for rover.co.uk.
And make what you want with rover.co.uk it shouldn't change anything for astonmartin.co.uk.
Pierre M.
You shouldn't care if they have separate servers for static pages, images and PHP. This is their job under the cover.
What matters about a hosting offer is one domain name linked to some web(file) space. domain.co.uk and extra.co.uk should have their own independant technical lives (even if commercialy linked).
Make what you want with domain.co.uk it shouldn't change anything for extra.co.uk.
And make what you want with extra.co.uk it shouldn't change anything for domain.co.uk.
Put otherwise :
Make what you want with astonmartin.co.uk it shouldn't change anything for rover.co.uk.
And make what you want with rover.co.uk it shouldn't change anything for astonmartin.co.uk.
Pierre M.
Re: .htaccess code conflicting, anyone advise?
In my hosting package control panel I have numerous domains and in the domain manager I point the name to a folder so when you hit multiintech.com it directs it to my multiintech folder, hit mit-computers.com and it goes to that folder hit multipleintegratedtechnologies.com etc. etc....
Don't even know if they are on same server, but from my end it looks like it...
Don't even know if they are on same server, but from my end it looks like it...
-
Metal Beryl
- Forum Members

- Posts: 69
- Joined: Wed Apr 18, 2007 9:57 am
Re: .htaccess code conflicting, anyone advise?
Plus net works in a weird way. You can only point the domain name to the cgi server. You cant point it to a folder via the domain admin panel. You have to point your urls to the cgi server then use a .htaccess to direct the url to the folders. This works but one CMSms site doesn't have the images linking in and the other doesn't have the menu links working. If I direct one url to a cms everything works fine. Something is stopping both CMSms sites working!
Does this make sense?
Does this make sense?
Re: .htaccess code conflicting, anyone advise?
That sounds like a config.php problem? no?...
Have you checked your paths?...
Have you checked your paths?...
-
Metal Beryl
- Forum Members

- Posts: 69
- Joined: Wed Apr 18, 2007 9:57 am
Re: .htaccess code conflicting, anyone advise?
my config files are as follows...
for the graphics site..
Global Settings in the admin panel)
#after making any changes to path or url related options
#-----------------
#Database Settings
#-----------------
#This is your database connection information. Name of the server,
#username, password and a database with proper permissions should
#all be setup before CMS Made Simple is installed.
$config['dbms'] = 'mysql';
$config['db_hostname'] = 'privateinfo';
$config['db_username'] = 'privateinfo';
$config['db_password'] = 'privateinfo';
$config['db_name'] = 'privateinfo';
#If app needs to coexist with other tables in the same db,
#put a prefix here. e.g. "cms_"
$config['db_prefix'] = 'privateinfo';
#Use persistent connections? They're generally faster, but not all hosts
#allow them.
$config['persistent_db_conn'] = false;
#Use ADODB Lite? This should be true in almost all cases. Note, slight
#tweaks might have to be made to date handling in a "regular" adodb
#install before it can be used.
$config['use_adodb_lite'] = true;
#-------------
#Path Settings
#-------------
#Document root as seen from the webserver. No slash at the end
#e.g. http://blah.com
$config['root_url'] = 'http://www.rapidreality.co.uk/graphic';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}
#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/files/home3/designreality/graphic';
#Name of the admin directory
$config['admin_dir'] = 'admin';
#Where do previews get stored temporarily? It defaults to tmp/cache.
$config['previews_path'] = '/files/home3/designreality/graphic/tmp/cache';
#Where are uploaded files put? This defaults to uploads.
$config['uploads_path'] = '/files/home3/designreality/graphic/uploads';
#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://www.rapidreality.co.uk/graphic/uploads';
#---------------
#Upload Settings
#---------------
#Maxium upload size (in bytes)?
$config['max_upload_size'] = 16000000;
#Permissions for uploaded files. This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';
#------------------
#Usability Settings
#------------------
#Allow smarty {php} tags? These could be dangerous if you don't trust your users.
$config['use_smarty_php_tags'] = false;
#CMSMS Debug Mode? Turn is on to get a better error when you
#see {nocache} errors.
$config['debug'] = false;
#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;
#------------
#URL Settings
#------------
#Show mod_rewrite URLs in the menu? You must enable 'use_hierarchy' for this to work for modules
$config['assume_mod_rewrite'] = true;
#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';
#If you don't use mod_rewrite, then would you like to use the built-in
#pretty url mechanism? This will not work with IIS and the {metadata} tag
#should be in all of your templates before enabling.
$config['internal_pretty_urls'] = true;
#If you're using the internal pretty url mechanism or mod_rewrite, would you like to
#show urls in their hierarchy? (ex. http://www.mysite.com/parent/parent/childpage)
$config['use_hierarchy'] = false;
#If using none of the above options, what should we be using for the query string
#variable? (ex. http://www.mysite.com/index.php?page=somecontent)
$config['query_var'] = 'page';
#--------------
#Image Settings
#--------------
#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';
#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/files/home3/designreality/graphic/uploads/images';
$config['image_uploads_url'] = 'http://www.rapidreality.co.uk/graphic/uploads/images';
#------------------------
#Locale/Encoding Settings
#------------------------
#Locale to use for various default date handling functions, etc. Leaving
#this blank will use the server's default. This might not be good if the
#site is hosted in a different country than it's intended audience.
$config['locale'] = '';
#In almost all cases, default_encoding should be empty (which defaults to utf-8)
#and admin_encoding should be utf-8. If you'd like this to be different, change
#both. Keep in mind, however, that the admin interface translations are all in
#utf-8, and will be converted on the fly to match the admin_encoding. This
#could seriously slow down the admin interfaces for users.
$config['default_encoding'] = '';
$config['admin_encoding'] = 'utf-8';
#---------------------------------------------
#Use the old stylesheet logic? It's much slower, but it works with older
#versions of CMSMS. You'll also need this set to true if there is a module
#that uses a stylesheet callback. Leave it as false instead you really
#need it.
$config['old_stylesheet'] = false;
# URL of the Admin Panel section of the User Handbook
$config['wiki_url'] = 'http://wiki.cmsmadesimple.org/index.php ... dmin_Panel';
#Enable backwards compatibility mode? This basically will allow some
#modules written before 1.0 was released to work. Keep in mind that this
#will use a lot more memory and isn't guaranteed to fix the problem.
$config['backwards_compatible'] = false;
#Not used anymore... kept around, just in case
$config['disable_htmlarea_translation'] = false;
$config['use_Indite'] = true;
?>
and for my product site...
Global Settings in the admin panel)
#after making any changes to path or url related options
#-----------------
#Database Settings
#-----------------
#This is your database connection information. Name of the server,
#username, password and a database with proper permissions should
#all be setup before CMS Made Simple is installed.
$config['dbms'] = 'mysql';
$config['db_hostname'] = 'privateinfo';
$config['db_username'] = 'privateinfo'';
$config['db_password'] = 'privateinfo'';
$config['db_name'] = 'privateinfo'';
#If app needs to coexist with other tables in the same db,
#put a prefix here. e.g. "cms_"
$config['db_prefix'] = 'cms_Product';
#Use persistent connections? They're generally faster, but not all hosts
#allow them.
$config['persistent_db_conn'] = false;
#Use ADODB Lite? This should be true in almost all cases. Note, slight
#tweaks might have to be made to date handling in a "regular" adodb
#install before it can be used.
$config['use_adodb_lite'] = true;
#-------------
#Path Settings
#-------------
#Document root as seen from the webserver. No slash at the end
#e.g. http://blah.com
$config['root_url'] = 'http://www.rapidreality.co.uk/product';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}
#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/files/home3/designreality/product';
#Name of the admin directory
$config['admin_dir'] = 'admin';
#Where do previews get stored temporarily? It defaults to tmp/cache.
$config['previews_path'] = '/files/home3/designreality/product/tmp/cache';
#Where are uploaded files put? This defaults to uploads.
$config['uploads_path'] = '/files/home3/designreality/product/uploads';
#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://www.rapidreality.co.uk/product/uploads';
#---------------
#Upload Settings
#---------------
#Maxium upload size (in bytes)?
$config['max_upload_size'] = 16000000;
#Permissions for uploaded files. This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';
#------------------
#Usability Settings
#------------------
#Allow smarty {php} tags? These could be dangerous if you don't trust your users.
$config['use_smarty_php_tags'] = false;
#CMSMS Debug Mode? Turn is on to get a better error when you
#see {nocache} errors.
$config['debug'] = false;
#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;
#------------
#URL Settings
#------------
#Show mod_rewrite URLs in the menu? You must enable 'use_hierarchy' for this to work for modules
$config['assume_mod_rewrite'] = true;
#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';
#If you don't use mod_rewrite, then would you like to use the built-in
#pretty url mechanism? This will not work with IIS and the {metadata} tag
#should be in all of your templates before enabling.
$config['internal_pretty_urls'] = true;
#If you're using the internal pretty url mechanism or mod_rewrite, would you like to
#show urls in their hierarchy? (ex. http://www.mysite.com/parent/parent/childpage)
$config['use_hierarchy'] = false;
#If using none of the above options, what should we be using for the query string
#variable? (ex. http://www.mysite.com/index.php?page=somecontent)
$config['query_var'] = 'page';
#--------------
#Image Settings
#--------------
#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';
#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/files/home3/designreality/product/uploads/images';
$config['image_uploads_url'] = 'http://www.rapidreality.co.uk/product/uploads/images';
#------------------------
#Locale/Encoding Settings
#------------------------
#Locale to use for various default date handling functions, etc. Leaving
#this blank will use the server's default. This might not be good if the
#site is hosted in a different country than it's intended audience.
$config['locale'] = '';
#In almost all cases, default_encoding should be empty (which defaults to utf-8)
#and admin_encoding should be utf-8. If you'd like this to be different, change
#both. Keep in mind, however, that the admin interface translations are all in
#utf-8, and will be converted on the fly to match the admin_encoding. This
#could seriously slow down the admin interfaces for users.
$config['default_encoding'] = '';
$config['admin_encoding'] = 'utf-8';
#---------------------------------------------
#Use the old stylesheet logic? It's much slower, but it works with older
#versions of CMSMS. You'll also need this set to true if there is a module
#that uses a stylesheet callback. Leave it as false instead you really
#need it.
$config['old_stylesheet'] = false;
# URL of the Admin Panel section of the User Handbook
$config['wiki_url'] = 'http://wiki.cmsmadesimple.org/index.php ... dmin_Panel';
#Enable backwards compatibility mode? This basically will allow some
#modules written before 1.0 was released to work. Keep in mind that this
#will use a lot more memory and isn't guaranteed to fix the problem.
$config['backwards_compatible'] = false;
#Not used anymore... kept around, just in case
$config['disable_htmlarea_translation'] = false;
$config['use_Indite'] = true;
?>
can you spot anything that maybe a problem??
for the graphics site..
Global Settings in the admin panel)
#after making any changes to path or url related options
#-----------------
#Database Settings
#-----------------
#This is your database connection information. Name of the server,
#username, password and a database with proper permissions should
#all be setup before CMS Made Simple is installed.
$config['dbms'] = 'mysql';
$config['db_hostname'] = 'privateinfo';
$config['db_username'] = 'privateinfo';
$config['db_password'] = 'privateinfo';
$config['db_name'] = 'privateinfo';
#If app needs to coexist with other tables in the same db,
#put a prefix here. e.g. "cms_"
$config['db_prefix'] = 'privateinfo';
#Use persistent connections? They're generally faster, but not all hosts
#allow them.
$config['persistent_db_conn'] = false;
#Use ADODB Lite? This should be true in almost all cases. Note, slight
#tweaks might have to be made to date handling in a "regular" adodb
#install before it can be used.
$config['use_adodb_lite'] = true;
#-------------
#Path Settings
#-------------
#Document root as seen from the webserver. No slash at the end
#e.g. http://blah.com
$config['root_url'] = 'http://www.rapidreality.co.uk/graphic';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}
#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/files/home3/designreality/graphic';
#Name of the admin directory
$config['admin_dir'] = 'admin';
#Where do previews get stored temporarily? It defaults to tmp/cache.
$config['previews_path'] = '/files/home3/designreality/graphic/tmp/cache';
#Where are uploaded files put? This defaults to uploads.
$config['uploads_path'] = '/files/home3/designreality/graphic/uploads';
#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://www.rapidreality.co.uk/graphic/uploads';
#---------------
#Upload Settings
#---------------
#Maxium upload size (in bytes)?
$config['max_upload_size'] = 16000000;
#Permissions for uploaded files. This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';
#------------------
#Usability Settings
#------------------
#Allow smarty {php} tags? These could be dangerous if you don't trust your users.
$config['use_smarty_php_tags'] = false;
#CMSMS Debug Mode? Turn is on to get a better error when you
#see {nocache} errors.
$config['debug'] = false;
#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;
#------------
#URL Settings
#------------
#Show mod_rewrite URLs in the menu? You must enable 'use_hierarchy' for this to work for modules
$config['assume_mod_rewrite'] = true;
#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';
#If you don't use mod_rewrite, then would you like to use the built-in
#pretty url mechanism? This will not work with IIS and the {metadata} tag
#should be in all of your templates before enabling.
$config['internal_pretty_urls'] = true;
#If you're using the internal pretty url mechanism or mod_rewrite, would you like to
#show urls in their hierarchy? (ex. http://www.mysite.com/parent/parent/childpage)
$config['use_hierarchy'] = false;
#If using none of the above options, what should we be using for the query string
#variable? (ex. http://www.mysite.com/index.php?page=somecontent)
$config['query_var'] = 'page';
#--------------
#Image Settings
#--------------
#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';
#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/files/home3/designreality/graphic/uploads/images';
$config['image_uploads_url'] = 'http://www.rapidreality.co.uk/graphic/uploads/images';
#------------------------
#Locale/Encoding Settings
#------------------------
#Locale to use for various default date handling functions, etc. Leaving
#this blank will use the server's default. This might not be good if the
#site is hosted in a different country than it's intended audience.
$config['locale'] = '';
#In almost all cases, default_encoding should be empty (which defaults to utf-8)
#and admin_encoding should be utf-8. If you'd like this to be different, change
#both. Keep in mind, however, that the admin interface translations are all in
#utf-8, and will be converted on the fly to match the admin_encoding. This
#could seriously slow down the admin interfaces for users.
$config['default_encoding'] = '';
$config['admin_encoding'] = 'utf-8';
#---------------------------------------------
#Use the old stylesheet logic? It's much slower, but it works with older
#versions of CMSMS. You'll also need this set to true if there is a module
#that uses a stylesheet callback. Leave it as false instead you really
#need it.
$config['old_stylesheet'] = false;
# URL of the Admin Panel section of the User Handbook
$config['wiki_url'] = 'http://wiki.cmsmadesimple.org/index.php ... dmin_Panel';
#Enable backwards compatibility mode? This basically will allow some
#modules written before 1.0 was released to work. Keep in mind that this
#will use a lot more memory and isn't guaranteed to fix the problem.
$config['backwards_compatible'] = false;
#Not used anymore... kept around, just in case
$config['disable_htmlarea_translation'] = false;
$config['use_Indite'] = true;
?>
and for my product site...
Global Settings in the admin panel)
#after making any changes to path or url related options
#-----------------
#Database Settings
#-----------------
#This is your database connection information. Name of the server,
#username, password and a database with proper permissions should
#all be setup before CMS Made Simple is installed.
$config['dbms'] = 'mysql';
$config['db_hostname'] = 'privateinfo';
$config['db_username'] = 'privateinfo'';
$config['db_password'] = 'privateinfo'';
$config['db_name'] = 'privateinfo'';
#If app needs to coexist with other tables in the same db,
#put a prefix here. e.g. "cms_"
$config['db_prefix'] = 'cms_Product';
#Use persistent connections? They're generally faster, but not all hosts
#allow them.
$config['persistent_db_conn'] = false;
#Use ADODB Lite? This should be true in almost all cases. Note, slight
#tweaks might have to be made to date handling in a "regular" adodb
#install before it can be used.
$config['use_adodb_lite'] = true;
#-------------
#Path Settings
#-------------
#Document root as seen from the webserver. No slash at the end
#e.g. http://blah.com
$config['root_url'] = 'http://www.rapidreality.co.uk/product';
if(isset($_SERVER['HTTPS']) && $_SERVER['HTTPS']=='on')
{
$config['root_url'] = str_replace('http','https',$config['root_url']);
}
#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/files/home3/designreality/product';
#Name of the admin directory
$config['admin_dir'] = 'admin';
#Where do previews get stored temporarily? It defaults to tmp/cache.
$config['previews_path'] = '/files/home3/designreality/product/tmp/cache';
#Where are uploaded files put? This defaults to uploads.
$config['uploads_path'] = '/files/home3/designreality/product/uploads';
#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://www.rapidreality.co.uk/product/uploads';
#---------------
#Upload Settings
#---------------
#Maxium upload size (in bytes)?
$config['max_upload_size'] = 16000000;
#Permissions for uploaded files. This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';
#------------------
#Usability Settings
#------------------
#Allow smarty {php} tags? These could be dangerous if you don't trust your users.
$config['use_smarty_php_tags'] = false;
#CMSMS Debug Mode? Turn is on to get a better error when you
#see {nocache} errors.
$config['debug'] = false;
#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;
#------------
#URL Settings
#------------
#Show mod_rewrite URLs in the menu? You must enable 'use_hierarchy' for this to work for modules
$config['assume_mod_rewrite'] = true;
#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';
#If you don't use mod_rewrite, then would you like to use the built-in
#pretty url mechanism? This will not work with IIS and the {metadata} tag
#should be in all of your templates before enabling.
$config['internal_pretty_urls'] = true;
#If you're using the internal pretty url mechanism or mod_rewrite, would you like to
#show urls in their hierarchy? (ex. http://www.mysite.com/parent/parent/childpage)
$config['use_hierarchy'] = false;
#If using none of the above options, what should we be using for the query string
#variable? (ex. http://www.mysite.com/index.php?page=somecontent)
$config['query_var'] = 'page';
#--------------
#Image Settings
#--------------
#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';
#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/files/home3/designreality/product/uploads/images';
$config['image_uploads_url'] = 'http://www.rapidreality.co.uk/product/uploads/images';
#------------------------
#Locale/Encoding Settings
#------------------------
#Locale to use for various default date handling functions, etc. Leaving
#this blank will use the server's default. This might not be good if the
#site is hosted in a different country than it's intended audience.
$config['locale'] = '';
#In almost all cases, default_encoding should be empty (which defaults to utf-8)
#and admin_encoding should be utf-8. If you'd like this to be different, change
#both. Keep in mind, however, that the admin interface translations are all in
#utf-8, and will be converted on the fly to match the admin_encoding. This
#could seriously slow down the admin interfaces for users.
$config['default_encoding'] = '';
$config['admin_encoding'] = 'utf-8';
#---------------------------------------------
#Use the old stylesheet logic? It's much slower, but it works with older
#versions of CMSMS. You'll also need this set to true if there is a module
#that uses a stylesheet callback. Leave it as false instead you really
#need it.
$config['old_stylesheet'] = false;
# URL of the Admin Panel section of the User Handbook
$config['wiki_url'] = 'http://wiki.cmsmadesimple.org/index.php ... dmin_Panel';
#Enable backwards compatibility mode? This basically will allow some
#modules written before 1.0 was released to work. Keep in mind that this
#will use a lot more memory and isn't guaranteed to fix the problem.
$config['backwards_compatible'] = false;
#Not used anymore... kept around, just in case
$config['disable_htmlarea_translation'] = false;
$config['use_Indite'] = true;
?>
can you spot anything that maybe a problem??
Re: .htaccess code conflicting, anyone advise?
A couple...
I have...
#Where is the url to this uploads directory?
$config['uploads_url'] = $config['root_url'] . '/uploads';
You have... in more than one place it's like this...
#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://www.rapidreality.co.uk/graphic/uploads';
But the biggest thing may be that you have mod_rewrite thru .htaccess and internal pretty URLs both turned on in the URL settings for both sites...
If you turn both of them off and just run it like fresh install does it work?...
I have...
#Where is the url to this uploads directory?
$config['uploads_url'] = $config['root_url'] . '/uploads';
You have... in more than one place it's like this...
#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://www.rapidreality.co.uk/graphic/uploads';
But the biggest thing may be that you have mod_rewrite thru .htaccess and internal pretty URLs both turned on in the URL settings for both sites...
If you turn both of them off and just run it like fresh install does it work?...
-
Metal Beryl
- Forum Members

- Posts: 69
- Joined: Wed Apr 18, 2007 9:57 am
Re: .htaccess code conflicting, anyone advise?
I have turned the mod_rewrite and internal pretty urls off and the page links now work.
Unfortunately on the http://www.designrealitygraphics.co.uk/ ... ness-cards website the images don't come in!
I changed the config to...
#--------------
#Image Settings
#--------------
#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';
#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = $config['root_url'] . '/files/home3/designreality/graphic/uploads/images';
$config['uploads_url'] = $config['root_url'] . '/uploads';
Is that correct?
Thank you for all your help so far. You have been awesome!
Jane
Unfortunately on the http://www.designrealitygraphics.co.uk/ ... ness-cards website the images don't come in!
I changed the config to...
#--------------
#Image Settings
#--------------
#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';
#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = $config['root_url'] . '/files/home3/designreality/graphic/uploads/images';
$config['uploads_url'] = $config['root_url'] . '/uploads';
Is that correct?
Thank you for all your help so far. You have been awesome!
Jane
Re: .htaccess code conflicting, anyone advise?
I see them. did you fix it?
Have you tried using the internal pretty URLs or .htaccess again, just not both at the same time...
Have you tried using the internal pretty URLs or .htaccess again, just not both at the same time...
-
Metal Beryl
- Forum Members

- Posts: 69
- Joined: Wed Apr 18, 2007 9:57 am
Re: .htaccess code conflicting, anyone advise?
To get the images working I went into the admin panel and changed the url links from the old link old domain to new domain.
Now when I try to add new images it wont let me, in the admin panel when i got through the usual process to add an image to the page the image doesn't show in the Image properties box and they link to the image comes in as http://www.something.com/uploads/images/picture.jpg the http://www.something.co.uk should be my website address why is it coming up with something.co.uk?
Any clues! This job isnt really going to plan
Now when I try to add new images it wont let me, in the admin panel when i got through the usual process to add an image to the page the image doesn't show in the Image properties box and they link to the image comes in as http://www.something.com/uploads/images/picture.jpg the http://www.something.co.uk should be my website address why is it coming up with something.co.uk?
Any clues! This job isnt really going to plan
Re: .htaccess code conflicting, anyone advise?
The paths are set in the config.php you may want to revisit it to see if something changed...

