Messages

You -may- have to change nameservers on the domains for them to be moved, I'm not sure if Plesk uses the same nameservers as the main server does

Plesk and the main server use different nameservers and IP addresses, so the change will be necessary.

The complete instructions are located there.

The mail function is still enabled on the main server.

It would probably be a good idea to move all your stuff anyway to the main server (because it is more flexible and up-to-date).

You know, it would have been simpler to just write http://lvcs.net/dreg.php

Probably the old members can get the name of the new path each time it is changed by subscribing to a mailing list?

Would work for Perl users, but not for PHP users. In PHP, the sendmail path is hard-coded in the serverwide configuration file (php.ini).

Either way, if theres much more problem with spamming, you won't have to worry at all because mail() will be a disabled function, like on the plesk server.

That would be sad. Some people like me rely on this function.

You need to use mysql_connect() to connect to the database server first. If you are already using it, verify that you are providing your database username and password properly. It should look like:

Code Select Expand

mysql_connect('localhost', 'my-db-username', 'my-db-password');

Note: You need to create a database before using it, if you have not already done so. You can add a database to your account using your account control panel.

It looks like the path to sendmail recently changed. This might be your problem (though I don't know, I never used Perl).

Try to use /usr/sbin/sendm2 to send e-mails.

Email is not working for me either, I am not using Plesk.

Please provide more information. mail() is working fine for me.

Have you tried to log in manually to phpMyAdmin using your new database's username and password?

Anyhow, do you have any suggestion on Rewrite tutorial website.  I read one from apache it's awesome but hard to undersatand.

Well, I started by learning how the PHP regular expressions work. Then, I learned the rest from the documentation on apache.org. It is mostly technical, but I got to understand how it worked with a lot of trial-and-error.

I guess you could also try this one. It should combine rules 1 to 3.

Code Select Expand

RewriteRule ^([^/]+)?miku([^/]+)?\.html$ doc/int_miku/$1miku$2.html [L]

If you are using Internet Explorer, its cache might be corrupted or stuck with old versions of pages.

Check with another browser, like Firefox or Opera. (Avant Browser and Maxthon are only a hidden IE.)

The RewriteRule is not applied because the request doesn't match the pattern. Patterns never match if they start with a /.

This one should work, however:

Code Select Expand

RewriteRule ^cours/(PHP)/([^/]*)\.php$ index.php?cours=$1&id=$2 [L]

There is a 500 error because your rule causes an infinite loop:

1. Rewrite /internet-miku-yoyo.html to /doc/int_miku/internet-miku-yoyo.html
2. Rewrite /doc/int_miku/internet-miku-yoyo.html to the same thing (and it keeps doing this forever).

The easy way to fix the problem is to rename your directory and files to not use the word "miku" (ie. use /doc/int/internet--yoyo.html).

The other way to do it would be to change your RewriteRule to:

Code Select Expand

RewriteRule ^([^/]+)miku([^/]+)\.html$ doc/int_miku/$1miku$2.html [L]