Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
aggregator.module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
9 Dec 2013 at 02:58 UTC
Updated:
29 Jul 2014 at 23:12 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ParisLiakos commentedComment #2
ParisLiakos commentedComment #3
ParisLiakos commentedComment #5
ParisLiakos commentedComment #7
dawehnerI would always consider aggregator to be part of the admin interface to be honest.
I installed it via simplytest and found /aggregator/sources and /aggregator clickable, but none of them had a link to add a new entry. Should we maybe add some menu link/local action as well?
From the pure code side, there is nothing to say.
Comment #8
ParisLiakos commentedThe add local action is in
admin/config/services/aggregator
/aggregator/sources is similar like the /node path. There is no add action there. Actually now that i think of, do we have local actions in frontend at all? But yes as a menu link it is actually a good idea. Like the "Add content" one. i ll roll a patch for that
I just think that feeds and its operations should have /aggregator/sources as base path like we do for other entities already in core. The sake of consistency
Comment #9
ParisLiakos commentedComment #10
ParisLiakos commentedreroll
Comment #11
dawehnerWe have a new system for that now.
Comment #12
ParisLiakos commentedoh yes, which is awesome:)
Comment #13
dawehnerThese changes are perfect!
Comment #14
webchickVery nice clean-up.
Committed and pushed to 8.x. Thanks!
Comment #16
ParisLiakos commentedi messed up the yaml definition, opened #2224951: Aggregator delete local task uses tab_root_id instead of base_route with correction + test