Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • in reply to: "NEW" banner on product page photo not translateable #31148
    romaxa
    Member
    Post count: 7

    Hi!

    I’ve been in contatct with you guys before regarding translations. Then I had problem translating in a plugin that I always use in my projects – CodeStyling, since its better than POEdit. My plugin found errors in your theme and the translations couldn’t be saved. I sent you screen dumps but no solution was given because you couldn’t find out what was wrong. So, I made the translations directly in the theme with help from Dreamweaver, which I know isn’t ideal, but theres where we are at. At that time there was no guarantee that it would work better with POEdit and I had a deadline. There’s still that tiny little word that can’t be find even by searching the whole installation. At this point I don’t have time to do a third translation. That will have to wait until updates are called for, so I need help with the location/file name. Thanks!

    in reply to: Translation of PO-files don't apply #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?

    in reply to: Translation of PO-files don't apply #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

    in reply to: Translation of PO-files don't apply #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!

    in reply to: Translation of PO-files don't apply #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

Viewing 5 posts - 1 through 5 (of 5 total)