I sucessfully updated my backup XOOPS xsas site-no problems whatsoever and showed the correct version info on the administrative area. This site is an exact copy of my online site; however, when I closed my online site (to all users except the webmaster) and updated it--exactly the same way I updated my local site, I get this error message in the header on the login page.

ate not allowed during processing of a GET request', 0); return false; } } ?>>

I then logged on as webmaster and the software returned a blank page with the same error as above.

Fortunately I had all files backed up and I simply deleted the updated files and ftp'd the backup files to my server which corrected all problems.

I'm certain I need this update, but how do I go about correcting this problem? Thanks in advance for any suggestions or help with this matter.

Using XOOPS 2.0.13 with default theme.

Non Standard Modules:
Tiny Content
Protector
Soapbox
CBB

Server info:
Apache 1.3.33 Running
DirectAdmin 1.24.3 Running
Exim 4.50 Running
MySQL 4.0.23 Running
Named 9.2.4rc6 Running
ProFTPd 1.2.9 Running
sshd Running
vm-Pop3d 1.1.7e Running

bump

Success!

Powered by XOOPS 2.0.13.1 © 2001-2005

I decided that my ftp program may have not written the files properly to my Internet site, so I decided to copy the relevant files and folder from my Internet site to my local computer and update from there. I then deleted the relevant files and folders from my Internet site and ftp'd the updated files from my local computer to my site. It worked like a charm.

I now know that I can't trust my ftp program to properly overwrite the files to perform a proper update. I'm using SmartFTP v1.5 and I may have not configured properly.

If anyone is versatile in the use of SmartFTP and can give me any pointers on what I may have done wrong; I would sincerely appreciate the help, and I hope the info I have presented here will help others.

Thanks to developers of what I consider to be a magnificent CMS portal--Xoops!

This thread helped me in deciding my FTP program may be the culprit.