Joomla! Discussion Forums

Thanks. I have exactly the same problem (exept that "Translation incomplete or original changed" shows up when editing back end, but it works). I am using 1.0.5.

Just reverted to 1.0.5 but I still experience the same problem in the front end. It keeps overwriting the original content i.s.o. the translation. >:(

EDIT>
It seems that the lang=en or other language parameters  is gone in all my URLs. Weird
MBF is properly initialized since the language switcher is OK and is the only one with a lang=en parameter.

I'm looking into this.  Translation seems ok from the administrator interface - agreed?

Geraint

Agreed, back end not any problems.
Just switched back to 1.0.7 because of missing lang= parm in 1.0.5.
But now I'm getting that problem too.
SEO off.
No cache.

I think I'm getting closer. 

The problem arises in PHP 5.1 but NOT in 4.4 (don't have easy access to 5.0).

Its probably a reference problem similar to the gettable function (ARGH!!).

@walb Can you confirm your setup?  Are you able to test in another config?

Geraint

Setup:
PHP built On:  Windows NT WE71528 5.1 build 2600
Database Version: 4.1.8-nt-log
PHP Version: 4.3.11
Web Server: Apache/2.0.52 (Win32) PHP/4.3.11
WebServer to PHP interface: apache2handler
Joomla! Version: Joomla! 1.0.7 Stable [ Sunburst ] 15-Jan-2006 20:00 UTC

Is a normal setup which worked before.

Maybe I'm looking at the wrong side, but with SEO on I see the lang parm properly displayed in the URLs. SEO off not.  ???

EDIT>
more observations:
Default language site $mosConfig_lang = 'english'; (Configuration.php)
Wiith lang=en it updates the original content and displays the english translation... To me in that case the english translation should be updated.
Switching to dutch updates the related translated content and displays it on the site

Summary:
SEO problem
Behaviour of translation in relation to the default language.

With
PHP built On:  Linux black 2.6.14-gentoo-r5 #3 SMP Sun Jan 15 11:55:10 GMT 2006 x86_64
Database Version:  4.1.14-log
PHP Version: 4.4.1-pl3-gentoo
Web Server: Apache
WebServer to PHP interface: cgi-fcgi

default lang = english. second lang = welsh.

It all work ok.  In other words:

Take content originally in english.  switch to welsh in front end, translate, save, publish (from back end  ).  Translation works fine.  The process works with SEO on or off.

If I edit the original english content with lang=en - the original is changed, translation untouched.

If I add something (via submit news) in welsh it appears as an unpublished translation.  If I edit this with lang=en and save the content, it becomes english but I still have an unpublished translation into welsh.

@walb? Is this not what you'd expect?

Hmm. For the moment I must assume that SEO  is a local problem on my site. The ghost lang parm.

About translations and my expectations.
As far as I understand the package.
The original content could have a translation or not.
In my parameter setting if translation is not avail show the original content.

My default is english, second dutch
I made a dutch translation. That seems to work if I update that in the frontend and it will display it subsequently correct.
However if I have an english translation too. It displays the translation, but any update is made to the original and only the translation was displayed. So I never see the update anymore unless I delete that translation from MBF.
Hmm. That might be confusing to ppl.

As far as I experienced, the process was rather simple. Check for a translation, grab it and display or edit it.

Plse correct me if I'm wrong.

BTW. I hardly translate in the frontend, since I feel I've better control over MBF in the backend. But for others that might not be possible.

Are you using the builltin SEO?  Do you not see the lang param at all or just on some links?



My exact understanding of the original package is comewhat clouded by the extensive modifications I made (and use in general) - e.g. dealing with not being able to publish from the front end even if you were Giod himself.

The complication arises if you have an english translation of english original content - it appears that you can only set this up in the backend.



Did you try republishing the translation in the backend or was that overwritten by the frontend?

Geraint

p.s. I found that PHP 5.1.1 will require the liveral use of clone($someobj) to work properly.

[modified to use correct form of clone function]

[quote=∓quot;Geraint"\]
Are you using the builltin SEO?  Do you not see the lang param at all or just on some links?[/quote]Yep, builtin SEO.
[quote=∓quot;Geraint"\]
My exact understanding of the original package is comewhat clouded by the extensive modifications I made (and use in general) - e.g. dealing with not being able to publish from the front end even if you were Giod himself.[/quote]I don't think you're clouded, but I'm just thinking about the ppl who are using MBF. Reading all the problems also in mambo I think front end is essential if you have more content editors.
[quote=∓quot;Geraint"\]
The complication arises if you have an english translation of english original content - it appears that you can only set this up in the backend.[/quote]I think so, but maybe I need somewhat more checking on the exact behaviour of MBF. It is a bit confusing in that area and certainly not intuitive.
[quote=∓quot;Geraint"\]
[quote=∓quot;walb"\]
My default is english, second dutch
I made a dutch translation. That seems to work if I update that in the frontend and it will display it subsequently correct.
However if I have an english translation too. It displays the translation, but any update is made to the original and only the translation was displayed. So I never see the update anymore unless I delete that translation from MBF.
Hmm. That might be confusing to ppl.
[/quote]Did you try republishing the translation in the backend or was that overwritten by the frontend?[/quote]I was only working in the frontend and republishing was not necessary (checked it in the backend!). In the backend I can manipulate MBF without problems. The English original was overwritten and not the English translation. The Dutch translation was overwrtten, the latter sounds logical to me.

So far my observations.

PS. Wales, very nice! Been there. But I'm still wrestling with the pronounciation of this word:
Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch
Llangollen. I'll manage.

For people how use PHP above 4.4.1
http://www.mademyday.de/Joomla!/Tipps-T ... ckfix.html
Change    -->      function getTable() {        with        function &getTable() {

Remember to update your PHP:
http://www.php.net/release_4_4_2.php


Thanx.

Hi!

Excellent work, i just installed your mabelfish files and everythig is working cool

I just created a contentelement file for bookmarks.




  Bookmarks
  info@open-antz.com
  1.0
  Definition for Bookmarks
 
 
  ID
  Title
  Description
  Detail
  Created
  Modified
  Check out by
  Check out date
 
 



I can translate the fields of com_bookmarks in the back-end but in the front-end the swith doesnt work with this component.

Any help is welcome!
Thanx.

So does someone have a hack which gets front end translating work? Or any idea when someone fixes it? 


(In 1.0.5 or 1.0.7)

@josoroma - thanks, the getTable fix is already included in the packages at the start of this topic.

Are you saying you can translate other content types from the frontend and not bookmarks or non-at all?  You are making sure the translation is published (which must be done the first time in the backend)?

Can I confirm that you have published the translation in the backend - this is needed for the first translation.  Thereafter changes in the front end are actived.

I am not seeing any problems with my fresh install of 1.0.7 with PHP 4.4.1.

I don't think you're clouded, but I'm just thinking about the ppl who are using MBF. Reading all the problems also in mambo I think front end is essential if you have more content editors.
[/quote]
I agree that front end translation is essential - in fact I believe that publishers and ablve should be able to publish from the frontend (maybe an admin configurable choice).  At present the first translation must be published from the backend regardless of who makes it - if this translation is published in the backend, further translations are published by the frontend.
I think so, but maybe I need somewhat more checking on the exact behaviour of MBF. It is a bit confusing in that area and certainly not intuitive.
[/quote]
See above
[quote=∓quot;walb"\]
[quote=∓quot;Geraint"\]
[quote=∓quot;walb"\]
My default is english, second dutch
I made a dutch translation. That seems to work if I update that in the frontend and it will display it subsequently correct.
However if I have an english translation too. It displays the translation, but any update is made to the original and only the translation was displayed. So I never see the update anymore unless I delete that translation from MBF.
Hmm. That might be confusing to ppl.
[/quote]Did you try republishing the translation in the backend or was that overwritten by the frontend?[/quote]I was only working in the frontend and republishing was not necessary (checked it in the backend!). In the backend I can manipulate MBF without problems. The English original was overwritten and not the English translation. The Dutch translation was overwrtten, the latter sounds logical to me.
[/quote]

So - apart from the behaviour of the English translation of English content, am I correct in saying that front end translating is working ok?

[quote=∓quot;walb"\]
PS. Wales, very nice! Been there. But I'm still wrestling with the pronounciation of this word:
Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch
Llangollen. I'll manage.
[/quote]
p.s. I live about 15km from Llangollen

@vsync
I get the content translated in the frontend with a few remarks.
The original content with the default language of the site as stated in in the configuration.php i.e $mosConfig_lang = 'english'; for english.
If you modify that the original content will be replaced if you are language sitched to english.

If you make a translation in the not default language e.g. dutch (my site by coincidence) it will make a trnaslation or update an existing translation of that content. If it is a new translation you need to publish that translation in the backend.
But after that it should be displayed correctly and after that in dutch mode any update is made thru MBF in the frontend should be applied only to the translation.

In the default (english) mode it will only change the origianl content. Now comes the confusing part.
If you made an english translation in the backend. MBF will only  display the english translation and not the original content, but it can be seen in the backend. My advise would be delete any english translation, since it confuses.

Could you confirm this behaviour?

I am using php 5.0.5. Like I said I have published the translation in the backend. When I try to edit the translation in my frontend and save it (I just change the language to english (not the default language) and push edit-icon) it replaces the translation in my default languages contents.

{modified : This is incorrect see : http://forum.joomla.org/index.php/topic ... #msg178470}

I dont have 5.05 to test with but did test 5.1 and found I needed a slight modification to "function updateMLContent" in administratori\components\com_mambelfish\mambelfish.class.php.  I didn't think it would be necessary before 5.1 but you could try it.

replace

with


Please let me know how you get on.

@Geraint

Thanks! 
It works like a dream!

(But still you have to publish the translation in backend, that is problem with news. I can publish other content to my client beforehand. But now the major problem is fixed. )

[quote=∓quot;Geraint"\]
I agree that front end translation is essential - in fact I believe that publishers and ablve should be able to publish from the frontend (maybe an admin configurable choice).  At present the first translation must be published from the backend regardless of who makes it - if this translation is published in the backend, further translations are published by the frontend.[/quote]
Yes publishing in the frontend is a much asked feature! You hit the hammer right on the nail.

[quote=∓quot;Geraint"\]
So - apart from the behaviour of the English translation of English content, am I correct in saying that front end translating is working ok?
[/quote]
Yeah I think so at least at my site. Just keepng this oddities in mind.

Now I need to sort out where my lang=nl or en is gone in non SEF mode. It is not a disaster since the language seems to be maintained well by the MBF cookie.

In the olden days a modification to sef was required to force sefRelToAbs to take account of lang.  It may be worth revisiting that.

Geraint

Yes and today it is still true. I'm already investigating that sef.php and the mbf_content check is in there, but maybe something went wrong.
I'll put some echo's in it to see what happens. :)
In 1.1 it's moved to a bot (oops plugin).

EDIT> Problem solved.
I thought I did deinstall Xeneon Extensions long ago, but not so. It did mask sefRelToAbs 
Now it works again, with or without SEF.

Deleted default translations (english) and everything works normal again in front & back end.

Thanks

I can translate content, weblinks, menus, and the other default contentelements. And also i can translate com_bookmarks, but in the front-end when i switch from language to other everything is translated, except com_bookmarks contents.

I installed the component bookmarks, then i create a contentelement file for this component, and yes, the translations is published:



  Bookmarks
  info@open-antz.com
  1.0
  Definition for Bookmarks
 
   
        ID
        Title
        Description
        Detail
        Created
        Modified
        Check out by
        Check out date
   
 



Thanks.

I would like to ask you about something
Could you in you first post when you put info about joomla's version write some changelog if there is something new from last relase?

Yes - sorry.  There's no point trawling though all the dialog to identify the changes.

The only thing that's changed since the first versions is a slightly modified initialisation mambot (so as not to recreate the $database if tere is no neede to do so).

Geraint

The original response was incorrect you should change the code as follows if you are using php5+

Sorry about any confusion

Hi, thanks for this definitive guide! Everything installed perfectly.
I'm adding a german translation to my dutch site (1.0.7). But when I use the search-function, no results turn up for the german content 
I did published the module and mambots...

And another question: When Joomfish is released, will it be compatible with mambelfish?

Great!

If you say you published the search mambot then there may be a problem to investigate.  Can you tell me your setup  (first few lines from system/info from the adminitrator.



Everyone, including Alex the main developer, will want a seamless transfer of settings and existing translations from mambelfish to joomfish.