Stock by Attribute v4.0 addon for v1.3.5-1.3.9

[fbroz]

mc12345678,

I have been following that guide, but I think I've made some errors along the way that will require starting over. Thanks for your insight. Here I go again....

[mc12345678]

mc12345678,

I have been following that guide, but I think I've made some errors along the way that will require starting over. Thanks for your insight. Here I go again....

Not sure which guide has been followed, but if it is just database related things to be "restarted" if you run the install/upgrade script again, the table of variants will remain but the settings added by SBA will be restored to their default. If it is further desired to clear the variants table, then there is a script for that as well..

[fbroz]

Hi mc12345678,

I started with a fresh copy of zc 1.5.5e and started applying my modifications and it is going a little better this time. I wonder if you have any thoughts on a performance issue I am seeing when loading pages with fairly complicated attributes. This product for example seems to stall for about 10 seconds when creating the dynamic dropdowns:

https://www.tokyopenshop.com/shop2/i...products_id=18

Products with less complicated attributes load much more quickly:

https://www.tokyopenshop.com/shop2/i...oducts_id=1278

Does this seem expected to you with complicated products? Maybe this is something I can improve on my web host with different MySQL tuning of some kind? Thanks in advance!

[fbroz]

One thought I had on this... I am currently using a very old PHP version (5.2.17) for the benefit of the 1.3.8a installation on this server. Maybe when I can migrate to the 1.5.5e site and upgrade my PHP version that could have an effect?

Also when I look in Tools -> Server/Version Info I do see: "MySQL Slow Query Log Status: On" and "MySQL Slow Query Log File: web-slow.log" but I can't seem to find that web-slow.log file anywhere.

[mc12345678]

Well, for one thing, though the fileset has now been updated to set $backorder = false; as described a few posts back, the fileset on your server still has it as true.

You mentioned that when changing that setting there was a difference in operation.

Otherwise since these last couple of posts I haven't been able to get to a computer to observe what is available to identify any slowdowns. I do see that part of the "price" area is affected for the one example, but I don't know what all else is going on during that period especially as I have also been presented with a mixed content message when accessing the pages. It appears that there is one script that has a src="http://...." instead of beginning with just a double forward slash.

Otherwise, there may be a way to split the single query up and make things faster, though haven't really looked into that as still have not had feedback on the feature's functionality to then warrant further review/investigation into improvement. Ie. If it doesn't provide what is sought, why spend time making changes? If it does and it's slow, then ok, fine improvement needed...

As to the log file, it seems as if it should be logged into your directory structure, but I would suggest speaking to your Web host about either where it is currently being stored, how the path should be modified to make it accessible/easier to access, and/or how to access it.

[fbroz]

Thanks mc12345678,

Well, for one thing, though the fileset has now been updated to set $backorder = false; as described a few posts back, the fileset on your server still has it as true.

You mentioned that when changing that setting there was a difference in operation.

Thanks for the reminder, I have re-applied that change, and there may be a minor improvement there, hard to tell.

Otherwise since these last couple of posts I haven't been able to get to a computer to observe what is available to identify any slowdowns. I do see that part of the "price" area is affected for the one example, but I don't know what all else is going on during that period especially as I have also been presented with a mixed content message when accessing the pages. It appears that there is one script that has a src="http://...." instead of beginning with just a double forward slash.

Thanks for that comment on the error, my template was calling that minimized jquery file and it seems to work just as well with an https:// call, so that seems to be corrected for the moment.

Otherwise, there may be a way to split the single query up and make things faster, though haven't really looked into that as still have not had feedback on the feature's functionality to then warrant further review/investigation into improvement. Ie. If it doesn't provide what is sought, why spend time making changes? If it does and it's slow, then ok, fine improvement needed...

