New Landing How can we help? Themeforest Theme Support Neighborhood Translation of PO-files don't apply

Viewing 15 posts - 1 through 15 (of 16 total)
  • #18514
    romaxa
    Member
    Post count: 7

    Hi!
    I’ve translated the theme files and created Swedish po-files, which are uploaded and put where they belong, see screen dump. I have used CodeStyling Localization as in many other WordPress projects. The files are there but nothing happens on the site, everything is still in English. I’ve emptied cache, waited a day but no changes are made.
    I see in your instructions that you recommend WPML and PO Edit, but the plugin I use is widely accepted and have worked great in other themes. Why is it not working in Neighborhood? This is for a client and we have a deadline. Thx in advance!

    #18843
    Melanie – SUPPORT
    Member
    Post count: 11032

    Please put the language files to the folder Neighborhood > languages

    Cheers

    #18867
    romaxa
    Member
    Post count: 7

    Hi again!

    Thanks, that helped! The same problem goes with the translations I made to WooCommerce though, which haven’t been a problem before. So, I went about moving and renaming the files (po & mo) in the same manner that you suggested for Neighborhood (WooCommerce language folder). It didn’t work unfortuneately. Theres is something with this theme that make my standard translation plugin (which is great) give warnings. Is this something that is related to your WooCommerce integration somewhow? It says:

    Warning: The actual loaded translation content contains mixed textdomains and is not pure translateable within one textdomain.
    It seems, that there is code contained extracted out of other plugins, themes or widgets and used by copy & paste inside some source files.
    The affected unknown textdomains are: yit, wooslider, woocommerce, tax-meta, swift_page_builder, rwmb, love_it, Swift Framework

    #19118
    Melanie – SUPPORT
    Member
    Post count: 11032

    Hey, have you checked this site out http://docs.woothemes.com/document/woocommerce-localization/

    Cheers

    #19386
    romaxa
    Member
    Post count: 7

    Yes I have! I’m using the recommended plugin Codestyling Localization and it have worked great on other WooCommerce installations on WordPress. With your theme it doesn’t have any effect accordingly to the error meassage I copied and pasted in my last message. So, I’m wondering if something needs to be configured in the theme, because there really shouldn’t be any problem. Thanks!

    #19826
    Melanie – SUPPORT
    Member
    Post count: 11032

    I will ask the developer about that, cheers! ๐Ÿ™‚

    #19926
    Swift Ideas – Ed
    Keymaster
    Post count: 15264

    Hi there,

    Just wanted to confirm, when you use the Codestyling plugin for translation, and follow the steps in the WooCommerce guide, it doesn’t work as intended?

    You shouldn’t be putting the WooCommerce translation files in the themes /language/ folder.

    – Ed

    #20260
    romaxa
    Member
    Post count: 7

    Hi!
    I follow the steps, they aren’t that complicated and I’ve done these theme and WooCommerce translatons several times on other installations with no problems. I haven’t moved the WooCommerce language file to the theme language folder. I have copied the W.C PO and MO-files, which ends up in another place, to the W.C language folder. It doesn’t help. I can’t think of anything else other than that it must be something in the theme, especially since I had to move the theme’s translation files via FTP. They should have been saved where they should be by Codestyling.

    When translating and saving a MO-file as instructed (with Codestyling) I get an error message which I copied to an earlier post here. Here it is again;
    Warning: The actual loaded translation content contains mixed textdomains and is not pure translateable within one textdomain.
    It seems, that there is code contained extracted out of other plugins, themes or widgets and used by copy & paste inside some source files.
    The affected unknown textdomains are: yit, wooslider, woocommerce, tax-meta, swift_page_builder, rwmb, love_it, Swift Framework

    #20661
    Melanie – SUPPORT
    Member
    Post count: 11032

    Hi,

    Ed was away over the weekend and will get back to you as soon as he can ๐Ÿ™‚
    Cheers!

    #20869
    Swift Ideas – Ed
    Keymaster
    Post count: 15264

    Hi there,

    Apologies for the delay.

    I honestly can’t think of any reason why this would be happening. The error message isn’t anything to worry about, just different parts of the theme, e.g. meta boxes etc.

    Can you please explain this part which you said – “I have copied the W.C PO and MO-files, which ends up in another place, to the W.C language folder”?

    – Ed

    #20907
    romaxa
    Member
    Post count: 7

    Instead of putting the language files in WooCommerce language folder, Codestyling seems to save them in another location. Along with the error message that I’ve copied here. I’ve copied the files from the other location and put them where they should be in WC folder among the other language files. It doesn’t help. So, since Codestyling translation have worked on other WordPress installations with WooCommerce before and I get this error message for the first time, to me it seem related some how.
    Is there something else I can configure differently with your theme do you think?

    #21136
    Swift Ideas – Ed
    Keymaster
    Post count: 15264

    That notice is actually referring to WooCommerce, and not the theme (just checking the plugin on our install).

    Just wanted to check, have you added the language files to /wp-content/plugins/woocommerce/i18n/languages/ (in the correct format)? What language are you trying to add, I’m guessing it’s not already included?

    – Ed

    #31151
    mr_pa
    Member
    Post count: 31

    Hi romaxa and Ed, to fix the translation issue with codestyling is enough that you delete the “lang” folder in:

    includes/swift-framework/meta-box/

    Rescan with codestyling and everything should works fine.

    Let me know,

    Mr_pa

    #31565
    Melanie – SUPPORT
    Member
    Post count: 11032

    Thanks for the heads up! I hope it works!

    #64966
    bargiel
    Member
    Post count: 7

    @mr_pa: Thank you! ๐Ÿ™‚

Viewing 15 posts - 1 through 15 (of 16 total)

You must be logged in and have valid license to reply to this topic.

License required for one of the following items
Login and Registration Log in · Register