[gharlan]

The add/edit methods of the handler classes took their data in different ways: $data arrays with legacy keys (catname, catpriority), the parent as a separate parameter or as an object, or a list of positional values (LanguageHandler). This aligns ArticleHandler, CategoryHandler, LanguageHandler and MediaCategoryHandler:

• the values to store are passed as one $data array, keyed like the columns, followed by $meta
• the identity of an existing record ($id, $languageId) stays a separate parameter
• in edit() missing keys keep their value, a given key (also null) is stored
• priority is optional in add() and appends the element

CategoryHandler::add(['parent_id' => 5, 'name' => 'Foo']);
CategoryHandler::edit($id, $languageId, ['priority' => 2]);
LanguageHandler::edit($id, ['status' => true]);
MediaCategoryHandler::add(['parent_id' => null, 'name' => 'Foo']);

Arrays rather than single parameters, because they can get new fields after the release without breaking callers, and they distinguish a missing key from an explicit null.

Breaking changes

• CategoryHandler::add(?int $categoryId, array $data, …) → add(array $data, …) with parent_id; catname/catpriority → name/priority; the separate start article name is gone, the start article gets the category name
• CategoryHandler::edit(): catname/catpriority → name/priority
• ArticleHandler::edit(): name is no longer required
• LanguageHandler::add()/edit() take $data arrays instead of positional values
• MediaCategoryHandler::add(string $name, ?MediaCategory $parent) → add(array $data) with parent_id; an unknown parent now throws a UserMessageException instead of silently creating a root category

Fix

MediaCategory read the root path | as [0], so getParentTree() threw for every media category and subcategories were stored with a leading 0 in their path.

MediaHandler follows in a separate PR (passing the file as a Symfony File/UploadedFile instead of the $_FILES shape).