ouch.... bad idea there, im guessing its set in the directadmin main configs or similar....... check your directadmin.conf and check for any admin config files for a skins option.........
If that fails, search for your skins directory, ***MAKE A BACKUP OF THESE DIRECTORYS*, make a copy of your 'default' (the directadmin skin) skin, remove your new skins directory, and rename the copy of the deirectadmin skin you have to the same as your new skin WAS: in simple terms:
(in skins directory)
DirectAdmin_default_skin
Power_user
Your_custom_skin
make a copy of the DirectAdmin default skin and backup the new skin just incase DA does not like this:
DirectAdmin_default_skin
DirectAdmin_default_skin_copy
Power_user
Your_custom_skin
Your_custom_skin_backup
now remove Your_custom_skin (the directory) so you have:
DirectAdmin_default_skin
DirectAdmin_default_skin_copy
Power_user
Your_custom_skin_backup
now copy DirectAdmin_default_skin_copy to the location of the skin you just removed, and DA is now using:
DirectAdmin_default_skin
DirectAdmin_default_skin_copy
Power_user
Your_custom_skin (PREVIOUSLY NAMED DirectAdmin_default_skin_copy)
Your_custom_skin_backup
Now, you should be able to login into DA and use the default skin, go into the skins section, set all users to use another skin aswell as yourself then remove the bothced up skin!
As long as the above message is, it should take no longer than 5 minutes, im sure there is an easier fix but im certain this will work until DA respond
Chris