[AndrewD]

Originally Posted by Mupetz

AndrewD, the mod_rewrite (admin settings field), what is supposed to do ?
If the seo friendly option is enabled and the rewrite conditions are given to the .htaccess file or directly to http.conf file ; what mod_rewrite field should do ?

I deleted all other .htaccess rules (from vbseo , etc) to see if it is a conflict or not. It doesn't work even with the proper rules you quoted ; so it must be the script/commands.

Does anybody made it work with .htaccess rules ?
Please anwser.

Sorry, we're going round in circles with this.

For me, the SEO features of LDM work fine with the htaccess rules I sent you (and which are now in the Wiki), and also works with (very similar) rules in http.conf.

The SEO features work at two levels:
- you tell LDM to generate SEO-friendly links (i.e. yoursite/forum/local_links/link/12/3 instead of yoursite/forum/local_links.php?catid=12&linkid=3) by setting the seo_friendly option on the LDM admin page
- you tell Apache how to process these links by the rules in http.conf/.htaccess.

It seems your problem is in step 2. The only way to get to the bottom of it is by step-by-step debugging of your Apache setup. The easiest way is with a combination of RewriteLog and RewriteLogLevel commands (see apache documentation). But maybe you cannot do this on your server, in which case, it's a matter of trial and error - add one line at a time until you discover what breaks.

The LDM admin setting "mod_rewrite" is confusing things, I think. This has absolutely nothing to do with search engine optimisation - turn it off - you should not be using it. It was added to LDM to implement a few of the functions of the Apache module. Its purpose is explained in the Wiki (see http://www.eirma.org/wikis/index.php/Hacking_LDM). It modifies 'on the fly' the hidden urls that are stored in your LDM database, at the instant before someone tries to visit one of them. Suppose (for example) you've set up a lot of LDM entries pointing to files at http://site1 and they've all moved temporarily to http://site2. Instead of editing your whole database, you can just turn on LDM's mod_rewrite, with a rule to translate site1 to site 2. As I said, turn it off, you don't need it.