When it comes to developing your own stuff, it is always the best to make the code yours too, not just the copyright and such.
As @Rarst already pointed out, the first thing to check if the theme’s folder. I faced the same issue before and changing the theme’s folder fixed the issue for me.
But for future goods, you should start prefixing your code. It means that you should prefix your theme’s name, functions, classes, etc … by your or your company’s name. It’s less likely if someone ever will publish a theme named burgi-professional, but a general name such as professional may exist anytime.
This also applies to class names and functions to. Prefix your functions like this:
function burgi_get_theme_options( ){ ... }
So there is a lower chance of running into such issues. Same goes for CSS classes, and HTML ID attributes.