I'm going through my email now and I guess I'm soon to find one from
you and reply to that as well, but mostly in case someone finds this post
later I figured I'd reply here as well.
Simon told you exactly right. When we install Strongbox we rename your old
.htaccess file to .htaccess_bak. To disable Strongbox temporarily you can
just rename .htaccess to .htaccess_sb and .htaccess_bak to .htaccess.
If your FTP isn't showing "hidden" files, which start with a dot, you can normally
correct that using the ettings in your FTP client. In WS-FTP I believe the
setting is called "remote file mask" and you want to set it to "-al".
To re-enable Strongbox just reverse the renaming procedure.
If your host broke Strongbox during the move that's almost always because
they failed to preserve the file permissions (chmod) and ownership (chown).
If they simply copied the files over without using any method to preserve
these important attributes they probably broke a lot of your scripts, including
your processor's script, so there's a good chance that new people are
unable to sing up to your site and that old expiring subscriptions aren't being
removed properly. If possible have your host copy the site over again
properly, probably using "tar" to preserve permissions and ownership.
Here's a page with step by step instructions on how to move a site without
breaking PHP and CGI scripts:
http://bettercgi.com/strongbox/manual/move_server.html
VictoriaXXX, you said you had some kind of trouble with my forum.
What was the problem, exactly, please? It does seem to be generally working
OK since other people have been posting.