oferwald

Hi,

Seems like your front page is not getting the edit param from the url, I don’t know why this would happen, but I guess something is messing with the way wordpress processes the paramaters sent.

I don’t know how you can bypass it, except setting the edit mode manually in code on your from page when this param (edit=y) is a part of the url

Hi,

Insisting is more then ok,

Regarding the slider, I am not sure I was even able to solve the problem last time, if its the same component, than it generated the texts using some inline javascript,

This is possible to fix, but needs some work and YMMV

Regarding the form, this is more simple, do you have the .po/.mo files for the component that have created this form? just put them in and enable the integration feature, and it should work.

An alternative would be to use the transposh_echo() function, but that depends on the implementation.

Premium support is offered directly in the support tab of our plugin, it would have not helped you much in the last week, because of a virus I caught (not a computerized one), but it will get the slider fixed 🙂

Sorry for the delays in replying (not just to you) and I hope I’ll be able to catch up asap

I have seen this, but can’t help, as those errors don’t mean much.

What does your php error logs show? Your webserver error logs?

@socialmo, please open your own topic next time, and to me, your site looks fine. I guess you fixed it

Thanks for sharing 🙂

You are probably missing the Chinese of Taiwan variant (zh-tw) language in the redirect, but I guess it is not really that important

Hi,

Since there are missing details here, like for example what component is generating those emails, etc. I can’t provide any specific answer.

In general, that component must be made aware of the language that was used, and make sure that the proper email goes out.

If you’ll provide more details I’ll try to see what I can do, but this is probably out of the scope of the free support we provide.

Hi,

Since I see parts of the frontpage are being translated, there are two main options:
1. broken html, please check the page with w3c validator
2. using hidden chars in the chr(1)-chr(4) range which will cause the parser to break.

If 1 passes fine, please use the contact form and contact us, we’ll try to solve it together.