Closed (fixed)
Project:
Language Assignment
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
14 Oct 2010 at 22:46 UTC
Updated:
20 Nov 2010 at 04:10 UTC
Jump to comment: Most recent file
hey
something went wrong... the language got set as "Array", instead of the intended language (pt-pt).
when editing the node, it defaults back to language neutral... in other words, it failed, resulted in a invalid array, and drupal rejects the language setting for the content
Tecnologias novo Page admin não publicado Array editar
tried setting pt-pt for multiple content, some were neutral some pt-pt... all were of content type page.
content type set as multilingual, translatable
this a bug or am i doing something wrong?
specs:
drupal 6.19
i18n latest
lang assign 1.2
language neutral/english disabled
defaulting to pt-pt
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | ladebug.txt | 674 bytes | Andrew Schulman |
Comments
Comment #1
Andrew Schulman commentedSounds like a bug allright. Sorry about that, that should never happen.
Can you please do some debugging for me, in order to help me figure out why this is happening? What I need you to do is to save the attached file (ladebug.txt) as ladebug.php, in the root of your site's Drupal directory. Then go to http://www.domain.com/ladebug.php, and post the resulting output here.
Comment #2
Andrew Schulman commentedI'd like to fix this bug, but I need your help with debugging (see comment #1) since I can't reproduce it on my site.
Comment #3
lpalgarvio commentedwill get back to you soon
Comment #4
lpalgarvio commentedsorry for the delay, had other urgent issues.
currently, i have 2 languages set.
* Portuguese, Portugal (pt-pt), as default language, in path /
* English (en), as secondary language, in path /en
Comment #5
Andrew Schulman commentedThanks, I think this helped me nail it. I just uploaded a revised module. Can you please test it, using either the new -dev release that will be available later today, or a CVS checkout? And let me know if the problem is fixed.
Comment #6
Andrew Schulman commentedComment #7
lpalgarvio commentedwill test soon, when i get some free time
Comment #8
Andrew Schulman commentedI tested this. It's fixed in version 6.x-1.3. Feel free to reopen if you think it's not fixed.