[pstidsen]

Hi Ed,

WPML is waiting for your answer. Will you please get back to Vuk from the WPML-team?

Hope we can get this fixed soon!

[pstidsen]

I have mailed Helena from WPML today again again.

[pstidsen]

The day before yesterday there was an update for the Neighborhood theme, but the WPML-issue is not fixed yet.

It is nearly two months since WPML took contact and nothing has happened. I do not think this is okay.

Please fix it!

[pstidsen]

The request about a smaller page did also came after the buy. However I thought it was more or less standard to have a couple of different widths. The full width and boxed page are nearly identical on a 1366px width screen.

[pstidsen]

I better hope my client will accept that!!

[pstidsen]

Ya, my concern is also about the responsiveness…

[pstidsen]

OK, but it will be possible with some width-fixes on the elements.

[pstidsen]

But what if I also adjusted the elements inside the div#container.boxed-layout?

[pstidsen]

Hmmm.. Isn’t it possible to change it with some custom CSS? I think I could do it on my own. Does it has some disadvantages in relation to responsiveness or anything else?

[pstidsen]

Should the new update fix it?

I have still problems.

[pstidsen]

I think I’ll leave it at the old position, then.

[pstidsen]

It is at style.css in my child theme. I have changed the CSS path to the valutaskifter, so it target the <select> tag.

[pstidsen]

The HTML output is placed different places. The <select> isn’t placed in the <div class=”valutaskifter”>. How can that be?

[pstidsen]

A bit.. I’ve added it like this:

$header_output .= '<div class="header-right span8"><div class="valutaskifter">'.do_shortcode('[currency_switcher]').'</div>'.sf_aux_links('header-menu').'</div>'. "\n";

[pstidsen]

Doesn’t seem to work as expected. What’s wrong?