What issue do you mean? Please post a link to discussion or bug.
[/quote]
On this forum I have repeatedly read optimization advise to turn off the image zoom addon.
However a forum search does not expose these posts. This is probably because IP.Board 3.4 uses mysql full text search which is not very effective for searching large sites like this.
If I remember correctly the image zoom addon caused slow queries. Is this correct?
Generally an image zoom has nothing to do with the database. The image path is retrieved from the DB for the main pair and alternate images. All zoom operations are performed in the browser via javascript and thumbnail sizes are determined and generated in PHP code.
Shouldn't be any relation between the image zoom and queries to the DB.
In short, since 4.3.1 you have full control over options, you can export/import the following:
option combinations (images)
option exceptions
option variants (price/weight modifiers, images)
Besides you can make update these properties not only with Export/Import but also using API.
[/quote]
Nice improvements. However…I hope you are also fixing a pesky problem with import of Options field. Allow me to explain:
Problem: multi-language import of Options field (Import data/Product/Product tab) ignores 2nd language row. Result: the first language row is applied to all languages in CSC.Even importing each language separately does not help. The last language imported will overwrite all other languages present in CSC
Example: please see example text below. 1 product with 2 languages (EN & NL). The result being that in our NL CSC, the EN Options text is imported instead of the NL Options text.
Why relevant: for many products we want to bulk-create Options in Excel and then import them into CSC. Creating Options for multiple languages in CSC by hand for thousands of products is a huge time inefficiency
Brownleather you are right, there is an extra step in Filtering process.
This is done because we have removed the number of products near each variant. So now the customer first see the number of products he will sen and in case he click “Show” he will see the results. This was essential for speed optimization.
[/quote]
I agree with Brownleather that the extra step in the filtering process is problematic from a usability standpoint:
[list=1]
[]It complicates an interaction that should be as simple as possible and can be potentialy confusing to the user. For example: When the user chooses many filters options it's not immediately apparent that the indicated number of available products corresponds to the combination of feature variants, and not the last clicked variant. I can understand it, sure, but I'm not so certain about the average user.
[]Also it breaks user expectations, even for experienced users like me, because it does not follow standard filtering as seen in most sites.
[]It may be faster in page loading terms, but it slows down the user in terms of interaction.
[]It greatly diminishes the usefulness of dynamic filtering in certain cases: Let's say that a user wants to see in what colors are dresses with “mini” length available. With the current system she just have to check the “mini” variant and the color variants that are not available are automatically greyed out. With the new system when she clicks on the “mini” variant the color variants do not change. Even if she clicks “show”, still all the color variants remain “active”. I see this as a very serious flaw.
[/list]
I strongly suggest that you consider giving as the choice in the admin to turn this feature on/off.
I would love to hear what other members of the forum think about this!
Nice improvements. However…I hope you are also fixing a pesky problem with import of Options field. Allow me to explain:
Problem: multi-language import of Options field (Import data/Product/Product tab) ignores 2nd language row. Result: the first language row is applied to all languages in CSC.Even importing each language separately does not help. The last language imported will overwrite all other languages present in CSC
Example: please see example text below. 1 product with 2 languages (EN & NL). The result being that in our NL CSC, the EN Options text is imported instead of the NL Options text.
Why relevant: for many products we want to bulk-create Options in Excel and then import them into CSC. Creating Options for multiple languages in CSC by hand for thousands of products is a huge time inefficiency
Please, please fix this in version 4.3.1
thank you
Olof
[/quote]
Olof,
I asked our QA team to check this issue. I will keep you informed.
