Hi There,
I seem to have a strange problem installing friendly url’s. I have tested to see if my web host is set up for .htaccess and all is fine. I have Modx installed into the root directory. I’m also aware there is another .htaccess in the manager folder although I can’t quite understand what this is for?
Below is the error message I get when I set everything up:
/homepages/26/d233536634/htdocs/manager/includes/document.parser.class.inc.php(814) : regexp code on line 1
Fatal error: preg_replace() [<a href=’function.preg-replace’>function.preg-replace</a>]: Failed evaluating code: (1 ? (isset($aliases
I’m using the latest version. Maybe I’ve set something up wrong. Can anyone help?
Thanks
-
MODX Staff
- 12,272 Posts
Please see the ’help us help you’ link in my signature. Thanks!
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
ok to add further to this it’s hosted on a: Apache/1.3.34 running mySQL 4.
-
MODX Staff
- 2,502 Posts
I assume you renamed the ht.access to .htaccess in webroot?
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub
yeah sure did. Like I said I’ve tested the .htaccess file and it works. I’m sure this is a PHP error of some sort as I get the message above even when I delete the .htaccess file and leave the friendly URL’s feature on.
-
☆ A M B ☆
- 24,524 Posts
It looks like something got corrupted in your cache file. I would suggest uploading the install folder again, deleting the cache files, and running the installer in upgrade mode to reset things.
You say you installed seo friendly urls? Are you reffering to the "Strict SEO Friendly" from the repository or the default SEO Friendly built into MODx?
If the first option (Strict SEO Friendly) then make sure that you installed it as a plug-in not a snippet. The error above has to do with the loading of snippets into the cache. So either the cache is corrupt or there is a bad snippet.