With Translation Management enabled, if I visit the Article content type to attempt to edit the translation-related settings at:
http://example.com/admin/structure/types/manage/article
two errors appear:
* Notice: Undefined index: method in drupal_prepare_form() (line 937 of /home/www/drupal7/includes/form.inc).
* Notice: Undefined index: #title in _icl_content_retrieve_title() (line 154 of /home/www/drupal7/sites/all/modules/translation_management/icl_content/icl_content.contentype.inc).
Possibly related, although also possibly a separate issue, when I visit the Multilingual settings tab, all settings are greyed out, and the messaging says:
Extended multilingual options provided by Internationalization module. These will be available only when you enable Multilingual support in Workflow settings above.
But there are no "Workflow settings above".
| Comment | File | Size | Author |
|---|---|---|---|
| #24 | honoredsoft_fix.patch | 1.44 KB | HonoredMule |
| #19 | translation-manager.patch | 596 bytes | stefgosselin |
Comments
Comment #1
reinvented commentedThe issue of the greyed out options on the Multilingual settings tab was solved by visiting the Publishing options tab, and selecting Enabled, with translation (or just Enabled
However when I do this, I see an additional error message:
* Notice: Undefined property: stdClass::$nid in icl_content_nodeapi() (line 1000 of /home/www/drupal7/sites/all/modules/translation_management/icl_content/icl_content.module).
Comment #2
scholli-d commentedI have the same two errors as described in the initial statement here with a fresh installation of Drupal 7.0 (from 2011-Jan-05) only installed the Translation Management (=copied release 7.x-1.0-beta1 from 2010-Dec-29 to the folder 'modules' in my drupal installation) and activated the modules
* 'Content translation' and 'Locale' from the Core section and
* 'Content', 'Core' and 'Translate' from the Translation management section
Comment #3
scholli-d commentedAfter I choosed Multilingual Support 'Enabled, with translation' for content type 'article', a third error appears when editing the content type article. So all three errors are
* Notice: Undefined property: stdClass::$nid in icl_content_nodeapi() (line 1000 of /.../modules/translation_management/icl_content/icl_content.module).
* Notice: Undefined index: method in drupal_prepare_form() (line 937 of /.../includes/form.inc).
* Notice: Undefined index: #title in _icl_content_retrieve_title() (line 154 of /.../modules/translation_management/icl_content/icl_content.contentype.inc).
When editing content type 'basic page', only this error message appears:
* Notice: Undefined index: method in drupal_prepare_form() (line 937 of /.../includes/form.inc).
Comment #4
knalstaaf commentedSubscribing.
Comment #5
knalstaaf commentedDisabling "Translation Services » Content" removes this message, bùt with this as a result: Call to undefined function icl_content_fix_links_in_all_dirty_nodes() in /icl_core/icl_core.module line 171.
Comment #6
jan101 commentedsubscribe
Comment #7
alex.cunha commentedthe same here:
Comment #8
ruth_delattre commentedsubscribe
Comment #9
ihamilton commentedsubscribe
Comment #10
FreeFox commentedSame here, when I do a fresh install and only enable local translation and I do a status check I get these errors:
* Notice: Undefined property: stdClass::$nid in icl_content_nodeapi() (line 1000 of /.../sites/all/modules/translation_management/icl_content/icl_content.module).
* Notice: Undefined index: method in drupal_prepare_form() (line 937 of /.../includes/form.inc).
* Notice: Undefined property: stdClass::$nid in icl_content_nodeapi() (line 1000 of /.../sites/all/modules/translation_management/icl_content/icl_content.module).
* Notice: Undefined index: method in drupal_prepare_form() (line 937 of /.../includes/form.inc).
* Notice: Undefined property: stdClass::$nid in icl_content_nodeapi() (line 1000 of /.../sites/all/modules/translation_management/icl_content/icl_content.module).
* Notice: Undefined index: method in drupal_prepare_form() (line 937 of /.../includes/form.inc).
* Notice: Undefined index: value in theme_status_report() (line 2501 of /.../modules/system/system.admin.inc).
* Notice: Undefined index: value in theme_status_report() (line 2501 of /.../modules/system/system.admin.inc).
Also I get these warnings:
Warning
i18n Taxonomy i18ntaxonomy module is not enabled
Enable the i18ntaxonomy module if you want to have taxonomy translated.
Warning
i18n Blocks i18nblocks module is not enabled
Enable the i18nblocks module if you want to have taxonomy translated.
However, these two modules are enabled:
Taxonomy translation 7.x-1.0-beta4
Block languages 7.x-1.0-beta4
Hope this helps and looking out for a solution.
Thanks in advance
Freefox
Comment #11
jorgush commentedsame here
Comment #12
tebb commentedSame here.
Comment #13
dream1 commentedAnd same here. It looks like the translation managemen does not work @ all normaly. And on my drupal its pointless.
Comment #14
aristeides commentedsubscribing
Comment #15
Pickau commentedI have the same problem. I moved to 7.2 and still the same problem. I need my site to be in french and english. I am new to Drupal, moving from Joomla, should I revert to version 6 to have a multi-language site?
When can I expect to have a functional multi-language site?
Comment #16
tebb commented@Pickau: If you can, I would stay with version 7.2 as it is generally better than 6 for a multi-lingual site.
There are many multi-lingual modules that help. Do you *absolutely* need this Translation Management module *now* for your site?
Comment #17
Tim Rasim commentedSubscribing
I just started using drupal and don't completely understand how it works, but am I correct in the assumption that the array "$row" should contain an element "nid" and that its absence is the reason for our error?
Comment #18
eeric49 commentedWow! I've spent the last one week trying to solve this error--->
Notice: Undefined property: stdClass::$nid in icl_content_nodeapi() (line 1001 of D:\xampp\htdocs\drupal78\sites\all\modules\translation_management\icl_content\icl_content.module).
but no success. I noticed it prohibits translation of the first language to the second language. You find out that when adding your own translation, you are deleting the default language article.
Any good Samaritan with a developing idea? It can help us move on. Thank you
Comment #19
stefgosselin commentedI had to come up with a quick fix for this, patch is included please review before using, in my case it cleared all the errors on this issue when used in conjucntion with this patch: http://drupal.org/files/issues/translation_management-n1115426-24.patch.
Use at your own risk -> not guaranteed to resolve the issue properly as I did not have time to go in depth, but it did make the error messages go away. Anyone with time to review this is most welcome to do so!
Comment #20
AlanO commentedI've been getting the same errors as comment #10. I used both patches from comment #19 and failed. I get this error when I'm editing an already configured multilingual content type(Basic Page). I'm using a fresh install of core 7.9 with the required Internationalization modules(Variable, Localization Update).
I get these errors from the Article content type.
I still get these errors in Configuration>>Translation Management>>Status Check
Yet I still have both modules already installed.
Comment #21
miro_dietikerCurrently we're reimplementing this module from scratch in our codesprint:
http://drupalevents.ch/drupal/codesprint-2012
Thus all current bug reports and feature requests are dropped. Please recheck once the the sprint is completed.
Comment #22
dewolfe001 commentedThis patch appears to clear up this error! I'll monitor to see if this clears up things or if this just masks some other problem going on.
All the best,
Mike
Comment #23
imjooseo commentedSuper. The patch cleared those error messages; haven't tested it on other areas though.
Comment #24
HonoredMule commentedThe provided patches haven't cleared the issue for me. Inspecting the data that was choking, I believe I identified two issues:
1 - A case where a title was being expected in a base array when it was actually in a sub-array, fixed by actually checking for the presence of the title in addition to the matching key.
2 - A case where defaults were missing from the provided form_state...misuse of theForms API, I think. Local arrays were replaced with a call to form_state_defaults(). Originally only two array keys were being set, and the first doesn't appear anywhere in the Forms API (version 6 or 7) nor the rest of this module's codebase.
There is of course the possibility that further bugs persist or have been uncovered in the process...testing has been light so far.
Comment #25
hectorelgomez commentedThanks, two patchs works perfectly.
site in: catalan, castellano, english.
Comment #26
hectorelgomez commentedComment #27
hectorelgomez commented