Hi Reynaldo,
WFSection seems to work perfectly with the hack. The only module I've encountered trouble with so far is Glossary, and I think I've fixed that by adding a XOOPS_URL to some of the paths.
On the other question, what I was trying to do was to add one additional rule to .htaccess to strip the xoops/ out of the URL for a site that I had moved from a subdirectory into the root directory of the domain, i.e. from
http://www.internetadsales.com/xoops/ to just plain
http://www.internetadsales.com. That rule, which I reproduced above, works by means of an external redirect flag on the RewriteRule. It seems to work successfully on that site (you can test by clicking the first link).
In theory, the way mod_rewrite works is to run through the list of rules in the order in which they are listed in .htaccess, so the requested URL should first get xoops/ stripped out of it, then the resulting URL should be modified by the changes applied in your hack.
However, in my frenzy of testing the only way that the initial rule seemed to work properly was by having both R and L flags applied to it. The R flag forces an external redirect, and the L flag, as I understand it, causes .htaccess to stop making changes to the URL when it is reached.
So, I was just wondering if you (and don't try to fool me with this "I'm no guru" stuff) knew of another way to strip the xoops/ out of the requested URL that would not require an L and R flag, and that would allow processing to continue through the changes applied by your hack?
I just reread this and realized I'm not quite sure what I'm looking for. Here's an attempt at an example:
Suppose Google has spidered an article in WFSection. The link on which the user would click is as follows:
http://www.internetadsales.com/xoops/modules/wfsection/article.php?articleid=13When they get to the site, the rewrite rule I added removes the XOOPS from the URL, placing the user here:
http://www.internetadsales.com/modules/wfsection/article.php?articleid=13which is the correct current location of wfsection. Users navigating internally, however, wind up at this URL:
http://www.internetadsales.com/m-wfsection+article+articleid-13.htmlwhich is, of course, functionally identical. I think what I'm looking for is a way to make sure that a user clicking on the first URL doesn't wind up with the second one displayed in the address bar, but the third. In other words, that users are presented with the same URL whether they navigate to the page externally or internally. I don't suppose it matters that much, but it would make for a cleaner site and potentially improved search engine placements in the long run.
I'm not sure if that's any clearer. I find this whole business confusing, but I'm delighted that your hack seems to be working so well.
Cheers,
Béla