plugin language dont work

Got PM - thanks.

First error:

Fatal error: Class 'JModel' not found in /home/eu000038/public_html/modules/mod_jabulletin/helper.php on line 16

So I unpublished the 2 modules you had with this.

Now I can at least look at user profiles from frontend.


I installed the test english cbcsubs plugin (see previous reply I gave) and switched your default site language to English.

As you can see your subscription tab is picking up the english translation just fine and showing:

!Your current Suscripción upgrade possibilities:

As you can see the ! shows that it is picking up the language string just fine.

So something is wrong with your language plugin.

nant wrote:
So something is wrong with your language plugin.

Yes, something is wrong with my language plugin :woohoo:

Could you tell me how can i fix it?

I need CB and CBSubs in spanish.

Did you try to install the spanish plugin?

If i put english like default into the lenguage manager:

dont read the CB spanish plugin

If i put spanish like default into the lenguage manager:

dont read the CBSubs spanish plugin

what happens does not make sense :pinch:

Could someone put me CB and CBSubs in Spanish?

Ok, I see whats wrong now.

Please edit your es-ES.xml language files located in your root -> languages -> es-ES and in your root -> administrator -> languages -> es-ES and modify the last name tag almost at the end of these files to show:

<metadata>
<name>Spanish</name>

instead of <metadata>
<name>Español (España)</name>


Then follow instructions for creating you CBSubs language file (as described in the CBSubs manual) and use the word Spanish instead of English.

Aleluya Aleluya Aleluya...

Everithing is in Spanish!!!

Thank you Nick!!!

I am very happy!!!

:silly: :lol: :silly: :lol: :silly: :lol: :silly: :lol: :silly: :lol: :silly: :lol: :silly: :lol:

You are welcome.

Hope you can share your CBSubs Spanish plugin with the rest of the Spanish CBSubs users.

We will be addressing these special language cases in next CBSubs release so things are immune to such name tag issues (actually solution is to use the tag value instead of the name).