This is not critical See https://docs.joomla.org/Bug_and_Issue_Tracker_Priority

I can confirm this issue

I can confirm this issue

Which sample data - there are several in j3

This was done on purpose.
See #24216

that was a hard breaking backwards compatibility issue that should not have been done in a patch release at all. @HLeithner

It was MUCH more dangerous before
Read #23991

So you solved the create category bug by completing disabling the ability to change category ?‍♂️

@HLeithner correctly said

If it's this way we can't change it in 3.9 but we should fix the "create" category bug.

Surely changing category should be linked with 'Edit state'. i.e. if A user is trusted to publish/unpublish an Article then they should be trusted to change Category? After all users could only select a category that they had edit Permissions for.

@Webdongle
the problem was larger than that in the sense that even with edit state, one may not know the full backend category structure when in frontend.
The readonly is only when editing an already saved article.

All that should have been changed was the ability to create a new category.

Everything else is a hard b/c break that should never me done in a patch release

I'm sorry but my users are in panic because they don't find the way to push an article in another category by frontend.
Let me know if i have to downgrade the joomla version.
Thanks.

Using an older version of Joomla is a security risk ... and you would loose everything new after installing an old backup. Work around would be
Create a new user group with Registered as Parent
Allow backend access
Article Permissions allow 'Access Administration Interface '
Put you required users in that new group
They can log in /administrator and only see the Articles/Categories

I have got 5.000 users in my site, it's a big drama to teaching them a new editing mode of their contents. Are you really want to mantain this feature? Are there any other possibility to solve this problem?

I have got 5.000 users in my site, it's a big drama to teaching them a new editing mode of their contents. Are you really want to mantain this feature? Are there any other possibility to solve this problem?

@dfrassi at the moment you can revert the changes from the related PR: https://github.com/joomla/joomla-cms/pull/24216/files

@Webdongle

Surely changing category should be linked with 'Edit state'. i.e. if A user is trusted to publish/unpublish an Article then they should be trusted to change Category?

See proposal here
#24640

Closed as having Pull Request.

@infograf768 That patch was merged before I checked it. great stuff thanks

it is not merged yet. needs one more tester and a decision by @HLeithner

@dfrassi
Have you tested the patch?

not yet, please can you send me the patched article.php file?

@dfrassi how to test > https://docs.joomla.org/Testing_Joomla!_patches

Ok, i have installed the jtester component, what patch i have to apply?

@dfrassi apologies, now i see #24640 is merged. @infograf768 can you please comment?

A merged PR can't be tested by patchtester.
In any case the PR is clear: now the category can be modified (after the article is saved) by users of type Publishers or UP, NOT by their own authors if they do not have edit.state permissions.

here is the modified article.php to replace
˜/administrator/components/com_content/models/article.php
article.php.zip

ok, now it's right
thanks

On the current joomla release, zero users can edit any existing article from the front end, (even super users). Joomla is broken and needs an urgent update.

luckily one of my customers contacted me for an urgent resolution. There are others that will just be swearing a lot...
It has wasted four hours of experimenting with permissions/templates and searching for answers to finally find this thread. The majority of Joomla users wont get off that light.
I appreciate the countless work that goes into joomla, however - it doesnt need this bad rap, this has been an oversight - not many end users will use github, and still - nothing shows on any joomla updates

@brianteeman - thanks for your comments.