translateforuser

Richard over 7 years ago

We are having problems with the translate for user function. We've wrapped it inside our own functions that determine the appropriate properties file, but one particular properties file is not loading and we're getting "???" wrapping the key field instead of the translation in some forms.

We've removed/re-added the plugin, restarted the application, renamed the file (successful result), but we already have a small mountain of code that references the file and don't want to "needle in a haystack" search and replace every reference.

Ultimately we're getting a NullPointerException on the file, but it's there in the correct folder in the document repository.

Anyone have a clue how to debug this? Is the file reference somehow corrupted? I don't think this is specific to the plugin any longer....

Discussion posts and replies are publicly visible

0 Richard over 7 years ago

To clarify, what I did was create a new pair of properties files and change the reference in some sail forms. That worked. The content was the same, only the names and document id's were different
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Richard over 7 years ago

Jenn - thanks for the suggestions, but I'm not sure what you mean that the file reference is now incompatible? I know that the plugin caches it's file references, and if I delete the file that will cause problems. According to the developer, restarting the application should fix that (which we've done). This makes me feel like the issue is likely centered on the document or folder, and I'm wondering if anyone has had an issue with that type of problem before?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Cichy
Appian Employee
over 7 years ago

Can you add a link to the plugin please? I am not too familiar with it.
Could it be that the contents are are cached and you just need to refresh it? The fact that when you renamed the file, things worked would indicate that the contents were reloaded.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rodgraham
Certified Lead Developer
over 7 years ago

Had the same problem with the plug in before and had to create a new file. We were using a constant to point to the file so only needed to make a single update to point to the updated file across all our forms. It's been stable since for the last few years.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Richard over 7 years ago

Damn, that's a good idea Rodgraham. Hadn't thought of that. Still have to go through all my interfaces and update them though to use the constant.

Mike Cichy, looking, will update shortly.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Richard over 7 years ago

Rodgraham, have you got an example you can share?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Richard over 7 years ago

Mike Cichy - Here's the news entry: forum.appian.com/.../e-77531
I've reached out to James, but haven't received a reply from him, is this an update to the shared component "Internationalization Resource Bundle" that you published?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rodgraham
Certified Lead Developer
over 7 years ago

We've created a function that wraps translateforuser - =translateforuser(loggedInUser(),ri!bundle,ri!key) - when calling that function we've a constant (type text) that we use for each bundle. It's the name of the translation file without the language identifier
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Richard over 7 years ago

Yep, that would do it. I'm going to hold off making a change like that until tomorrow. It will be significant work, and though it seems like the right thing to do, I'd also like to know why a file that exists in the document repository / available to download/check-in/check-out/update with new versions is throwing a "not found" and a "nullPointerException" when referenced by the plugin.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rodgraham
Certified Lead Developer
over 7 years ago

What are you translating to? I've also seen if you're translating to a language like Russian with UTF8 characters in it, if there's an error in the codes then the plugin can't read the whole file and uses the last previous cached version
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel