I will do a PR against your branch next week to make the language files correct english.

Can you please change the qn to quotename etc

@bembelimen can you fix the conflict files here, for test it?

I tried to test this and on apply the database changes I got

"1101 BLOB, TEXT, GEOMETRY or JSON column 'description' can't have a default value"

Having two columns with states (states and 0) is confusing and probably not needed

I would remove the second one (0) and at the same time give the transitions column a name and not just an icon

The workflows, transitions and states should have "Names" not "Titles"

COM_WORKFLOW_TITLE="Title"
==>
COM_WORKFLOW_TITLE="Name"

On a new item there is no visible state - this is confusing and unexpected. For me a new article should have a state displayed and this should be the default for that user

It is confusing that sometimes you write State and sometimes you wrote Status

I dont find using the state icon to open the select list to be intuitive. Maybe its just me. Maybe it should either not display the text until the select is displayed OR it should always display the select. A better UX than me can advise ;)

Has this been abandoned?

No? There will be some updates this months.

It would be great if the merge conflicts could be resolved so that we can test the latest changes

We're working on it. We have to rebuild the implementation of com_content

@brianteeman we have here two different things with the same wording:

1. The "Status" which representate the status of the current viewed item (like a banner is published, a workflow itself is unpublished etc.)
2. The "States" which are the new "layer" in the workflow, where you define your workflow states

I would like to have the 2nd one completly renamed into something "unique" which don't leads to confusion ("All states have a status" e.g.)

Is there any good English term which describes the functionality of "States" without confusion with "Status"?

I agree 100% with your observation about the similarity and confusion of using status and states although they are technically the correct terms

I will take a look at what others do in this case

I am still getting my head around it but

The "States" which are the new "layer" in the workflow, where you define your workflow states

Could that be stages?
eg
Stage 1 create content
Stage 2 review content
Stage 3 Publish content

I'm going to merge this to push this forward as there are issues keeping this in sync. There's clearly several issues still to work out but people can create PRs as they go

For the record I dont agree with this being merged in its current state and would like to see it reverted and instead of being on a personal repo moved to a joomla-projects repo like all the others and then issues can be worked on there.

This is nowhere near mergeable

This PR has totally broken a new clean 4.0 installation when trying to create articles.
500 'v40_multi.wa.state_id' isn't in GROUP BY

0 Argument 1 passed to Joomla\Utilities\ArrayHelpergetColumn() must be of the type array, boolean given, called in /Applications/MAMP/htdocs/installmulti/joomla40/administrator/components/com_content/Model/ArticlesModel.php on line 483

• no postgresql

@infograf768 similar #21474

@franz-wohlkoenig

As I have done a fully clean install from 4.0-dev, the new tables exist here.
Issue is in code.

a nightly didn't work so a clean Install is better?

My issue above is when using multilang.
Creating an issue now

See #21475

Sorry but this is way beyond not ready it is not correct #21476

Please open new issues or pull requests regarding the new workflow feature. This pr got merged and all comments will likely get forgotten.

ok will do, but ......

Please open new issues or pull requests regarding the new workflow feature. This pr got merged and all comments will likely get forgotten.