Clearing site cache then taking "Manage Fields" pages like "admin/structure/types/manage/article/fields", leads to non existing path like "admin/structure/fieldable-panels-panes/article/fields". This issue happens if we use these threee modules: FPP, admin_menu, and panopoly_widgets

I have detailed out this issue more at #3039174: FPP cause to redirect to non existing path like "admin/structure/fieldable-panels-panes/article/fields" when taking "Manage Fields" paths like "admin/structure/types/manage/article/fields".

Basically it happens because FPP redirects wrong way as panopoly_widgets module uses legacy paths from FPP module for the FPP types this module creates.

CommentFileSizeAuthor
#2 repace-legacy-paths-of-fpp-3039431-2.patch5.46 KBjunaidpv

Comments

junaidpv created an issue. See original summary.

junaidpv’s picture

junaidpv
Location Kannur, Kerala
commented
Status: Active » Needs review
StatusFileSize
new repace-legacy-paths-of-fpp-3039431-2.patch5.46 KB

Here is path to improve panopoly_widgets module to replace legacy paths from FPP module.

  • dsnopek committed fbf1ab2 on 7.x-1.x 
    Update Panopoly Widgets for Issue #3039431 by junaidpv: Taking "Manage...
dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented
Status: Needs review » Fixed

Thanks! This makes sense to me. Committed!

  • dsnopek committed c159a43 on 7.x-1.x authored by junaidpv 
    Issue #3039431 by junaidpv: Taking "Manage Fields" paths of content type...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

chrisgross’s picture

chrisgross commented

This commit breaks the FPP UI on some of my sites. I haven't figured out why only some sites are affected, but something's not right with this patch, as all sites are running FPP 1.13. On those sites, it causes all fieldable panes to list no fields in the UI and to spit out this error in dblog:

Notice: Undefined index: fields in _field_ui_bundle_admin_path() (line 335 of ../modules/field_ui/field_ui.module).

I suspect that this commit just needs to modified a bit, but I'm not sure how, as I never experienced the underlying issue it was trying to fix.