Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#42 Select/Multi-Select translated value not working

open
core (16)
5
2014-02-18
2012-07-04
Anonymous
No

Hi,

Looking to use the Magmi select feature to translate an attribute value, but it doesn't work. Myselect is used for configurable products.

"store","sku","myselect"
"store1","sku001","store1val1::[adminval1]"
"store2","sku001","store2val1::[adminval1]"

Bug 1: This method above doesnt support "global" attributes. So configurable attributes doesnt work.
Bug 2: Even if the attribute is changed to storeview, the "translated value" is not beside the admin value when seeing it via backend. It's created as an independent value .

Screenshot: http://www.diigo.com/item/image/24p3p/av8i?size=o

Discussion

  • Stefan Skotte
    Stefan Skotte
    2012-09-25

    Appears to be the same error for me in ticket #47.

     
  • Tony
    Tony
    2012-12-10

    I just tried that right now too. Experiencing the same issue.

    I looked at the code in magmi/engines/magmi_productimportengine.php at around line 468 is where the separation of the store1val::[adminval1] using a regular experssion.

    if(preg_match("|^(.*)::\[(.*)\]$|",$val,$matches))
            {
                $svalues[]=$matches[2];
                $avalues[]=$matches[1];
            }
    

    Problem is that I don't see the svalues array being used anywhere in the code after storing the value. So I dont think it's properly implemented.

    I checked a few versions back and the

    function getOptionIds($attid,$storeid,$values)

    is pretty much the same from current version to the pre 0.7.15b.

    I haven't checked exactly how the whole system works but it looks like the issue is in that function.

    I want to say the avalues array is the admin array but it isnt. Svalues should be the store view array but it also isn't.

    I'm just going to poke around til it breaks.