Re: workflow with multiple languages

Hi,

I reproduced the problem with the workflow with de-activated languages on
your demo site.

I added the language dutch-belgium, i created a new page (pid 90, called
testLang, title shared with all languages).

Some text containers were added for test purpose.

Then a text container with the title "test met ned" was added, with "share
title" and "share content" checked, english, french and dutch being active
languages. The page was published with success.

Now the dutch language is deactivated. I deleted the "test met
ned" container, the container disappears, but the workflow doesn't go green
no more.

Is this normal behavior?

Regards,

Tom


On 07/03/06, Stéphane Croisier <[email protected]> wrote:
>
> Hi,
>
> Quite strange, because this problem should only occurs if you have a page
> in the language you will desactivate and which is not translated in the
> other language(s) yet. If all the pages in the language you desactivate ARE
> validated at that time (all green pages then you desactivate this language),
> you shouldn't have any problems any more.
>
> So if you experience another problem, we would be glad to know how to redo
> it as we could not reproduce the issue on our test servers (you can just do
> some tests on demo.jahia.org).
>
> Stéphane
>
>
> At 10:05 07.03.2006, you wrote:
>
> Hi,
>
> I'm back on this issue. Our customer is not able to get the workflow green
> for a page, although the checkbox "share title with other languages" for
> that page was checked and workflowed for the disabled language, with this
> language enabled.
>
> Only when enabling this language again the workflow gets green for the
> page.
>
> The customer is really getting anoyed with this workaround, is there
> really no way for us to permanently delete this disabled language?
>
> Regards,
> Tom
>
>
> On 28/02/06, *Serge Huber* <[email protected]> wrote:
>
> Hi Lars,
>
> Yes I understand the bother, but at the same time it is a natural side
> effect of de-activating a language. We used to have a delete-language
> feature, which would have "solved" this problem, but it was very buggy,
> so we removed it until we had the occasion to fix it properly.
>
> But the good news in your client's case is that if the language stays
> deactivated this problem should not re-appear. I had the same case at a
> client's here and they are happy campers now :)
>
> Btw I just love to see screenshots of Jahia in languages I don't
> understand :) Thanks ! It's like a baby that has grown up and surpassed
> you :)
>
> cheers,
> Serge...
>
> [email protected] a écrit :
> > Hi Serge!
> >
> > I understand your explanation.
> >
> > It happend to bother a user and she tried for a couple of hours and
> > did not know what she had done wrong and the reason was some old page
> > in a language we activated just for test purposes long ago (during
> > development). She had the feeling that the changes her boss wanted her
> > to publish was not visible until she got the green dot.
> >
> > Later on she called me and I did some magic things (the procedure I
> > mentioned) and tried to explain but "users are on different levels"
> > when it comes to understand the pros and cons (is it "by design" or
> > "bug"?).
> >
> > Regards
> > /Lars
> >
> >
>
>
>