Updated: Comment #82
Aggregator categories are one of the last core sub-systems that do not use the entity API.
Instead it relies on its own API. While we tried making its storage swappable with a seperate service, categories are still un-translatable and we are still re-inventing the wheel.
Categories should be Terms instead.
Get rid of the custom code and the raw-sql queries. Use the entity API instead.
Get rid of the custom tables that handle the relations between categories and feeds/feed items and instead use Field API ; Attach an entity reference field on feeds and feed items entities instead.
We will also need an aggregator specific vocabulary to put existing categories from sites upgrading from D7.
A maintainer is needed to approve this API change for D8
Reroll patch in #72 and see wherre we stand with tests after was fixed.
Fix any potential newly introduced failures.
Review and RTBC
User interface changes
All the category crud forms will use the term forms instead provided by the taxonomy module, which means taxonomy will be a dependency
Aggregator will get its own field-ui for managing feed entities under the current administration page
aggregator_category_item tables are being removed in favor of taxonomy tables and tables created by Field API
aggregator_category_selector is removed from aggregator's config and moves to the field instance settings instead
aggregator_save_category is removed in favor of just
aggregator_category_load is removed in favor of
Original report by qgil
The Aggregator module allows the creation of categories to file the news feed. The creation of categories is done manually, though.
What about the possibility to assign an already created vocabulary to define the aggrgator categories?
It would be quite useful. For example, if my site has a vocabulary "topic" with entries such as film, radio, tv, press with which I organize articles and the forum, I could use this same vocabulary to organize news feeds.
|FAILED: [[SimpleTest]]: [MySQL] 55,846 pass(es), 35 fail(s), and 1 exception(s).|
|FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch drupal-aggregator_taxonomy-15266-68.patch. Unable to apply patch. See the log in the details link for more information.|
|FAILED: [[SimpleTest]]: [MySQL] 55,731 pass(es), 42 fail(s), and 7 exception(s).|
|FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch drupal-aggregator_taxonomy-15266-62.patch. Unable to apply patch. See the log in the details link for more information.|