[Talisman]

Originally Posted by Infantrymen

^ if you don't know what you're doing then don't try to do it... AND if you do decide to do it after the fact, don't go blaming others for your mistake..... Not jumping on anyone just saying don't go blaming others if you are the one that did the messing up...

@ Infantrymen:

I've read these posts, Infantrymen, and yumyumcat isn't blaming anyone. What she's doing is voicing her complaint that no one will help her after a simple install causes problems she didn't or couldn't anticipate beforehand. This is not the only new(ish) member who has found out -- the hard way -- that (like the rest of us) she really is on her own if she attempts even a simple modification to customize her board.

This person is obviously frustrated..... to the point that she came here to post about it.... and being so new to vBulletin in the first place, she's understandably confused about what support there is (or isn't) and where it comes from.

My question to you is... exactly how does it help this person (or any other newer members here) for you to tell her off by saying it's her own darned fault for trying something new? Not only do you offer her no helpful advice, whatsoever, but the outright unfriendliness you've shown is appalling.

Originally Posted by yumyumcat

I've been installing your hacks and everytime I do this, my default skin turns into a nitemare and now after the marquee install, NONE of my skins are are working, but two.

@ yumyumcat:

First of all, what skin are you using as your default skin? Did you download it from here..? somewhere else..? is it an adaptation you or your admin have modified yourselves?

Most hacks really don't mess around with the skins we use - except when it comes to content changes needed on the templates. And for those hacks, the author will typically provide the necessary step-by-step html code changes you need to make yourself for the DEFAULT templates you get with your initial install of vBulletin. (This means that if you're using some other skin as your default, there may be a lot of differences between those templates and the original vB versions and those code changes you get from the hack author won't work as well.)

Those of us who wish to use multiple skins AND install various vB hacks do our best to simplify code changes by setting the default vB skin as the default skin for the board, which functions as the PARENT skin. Then, all other skins we want would be installed as a CHILD skin beneath that default.

When you install a hack, make needed template changes to the default template set - only. Then take a look at how the hack displays using other skins. Jot down any glitches you see before going back to the ACP because you'll need to track those down to make adjustments.

Pay attention to the color-coding system in use for the templates (in the ACP). If the template name is shown in white, nothing has changed. If it's yellow, all the code details are determined/applied by the default (parent) skin. You don't need to change anything there, either. You only have to modify templates in child skins when they show up with red names. Those are the templates that were customized for that skin.

To figure out where to begin, you can compare the code contained in whichever template you're working on between the default version of the template and the new skin's version of the same template. By finding out what was changed for the skin, you then know where the problems are that need to be fixed.