Default HOME as unique #122

Closed
alainroger opened this Issue Jan 15, 2013 · 7 comments

Comments

Projects
None yet
3 participants

Hi Everybody,

once again this topic is here. In latest version of JF-Future downloaded yesterday i have the same issue, when several languages are used...HOME isnot anymore unique and can't be saved in case of modification of home parameters :(
see issue #33

Member

klas commented Jan 15, 2013

Please try this revision https://github.com/JoomFish/jf-future/tree/2553533bd30c0820560f0fc5a0836eb5ecb537ef

My guess is contentelement loading could be broken after https://github.com/JoomFish/jf-future/commit/71c1e9bbd398cb1877dcc734a59b9707187164b5 and since necessary functions to work around menu issue are not executed

Is it an older version than the existing one or a newer ?

Member

klas commented Jan 16, 2013

This is few revisions older than the last one

2013/1/16 alainroger notifications@github.com

Is it an older version than the existing one or a newer ?


Reply to this email directly or view it on GitHubhttps://github.com/JoomFish/jf-future/issues/122#issuecomment-12325915.

Owner

akempkens commented Jan 16, 2013

Klas, what part of the content element loading do you think is broken? The change is related to loading different translation object classes. The loader still loads the rights classes.

Member

klas commented Jan 16, 2013

can't test from where I am at the moment so this is just a guess, it could be that translaltionObjectMenu is not properly loaded and since unsetHomeTr is not run which would cause this error. Relates to transaltionObject subclasses loading, not content element itself.

Owner

akempkens commented Jan 17, 2013

Ok I was able to debug that during the translation process the preHandler is called. The class is loaded correctly.

However during my investigations so far I figured out that the update of language information within the original table rows (the one you translate) seem to get out of synch. At least what the Joomla interface is showing. Even so a translation exists the Home menu still shows it is "default" and for "all" languages.

As soon as you edit the menu it switches to English only and starting at this point the described issues appear. I feel some more investigations are needed.

Member

klas commented Jan 17, 2013

ok, this is a different issue than #33 - tha one was about traslations, transaltions still work if done in joomfish. The one that does not work is original item editing.

@klas klas closed this in d9134a1 Jan 17, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment