I am just picking up on the recent dialog, so I'll try to cover a few responses here.
Firstly: I am aware of the different behaviour in different browsers, but I regret that dealing with these quirks is way, way beyond my capability as a 'dabbler'. I took someone else's code and played with it - and the reasons are documented previously in this thread, I believe. If someone with the necessary skills feels that he/she can hack the code so that it is entirely cross-browser friendly, then PLEASE go ahead, it will, of course, enhance this module!! In the meantime I will make some enquiries to see if there are any PHP gurus out there who would be prepared to take at look at it, but it may be some time before I can get round to this, because an enforced change of server means that I am in the process of painstakingly rebuilding my store!!
Secondly, I have just taken a look at the version of the 'attributes.php' file that is supplied with zen cart 1.3.7.1 i.e. the latest update. Lines 219 to 227 inclusive of this 'unedited' file are as follows:
// select default but do NOT auto select single radio buttons
// $selected_attribute = ($products_options->fields['attributes_default']=='1' ? true : false);
// select default radio button or auto select single radio buttons
$selected_attribute = ($products_options->fields['attributes_default']=='1' ? true : ($products_options->RecordCount() == 1 ? true : false));
}
}
switch ($products_options_names->fields['products_options_images_style']) {
case '0':
This explains the change to the code in this vicinity. I have removed the comments - I am a bit obsessive about what I consider to be unnecessary comments, lines, white space etc. and tend to edit them out. I suppose it's a legacy from when the days when computers had very little RAM - I don't think it can do any harm, and it might improve the speed by one jillionth of a second!! In this case it may have been prudent to leave the comments in so that those with enquiring minds might understand the reason for the change. (This may explain why the setting discussed previously in this thread needs to be '0'.)
As for mauryg's problem with the javascript file not loading, all I can say is that it *ought *to load. ckosloff is correct in stating that v 1.02 moved the js file so as to avoid a conflict (that ckosloff discovered) with Image Handler 2. This new location was tested on both ckosloff's and and on my set-up, and was found to work. As I understand things, if the file is included in the YOUR_TEMPLATE subdirectory, the js will definitely load, but I believe that it will load every time a page is displayed, which seems somewhat unnecessary - by including the js file in the template_default subdirectory, I believe that the js file loads once and stays in the browser's memory or cache.
So, for mauryg's problem, the only things that I can suggest are: 1) ensure that the browser's cache is cleared; and 2) ensure that you have removed the js file from the YOUR_TEMPLATE subdirectory.
