My multi-content solution is ready to be tested... who wants to test?

Here I am (not @ home for some time)... I am still working on my solution, simply because I NEED it on my website ... I am sure that there is the need of a core modification, in order to make it simpler for the webmaster to add translations...

the problem is with existing snippet/plugin/etc, as wendy says: I am working on it (working on avoiding to have to rewrite all snippet/plugin/etc :-D)

the only core modification are in manager code in order to manage the two new database fields... document parsing, redirecting, etc is done by plug-ins and snippets

I think that in a week I will release a beta version (better than the "demo" on my website... I think currently not working :-D)

"Some weeks are longer, but sometimes it’s stronger."
(french joke nearly bedtime)

Just another wish perhaps: the message alert could better be in a css class instead of this:

<div style="font-weight: bold; color: red;">We are sorry, but there is no translation in language fr for this page, you have been redirected to the default language (en) translation of this page</div>

Good night and good luck

Quote from: madmage at Jan 19, 2006, 04:39 PM

I think that in a week I will release a beta version (better than the "demo" on my website... I think currently not working :-D)

This is COOL !
I love your solution, it’s great.

I’ll gladly test the beta

Quote from: madmage at Jan 19, 2006, 04:39 PM

I think that in a week I will release a beta version (better than the "demo" on my website... I think currently not working :-D)

Madmage, following up on this : any update ?

Thanks !

I have a question here. The only concern of having subfolders in maintaining document translation will be the ability of directing user to the default language folder, when the translation is not available for that page, right? Other than that, maintaining to identical folder with different languages will not be a major problem, am I right? Is there any other major concern? Do we need localization? Can’t we just use different snippets/chunks/templates for the other language? Any thought of having this as a plugin?

Honestly, this multi language solution is really tricky, and I always found a stumbling wall, everytime I thought I found the right/best solution to use.

Any thought on my question will be great.

Wendy, I see you have ideas regarding the multilingual solution... did you have a chat with madmage ? I can’t seem to find him on the board this past two months, with is too bad since his solution was really exciting !

If nobody has heard of him, I’ll PM him about this...

Yeap, I did make a contact to him, but before going any further with it, we found out that it might not working with most of the current snippets that we have, especially the one that deal with document tree right from the database.

The last time I talked to him, it seems that he’s going to look into this further, since few months ago as well.

okay thanks for the input... that’s too bad that there are some problems with his solution... I kind of like the path he started taking with this...

Quote from: davidm at Feb 25, 2006, 05:20 PM

okay thanks for the input... that’s too bad that there are some problems with his solution... I kind of like the path he started taking with this...

To clarify it, we haven’t test it out yet, but I’m assuming the changes in the doc tree db structure will affect some of the snippets that are accessing the database directly without changing it to meet with the new multi language solution.

Quote from: madmage at Jan 19, 2006, 04:39 PM

Here I am (not @ home for some time)... I am still working on my solution, simply because I NEED it on my website ... I am sure that there is the need of a core modification, in order to make it simpler for the webmaster to add translations...

the problem is with existing snippet/plugin/etc, as wendy says: I am working on it (working on avoiding to have to rewrite all snippet/plugin/etc :-D)

the only core modification are in manager code in order to manage the two new database fields... document parsing, redirecting, etc is done by plug-ins and snippets

I think that in a week I will release a beta version (better than the "demo" on my website... I think currently not working :-D)

Any progress here madmage?

Also, should we seriously consider using this or a similar implementation for MODx multiple language sites by default in the manager? I would like to have this addressed much sooner than later. (Jason, see any problems in porting madmages’s solution to the contexts/versions in Tattoo?)