Regarding this feedback, I can share my personal thoughts at this point: I do see that it works correctly to populate the dropdowns with the correct attribute option names and values and allows customers to add the correct products to the cart. That is obviously the most important thing, and for me, the older sequenced_dropdowns in zc1.5.5e does not do this (no option values appear in the list, although the list seems to be the correct length). The "out of stock" or "backordered" functionality doesn't quite fit my purposes. In a sequenced list like mine, the option values from the first list in the sequence should not say "out of stock" unless all of the corresponding option values in the second list are out of stock. As it is now, all the option values from the first list (.25mm, .3mm, etc.) say they are out of stock. For my uses, only the second list needs to show out of stock notifications, really.

As to the log file, it seems as if it should be logged into your directory structure, but I would suggest speaking to your Web host about either where it is currently being stored, how the path should be modified to make it accessible/easier to access, and/or how to access it.

I did some more digging into this, and I think the log file does not exist because the slow query is not being triggered at the current threshold. I can look into this more in the future possibly.

[fbroz]

mc12345678,

I'm not sure if this thread is the right place for this, if not I can remove the post.

As a long time user or SBA, I modified the "Products Purchased" report to allow store owners to find out which attributes of a product (or combination of attributes) is selling well or needs to be restocked. I have attached the file here for your consideration and possible inclusion into the SBA project if you think it is useful. I am not a professional programmer and there are likely many improvements that can be made to this report, but here it is in a state that works with my zc 1.5.5e.

stats_products_purchased.php.zip

[mc12345678]

mc12345678,

I'm not sure if this thread is the right place for this, if not I can remove the post.

As a long time user or SBA, I modified the "Products Purchased" report to allow store owners to find out which attributes of a product (or combination of attributes) is selling well or needs to be restocked. I have attached the file here for your consideration and possible inclusion into the SBA project if you think it is useful. I am not a professional programmer and there are likely many improvements that can be made to this report, but here it is in a state that works with my zc 1.5.5e.

stats_products_purchased.php.zip

Haven't looked at it yet, but that concept is one additional thing to be added to this. That information will be useful to users of the software. Thank you, whether incorporated as is or with other modifications, let me know if credit should be given to not only you but whom else for its inclusion.

[mc12345678]

Thanks mc12345678,



Thanks for the reminder, I have re-applied that change, and there may be a minor improvement there, hard to tell.



Thanks for that comment on the error, my template was calling that minimized jquery file and it seems to work just as well with an https:// call, so that seems to be corrected for the moment.



Regarding this feedback, I can share my personal thoughts at this point: I do see that it works correctly to populate the dropdowns with the correct attribute option names and values and allows customers to add the correct products to the cart. That is obviously the most important thing, and for me, the older sequenced_dropdowns in zc1.5.5e does not do this (no option values appear in the list, although the list seems to be the correct length). The "out of stock" or "backordered" functionality doesn't quite fit my purposes. In a sequenced list like mine, the option values from the first list in the sequence should not say "out of stock" unless all of the corresponding option values in the second list are out of stock. As it is now, all the option values from the first list (.25mm, .3mm, etc.) say they are out of stock. For my uses, only the second list needs to show out of stock notifications, really.



I did some more digging into this, and I think the log file does not exist because the slow query is not being triggered at the current threshold. I can look into this more in the future possibly.

It is intended that out-of-stock (when displayed) be shown at the earliest selection point where such selection would result in any further selection to also be out-of-stock.

That said and seeing the indication of out-of-stock being displayed in the first dropdown, this would be a factor of the entry of data for the variants associated. Could you please identify the variant "arrangement" and quantity for each selection combination as well as the total quantity of stock identified to the main product?

Then may discuss settings, but let's start there first.

[fbroz]

Haven't looked at it yet, but that concept is one additional thing to be added to this. That information will be useful to users of the software. Thank you, whether incorporated as is or with other modifications, let me know if credit should be given to not only you but whom else for its inclusion.

Thanks mc12345678,

This is my work, but I can already thing of some things that should be generalized (hardcoded order numbers, etc.) before it will be robust for others.