Sorry, could you explain how qTranslate works? Does it automatically translate, or do you provide a translation in the back-end?
Unfortunately there will always be plugins that are incompatible with the front-end-editor. Especially unconventional ones. It’s up to plugins to support it. I’m not sure yet how we’re going to handle this, but it’s indeed necessary to think about it.
Please also note that this plugin is in development and might break things or accidentally erase data. It’s not yet ready to use on production websites.
Of course. You have to provide every lang translation.
Basicly, QTranslate wraps each translate like this tags. <!–:es–>Content<!–:–>
The content saved on the DB by qtranslate in two langs (spanish and english) will look like this:
<!--:es-->Content wrote by me in spanish<!--:-->
<!--:en-->Content wrote by me in english<!--:-->
The user never see this, because the plugin add a tab for each lang on the edit screen (Like the “Visual” and “Text” ones).
If in edit with WPFE a post, it replaces all the post content without the mentioned lang tags.
I noticed that it is on development, but i like and for that reason i’m trying help to make it better. 😉
Right. So you get all the translate content at once without the tags (<!–:lang–>)?
I can make these tags show up, but providing tags is something the plugin will have to do in the future.
Nope. I just get the content of the lang i’m actually reading.
For example (for a post saved from the backend and with both langs filled up.).
Given the post “my-post” y have 2 urls:
- http://mysite.com/my-post
- http://mysite.com/es/my-post
If i hit edit on the front from the http://mysite.com/en/my-post, i get just the spanish content, BUT if i then modify text and save, the english content is erased.
I think this is because qtranslate process the post content before it’s is returned to the front, and it saves BOTH langs if it is modified from the end. On the other hand, WPFE saves the post content as it is in the current lang (replacing this way, the other ones).
Note the different editing urls from the front creating the same result.
- http://mysite.com/my-post/edit
- http://mysite.com/es/my-post/edit
Sorry if i’m not explaining this good enough.
Regards.
Right. This is something the plugin needs to take care of later on. It’s impossible to fix that with this plugin, even if I wanted to.
