@Hackwar for shake of B/C shouldn't you leave the public facing functions in the library [libraries/src/Table/CoreContent.php] (so it won't break things)? eg

public function bind($array, $ignore = '')
{
}

public function publish($pks, $state, $userId)
{
return true;
}

Those aren't gone. They are still in the parent Table class and are all used there. All those methods just implemented special behavior (like the publish methods) because fields were named differently. Since we can now alias a column, we don't need a special case for a table that has a column named state instead of published anymore and this can simply be removed. It is completely B/C

@Hackwar my comment was just by looking at the public part of the function. If it's not reachable or the parent will take care of it then it's fine

Remove use statements.

Remove use statements.

done

I have tested this item ✅ successfully on 7dab791

I have tested this item ✅ successfully on 7dab791

I have tested in backend in several components with adding / changing / ordering items and found no issue.

Not tested with 3rd party components or updated installations.

@bonzani How did you test this pull request? It doesn't provide any testing instructions.

@Hackwar Ever thought about providing testing instructions? And (inspired by past experience): Have you tested your changes yourself?

@richard67 I did move around items in the backend components. Since test instructions are missing, I just tried to cover code paths that where affected by this PR. But might also just have been a lucky test. Hard to say without specific instructions! But since it is analogous to the other two PR's that removed about the same code the changes looked fine.

@bonzani Thanks for the feedback.

Your welcome. I try to allocate a little spare time (but I do not have much), to help with the testing so that we hopefully see version 4 released this year!

RTC.

Thanks!