UBB.threads PHP Forum Software Community Forums UBB.threads 7 Version 7 Support Creating a new style documentation

Hi all. In the documentation there's information on importing a stylesheet, which is great as I've done that. There's no info I can see on the steps to create a new stylesheet (step 1, step 2 etc).
I can copy a style to edit and then go through the steps to change the look and feel but it's the saving the new file that has me stumped.

When I click on the "Update or Add Style" button all it does is update the style I copied with no option to name it as something different from the one I copied (I've had 3 or more copies of UBBThreads stylesheet on the styles list). Or I'm missing something really simple!
Thanks for any help,
Timo

Your missing somthing lol

I scratched my head with this one too.

Go into your style,
and click on the first opening links.
You will find the current style name in there.
Re-name it.

Save and update.

You should now find it in your styles list.

Hope that helps

There's a "Create New Style" button at Control Panel » Styles if you wanna start from scratch, but I'd recommend this:

Export a style you want to modify, then change the name of it (on your hard drive). You'll also want to edit the .txt file and change the second line to rename the style: STYLE_NAME:NEWNAME Then, import it.

Names, Images and wrapper link while editing your new stylesheet will give you the option to change the name before saving/adding it.

Ah, I think I see now, let's see if I have this correct:

1. Click on "Create New Style"
2. Copy whichever stylesheet you want to start from (if any)
3. Click on "Name, Images & Wrapper", the first option on the left.
4. Rename the "Style Name" in the first box from the one you copied to the one you want to name (for example - UBBThreads to Test1)
5. After you've done the changes you want and click "Update or Add Style" and it will save the name you entered from step 4 (in this case, Test1).

Do I have that right?

Thanks muchly,

Exactly. You should be writing some of the documentation around here.

Thanks Harold. It's just that I think of the person who is completely new to the software and needs guidance. I've been around since the old days and if I can't do it then perhaps the person who's a newbie might not either (maybe I'm too old??).

This is good business sense to promote the great features of the upgrades to the masses.

I know for a factoid that detailed, up-to-date documentation is always the last thing to get updated (I work in government, nothing more to be said about that) and distributed to the public so here I'll ask, what else do we need to know?
I'm willing to help out only because then I'll know how to do the darn things, heh.

Cheers,
Timo