Thanks for the information. It was pretty much what I expected, bu it was nice having it confirmed.

Thanks again.

Wordpress gives options for generating nicer permalinks. After you've configured the way you want the link to show, Wordpress creates the code you're supposed to add to the .htaccess file.

Question: does that .htaccess file go into the Wordpress module folder, or into the root folder?

Maybe it's because I'm not feeling well, but I haven't found any posts that answers my question.

I deleted both those sites and instead of using WS-FTP 9.01, I used Cute FTP Pro.

Everythiing seems fine, thuugh I only did some brief tests. The menus display properly and sendmail works just fine.

I'm never certain about anything, but I did have another problem with another CMS -- a theme uploaded with WS-FTP failed with a "parse error." There were other people on the forum with the same problem.

So I uploaded the theme again with Direct FTP. Worked perfectly.

I started a new thread, because I've read a few posts here from people having the same problems I had. I'm hoping more people who have the problem will see my story.

I wonder if the others were also using WS-FTP?

I tried installing three XOOPS installations -- different domains on my shared webhosting account -- with WS-FTP 9.01.

One seems okay.

One wouldn't use sendmail to send activation letters to verify sign-ups.

One would use sendmail for the activation letters, but delivered some strange menus in the preferences section. I also noticed that when I logged into administration for the first time, I didn't get the red box that told me to delete the installation directly and permission mainfile.php to 444.

I recalled that a few weeks ago, I tried using a new theme on a differt CMS. I always got a parse error, as did others.

In that case, I used Direct FTP to upload the theme and it worked perfectly.

Aha! I deleted the two failed installations, and then used CuteFTP Pro to upload. I tried keeping the conditions the same and all that.

Both installations are working fine now.

I don't know if it's just weird coincidence, or if there's a bug in WS-FTP that makes it hiccup from time to time, or if the program just hates my computer. Or maybe I triggered an option in the program that messes things up. But I've noticed there are quite a few posts describing exactly my problem.

Who knows? Computers are funny things.

An edit -- What I'm getting at is that sometimes it seems WS-FTP botches the scripts that call sendmai.

Yes, everything looks okay there.

Now the plot thickens. After I wrote the previous post,I installed XOOPS on two more domains using my reseller account.

Site 1: everything appears to be fine, even on the sendmail thing

Site 2: it does sendmail okay, but when I go to system admin | preferences, I come up with this:

_MD_AM_SITEPREF
[Edit]
[Edit]
[Edit]
[Edit]
[Edit]
[Edit]

I don't know what to do. Only thing I can figure is that something's happening during the upload. (I use WS_FTP Pro).

Like many others, I'm having trouble sending an activation email to new users. There's a lot of posts on the subjet, but none of them really answer the question.

Same story: after the user registers, the screen goes blank. No email is sent. I've tried all the solutions except SMTP because it's a business address and the name will show up in the headers.

When the user tries to log in, he gets the "not activated" stuff.

Last week, I was playing with another CMS and sending the activation email worked just fine.

Here's the details, if anyone can help:

Xoops version: 2.0.9.2 stable
Hosted: shared hosting
Server software: Apache
Apache version: 1.3.33 (Unix)
OS: Linux
Linux kernal version: 2.4.21-20.EL
PHP version: 4.3.10
perl version: 5.8.1
MySQL version: 4.0.22-standard-log
Apache version: 1.3.33 (Unix)
Path to sendmail: /usr/sbin/sendmail
Path to Perl: /usr/bin/perl

That's about all I know. If anyone can help, I'd sure appreciate it.