Script Testing

[jagtpf]

Originally Posted by Dragonsys

This usually happens because of hard coded variables, or something which makes the script not be universal (lazy coding, or different strictness settings in PHP)



I use Notepad++ for the coding, and then test on my test sites (one on Windows/IIS and one on Linux/Apache). I have a few scripts with thousands of lines, and have never had an issue doing things this way.

Thanks . I use scite as editor, fairly basic but good and simple (like me!)

Obviously the days when one could use a 'record new macro' as a starter are long gone.

--------------- Added [DATE]1452074302[/DATE] at [TIME]1452074302[/TIME] ---------------

Originally Posted by squidsk

This will usually be caused by the fact that your test site is not identical to your live site, including but not limited to, php version/settings, mysql version/settings, vb version/settings, installed mods verion/settings, data on your live site is different from your test site, and a host of others as well.

One obvious quirk is the Test Site has a "Master Style" and yet the Live one doesn't have one (in view).

Best place then, for a test bed, is on the main server!



--------------- Added [DATE]1452074597[/DATE] at [TIME]1452074597[/TIME] ---------------

One question that keeps bugging me is where to put files on the server. Some are obvious, such as "images"/"admincp" etc - but "includes""clientscripts" ?

[S]Does anyone know of a list of vBulletin variables - and what each one does .... ?[/S] Ah - I can glean something using Firebug DOM