Currently, you can go to admin/structure/feeds/i_dont_exist, and Feeds will show an edit form for a new importer, this is just weird, and we should return a 404.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | interdiff.txt | 1.76 KB | twistor |
| #6 | 2305919-non-existent.png | 83.87 KB | megachriz |
| #6 | 2305919-FeedsHTTPFetcher.png | 106.38 KB | megachriz |
| #6 | 2305919-log.png | 39.02 KB | megachriz |
| #4 | interdiff.txt | 598 bytes | twistor |
Comments
Comment #1
twistor commentedComment #2
twistor commentedComment #4
twistor commentedComment #5
megachrizI believe something weird also happens when entering the url for a existing, but not currently chosen fetcher/parser/processor on a feeds importer that does exist. Hope to look at this patch in a few days.
Comment #6
megachrizWith patch applied, 404's are correctly returned for:
For the following paths no 404's are returned (see also attached images):
This page is returned by a View. The feeds importer is set as a contextual filter, but there is no feeds importer validator available. Should we implement such one or is that overkill?
One can go to setting pages of fetchers, parsers and processors, even when these are not selected for the importer. Ideally, the path to the plugin's setting page should be something like
/admin/structure/feeds/%feeds_importer/fetcher/settingsor would that possibly break contrib (if, for example, a contrib introduced a fourth type [not fetcher, parser or processor] of plugin)?This results in an empty page instead of a 404.
Comment #7
twistor commentedThese should be fixed, but I think we can push them off into separate issues. I agree that the /admin/structure/feeds/node/settings/FeedsHTTPFetcher should be /admin/structure/feeds/node/settings/fetcher, but that's going to be a huge patch, lots of tests and things will change.
I'll fix this one up.
Comment #8
megachrizSounds good to move "/import/non_existent/log" and "/admin/structure/feeds/node/settings/FeedsHTTPFetcher" to separate issues. They aren't big "showstoppers" anyway.
Great. Be sure to check that it doesn't hurt contrib modules that add extra subpages to the Feeds UI. My sandbox module Feeds Quick Mapping (which provides an alternative way of defining mappings) adds such a subpage.
Comment #10
twistor commentedI went ahead and committed this with some minor changes.
Thanks for pointing out Feeds Quick Mapping, which does get broken by the fix for /admin/structure/feeds/node/non_existent.
There's not an easy way at this point to fix that, we'll have to have some sort of API to extend the Feeds UI. But, I want to re-vamp the UI anyway.
Comment #11
twistor commentedFollowups:
#2333005: Change plugin path from plugin id to plugin type.
#2333009: Add importer validator for Views.
#2333011: Create API for extending the Feeds UI.