--- old +++ new @@ -1,5 +1,5 @@+* export trove category choices from alexandria; load them into mongo via bootstrap
* new page under Admin
-* add all the trove category choices from alexandria
* like http://screencast.com/t/lAwwlzWUX8qG
* but use ajax and make it nice!
* forge-classic hook to save them on the alexandria project record
size: --> 8
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Changes are on js/1914 on allura and forge-classic. To test, go to the new "Categorization" admin page and add/delete some categories. Make sure the categories get updated in gutenberg too.
This command needs to be run after push: allurapaste create-trove-categories /var/local/config/production.ini Before that, setup.py will need to run. Does that get run automatically during a push anyway?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have more testing to do, but one thing I noticed is the forge-classic hooks need to do more. Alexandria needs to be updated so that project search and other things have the trove categories. You can look at John's work on [#1998] to see how he did it via the API. Going directly to the DB would be fine too. And then if it's updated in Alexandria, gobble will get the categories and update gutenberge, so the gutenberg update isn't really necessary.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also, on /admin/trove/trove_cat_add.php and /admin/trove/trove_cat_edit.php, we should at minimum put a notice saying that changes need to be manually done on the Allura database. (Right now, I don't think its worth updating that code to have it update allura mongo too)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On the UI side, <optgroup> might be nice for the 2-level categories, instead of 2 separate drop-downs. I'm not entirely sure how well that'd work for 3-deep categories though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
File "/home/dbrondsema/dbrondsema-7024/forge-classic/sfx/sfx_main.py", line 219, in project_updated
api.update(pylons.c.user, pylons.c.project)
File "/home/dbrondsema/dbrondsema-7024/forge-classic/sfx/lib/sfx_api.py", line 253, in update
group_id = r['Project']['id']
TypeError: string indices must be integers, not str
a few UI suggestions too:
change the button from Save to Add
move Topic & License to the top of the page, since they're most used
indent each subgroup drop-down visually
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Diff:
Changes are on js/1914 on allura and forge-classic. To test, go to the new "Categorization" admin page and add/delete some categories. Make sure the categories get updated in gutenberg too.
This command needs to be run after push: allurapaste create-trove-categories /var/local/config/production.ini Before that, setup.py will need to run. Does that get run automatically during a push anyway?
I have more testing to do, but one thing I noticed is the forge-classic hooks need to do more. Alexandria needs to be updated so that project search and other things have the trove categories. You can look at John's work on [#1998] to see how he did it via the API. Going directly to the DB would be fine too. And then if it's updated in Alexandria, gobble will get the categories and update gutenberge, so the gutenberg update isn't really necessary.
Also, on /admin/trove/trove_cat_add.php and /admin/trove/trove_cat_edit.php, we should at minimum put a notice saying that changes need to be manually done on the Allura database. (Right now, I don't think its worth updating that code to have it update allura mongo too)
Made [#2102] to count points of prior work in prior sprint.
Related
Tickets:
#2102On the UI side,
<optgroup>
might be nice for the 2-level categories, instead of 2 separate drop-downs. I'm not entirely sure how well that'd work for 3-deep categories though.Added the message on sfx js/1914. I also changed the forge-classic code to update in alexandria.
I get this when adding trove categories:
a few UI suggestions too: