[HM666]

That has nothing to do with your default skin at all. The original developer more and likely created the theme for a vB version other than what you are using. Occasionally they change the templates to fix bugs in new versions so there may be a conflict between what they had on their site and what you are running on yours.

What version of vBulletin are you running?
What version of vBulletin do they say that skin is for?

Answer those and you may find there is a conflict within the versions. Sometimes templates can change from one small step up like 4.1.1 to 4.1.2. So that can matter depending upon which versions they area and what was changed in the version.

Do you have any mods/add-ons installed on the site?

If you are then there could possibly be a conflict with a mod that you have installed and the skin as most designers when they create a skin do it on a dev board with no hacks installed for obvious reasons. So try the following first:

You will need a HTML editor like Dreamweaver or use NotePad. DO NOT use MS Word or Word Pad. Global disable: open your includes>config.php file and find:

<?php

and under place:

define('DISABLE_HOOKS', true);

Save and upload again to your server in the includes directory.

If you find that it works after disabling the plugins globally then re-enable the plugins by putting // in front of the code so it looks like this:

//define('DISABLE_HOOKS', true);

Save and upload again.

Then you will have to go through your mods one by one until you find the one that is causing the conflict.

If you globally disable everything and you still have this issue then its a poorly coded skin or the skin version is not compatible with the version of vBulletin you are running. There are a couple of ways that you might go about fixing this.

1. If your vBulletin version is a lower version (say you are running vBulletin 4.2.1 and this skin is for vBulletin 4.2.2) then upgrade to the latest version of vBulletin 4.2.2 and it may possibly fix your issue.

2. And this is usually the case unfortunately, you may have to edit the file yourself and fix it or hire someone to fix it. I say this because looking at the ThemeCrate site he is running vBulletin 4.2.0. So you are most likely gonna have to fix this yourself. If you are code savvy then this is just a PITA and you should be able to do it if not, then you may want to hire someone who can fix it for you.

To Fix It Yourself:

Try going to your admincp and go to Styles & Templates > Style Manager and choose your style. Click the "Go" button next to the StyleVars drop down. See if there are profile changes that can be made in there. Make the changes, save them and then view the skin to see if that is what you want. If not go back and try again. If none of those changes work then...

...You will need to do some research.
First, you will need to turn on template notifications. To do this login to your admincp and go to Settings > Options > General Settings and then find "Add Template Name in HTML Comments" and tick the "yes" box and save.

Second, in this instance its probably best to use FireFox if you do not use it already install it and then download and install the FireBug add-on. The FireBug add-on allows you to view code and see where exactly in the code the things you need are found so you can change them. You will need to open up the profile page and right click on an area and choose "Inspect Element With FireBug". This will allow you to see the code that is associated with that area only. Find the tag that you need to change probably something as a div or span class tag and make a note of it. Write it down, copy and paste it to a notepad file whatever you do.

Third, Right click on the profile page and now choose "View Page Source", this will open a new window and give you the page source. Now take your tag from above and go to Edit > Find and paste the tag into the search field at the bottom of the page. now you can find every instance of this tag. Above the area that you are working with you will now see the template marker telling you what template this tag and this code is found in so you can go straight to that template in your admincp and make the change.

Hopefully this should get you started. I'm assuming you may have some coding knowledge, if you are not code with code or I lost you then you may want to hire someone to fix this for you from the Paid Requests area.