1) an editor person here was adding an article using Actions -> Add
new article
and the system forces to put name, language and then Publication and
Issue.
The editor didn't put the section though and it was accepted and she
made an article saved it and it could be seen (by other user codes)
via the Recently Published articles.
The editor who added the article anyhow got kind of blocked by seen
only the top menu and the navigation including "Recently Published
Articles" on the left but when clicking that nothing appeared. When I
removed - using other user codes - the article without a section away,
then the original user could use the system as well again.
2) Then the user added a new section for the system (in English) that
she could make a new article (in Swedish) and of course couldn't see
the new section as selectable when trying to make a new article. I
guided to make the new section to Swedish language first that she
could see the section name when adding the article. The sections are
used as "company" names that are the customers of this news agency.
The problem is that since English had already this section number in
usage that was the next one to be taken into usage in Swedish, so now
the article list is showing mixed section info: including the two
different section name articles from Swedish and from English. So,
there should be only one Company (section) listed but now it comes to
the same article list another company from English part and another
from Swedish.
Meaning that the original article in Swedish:
.../sv_SE/100/846/1957/
gives in the end-user side the translation for this article in English
(even though it doesn't have it),
because the address
.../en_UK/100/846/
exists (even though the article number doesn't).
How could we avoid that the system wouldn't give the same section
number for the other language for the other usage (in this case for
other company)? This breakes the translation chain of languages.
The news angency doesn't have always the same default language as
origin, although it is very often English but this time would be
Swedish.
The editor would not have been able to publish the article if the section
was not specified.
"How could we avoid that the system wouldn't give the same section number
for the other language for the other usage (in this case for other company)?
This breakes the translation chain of languages."
I'll implement a fix in 3.3.4. For now you'll have to make sure the section
number was not already in use in another translation.
Please delete the new section you created and recreate it with a new number,
otherwise the article display issue won't be fixed.
Mugur
On Mon, Nov 9, 2009 at 4:40 PM, Generare Management Department < management@generare.com> wrote:
> Hi,
>
> 1) an editor person here was adding an article using Actions -> Add new
> article
> and the system forces to put name, language and then Publication and Issue.
> The editor didn't put the section though and it was accepted and she made
> an article saved it and it could be seen (by other user codes) via the
> Recently Published articles.
>
> The editor who added the article anyhow got kind of blocked by seen only
> the top menu and the navigation including "Recently Published Articles" on
> the left but when clicking that nothing appeared. When I removed - using
> other user codes - the article without a section away, then the original
> user could use the system as well again.
>
> 2) Then the user added a new section for the system (in English) that she
> could make a new article (in Swedish) and of course couldn't see the new
> section as selectable when trying to make a new article. I guided to make
> the new section to Swedish language first that she could see the section
> name when adding the article. The sections are used as "company" names that
> are the customers of this news agency. The problem is that since English had
> already this section number in usage that was the next one to be taken into
> usage in Swedish, so now the article list is showing mixed section info:
> including the two different section name articles from Swedish and from
> English. So, there should be only one Company (section) listed but now it
> comes to the same article list another company from English part and another
> from Swedish.
>
> Meaning that the original article in Swedish:
> .../sv_SE/100/846/1957/
>
> gives in the end-user side the translation for this article in English
> (even though it doesn't have it),
> because the address
> .../en_UK/100/846/
> exists (even though the article number doesn't).
>
> How could we avoid that the system wouldn't give the same section number
> for the other language for the other usage (in this case for other company)?
> This breakes the translation chain of languages.
>
> The news angency doesn't have always the same default language as origin,
> although it is very often English but this time would be Swedish.
>
> Sanna @ Gene
>
>
>
Oh dear, I hope we do not have a mess here then because we have 14
different languages currently!
What about if I try to change that in the database directly? Which
tables it affects to?
The new section has also content already now (although it gives only
partly visible what it has and other articles, non-related as its
translations). But I think if we just correct this new section number
in all places than it is needed in the database, like tables
"Articles", "Section"... any other?
Sanna @ Gene
On 10.11.2009, at 20.07, Mugur Rus wrote:
> The editor would not have been able to publish the article if the
> section was not specified.
>
> "How could we avoid that the system wouldn't give the same section
> number for the other language for the other usage (in this case for
> other company)? This breakes the translation chain of languages."
> I'll implement a fix in 3.3.4. For now you'll have to make sure the
> section number was not already in use in another translation.
>
> Please delete the new section you created and recreate it with a new
> number, otherwise the article display issue won't be fixed.
>
> Mugur
>
> On Mon, Nov 9, 2009 at 4:40 PM, Generare Management Department
> > wrote:
> Hi,
>
> 1) an editor person here was adding an article using Actions -> Add
> new article
> and the system forces to put name, language and then Publication and
> Issue.
> The editor didn't put the section though and it was accepted and she
> made an article saved it and it could be seen (by other user codes)
> via the Recently Published articles.
>
> The editor who added the article anyhow got kind of blocked by seen
> only the top menu and the navigation including "Recently Published
> Articles" on the left but when clicking that nothing appeared. When
> I removed - using other user codes - the article without a section
> away, then the original user could use the system as well again.
>
> 2) Then the user added a new section for the system (in English)
> that she could make a new article (in Swedish) and of course
> couldn't see the new section as selectable when trying to make a new
> article. I guided to make the new section to Swedish language first
> that she could see the section name when adding the article. The
> sections are used as "company" names that are the customers of this
> news agency. The problem is that since English had already this
> section number in usage that was the next one to be taken into usage
> in Swedish, so now the article list is showing mixed section info:
> including the two different section name articles from Swedish and
> from English. So, there should be only one Company (section) listed
> but now it comes to the same article list another company from
> English part and another from Swedish.
>
> Meaning that the original article in Swedish:
> .../sv_SE/100/846/1957/
>
> gives in the end-user side the translation for this article in
> English (even though it doesn't have it),
> because the address
> .../en_UK/100/846/
> exists (even though the article number doesn't).
>
> How could we avoid that the system wouldn't give the same section
> number for the other language for the other usage (in this case for
> other company)? This breakes the translation chain of languages.
>
> The news angency doesn't have always the same default language as
> origin, although it is very often English but this time would be
> Swedish.
>
> Sanna @ Gene
>
I strongly suggest to backup your database before running the following SQL
commands:
1. UPDATE ArticleIndex SET NrSection =
WHERE IdPublication =
AND IdLanguage =
AND NrIssue =
AND NrSection =
2. UPDATE Articles SET NrSection =
WHERE IdPublication =
AND IdLanguage =
AND NrIssue =
AND NrSection =
3. UPDATE Sections SET Number =
WHERE IdPublication =
AND IdLanguage =
AND NrIssue =
AND Number =
Replace the <..> sequences with the proper numbers.
Now you must reset the cache. Hope this helps.
Mugur
On Tue, Nov 10, 2009 at 10:18 PM, Generare Management Department < management@generare.com> wrote:
> Oh dear, I hope we do not have a mess here then because we have 14
> different languages currently!
> What about if I try to change that in the database directly? Which tables
> it affects to?
>
> The new section has also content already now (although it gives only partly
> visible what it has and other articles, non-related as its translations).
> But I think if we just correct this new section number in all places than it
> is needed in the database, like tables "Articles", "Section"... any other?
>
> Sanna @ Gene
>
> On 10.11.2009, at 20.07, Mugur Rus wrote:
>
> The editor would not have been able to publish the article if the section
> was not specified.
>
> "How could we avoid that the system wouldn't give the same section number
> for the other language for the other usage (in this case for other company)?
> This breakes the translation chain of languages."
> I'll implement a fix in 3.3.4. For now you'll have to make sure the section
> number was not already in use in another translation.
>
> Please delete the new section you created and recreate it with a new
> number, otherwise the article display issue won't be fixed.
>
> Mugur
>
> On Mon, Nov 9, 2009 at 4:40 PM, Generare Management Department <
> management@generare.com> wrote:
>
>> Hi,
>>
>> 1) an editor person here was adding an article using Actions -> Add new
>> article
>> and the system forces to put name, language and then Publication and
>> Issue.
>> The editor didn't put the section though and it was accepted and she made
>> an article saved it and it could be seen (by other user codes) via the
>> Recently Published articles.
>>
>> The editor who added the article anyhow got kind of blocked by seen only
>> the top menu and the navigation including "Recently Published Articles" on
>> the left but when clicking that nothing appeared. When I removed - using
>> other user codes - the article without a section away, then the original
>> user could use the system as well again.
>>
>> 2) Then the user added a new section for the system (in English) that she
>> could make a new article (in Swedish) and of course couldn't see the new
>> section as selectable when trying to make a new article. I guided to make
>> the new section to Swedish language first that she could see the section
>> name when adding the article. The sections are used as "company" names that
>> are the customers of this news agency. The problem is that since English had
>> already this section number in usage that was the next one to be taken into
>> usage in Swedish, so now the article list is showing mixed section info:
>> including the two different section name articles from Swedish and from
>> English. So, there should be only one Company (section) listed but now it
>> comes to the same article list another company from English part and another
>> from Swedish.
>>
>> Meaning that the original article in Swedish:
>> .../sv_SE/100/846/1957/
>>
>> gives in the end-user side the translation for this article in English
>> (even though it doesn't have it),
>> because the address
>> .../en_UK/100/846/
>> exists (even though the article number doesn't).
>>
>> How could we avoid that the system wouldn't give the same section number
>> for the other language for the other usage (in this case for other company)?
>> This breakes the translation chain of languages.
>>
>> The news angency doesn't have always the same default language as origin,
>> although it is very often English but this time would be Swedish.
>>
>> Sanna @ Gene
>>
>>
>
>
>
>