Upgrade Conflict index.ini

[Tim Weaver]

Hi

Going through an update of a heavily customised site from v6.1.3 to v7.0.1 we have a number of template conflicts that with time, I can resolve.

However, we also get a conflict with index.ini which is not something that I am aware I have previsouly edited directly. The before and after listings in the upgrader are so different that I do not know where to begin to fix this.

It is not mentioned in the help or the Advanced Guide.

Could someone please advise what index.ini is used for and are there any guidelines for editing it?

Thanks,

[Tim Weaver]

No replies to my post yet, but I went ahead with the upgrade suggested by the upgrader - really not sure what the conflict was that it was reporting, but so far it seems to work, (even if I don't know what it does)!

[cdicken]

index.ini is used when applying a theme to pre-set a few database fields when you first apply a theme.

The index.ini file just sitting round in your 'Site1' folder will not actually affect the running/design of the store.

[Tim Weaver]

Thanks Chris, that's good to hear.

Maybe the Site Upgrader should skip it in future releases?

[cdicken]

I agree. I'll pass this onto the team.