[tt1011]

This reply has been marked as private.

[tt1011]

Hi Kyle, did you see where I said (in the first post):

“I have the HTTPs plugin installed”

Yes. I have the plugin.

[tt1011]

When someone says they “have no padlock” that means the SSL cert is good, and valid, but there is probably assets loaded via http instead of https.

I have no padlock.

and the reason i do not is because ulrs generated by your theme, in this case the top boar social links, are not using https.

how do i fix this?

[tt1011]

This reply has been marked as private.

[tt1011]

Ed, just a heads up. I was on support with woo, and they

The fields not translated on the checkout page is apparently an issue within WooCommerce itself since the latest version, we are currently working on this, and that should be fixed shortly.

[tt1011]

Cart dropdown is now showing. The fix came after I added a custom currency symbol for PERU via the snippet from this link: http://docs.woothemes.com/document/add-a-custom-currency-symbol/

the issue might have been tied to a widget i installed from woothemese that does currency conversion. So your lang files are prob fine. The checkout however is still in English. Not sure why. would like to get to the bottom of that.

As for the location of lang files, i restored the files that came with the theme download. I will try again this time substituting your attached files to the location /neighborhood/language

[tt1011]

I even went ahead and changed

define('WPLANG', 'es_ES');
to
define('WPLANG', 'sv_SE');

(to test, because i saw both of those files in your themes directories)
but that had the same result: some strings on the product page where translated, but not the cart hover and checkout pages.

[tt1011]

they look like they belong in neighborhood/includes/swift-framework/meta-box/lang
i put them there, no change.

[tt1011]

Which directory do you want me to put these:

neighborhood/includes/swift-framework/meta-box/lang
or
neighborhood/language

[tt1011]

Then I get this warning:

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, woocommerce, tax-meta, swift_page_builder, swift-framework-admin, rwmb, love_it

[tt1011]

What i do to try to resolve the above issue is rename includes/swift-framwork/meta-box/lang/es_ES{.mo|.po} files to es_ES, then do a rescan via codestyling-localization

[tt1011]

This reply has been marked as private.

[tt1011]

The included language file.

[tt1011]

Hi @ed
I had version 1.8 (latest) but I also tested with a fresh download and install of 1.8 too.

Most of the site is in spanish, as it should be.
The shopping cart hover drop down is in english, should be in spanish.
The field names on checkout are in english, should be in spanish.
The cart page is all in spanish, as it should be.

Any other ideas?

[tt1011]

Thanks Kyle. I will take a look into the image sizes that were uploaded.