i18n_taxonomy issues

[laryn]

i18n_taxonomy issues

[laryn]

Just to update, after the latest commit this timeout bug still exists. But I can now visit admin/structure/taxonomy/tags and view a "Translate" tab, which seems to function at a basic level (as opposed to the 2nd error above).

[laryn]

Same as #2 -- a matching error shows up in watchdog if I've got i18n_menu disabled and i18n_taxonomy enabled, and I try to go to the vocabulary's "Configure" page:

Notice: Undefined property: stdClass::$language in i18n_langcode() (line 277 of /Users/user/buildkit/build/backdrop-demo/modules/i18n/i18n.module).

https://github.com/backdrop-contrib/i18n/blob/1.x/i18n.module#L277

[indigoxela]

A new PR is available. Please test. It fixes (should fix) all those errors plus brings basic functionality.

Really, please test.

[laryn]

@indigoxela The main functionality seems to be working well -- amazing! Here are some observations and a few issues I found along the way. Take them for what they are worth at this stage.

1. Taxonomy > Manage Display shows a blank field (when that vocabulary is set to "Translate."):
   
2. Taxonomy > Manage Fields gives an error (when that vocabulary is set to "Translate."):

Error: Unsupported operand types

3. An "Undefined" translation set is created at some point:
   
4. Not sure if it's related to this module, but on vocabs that do not have multilingual options enabled, the table columns/headers are not matched correctly:
   

[indigoxela]

@laryn many thanks for testing! Yes, I also observed some odd behavior when switching between types (translate, localize, none...). And I also observed that handling translation sets should get more robust.

I'll have a look at that table header problem, too. (Weekend is coming 😉)

[indigoxela]

@laryn More commits have been made to my PR, which address point 1 and 2 (many thanks for pulling this out).

And it should be much harder now to create a broken "Undefined" translation set (point 3). It might still be possible, though.

As you already suspected, point 4 is unrelated to i18n. Thats backdrop/backdrop-issues#3869

In case you still see php notices, try to start with a fresh database. The broken translation sets might have created incomplete taxonomy terms that could interfere.

...and report all the remaining issues here. 😉

[laryn]

Thanks again @indigoxela ! More comments from a walkthrough on a fresh install:

1. There is no default or requirement on the "Extended" radio buttons after enabling Multilingual on a vocab. Is that supposed to be that way?
   

2. I tested "Localize" first and that seemed to be working well. Then I changed configuration to "Translate" and the term I had localized had no translation (I suppose the localized data doesn't transfer automatically) so I added a translation to the term. This seems to work pretty well (1 and 2 in my earlier comment are fixed) however, I see this twice in the log:

Notice: Undefined index: langcode in i18n_taxonomy_form_alter() (line 918 of /app/modules/i18n/i18n_taxonomy/i18n_taxonomy.module).

Also, the "Translation sets" page continues to create/show an "undefined" set:

3. I was going to test "Fixed language" but I'm not sure what that is supposed to do. It forces me to choose a language in the configuration for that option:
   

But when I am creating a new term, it still lists all language options:

[indigoxela]

@laryn Thanks again for testing.

Re point 1 - probably this should have a default value...

Re point 2 - nice catch! I didn't realize that php notice, should be fixed now. And to clarify: localize and translate are fundamentally different (different submodules actually).

Re "Undefined" translation sets: can you provide the steps to create one, please?

Re point 3 - fixed language. I took a look at that now, it should be working with the latest commits (the language dropdown in Backdrop is provided by core).

Happy testing again. 😉