[anettemossbacher]

Hi David,

I am afraid that there actually is something wrong and you can simulate it:

• Go to header-options in the Atelier theme options
• Select a Contact Slideout Page language A and save … test and it will work in the site … all fine
• Switch language to language B … select the contact page for language B and save …
• Now switch bak to language A and see what the Contact Slideout Page option says: nothing!

What happens is that the theme options saves the slideout page specified last (in this case language B) only and uses it in all languages. There is no way using the theme options to fix this. There also is no field available in {sf-atelier-options] that stores the data involved, so I cannot fix it there either. This is very inconsistent compared to how other translated strings get save in Theme Options in alternate languages.

This behavior wasn’t clear to me when I first opened this ticket. I then fixed it by digging out record id’s in the database and putting those number in in another field in the strings overview somewhere .. but those got lost again when saving the theme options.

So following the pdf instructions as you suggested, I found the field contact_slideout_page again … it was already ticked on but it cannot be found in the string translations page … regardless of whether I turn on “translate the theme and plugins” in localization …

So what do you suggest. Is this a bug or am I missing a feature? 😉

Cheers,
Johan Peijnenburg
(on behalf of Anette)

[anettemossbacher]

Many thanks Ed for chasing this! It’s fixed. Much appreciated!!!! Will this be automatically included in a next release or do I need to keep the code in the child theme once an update of the theme comes?

[anettemossbacher]

Hi Ed,

Just to be sure: I sent you an email to let you know it didn’t work. The page product just goes blank now. I have included ftp and normal login credentials in my mail, in case you want to have a look.

Cheers,
Johan

[anettemossbacher]

Haha, never skip the getting started guide ejh! 😉

So, I actually do not need to set “Translate the theme and plugins using WPML’s String Translation” to on in Theme and Plugin Localization right? That is just for when people want to work with a interface in a different language right?

[anettemossbacher]

Hi David,

Thanks for getting back to me 🙂

What I did is created 5 forms in contact form 7 … one for each language. Then I created a page that incorporates the UK version and subsequently created translations for them (via the normal WPML translation options for pages) in which I point to the contact forms for the corresponding languages.

That works fine when approaching the pages directly (via the page url). When switching language all works fine.

That doesn’t work when subsequently including the UK version in the slideout menu option in Theme Options. I can’t specify a language there so I figured the theme would make sure it switches to the right language based on the page translations. It doesn’t.

So what should I do differently?

No I have not translated my theme options for each language I use on the front-end. Should I? I did enable translation for theme strings at some point to be able translate some of the strings that I couldn’t translate without enabling that option. Is that what you mean?

Thanks

[anettemossbacher]

Please do … and it it it is rather urgent. I am postponing going live for this issue!

[anettemossbacher]

Ok, that worked. Thanks!

[anettemossbacher]

Hi Rui,

That doesn’t really work, so I will not be the last to ask. The “slideout contact field” points to a page based on an record number in a database table somewhere. There is no way to find the comparable record numbers for the translated versions via the Atelier interface nor the WMPL interface. The only way to get them is by doing a query in the actual database table to get the corresponding record numbers for the translations. I did that and managed to get it working.

It is however definitely something Ed should have a look at … seriously 🙂

Cheers,
Johan Peijnenburg
(on behalf of Anette)

[anettemossbacher]

Hi Rui,

Yes all is done according to the docs. Let me explain myself better …

– Products have been created
– Via Product Meta the Product decsription was filled in
– Swift Page Builder is enabled …. the pre-requisite for it to show up in the tab at the bottom of the page …. and it does in the basic language
– For translation purposes the related SF custom field “sf_product_description” has been enabled via Multilingual Content Setup
– Translations for the field have been entered.

In the base language, the decsription-tab shows up as expected (see att). In the translated products, the description tab doesn’t show up. I have tried to find the custom field that makes the tab active for the translated content. It doesn’t seem to be available in translation management however.

I believe it is related to a problem David has been working on: http://www.swiftideas.com/forums/topic/page-builder-not-staying-enabled/page/2/. As if the Page Builder Active parameter isn’t included when translating a product …

I implemented that workaround in the child team as suggested by David in that thread, but it doesn’t take yet …

Hope this helps. Thanks, Anette

Attachments:

You must be logged in to view attached files.

[anettemossbacher]

I fill out all the fields with the other languages, but it does not show on the product page

[anettemossbacher]

Yes of course

[anettemossbacher]

Thanks Kyle

[anettemossbacher]

Thank you very much Kyle 🙂

Have a great day

Ciao Anette

[anettemossbacher]

Hi Kyle,

thank yo very much. I have set it to

.my-custom-class.spb_parallax_asset {
background-position: 0 30% !important;
}

That did the job to show the person as well on bigger screens like 24″++

Thank you very much.

From which width size on does the theme start to resize the logo?

Ciao Anette

[anettemossbacher]

HI ED,

no it isn’t.
Sorry for the confusion!