Joom!Fish for Joomla 1.6

[alex]

Please don't get me wrong - don't you think these various options and alternatives are far to complex to explain and understand for a "normal" user/administrator?

If I read your set of combinations this gets very, very heavy. Now e.g. why do I need to change an article that I set to "all" after I started the translation? What happens if I miss to change the language of this article - is it automatically assumed he is written in the default language?

I understand from what direction you are coming from, but honestly I think this kind of combination thing is far to complex. And this is a reason why I have some many questions related this thing in general.

Alex

[svehex]

I would like the "copy original to language" to start working again. I have a huge site, and many things don't really need a translation, or the translation is so close, that it's better to copy and change.

How far away is 3.0? I hope to upgrade to 1.6 a.s.a.p, but I can't without Joomfish.

[Tohm]

Hello everybody, hello Alex,

I think that you should stick to joomla 1.6 as it will be improved and will evolve anyway (so questions will be the same for next releases of joomla).

The way one can translate articles indepentely in J1.6 is good, the only things lacking are:

1/ A binding table between articles and/or menus
So, case 1: there isn't any correspondance, when changing languages you get the home page (as today with J1.6) or a default page.
case 2: there is a correspondance, you get the bound page.

2/ And, as I already talked about it, for big websites with domain names management, a new router plugin like the router pro you made for joomfish, with the possibililty to switch between domain names or sub-domains.

What do you all of you think about it?

i hope I'm understundable.

Thomas

[progandy]

Hello Alex,
My suggestions really are very complex, and when I think about it, they are too complex. Propably you should just stick to the current Joomfish-bahviour and make a per-article option for "Show untranslated article if no translation available". This should result in a similar behaviour. Then Joomfish won't integrate seamlessly in an already existing page, but the workflow will be easier just as you said.

As an alternative, the ideas of Tohm are not bad, either.

[ivo.apostolov]

The deeper I get in 1.6, the more I am convinced that Joom!Fish should totally ignore the language flag in the core:
1. It is inconsistent (i.e. no field in banners, contacts etc.). Unfortunately it was implemented in a very poor way. I remember the talks 3-4 years ago and it was hard to convince anyone that the core should either support it in each table or not support it at all. What happened is something in between that makes more mess than it solves.
2. I would vote for implementing re-write of classes, so JF would integrate in core extensions deeply.
- Problem 1 here: How to make it working for any extension? Use the different DB way?
- Problem 2 here: What happens if other extension is overwriting the same class (i.e. FlexiContent, jSeblod, Advanced Module Manager)?
3. The more I think, the more I am convinced that changing the database layer approach will solve many issues (however may create new).

[lizhuberx3]

I am looking forward for the release of Joomla 1.6. I think that it should have all the advance feature with simple codes.

[starbucks101]

If you solve one issue you end up creating more imo. Best to get used to working with the 1.6 version.

[alex]

Ok just a note to everybody.

We started with an initial version that will just transfer the features of 2.2 to a Joomla 1.6 compatible format. As the roadmap for 1.7 as well as the Joomla framework 11.1 is now getting a bit more clear we have more confident in the future roadmap and developments.

We will update our roadmap documents soon to reflect the upcoming changes.

- Alex

[alex]

Hi all,

some first impressions can be found here: http://www.joomfish.net/en/blog/29-gera ... 6-progress

Alex

[Chacapamac]

As I'm looking around to get information about Joomla 1.6/1.7 multilingual capabilities. I'm maybe wrong, but I have the impression that Joomla completely ignore that offering a partial capability to translate Joomla site will be disastrous for the Joomla Platforme itself. In this multilingual, multi ethnic world, a so so, half half solution is totally unacceptable for any serious modern web presence and will provoke a huge migration toward other systems that do procure that function.

Me first as a web designer.
I will never offer to my clients a system that will not provide a complete solution on the language.

Remember Joomla that so far, only Joomfish give that ability to Joomla and I hope that the joomla Dev are aware of the crucial part Joomfish play in the Joomla platform success. It seems, with what I see here, that joomla Dev ignore somewhat that fact and that they are going their merry way.

Hopefully Joomfish will come to the rescue and keep Joomla to sink to oblivion as their loyal supporters and users flock to other platform that offer serious complete solutions.

Beware Joomla, be smart. And hope and please support ($) the Joomfish team to help Us All.