JMorris wrote:
The activation link problem is a known bug. This is being addressed in RC2 which should be out soon. In the meantime, the following activation link workaround worked for my RC1 site, it will probably work for yours too.

Link: Activation Link fix

The issue with receiving the error message when logging in with a FQDN (Fully Qualified Domain Name) that is not what you set XOOPS up with is a strange one, but I don't think it is a bug per say.

Example: You installed XOOPS using http://www.yoursite.com, but people get the error when they log in using yoursite.com (no www.).

I had the same issue on my site. What I did to resolve the problem is use mod rewrite to create a 301 redirect from http://www.mywebresource.com to mywebresource.com. This way, regardless of which url the end-user uses, they will automatically be forwarded to the url I've specified.

Put the following in the directory where you installed XOOPS in a file called .htaccess

Options All -Indexes
RewriteEngine on
RewriteCond %{HTTP_HOST} !^brianrsmith.net$
RewriteRule ^(.*)$ http://brianrsmith.net/$1 [L,R=301]

Make sure the following lines in mainfile.php use http://brianrsmith.net or you're gonna have a headache or two.

// XOOPS Virtual Path (URL)
    // Virtual path to your main XOOPS directory WITHOUT trailing slash
    // Example: define('XOOPS_URL', 'http://brianrsmith.net');
    define('XOOPS_URL', 'http://brianrsmith.net');

For future reference, all of the above information can be found using using the FAQ section of this site and using the search function of this site. I'd also recommend using google with the site:xoops.org qualifier appended to the end of your query string.

Hope this helps.

James