No translation columns in the DB - Unknown column 'f.handle-fr' in 'where clause

[nitriques]

I really do not know what cause this, I was running 1.3 at the time.

I did update to 1.4.1 but still no luck.

When I save/create an entry, I get Unknown column 'f.handle-fr' in 'where clause'

I think it may be related to the fact that we develop this backend specifying only one language. We did that because the client does not have a translator but wishes to translate its content later. So in LR, only one language was set.

I will investiguate more tomorrow.

[6ui11em]

I have some sites with just one language in the LR and works without problem. I hope to have some time soon to update this extension, I will try to re-write the extension to make it more "multilingual standard" and use the methods vlad-ghita create for the other multilingual extension he created. Maybe if your problem is a bug of the extension this will be fixed. So maybe you could solve the problem updating the database directly.

[nitriques]

@6ui11em here is what I did to solve my issues:

Since all translated column where no longer available, I added a second language in the hope that the ext would create all missing column.. and it did ! I then remove the temporary language (leaving an extra comma (,) at the end, i.e. "fr,") and consolidate the data column. I was then able to update all the value-fr and handle-fr fields with the values that were still in value and handle.

Honestly, I was hoping that you did ran into this issue. But since it's soooo much complicated and kind of impossible to reproduce, I think this issue is closed. But everybody should keep an eye open for this and report the exact steps needed to reproduce this issue.

Finally, I am trilled about the update. Do not hesitate to contact me personally if you need any help, I'll see what I can do. We should consider updating to the lastest LR version too and make sure it's 2.3 compatible.

[vlad-ghita]

I will try to re-write the extension to make it more "multilingual standard" and use the methods vlad-ghita create for the other multilingual extension he created.

Maybe I can help around here :)

link With the next update we will extend the Texbox Field extension and we will use all his original methods

I've been dreaming for some time now to derive this field from Textbox.

[6ui11em]

Thank you, if I need help I will tell you. I already write a Multilingual Taglist extending the original extension using your methods, it was so easy great job! I will pull it to the git after some more tests.

[nitriques]

@vlad-ghita I don't think extending the texboc field would be such a great idea.

I really dislike the fact that simple one line of text can't be converted easily to a multiline one. Text is text no mater on many lines you have.

That's why I use this extension even though I only manage one language for the whole thing.

[nitriques]

@6ui11em Can't wait to see your ML tag list. Are each tag gonna translated ? Or you have languages separated lists ?

[6ui11em]

works like the multilingual text field, value-{lang_code} and handle-{lang_code} is generated for each field entry (tag)

[nitriques]

Sounds great !