After my initial submission, I have searched again in mojoportal site, and I found the dbo.mp_language table quoted in an article named "Coming Soon - The mojoPortal Store" by Joe Audette:

"I've been doing a lot of re-factoring in the WebStore to get the re-usable pieces built into mojoPortal core so they can be used across features. For example, Country List, State List, Currency List, Language List and their administrative features were originally in the WebStore projects but I've moved them into the core of mojoPortal because they will be needed by other features."

Unfortunately I was not able to find other documentation, and the table seems not to be actually used in mojoportal 2.3.10 (except for its "hidden" administration page).

Please, does anyone know what is this table intended for?

Thanks again

Hi Joe,

thanks a lot for your help!

We did not realized that there was a way to build a custom culture helper http module and to point to it simply editing the we.config file; the other changes to the core that we made during our test (necessary to read the custom key added to web.config file to enable/disable our feature) are useless, since pointing to our custom culture helper http module already expresses the will to use our custom feature.

The new field in the user's profile is managed through the standard  mojoprofile file, so no changes to mojoportal core are required (luckily, since we are aware that touching the core is not a brilliant idea  ).

Just a clarification: we have to create our custom class in the web/components folder (and therefore recompile it in the core dll), or act in a way similar to the one described in the "User Sign In Event Handlers " article?

Regarding to dbo.mp_language table, it seems that your initial intention was quite equal to our: implement a system for having multiple translation of particular DB fields, mainly the "description" of the item;personally, we took the idea of the "active" languages from Dotnetnuke, and of a nice user interface to manage items descriptions from a DNN open source ecommerce module called NevoWeb Store (or NB Store).

As I can understand, the dbo.mp_language table is actually "under development" (and that it might change depending on the development of the web store module): in this case, probably it is better that we implement a similar custom table (with culture entire codes, rather than the first two letters of the language), waiting for possible future implementation in mojoportal standard table.

Thanks again

Riccardo

Hi Joe,

your hint about the implementation of our custom culture helper http module has been very useful, and the solution worked perfectly.

Mojoportal is a great product, and you are very kind and patient.

Thanks a lot again for your help

Riccardo