All email submissions get imported correctly during the fetch processes, however they don't show up in the jobtrack/clientname screen. They DO show up under admin/content/node/overview where it shows that the ticket has the "Language Neutral" option. If I create a jobtrack ticket on the site, and apply a language that is not "Language Neutral", then they do show up in the lists.

It seems like "Language Neutral" is rearing its nasty head again, and I would propose two possible solutions:

1) an additional field gets added to the Jobtrack Add Client page where (if the jobtrack node has been setup to enable multilingual) you can define the language for the client. This language gets applied to all email-submitted tickets upon node creation.

AND/OR

2) rework the code so language neutral nodes shows up on the clients jobtrack listings pages.

Comments

jwilson3’s picture

jwilson3
Primary language English
Location Ecuador
commented
Title: Add language support for clients on a multilingual site. » Better language support for multi-lingual (i18n) sites

improved the title of this issue.

jwilson3’s picture

jwilson3
Primary language English
Location Ecuador
commented
Status: Active » Needs review

I scratched my own itch here...

In file jobtrack.module at line 699, at the very end of jobtrack_save_message() function, just before node_save($node);

I inserted one line:

 $node->language = $account->language;

The resulting code looks like this:

    $node->jobtrack_email = TRUE;
    $node->language = $account->language;  // my new line
    node_save($node);

And this in fact solved the problem for me. Now when I submit a new ticket via email, and run cron (or the fetch function) a new ticket will automatically get the user accounts' language assigned to its node, and thus DOES show up in the jobtrack client's ticket listings.

Would be awesome if you could add this into the next version!

Is a patch file necessary here? i hope not ;)

jeremy’s picture

jeremy commented
Status: Needs review » Fixed

Excellent, thanks for following up to your bug report with a fix! Fix committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.