1.1.3 Multiple 

skins 

To support the multi language capabilities of CactuShop, multiple skins are 

required (one for each language). The names of these are no longer set in the 

config settings. Instead, the path to each skin is set on the 

_modify_langs.asp 

page of the back end. 

1.1.4 

Multiple back end logins 

On CactuShop v4, the back end username and password were stored as 

config settings. However, v5 supports multiple back end users, so these are 

now set up from the

 _modify_login.asp 

page and stored in the 

tblCactuShopLogins

 table. 

1.1.5 Naming 

conventions 

In order to make CactuShop easier to work with, variables throughout have 

been renamed according to conventions that are more consistent. Each is 

prefixed with a three letter code indicating the type of variable it is. These are 

as follows: 

Prefix

Meaning 

bln boolean 

(true/false) 

num 

numeric (integer or real) 

str string 

obj object 

dat date 

Values that have been directly drawn from particular database values retain 

that name. For example a product ID number will normally be used within a 

page as 

P_ID

 rather than 

numProductID

 because the database field from 

which it was pulled is called P_ID. 

Config settings have not been renamed according to this convention as it 

should be clear from the context. 

1.1.6 

Config setting changes 

In addition to a host of new config settings, some things that were previously 

config settings have been moved elsewhere. For example, 

ownertoemail

 and 

ownerfromemail

 are now language specific and hence updated from the 

languages back end section (see 6.21.4). The location of the skin is also set 

individually for each language here rather than in the config settings (as was 

the case for prior CactuShop versions). 

15