TAPevents / tap-i18n-db

MIT License
51 stars 17 forks source link

insert failed: TAPi18n is not supported #26

Open seanmiddaugh opened 8 years ago

seanmiddaugh commented 8 years ago

I put together a demo project the other day and things were working. Today, I decided to implement tap-i18n-db into my core project and when trying to seed the database with:

Interests.insertTranslations({slug: "ball-hockey", name: "Ball Hockey"});

I'm getting the error:

insert failed: TAPi18n is not supported

I have no idea what's causing this. I'm following the docs. Any ideas?

samuelluis commented 8 years ago

Same problem here

samuelluis commented 8 years ago

In my case it works updating tap-i18n and tap-i18n-db to the latest version, 1.8.0 and 0.4.0 respectively.

louis49 commented 8 years ago

+1

teddymeksavanh commented 8 years ago

+1

maevaD commented 8 years ago

+1

AdrienDesola commented 8 years ago

+1

R0binT commented 8 years ago

+1337

lucasprag commented 7 years ago

+1

ibihim commented 7 years ago

-1

does not work. even tried to downgrade from 1.8.2, still not working

thesmooth commented 7 years ago

+1 The same problem

LiFuPing commented 7 years ago

+1

mahfuzmohammad commented 7 years ago

Hi, I had the similar problem but I made it work. Here I will try to explain the reason and the solution of the problem. Basically this is an issue of project settings.

I am using tap:i18n@1.8.2 and tap:i18n-db@0.4.0

Why this problem occurs? If you check the codes in tap_i18n_db-common.coffee there are two functions verifyI18nEnabled and isSupportedLanguage who check TAPi18n._enabled() and TAPi18n.conf.supported_languages. When I created an empty project TAPi18n._enabled() returned false and TAPi18n.conf.supported_languages was null.

Solution (how it worked for me) Step 1: I created i18n folder in the project's top directory and created a language file en.i18n.json. Now TAPi18n._enabled() returned true and the error insert failed: TAPi18n is not supported was gone. But there arise another problem. When I insert a translation, nothing was generated in db and the returned id was null. I found that TAPi18n.conf.supported_languages was null.

Step 2: I created another file in the project's top directory project-tap.i18n and added the following lines:

{
    "supported_languages": ["en",  "zh", "ru"]
}

Here I used English, Chinese, and Russian as supported languages but your ones might be different based on your need. Note: If your desired language for translation is not listed in this file you CAN NOT insert the translation in the db.

Summary: You need to have i18n folder with at least one language file in it and set supported languages in project-tap.i18n file.

Hope it helps. Cheers!

ahmb84 commented 7 years ago

Hello, I've the same problem. I've ever created i18n folder with en.i18n.json file inside and project-tap.i18n file in my project's top directory. I am using tap:i18n@1.8.2 and tap:i18n-db@0.4.0 and METEOR@1.4.4.1 I think the problem is tap:18n-db doesn't support METEOR@1.4.4.1. Also I work on Linux Mint 18.1 Serena. Thanks.

aadamsx commented 5 years ago

Did anyone get this working besides @mahfuzmohammad ? Does this lib work with Meteor 1.8?