Version 1.23.4

Released: 2005-02-03

custom scripts for databases new

environmental variables for both scripts:

username - DA username
database - name of the db
user - name of the user created
passwd - password used.  

Note that will not be called when a database and it's user is being created. This means that any code used in will have to be doubled in as well for anything you want done to a new user.

Add the contents of users home directory to backups new

currently user backups include serveral directories from the users home directory, but any extra files added by the user in /home/username wont be added. This change will add the extra contents of their home directory to the backups.

template for new email account new

The new template allows admins to show which pop/smtp server they want to show their users to use, and also change the output in case they have a different email server.

If you'd like to use your own custom template, first copy it to the "custom" directory, and edit the template in there.


### START ###
Your account |USER|@|DOMAIN| has been setup. In your e-mail program, use:<br><br>

<table class=list cellpadding=3 cellspacing=1>
<tr><td class=list2 align=right><b>Username:</b></td><td class=list2>|USER|@|DOMAIN|</td></tr>
<tr><td class=list  align=right><b>Password:</b></td><td class=list >|EMAIL_PASS|</td></tr>
<tr><td class=list2 align=right><b>Pop3 Server:</b></td><td class=list2>mail.|DOMAIN|</td></tr>
<tr><td class=list align=right><b>Smtp Server:</b></td><td class=list>mail.|DOMAIN|</td></tr>
### END ###

reset password and resend welcome email with pass. (SKINS) new

I'll add a checkbox in the "resend welcome email" area. If unchecked, the password will be unchanged and shown as "irretrievable". If checked, the password will be set to a new random password and included in the email.



add the following to the resend email form:

<input type=checkbox name=newpass value="yes">New Random Password

Checkbox to enable safemode for new domains by default (SKINS) new

Add a checkbox in the php safemode section to enable safemode by default for new domains. It will just set:


in the directadmin.conf file (or alternatively, safedmode=OFF)



<form action="/CMD_PHP_SAFE_MODE" method=POST>
Default for new domains:
<input type=radio name=enabled value="ON" |ONCHECKED|>ON
<input type=radio name=enabled value="OFF" |OFFCHECKED|>OFF
<input type=submit value="Save">

newsyslogd on freebsd 4.x produces error fixed

flags N and U should be replaced with - in the /etc/newsyslog.conf

fix, run:

perl -pi -e 's/\\sN\\s/\-\/' /etc/newsyslog.conf
perl -pi -e 's/\\sU\\s/\-\/' /etc/newsyslog.conf

mysql 4.1.x requires old_passwords fixed

If you are using mysql 4.1.x, phpMyAdmin isn't able to work with the new password format for mysql.


cd /usr/local/directadmin/customapache
./build clean
./build update
./build php n

NOTE: If you are using apache 2, use "./build php_ap2 n" instead.

What it does:

uses --with-mysql=/usr instead of just "--with-mysql" in the configure.php file, assuming you have /usr/include/mysql/mysql.h. For FreeBSD, it would be "--with-mysql=/usr/local/mysql". The customapache script is updated with this change, so do a "./build clean; ./build update; ./build php n" and it should use the actual installed mysql client libraries you have on your system instead of using the client mysql libraries that php includes (3.x).

If you are upgrading to 4.1, then you'll also have to update the grant tables to have a longer password field. Type:

mysql_fix_privilege_tables --user=da_admin --password=`cat /usr/local/directadmin/conf/mysql.conf | grep passwd |cut -d= -f2`

Once updated, you'll have to resave the passwords so that they are stored in their full length.

Another possible fix:



To the /etc/my.cnf. Reset your mysql passwords through DA.

CMD_API_DATABASES login format fix fixed

issues with "usrename" vs "admin|username" fixed. It was checking the sessions file for the username being used, but the api doesn't generally receive session login info (only base64 auth data), thus causing a segfault.

This fix might apply elsewhere if the same issue exists.

custom ftp accounts not included in backup fixed

Notes about this fix:

If you change the user's username custom ftp accounts will not be restored because they'll be pointing to an incorrect directory.

Eg: user bob, has custom ftp in /home/bob/customftp

You rename bob.tar.gz to fred.tar.gz and restore fred.tar.gz

The custom ftp will still be pointing to /home/bob/customftp which is not in /home/fred and will not be restored. Since DA does not know the previous username (bob) in the fred.tar.gz, it makes it difficult to do the home directory swapping, especially when some are /usr/home/bob, etc.

Domain doesn't show up in domains.list file for a reseller restoring his own domain fixed

When a reseller is restoring his own user data, the restore process was treating the User as it's own entity and saving everything correctly. But because the reseller was also using the domain.list file at the same time, it was overwritten to the previous version when the backup was completed.

This fix does a simple name check to see if the reseller is restoring himself, and if he is, it will fill the domains.list file controlled by the active sessions after restoring the backup so the domains.list file will be filled with the newly restored domains.

Last Updated: