How do I import replacement variable from vB2?

[Craig A]

Simple really - I need to import the various replacement variables associated with each style from vB2 - how do I do it? The standard upgrade loses them (I have around 100 styles with an average of 5 replacements per style (such as title, url, headinsert, header, footer) and I can't believe I have to lose them all and start again? Help!

[Wayne Luke]

You will have to reapply your changes of those to the vBulletin 3.0 templates because vBulletin 2 templates and replacements are not compatible. However, it should be easier with child styles and inheritance depending on the changes. One people announced that they updated all 66 of their styles and translated the board into German in a few hours after upgrading to Gamma.

My suggestion is to upgrade a test board, update all the styles you need. Export those styles in their XML format. Then upgrade your live forums and import your styles.

[Craig A]

So there is no way of importing the styles then is what you're saying? That sucks. I realise that templates were completely out the window but why do I completely have to redo the styles and replacements? Why is it impossible to take the following:

{sitetitle}
10 Tenths Motorsport

from the old database and put it in the new one?

I can't remember the wording but I seem to recall during the import that it told me it was taking the old replacements and putting them in the new database. Yet nothing remotely like that has happened?

[Craig A]

Anyone got any ideas on this? I am sure I saw something that said existing replacements would be imported?

[Wayne Luke]

They are imported and should be found in the Replacement Variable Manager. However since the entire style structure is changed for vBulletin 3 which includes Templates and Replacement Variables they are imported for reference purposes only. Each one of your old styles should be listed in the Style Manager and in the Replacement Manager.

Replacements don't work the same in vBulletin 3 as they did in vBulletin 2. In vBulletin 2.X they were used for structural markup (i.e. <smallfont>) as well as color control (i.e. {firstaltcolor}). In vBulletin 3, they are used simply to replace word X with Word Y on a global basis. All structural formatting and so forth is control by CSS now. And replacements are applied after the page is drawn but before delivered to the browser.

[Craig A]

Understand that things have changed but I think we're talking at cross purposes here? I realise that the templates will be different now but there are no replacement variables AT ALL in the replacement variable manager - even for the old archived vB2 styleset - all I have is 'No replacement variables are defined for this style'

Not one single replacement value has been imported at all - even the custom ones which I added - is this right? The names of the styles have all been imported but that's it - there are no replacements associated with them, nor have any of the colours been imported. Is this correct? I can't believe it is as it makes no sense whatsoever and it contradicts what you just said.

[Wayne Luke]

In my experience they are imported. What version did you upgrade from?

[Craig A]

2.3.3 which was recently upgraded from 2.2.8. However this is not a factor as my 'live' database is running just fine.

[Craig A]

Sorry to reply to myself but I thought I might not get a reply as this thread had dropped to page number 6 on the forum!!

[Wayne Luke]

Hmmm okay.. I think I have a 2.3.3 database lying around somewhere that I can use to test this. Might take a couple days though.

[Craig A]

Thank you, Wayne, I look forward to hearing how you got on.

[Craig A]

How did you get on Wayne? If you've not yet had chance would you be able to speak with one of the developers and ask them to spell out precisely what the upgrade is supposed to do. I am very keen to get this up and running and, from what has been said, I can only presume that the lack of style importation is a direct result of a bug in the upgrade script.

[Craig A]

How did you get on Wayne? If you've not yet had chance would you be able to speak with one of the developers and ask them to spell out precisely what the upgrade is supposed to do. I am very keen to get this up and running and, from what has been said, I can only presume that the lack of style importation is a direct result of a bug in the upgrade script.

Any updates yet? My staff are desperate for the extra admin features and I cannot move on this?