Attribute image replaces main product image on select [Support Thread]

[mc12345678]

Good morning!

I'm working locally.

I renamed the template and admin folders in 1_Main_Files and 2_ZC_Version.

I copied the contents of both folders to my ZC folder. I used ZC156 from the 2_ZC_Version folder.

When I checked Option Name Manager, there were no options (the page was blank).

I then ran the following (and it said it was successful):

SELECT @products_options_types_id := pot.products_options_types_id+1 FROM `products_options_types` pot order by pot.products_options_types_id desc limit 1;

When I ran the following, I received the message: WARNING: An Error occurred, please let us know! If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you entered valid data.

INSERT INTO `products_options_types` (products_options_types_id, products_options_types_name) VALUES (@products_options_types_id, 'Link');

INSERT INTO `configuration` (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added, use_function, set_function) VALUES ('Link product option type', 'PRODUCTS_OPTIONS_TYPE_LINK', @products_options_types_id, 'Numeric value of the link product option type', 6, 0, now(), NULL, NULL);

and my Option Name Manager screen was still blank.

Backup to the rescue!

Can anyone tell me where I've gone wrong?

Thanks in advance.

Well a couple of things at least to try to help. It's hard to say what if anything was done wrong without first knowing what version of Zen cart is involved. Then there is the question of what else might have been installed as an edit or additional plugin. Lastly and perhaps most helpful if attempting to again apply the files, is to report back what information is provided in the debug logs when either experiencing a black screen, partial blank or one of those errors in the SQL statement reports.

Ultimately what is needed to be applied for this module should be commented in the file(s) that are merged with original Zen cart code.

[Techiant]

Will this work with ZenCart 2.0/2.1? What are the options?

[mc12345678]

Will this work with ZenCart 2.0/2.1? What are the options?

Unfortunately, because of changes to ZC 2.1.0 in the following PR: Additional sanitization by lat9 · Pull Request #6652 · zencart/zencart (https://github.com/zencart/zencart/pull/6652), changes are needed for this plugin to function in ZC 2.1.0. There is also the small amount of code needed in the applicable admin file that would need to be merged.

I have it working on my test ZC 2.1.0 site and am looking to more formally report this issue in github here in a moment, but wanted to report what had been found in attempting to answer the question since no one else had yet.

[Techiant]

Well, wish I knew you were working on it, but this thread has been so quiet that I had no hope and just went with it. :)
I just have the product_info page finished with a fully encapsulated version working on a local 2.1 install, and really close to the shopping cart update.
Would love to collab unless yours is already done and dusted. If you want to DM me your public IP address, I'll open up the firewall for you to take a look.

Plus, I would love to see your feedback on how I did with the new standards, as I had to dig through encapsulated plug-in info at different places, including existing plug-ins.

Thanks!

[mc12345678]

Well, wish I knew you were working on it, but this thread has been so quiet that I had no hope and just went with it. :)
I just have the product_info page finished with a fully encapsulated version working on a local 2.1 install, and really close to the shopping cart update.
Would love to collab unless yours is already done and dusted. If you want to DM me your public IP address, I'll open up the firewall for you to take a look.

Plus, I would love to see your feedback on how I did with the new standards, as I had to dig through encapsulated plug-in info at different places, including existing plug-ins.

Thanks!

Well, happened to see your post in passing a while ago, but have had to work through some core problems with ZC 2.1.0 to gain functionality then had two other plugins to look into before attempting this one. I didn't/haven't gone to making the plugin encapsulated as there's already/still 3+ year old uncorrected issues with the way it operates. So I'm not a fan yet of trying to use that broken/unstable environment.

I didn't have to do much tweaking to at least make/get it to work. I started a few hours ago, found a few minor updates desirable and then discovered the above bug introduced to 2.1.0.

Otherwise, you'll note I don't post here much these days (result of management not wanting to address problems).

I'll be updating my github site in a moment once I capture the changes where applicable... Need to remember to update "versioning". :/

[Techiant]

I have a ZC_plugins package if you want to take a look. Just lmk, otherwise I guess it's just going on the production site after some testing.
It takes so much effort to override everything during updates, I made a conscious decision to make everything encapsulated even if for own use.

This one loosely uses the same logic as yours but it's completely redesigned for encapsulation support - should not be any major issues.

[mc12345678]

I have a ZC_plugins package if you want to take a look. Just lmk, otherwise I guess it's just going on the production site after some testing.
It takes so much effort to override everything during updates, I made a conscious decision to make everything encapsulated even if for own use.

This one loosely uses the same logic as yours but it's completely redesigned for encapsulation support - should not be any major issues.

Be glad to (Can contact me through the site on my current posting signature until the day I remove it from my profile). I've also just pushed version 1.5.12 to github.

Includes either of two fixes, change to ajax.php which would support continued operation; however, I believe the new language files (prefix including "lang.") would be necessary and the minor incorporation of the change to options name manager (though probably could increase some of the complexity, coming up with an ajax call to not need touching the file). Or, load all the files now included in the v210 folder, some of which replace files already loaded for the plugin but at least allow it to operate under the base/core installation.

[Techiant]

Be glad to (Can contact me through the site on my current posting signature until the day I remove it from my profile). I've also just pushed version 1.5.12 to github.

Includes either of two fixes, change to ajax.php which would support continued operation; however, I believe the new language files (prefix including "lang.") would be necessary and the minor incorporation of the change to options name manager (though probably could increase some of the complexity, coming up with an ajax call to not need touching the file). Or, load all the files now included in the v210 folder, some of which replace files already loaded for the plugin but at least allow it to operate under the base/core installation.

Dropped you a line through your contact form. Thanks!

[jimmie]

installed newest version today 1_5_12 on version 2.10 and i cannot seem to get images to change on select, ( i did see it happen once, but not again.)
my theme has many ways to display product images, ive tried them all, nothing is working.
here is product https://jnsflooringandsupplies.com/t...e-trowel-blade
not all attributes have images. i have it set on 8 to see which one have them.

[Techiant]

installed newest version today 1_5_12 on version 2.10 and i cannot seem to get images to change on select, ( i did see it happen once, but not again.)
my theme has many ways to display product images, ive tried them all, nothing is working.
here is product https://jnsflooringandsupplies.com/t...e-trowel-blade
not all attributes have images. i have it set on 8 to see which one have them.

I made an encapsulated version in June that is working for me in v2.1 and submitted it for the author's review. I'm not sure if they will take action on it, though.