I have a few problems relating to Friendly URLs, particular using an alias path. Allow me to explain where I’m coming from...
I’m setting up a site that will end up having multiple locales for the site, but it’s intended that they will all stem from the one MODx installation. To achieve this I want to use FURLs to create locale folders. For instance: Australia (www.domainname.com/au/), United Kingdom (www.domainname.com/uk/), Spain (www.domainname.com/es/). Using FURLs will also assist with SEO presence. Currently the modx installation is in a subfolder: www.domainname.net.au/modx/ - I don’t know if this is having an impact on any of the following.
I finally have FURLs working, but I’m getting some significant errors:
1. For starters, the Wayfinder Menu I’m using is not working. I noticed that on uploading the MODx database from our local dev environment to an online server, I had the same problem, and could correct it by correcting the File Manager Path in the Modx Config. Though the config is now correct, I’m wondering if the alias path is conflicting with this setting.
2. Links to images, js and css are not working. I can’t figure this one at all.
3. Having set up the /au/ alias path, each time I click a link, the browser will add another /au/ to the link. So if I’m browsing at www.domainname.com/modx/au/home.php (alias+suffix), the link I click will go to www.domainname.com/modx/au/au/home.php. The next time I click the link it will go to www.domainname.com/modx/au/au/au/home.php, etc.
4. AjaxSearch is requesting php_mbstring, where prior to activating FURLs, it worked fine. I’ve changed &mbstring to 0, but that’s doesn’t answer the question of why the change was needed in the first place.
I’m using Modx 1.0.0 on Linux with Apache 2.0.63 and PHP 5.2.10.
Can anyone help with either of those 4 errors? I’m hoping that there’s a single solution to all of these.
I would move the MODx install to root and then use "use alias path" option. That makes
MODx threat containers as folders in the url.
I’m not able to move the modx install to the root folder because it’s currently hosting the old website. So I can understand better, how would having modx in the root folder make a difference to the way the FURLs work? Shouldn’t it just make the change to the end of the doc root?
What if I moved the .htaccess file to the root, and change the "RewriteBase" and RewriteRule to include "/modx"?
The use alias path config is on.
Some hosts need follow symlinks to be commented out and some doesn’t.
But another approach on this is hack:
http://modxcms.com/forums/index.php/topic,37122.msg224439.html#msg224439
and NOT using "alias path" but slashes as aliases...
