Viewing 15 replies - 16 through 30 (of 41 total)
  • Hi decarvalhoaa!

    Works great with products already created!! Thank you very much! Let’s wait to test the issue number 2 and do you have a clue about my issue #3? I know is just in my staging site :/

    Have a nice day!

    I’m working on 2. but it turns out to be a can of worms ??
    I found a few other problems in the code and it is a bit more complicated than I anticipated. It should be solved by next weekend.

    Regarding issue 3.), honestly I don’t have an idea of what can be the issue, and it is very hard to troubleshoot without admin access to your files and database.
    Does it happen to all products or just some? if your create a new product, does it happen also? is there a specific product type (e.g. variation) where it happens or happens with all types?
    My guess is that, because the plugin was not handling well translation for products created before the plugin activation, there might be some database data corruption.

    Hi decarvalhoaa!

    Searching in google i found 3 persons that had the same problem as me with that plug in (the issue #3), also i realized that the problem just happens in Chrome and Firefox. But In the safari browser its OK, there is no problem. I’m testing the plug in in a localhost installation.

    I think i have a clue, it happens in all the variation products which i had set the general “stock quantity” = 0

    I had that setting because i’m defining each stock quantity under each variation. So, just by changing the general stock quantity of each product to a big number it will work! It will take that number as the maximum stock number for every variation of that product.

    The proper way will be to ignore that general stock number and take the stock number of each variation. I also can confirm this problem on the fresh online installation of WP + WC + Poly + WooPoly

    I don’t know if i explain myself well.. but for sure there will be someone with this problem and don’t even know it.

    Thank you very much for your support!!! ??

    I believe that you are not supposed to configure stock like that.

    I have asked the question in the woocommerce support forum, but I believe that fi you want to manage the stock at vatiation level, you need to leave the Stock Qty blank and untick ‘Managed Stock?’ at the parent level (what you called general stock).

    The dependency on browser is strange. Because this plugin doesn’t change any html/css or javascript (except for regressing fragments that doesn’t impact that field).

    Nke Jolley just responded. I’m correct, you should leave the parent stock unchecked if you want to manage stock at variation level.

    If you set stock both parent and variation, the parent stock is ignored but if you missed to setup stock for some variations (by mistake for example) the general/parent stock is used as a single stock inventory for these variations that didn’t had stock set at its level.

    I think is not an issue.

    BTW, issue #2 is solved but I still have to do more testing, because I had to create a new “add to cart handler” for variations from scratch to solve this because WooCommerce was missing hooks.And there are plenty of use cases to test. should be out in the development branch tomorrow nigh or Friday.

    Nice! I guess i didn’t know how that feature really worked.

    Hey guys any fix for the tabs in My account page till the other problems are cleared ? That issue #3 is driving me crazzzzzzzzy ??

    As I mention above, the issue #3 is not a bug. As confirmed by WooThemes folks, it is mis-configuration/misuse of the Parent and Variantions stock management feature.

    I’m not sure what My Account page tab problems are you talking about. Can you please elaborate?

    Please note that Themes need to style the new links in the My Account page. For example, WooThemes released a new version of Storefront Theme (v2.0.x) exactly because of that.

    What I mean is when you open orders , or downloads or any of the tabs and the tab loads, then if you try to open another tab it reloads the same page with the same tab opened as before. No action can fix this, only going to another page, different from Mu Account page.. The only thing breaking those links for me is the Hyyan WooCommerce Polylang Integration plygin v.0.27 (not releaed) but i need it badly for my translations of cart and checkout and my account in order to work on 3 of my translations..

    Hi Ownya!

    I know the problem about the broken links on the account page, the problem it’s solved (and many others) if you install the latest version developed by Decaravalhoaa, version 1.0.0

    I think is this:
    https://github.com/decarvalhoaa/woo-poly-integration/archive/development.zip

    And the third “issue #3” can be “solved” as decarvalhoaa explained 2 days ago:

    Nke Jolley just responded. I’m correct, you should leave the parent stock unchecked if you want to manage stock at variation level.

    If you set stock both parent and variation, the parent stock is ignored but if you missed to setup stock for some variations (by mistake for example) the general/parent stock is used as a single stock inventory for these variations that didn’t had stock set at its level.

    I think is not an issue.

    Cheers!

    Hi kamarena! Thanks for the link, tried it and as I didn’t doubt, it worked perfectly. Will make some test with the environment and let you know if something goes wrong. Looks stable though ??

    Cheers guys!

    Plugin Contributor jomo

    (@jonathanmoorebcsorg)

    Hi, testing your scenario:
    1.) Global attribute named “Color” (EN) translated to “Farbe” (DE – 2nd language).
    Values are “Blue” and “Green” (EN), respectively translated to “Blau” and “Grün” (DE).

    Ok, I can translate the Global attribute Color but not the Values…
    On clicking through to Configure Terms:
    – the listing is missing normal Polylang/Lingotek symbols are missing from the language columns
    – Polylang/Lingotek actions do appear however don’t seem to take effect
    – the detail terms edit misses the language option
    – the terms don’t appear in strings translation

    I’m not clear whether there’s a bug or I am just missing something..

    Plugin Contributor jomo

    (@jonathanmoorebcsorg)

    Actually I fixed it for that attribute, then had repeat problem on testing the second attribute.

    The issue is that when creating a new Attribute, no language is set – there is no option to set one in fact.

    This can then be resolved by going to:
    Settings, Languages, ….set them all to the default language

    Plugin Contributor jomo

    (@jonathanmoorebcsorg)

    However on creating and translating a new product,
    the translated product is reset to simple product, does not include any product details (SKU, weight, dimensions, attributes, variations are all lost and locked for editing).

    Hi,

    Ok, I can translate the Global attribute Color but not the Values…

    you can translate the attribute values for Global attributes. Click on the Attribute name (or at the settings icon on the left hand side of the screen – over the mouse and should say “Configure terms”).

    The issue is that when creating a new Attribute, no language is set – there is no option to set one in fact.

    After clicking the attribute name, you should have a form to add new values on the right hand side. The last fields of this form – just before the “Add New <attr. name>” – should be the Polylang settings where you can set the language and link translations.

    This can then be resolved by going to:
    Settings, Languages, ….set them all to the default language

    Don’t really understand this solution. Under Settings -> Languages -> Strings Translation, you can only translate the Attribute Name. The Values translation is done as I mentioned above under Products -> Attributes.

    However on creating and translating a new product,
    the translated product is reset to simple product, does not include any product details (SKU, weight, dimensions, attributes, variations are all lost and locked for editing).

    Which version of this plugin are you using?

Viewing 15 replies - 16 through 30 (of 41 total)
  • The topic ‘WooCommerce 2.6’ is closed to new replies.