r1686: two suggestions

Hi,
the tab based item management is great, but I would group the absolute necessary information in one tab. Or at least I would combine the tabs General and Categories to be one tab.

Also, why is it not possible to assign a translation to a standard language item? It is only possible editing a non-standard language item. Actually there is also a bug. The popup window to select the translation does not show all categories in the pull down selection menu.

Rooney

actualyu we work on it to produce best storage to concentre on content for user-friendly

Rooney wrote: Hi,
the tab based item management is great, but I would group the absolute necessary information in one tab. Or at least I would combine the tabs General and Categories to be one tab.

hhmm,
- this TAB (categories) also includes TAGS called (categories/tags)
- this TAB (categories) is combined (frontend ) with 'General' when not using single category assignment, you think to combine (FRONTEND) when:

a. using single category with not tags (this is done now)
b. combine when not using TAGS ?
c. always combine categories/TAGs into General
d. use a new parameter to control this ?

Rooney wrote: Also, why is it not possible to assign a translation to a standard language item? It is only possible editing a non-standard language item. Actually there is also a bug. The popup window to select the translation does not show all categories in the pull down selection menu.

Rooney

It had different behavior in a previous version ??

ggppdk wrote: hhmm,
- this TAB (categories) also includes TAGS called (categories/tags)
- this TAB (categories) is combined (frontend ) with 'General' when not using single category assignment, you think to combine (FRONTEND) when:

a. using single category with not tags (this is done now)
b. combine when not using TAGS ?
c. always combine categories/TAGs into General
d. use a new parameter to control this ?

To be honest I am not using frontend editing nor tags. Somebody else has to answer. My point is coming from a usability view. To quickly create an article changing tabs takes time. I also read in another post that an issue might be that an error message appears if not all needed fields are filled in. So putting them in one tab would be a helpful here also.

ggppdk wrote: It had different behavior in a previous version ??

Hmm. I actually don't know. I just found out now. Before I had all articles in German and translated in English. So I created English articles and made associations to German articles. Now I found some German articles that had translations but were not grouped. So I opened the German and wanted to chose the English translation and this did not work.

Rooney

Topic 1:

Rooney wrote: I also read in another post that an issue might be that an error message appears if not all needed fields are filled in. So putting them in one tab would be a helpful here also.

Auto-focusing will focus the TAB that has the required / invalid field and page will be scrolled to it and field label will be made RED

Topic 2:

Rooney wrote: Before I had all articles in German and translated in English. So I created English articles and made associations to German articles. Now I found some German articles that had translations but were not grouped. So I opened the German and wanted to chose the English translation and this did not work.

You cannot associate Content of default language to an original translation because it is the 'original' article. ()

"So I opened the German and wanted to chose the English translation and this did not work."

-- so you need to open article with English translation and associate it to German Article, does this not work?

ggppdk wrote: "So I opened the German and wanted to chose the English translation and this did not work."

-- so you need to open article with English translation and associate it to German Article, does this not work?

Yes, this is working. But what is the original language? On a multi-language page there might be German articles first or English ones or Chinese one that might be translated later in different languages. So there might not be the one original language. Only translation groups.

I am talking about workflow. From a usability point of view it makes no sense that I can not "create" a translation group starting from the original article.

ggppdk wrote: Auto-focusing will focus the TAB that has the required / invalid field and page will be scrolled to it and field label will be made RED

To quickly create an article one minimum needs title, description (if not disabled as a field), at least on category association and clicking the save button. Here I am also talking about workflow and usability. And from this point of view, workflow and usability, it should be in one tab.

Just my two cents...
Rooney