Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi!
When I went to create new vocabulary (admin/structure/taxonomy/add) I got this notice:
Notice: Undefined property: stdClass::$i18n_mode in i18n_taxonomy_form_taxonomy_form_vocabulary_alter() (line 368 of /var/www/www.example.com/sites/all/modules/i18n/i18n_taxonomy/i18n_taxonomy.module).
Notice: Undefined property: stdClass::$i18n_mode in i18n_taxonomy_form_taxonomy_form_vocabulary_alter() (line 377 of /var/www/www.example.com/sites/all/modules/i18n/i18n_taxonomy/i18n_taxonomy.module).
Enabled modules:
drush pml --status="Enabled" --package="Multilanguage"
Name Type Version
Internationalization (i18n) Module 7.x-1.0-alpha1
Multilingual content (i18n_node) Module 7.x-1.0-alpha1
Multilingual select (i18n_select) Module 7.x-1.0-alpha1
Multilingual variables (i18n_variable) Module 7.x-1.0-alpha1
String translation (i18n_string) Module 7.x-1.0-alpha1
Synchronize translations (i18n_sync) Module 7.x-1.0-alpha1
Taxonomy translation (i18n_taxonomy) Module 7.x-1.0-alpha1
Hope so it's enough data. :)
Vocabulary is successfully created.
Comment | File | Size | Author |
---|---|---|---|
#29 | 1026290.i18n_taxonomy_taxonomy_vocabulary_update.v2.patch | 583 bytes | webflo |
#26 | 1026290.i18n_taxonomy_taxonomy_vocabulary_update.v1.patch | 448 bytes | tricasse |
#15 | screenshot2.png | 47.91 KB | Jose Reyero |
#12 | screenshot-mysql.PNG | 13.65 KB | gurvan |
Comments
Comment #1
mariomaric CreditAttribution: mariomaric commentedAlso when listing (3) terms from created vocabulary (admin/structure/taxonomy/vocabulary_name) I got following error:
One more thing: I can't find option to translate terms?
Comment #2
delugestudios CreditAttribution: delugestudios commentedI'm running into the same exact problem. Unfortunately this could prevent me from using Drupal 7 on a site I'm currently working on, which would break my little heart. Any clue on how to move forward?
Comment #3
kunago CreditAttribution: kunago commentedI am having the same problem. It prevents me from setting a language for a vocabulary and in a result I am unable to use the taxonomy module for a multilingual website.
Comment #4
robertgarrigos CreditAttribution: robertgarrigos commentedThis should be fixed in the master branch of Jose's repo at github https://github.com/josereyero/i18n
You should be able to have a multilingual D7 with that code. He will create a new release ASAP.
Comment #5
kunago CreditAttribution: kunago commentedI have just tested the most recent version of i18n from GitHub and the problem persists.
EDIT: Adding the errors with the newest code
Comment #6
jaxpax CreditAttribution: jaxpax commentedI have just installed the latest version from Github and I'm having the same problem as pointed out in this issue.
Comment #7
WilliamV CreditAttribution: WilliamV commentedI confirm this issue as well.
Comment #8
joostvdl CreditAttribution: joostvdl commentedSubscribe
Comment #9
comerer CreditAttribution: comerer commentedAlso having same problem.
Tried the link above (https://github.com/josereyero/i18n), but it didnt fixed the issue.
Thank you
Comment #10
BVod CreditAttribution: BVod commentedSubscribe
Comment #11
gghh2 CreditAttribution: gghh2 commentedHi,
I have the same problem :
but I can't add term anymore to the vocabulary created with i18n. Drupal says "New term 'gggggg' has been created" but it doesn't appear in the list of term
Comment #12
gurvan CreditAttribution: gurvan commentedthe same as gghh2, note that the term is present in the DB (cf screenshot)
Comment #13
gurvan CreditAttribution: gurvan commentedReply to myself
I disable i18n_select & it works...
Comment #14
jaxpax CreditAttribution: jaxpax commented@carcs - Could you please be more specific on how you fixed this?
Thanks.
Comment #15
Jose Reyero CreditAttribution: Jose Reyero commentedThe issue original issue has been fixed in latest version (github).
Also, the issue about terms not showing up is just i18n_select module in action. Give a try to latest version, or wait for alpha3
Attached, screenshot from latest dev version (github).
Comment #16
klonosI just got this on a fresh installation of core 7.x-dev using the latest 7.x-1.x-dev:
I am stressing the fact that latest dev builds are used - both core & i18n.
Comment #17
Jose Reyero CreditAttribution: Jose Reyero commentedOn which page? What are the settings for the vocabulary, etc?
We need some clues to reproduce the issue.
Comment #18
klonos...sorry Jose, I've been trying a few new things in the past two days real quickly, so I didn't get to jot down where I got this. I know #16 is a stupid report, but I guess I thought it'd make sense without the info you request -my bad. Let's just close it then till I get it again (if I ever will) and then I'll re-open with proper info.
Comment #19
dqdklonos please read -> http://drupal.org/node/156119#closed
The silly ...
Notice: Undefined property: stdClass::$i18n_mode in i18n_taxonomy_vocabulary_mode() (line 1022 of /root/xxx/www/xxxx/sites/all/modules/i18n/i18n_taxonomy/i18n_taxonomy.module).
... occures about 6 times on each page load needing any taxonomy variables, with latest i18n + i18n sub modules activated in our testing enviroment.
if I am not too tired (2 pm night over here in Berlin) ... the property taxonomy_vocabulary_load($vid) can't be loaded from object i18n_mode successfully.
Another issue I recognize with it may be, that I can't save locale status of vocabularies, meaning checkboxes stay unchecked after trying any combination of localize / translate / etc
on structure/taxonomy/vocabulary_name
and hitting save without any luck. m... not sure of both is connected to each other.specs -> --dev updates an hour ago ... ... D 7.8 official stable release, i18n-dev, variable, token, views, ctools, ds, webform, pathauto, etc
I hope it helps, will test more tomorrow ...
good night
Comment #20
dqdok --- changing back to english as default language and setting admin profile to english while language per user is allowed incl. running cron + cc all (clear all caches) made the error disappear.
... strange ... I'll report any further conspicuousness ....
Comment #21
ckrinaI'm having exactly the same error (Undefined property: stdClass::$i18n_mode in i18n_taxonomy_vocabulary_mode() ) in a today's clean D7.8 install in my localhost, so I can't show you.
I have 2 languages (Spanish & Catalan), and english dissabled. Catalan is the default language.
I have not introduced any term and it's showing me the error when I enter
Home » Administration » Structure » Taxonomy » Tags
If I turn on english, make it default language and clear cache (I know it's useless), the problem persists.
Comment #22
ckrinaI reinstalled my Drupal using English as default language, I installed the module again and created the terms. Then, I traduced them.
Now, I've changed the default language to Catalan again and everything works.
I don't know if it helps to fix this, but I solved the problem.
Comment #23
jox CreditAttribution: jox commentedSame problem as #19 here: Several of these errors on any page that uses taxonomy terms. Also on every "edit vocabulary" and "list terms" admin page.
Site has 4 languages (en, de, fr, es), default language is english. Happens since updating Drupal to 7.8. Module i18n is 7.x-1.0.
Comment #24
Jose Reyero CreditAttribution: Jose Reyero commentedOk, fixed that line. I hove we got ride of this notice for ever.
Comment #26
tricasse CreditAttribution: tricasse commentedSame issue on line 600 when importing taxonomies through Features:
Notice : Undefined property: stdClass::$i18n_mode in i18n_taxonomy_taxonomy_vocabulary_update() (line 600 in /drupal_root/sites/all/modules/i18n/i18n_taxonomy/i18n_taxonomy.module).
Fixed for me with the attached patch.
Comment #27
Jose Reyero CreditAttribution: Jose Reyero commentedThe patch looks good.
Comment #29
webflo CreditAttribution: webflo commentedRerolled the patch and committed to 7.x-1.x. Thanks!