Download
2011-06-25, 03:41:27
Hi,
Firstly, finally im actually accepting a CMS as a method to manage content on our site (kudos ccagle8 for changing everything). GS was introduced via our svr admin (who is away on holiday and i doubt will be able to help with this issue so quick when he comes back).
GS is brilliant and everything has worked perfectly for us in the past and for me now during the upgrade though i am stumbling upon my first problem. I have just upgraded GS to 3.x (3.0 stable from 2.03) and thought i'd take the opportunity to move the installation out of the web root directory (.../public_html/) and into the 'cms' directory (.../public_html/cms) as the required subdir's QS needed shall i say was making a 'mess' of the otherwise 'organised' dir structure we have with other components of the site... hence wanting things a little more manageable by moving it into the '.../cms' dir.
As QS is the main component of the website, i've been trying to establish a way (via .htaccess) to have QS reside in .../cms with the "fancy url's" being accessible via the root dir ... eg "www.mydomain.com/contact-us". Naturally this works just fine when QS is installed into the root '/' but after installing it into '/cms' (even after a clean install) i cannot manage to stop the browser from displaying 'www.mydomain.com/cms/contact-us'.
Is there some magic i can place within a .htaccess file to do this? personally i am a Windows desktop app programmer and web/apache/server stuff is unfortunately a little outside my scope. I've been playing w/ it for quite a while now and am at a loss, so have resorted to the forums here to hopefully receive some help from one of the experts. It would be great if the resolution is a generic .htaccess mod (rather than a index.php solution in the root or manually doing RewriteCond/Rules in .htaccess for every 'slug'/page (hope thats the correct term))
Kind regards and thanks in advance!
Ben
Firstly, finally im actually accepting a CMS as a method to manage content on our site (kudos ccagle8 for changing everything). GS was introduced via our svr admin (who is away on holiday and i doubt will be able to help with this issue so quick when he comes back).
GS is brilliant and everything has worked perfectly for us in the past and for me now during the upgrade though i am stumbling upon my first problem. I have just upgraded GS to 3.x (3.0 stable from 2.03) and thought i'd take the opportunity to move the installation out of the web root directory (.../public_html/) and into the 'cms' directory (.../public_html/cms) as the required subdir's QS needed shall i say was making a 'mess' of the otherwise 'organised' dir structure we have with other components of the site... hence wanting things a little more manageable by moving it into the '.../cms' dir.
As QS is the main component of the website, i've been trying to establish a way (via .htaccess) to have QS reside in .../cms with the "fancy url's" being accessible via the root dir ... eg "www.mydomain.com/contact-us". Naturally this works just fine when QS is installed into the root '/' but after installing it into '/cms' (even after a clean install) i cannot manage to stop the browser from displaying 'www.mydomain.com/cms/contact-us'.
Is there some magic i can place within a .htaccess file to do this? personally i am a Windows desktop app programmer and web/apache/server stuff is unfortunately a little outside my scope. I've been playing w/ it for quite a while now and am at a loss, so have resorted to the forums here to hopefully receive some help from one of the experts. It would be great if the resolution is a generic .htaccess mod (rather than a index.php solution in the root or manually doing RewriteCond/Rules in .htaccess for every 'slug'/page (hope thats the correct term))
Kind regards and thanks in advance!
Ben
