Support i18 translation for Classified Ads categories

i18n is indeed something that has been consistently overlooked in the module, which assumes a single language and hopes for the best.

Can you describe an actual procedure to follow to reproduce the problem in as little steps as feasible to localize the problem, and include the expected result along with what you observe ?

Ideally, a simpletest failing on the actual problem you meet would be ideal, but unless you feel like it, just stick with the "text" version of the problem.

After looking into it, supporting multilingual is too big of an issue at this point in the module lifecycle: we need to have a stable - albeit limited - version 6.x-3.0 so people can start switching from 5.x and 6.x-2.x, and reopen this for the next version, instead of maintaining an unstable version no one can really track.

Changing issue description accordingly. I will reopen this for 6.x-3.1.

Related issue #1244678: Undefined index: und in the function _classified_list_nodes() : Classified Ads 3.0 only supports language-neutral content.

Hmmm version 3x is displayed as stable but this version is NOT trasnlatable

At least someone should place a big warning in the description,

I should try version 2 then?

@pitxels: I would advise against it. Classified 2 was never really made workable and the code base is just not worth it.

Good idea to mention the "single language" limitation on the project page: I just added it.

3.1 is out, and I'm wondering if anything is going to get moving with i18n… Reopen?

Seeing how close we are now to Drupal 8 being release, my bet is there will never be a 7.x-3.x version with i18n support. Unless someone comes up with a working patch. At any rate, nothing will change on 6.x-3.z, since Drupal 6 is going to be out of support three months after D8 release.

Since Drupal 6 was EOL-ed in 02/2016, no additional fixes will be added, so marking won't fix.