I can reproduce the issue without API. title column in #__assets table has 100 character limit. In J3 longer titles were truncated and in J4 the entry is not created.

I am not sure what you are expecting. You tried to submit an article with a title that was too long and correctly received a message that it could not be saved as the title was too long. When you submitted an article with a title that was short enough then the article was saved.

So the publish part is kinda a known issue - I’m not even 100% if it’s a bug. This is how workflows functions right now. State is effectively read only as a property - we’d need to update the workflow_id property.
I’ve written that up a bit more here #26841

or simply drop workflow as it is not ready

@alikon I will repeat what I said in Spain. If you believe that it is not ready then where are the issues reported that make that clear. Everything I see is relatively easy to fix.

#24536
#21702 (comment)

it's bad design it is not a https://en.wikipedia.org/wiki/Finite-state_machine as it should be
and + simply use what it already used and tested like https://symfony.com/doc/current/workflow/workflow-and-state-machine.html

• don't reinvent all the time the whell

• https://volunteers.joomla.org/teams/workflow-project-team what they have done ?

such a shame that this wasnt mentioned when it was submitted and then merged. I was the only one really saying it wasn't ready etc

it was , till someone blocked the discussion

This conversation has been locked as resolved and limited to collaborators.

where?

#20381
#21476 (comment)
#21476 (comment)

thanks - I was missing the locked one.

18 months since I said it wasn't ready and should be reverted then. A lot of work was done on it since then.

My point is that other than my closed call for it to be reverted there hasnt been any further discussion in 18 months

yes a lot of work has been done (after) to let it barely working, but my main concern it's about the performance of a real site with more than 100 articles, plus a team was setup to create an enhanced version before beta iirc (so it was clear from the start that wasn't ready)

I can reproduce the issue without API. title column in #__assets table has 100 character limit. In J3 longer titles were truncated and in J4 the entry is not created.

Yes, but title column in #__content table has 255 character limit...

Also if I try to create the article from the back-end, as you correctly said, I get the same error.

But the strange thing is that going to see in the table #__content the article is present (creating the arcticle from the back-end or via API is the same):

As regards the aspect of the publication workflow, I partially understood what was said.

What I don't understand is why it is different between creating articles from back end and with API.

As superuser I can safely create an article as already published by the back end:

@Razzo1987 try using condition property instead of state to set article status.

What do we do with assets table issue? Increase column length 255 and hope nobody uses longer titles? Truncate the title in code? Add some rollback actions?

I think, truncating the title in the code for the asset table has no risk, as the title is not used as identifier.

A 100-character header is not enough.
We don't make headlines to make it easy to search for an article in the archive. We create headlines to sell products, to write news, to attract people. Thus, the CMS must adapt to the needs, content Creators should not adapt to the CMS, especially when the CMS is at the development stage, we must and can already take into account the requirements of the market.

Maybe it is a misunderstanding. I meant the title in the table #__assets which is only visible for maintainers in the database. And think that the title there could be truncated.
In #__content the length of title is 255.

@korenevskiy Do you think this is to short?

I can reproduce the issue without API. title column in #__assets table has 100 character limit. In J3 longer titles were truncated and in J4 the entry is not created.

This is the issue. It isn't anything to do with the webservices API

there are some issues when we have a very long article title like :
"La Nigeria prende in consegna l'ex procuratore generale Adoke per un affare di petrolio da 1,3 miliardi di dollari"

despite the content title of the#__content table field allows 255 chars
https://github.com/joomla/joomla-cms/blob/4.0-dev/installation/sql/mysql/extensions.sql#L162
the#__assets table don't allows more than 100 chars
https://github.com/joomla/joomla-cms/blob/4.0-dev/installation/sql/mysql/base.sql#L15

plus the #__finder_links' table field route
https://github.com/joomla/joomla-cms/blob/4.0-dev/installation/sql/mysql/extensions.sql#L262
will add some more chars to the title length

so even if the title length of an article in theory is 255 in pratice should be less than 200

a dirty attempt to circumvent is #28734

for the unpublished status when an article is submitted from the api
if you add "transition": 2 to the body of your POST request something like this

your article will be saved with the published status

don't forget to apply pr #28734
and "transition": 2 will work only if you are using the default workflow stage/transition

so i'm closing this issue

@alikon wondering if it would be useful to give people a helpful hint in the API if they try to update the state field directly

maybe best to wait till the new workflow will land in core, and then reconsider it