-
Notifications
You must be signed in to change notification settings - Fork 462
Allow arbitrary nesting depth in categories #10404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow arbitrary nesting depth in categories #10404
Comments
The UI library aspect of this is filed in #10449. |
Would @eirikhanssen take this one? |
Yes! Thanks Bozana. |
…ation in validator
…ries, and GET category form
…ries, and GET category form
…ation in validator
* Implement endpoints to create, edit, and delete categories * Added migration to move category images into application's public directory * Load category thumbnail & full size image from application's public directory * Update logic for generating breadcrumbs, to ensure nested categories are handled * Delete sub-categories when a parent category is deleted * Remove ability to order categories
All merged! |
@taslangraham Testing went well. Looks good for OJS. I couldn't see issues with it. I'm going to be doing a quick test for OPS/OMP as well but I don't see much difference in the requirements for these projects. OMP has catalogs by default so I can see if there are many differences there. OPS should work the same. I'm not sure if you want to automate 1, 2 and 4 (only removing from the category list) Test Case Overview:
|
Uh oh!
There was an error while loading. Please reload this page.
last updated: Sept 2024
Journal Managers can currently create Categories and Subcategories in Settings > Journal > Categories:
https://github.com/user-attachments/assets/42e25d1e-e681-42a5-a3f8-b23930a6caa3
However, this artificially limits the nesting depth to 2 levels. It should be easy to support arbitrary nesting depth. The database already supports this, but the user interface does not.
The text was updated successfully, but these errors were encountered: