2.0.0

This release is compatible with Kirby 5, with a completely different approach.

Breaking changes

Well, pretty much every piece of the previous versions is broken with 2.0.0.
The plugin registered a custom field, now it doesn't.
The plugin registered custom methods, now it doesn't.

Why?
The previous approach had a few downsides:

• The UI wasn't good with more than 2-3 languages.
• It didn't allow for rich text, only a plain text string
• It only provided a single text field per category, which isn't enough in lots of cases (for example, having a plural name for filters and a singular one for a product page).

I stopped using it, hence there's been no update / maintenance for a while.

What now?
I've shifted towards using a native Structure field (in order to populate it with as much fields as needed) and keeping it synced accross languages with a dedicated UUID assigned to each item. I’ve been using it privately so instead of archiving this repo, I'd rather update it to this new method.

You will need to refactor manually your pre-existing categories fields (id becomes uuid in 2.0.0+ to match Kirby's native naming) and replace your categories fields by structure ones.

1.0.3: Merge pull request #6 from DodoVoelkel/master

• Merge last commit from @DodoVoelkel (untested – bring compatibility with K4) before refactoring.

1.0.2

• Compatibility with 3.6
• Index incrementation is now based on the highest index that has existed, instead of the actual categories count

1.0.1

Make the updateCategoriesStructure method more secure

1.0.0

In case anyone used the field before this first release, this commit will require you to update the data structure of your categories fields. In order to do this, please run for each page in which you have a categories field:

$page->updateCategoriesStructure('fieldname');