How do you set your template editing environment?
 

Hello,

Editing templates on large scale basis can be really overwhelming. I've come across this when trying to make huge editing to my FORUMHOME template. In order to be able to experiment freely, I made another template & called it FORUMHOME_test & copied FORUMHOME content into it. Then I made a test.php script using Gary King's method to work as a second index page.

But things were not satisfying to me as the new index page was empty & I have to manually create other forums so that I can visually test modifications results! Another problem I came upon is vBulletin variables within templates as there are no ready lists to variables that are required in templates. I thought of using some IDE editors but I know of no FREE ones that can do this. Other simple editors like EditPlus & Notepad do not provide such advanced features.

So, how do you work with template editing inside vBulletin? Do you have any tips & tricks you would like to share that can make template modifying easier?

I have set up a dev board for anything I may want to test out.

Just make install a separate instance of vB installed on your server that is not open to the public to test things out.

I already have a localhost server setup on my PC which I use for all development & non-production activities. I am looking for another way of editing templates rather than the traditional way of editing then reverting.

I create a child style and work in that then when I have it right I copy the template to the parent.

Of course if the template isn't edited to start with then if it all goes wrong a revert fixes everything.

Thanks peterska2.

I didn't thought of creating child styles! Good idea, but how do you deal with template variables? Do you write them down on a paper or just depend on your eyes? I'm talking about large-scale template editing!

I just make them up as I go along ;)

Well actually most of them I know now without having to look things up so I know that if one doesn't work then it is the other one.

I know about large scale edits too. Some of mine are complete rewrites so it can be fun and games sometimes.

If it is a really large scale thing, then every time you get a bit done and functioning correctly, create a child style of that one and carry on.That way if you need to debug then you can always revert back a step without losing the whole lot.

You should see the style manager on my dev board. It's horrendous for child of child of child of child of child of child of default style and even longer chains!

in most cases, the compare ('View History') option in vbulletin would suffice ... I suggest checking it out.

if you don't like ... get yourself Beyond Compare

The compare tool is very good for when you are performing upgrades to see what has changed. Generally though, the method that you use depends entirely on exactly what you are doing.

Thank you both for comments. I found this to be very useful & fits exactly into what I've been trying to overcome:
http://www.vbhackers.com/f93/tool-te...ml-files-5419/