Ok, now that I got past my protector issue and actually have the sites online I have another problem.

My old sites were on a different host...

I just started using a new host and decided to upgrade to the lastest XOOPS on the new site and restart the sites from scratch.

I have 2 sites I moved to this new site.

When I was creating the site I put them on the live server as a sub domain to make sure they worked right before going live. This meant they were available by going to...

mysite.host.com

When I got the sites up and running I pointed the name servers from the old sites to the new sites and you can get to them by going to...

mysite.com

However once you type in mysite.com, ANY action on the site goes back to the mysite.host.com URL. And although it does work it is not my intention. It should always use the mysite.com URL.

Is this a XOOPS "feature" or a hosting issue?

I would appreciate any feed back.

I tried deleting cookies and other history and that wasn't the issue and even went to another computer that never was on the sub domains and it operated the same way.

Should have looked through the source before I asked this but assume this line in mainfile.php is the culprit?
define('XOOPS_URL', 'http://myhost.com');

Rodney

hi' one more

1 file contains all your codes and path : mainfile.php.

3 steps :

1) In mainfile.php, you have to enter your new domain name instead of old one.
2) Export your database and make a backup. Use search and replace function (eg with Notepad++) and save. Import it !
3) Clean all XOOPS cache by deleting* content of :
• xoops_data/caches/smarty_compile/
• xoops_data/caches/xoops_cache/


* :
- for security reason, do not delete index.html files
- you should make a copy of xoops_adminmenu_XoopsGui...php file before deleting