Josh Byers

That was blunder in trying to get subversion to bend to my will. I’ve updated the versions and the issue should be corrected.

I have updated the plugin with some bug fixes so the current version (3.0.3) should work. I also re-uploaded version 2 if you would like to downgrade. I won’t be supporting that version but it will be there for you to use if you prefer.

Gotta love it when a missing bracket is the cause of the troubles.

I have updated the plugin and fixed the ever expanding donate box problem.

It was not my intent to require donattion – but I did receive more donations in a few days than I’ve received in the last couple of years ??

And new psd files were uploaded so that should be fixed.

Can you let me know what browser you are using? Thanks.

The new version has been uploaded successfully I believe…

Let me know if there are any issues.

Can you explain your issues a little more?

I just posted an updated version – should be up in a few minutes. There was an issue with subversion uploading the plugin to the WordPress repository. Sorry for the troubles.

I just posted an updated version – should be up in a few minutes. There was an issue with subversion uploading the plugin to the WordPress repository. Sorry for the troubles.

Hey everyone sorry for the troubles. There were some issuses last night with subversion uploading the new version. I’ll try and get this all ironed out today.

I was correct in that the dns was not refreshed by the webhost (Dreamhost)

Once I manually refreshed the dns through their control panel the site was working great after a bit of propagation time.

Like Ron said I did not need the additional domain mapped in the plugin.

For anybody else that might come across this scenario I have the “a” record pointing to my main ip that WordPress multisite is installed to, and the “www” cname record pointing to @.

Thanks for the advice.

After doing some more investigating I believe that the dns was not refreshed by the webhost – so I manually refreshed and am now waiting for propagation to occur. I’ll post back the results.

Thanks for the code addition. I always knew this happened but never looked at it as a bug.

I suppose it would be best if the header didn’t appear in those situations.

Thanks for the heads up on the custom css issue with the login page. As you figured out I didn’t add in the variable to pull in the custom css to that page. I have corrected that for the next release.

As for the “linking to my stuff” I always found it easiest to dissect code if it has real world examples – and so why not use my url?

Not sure about the invalid script tags – maybe you can educate me – but I’ve never seen the script tag matched up with “css” before.

I realize that the admin header is inserting in the head tags but the only WordPress hook that I have found that allows for the custom header to be placed properly is ‘admin_head’. If you or someone else has a answer I would be more than willing to rectify the situation.

I’ve uploaded a beta version of next release of the Custom Admin Branding plugin that should solve these problems. Please let me know if there are still issues.

Download plugin version 2.1