You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a site that uses Views to generate pages using data from a specified node. One example is a page with path eventreport2/%. This is displayed by a layout specifically for this path. On the configure layout admin page the Context is set to 'Position 2:eventreport2/%' and the Type then automatically becomes 'string pass-through'.
Such pages with custom layouts are no longer being displayed after update to 10.0 and the log shows two reports Notice: Undefined index: load callback in layout_get_layout_by_path() (line 1082 of layout.module)
and Error: Function name must be a string in layout_get_layout_by_path() (line 1083 of layout.module)
I have fixed this temporarily by reverting to the previous version of layout.module, i.e. before Issue #3004.
Note: I am not using the Taxonomy module which was perhaps the reason for #3004.
The text was updated successfully, but these errors were encountered:
Fixing this is pretty simple, we should just check if a "load callback" is specified before attempting to call it. Right now it looks like it's NULL in @Graham-72's example. PR at backdrop/backdrop#2214 adds a simple check.
I have a site that uses Views to generate pages using data from a specified node. One example is a page with path
eventreport2/%
. This is displayed by a layout specifically for this path. On the configure layout admin page the Context is set to 'Position 2:eventreport2/%' and the Type then automatically becomes 'string pass-through'.Such pages with custom layouts are no longer being displayed after update to 10.0 and the log shows two reports
Notice: Undefined index: load callback in layout_get_layout_by_path() (line 1082 of layout.module)
and
Error: Function name must be a string in layout_get_layout_by_path() (line 1083 of layout.module)
I have fixed this temporarily by reverting to the previous version of layout.module, i.e. before Issue #3004.
Note: I am not using the Taxonomy module which was perhaps the reason for #3004.
The text was updated successfully, but these errors were encountered: