| Project: | Chaos tool suite (ctools) |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Fatal error: Call to undefined function expand() in \wwwroot\sites\all\modules\ctools\plugins\access\term.inc on line 115
Call Stack
# Time Memory Function Location
1 0.0038 338928 {main}( ) ..\index.php:0
2 0.6581 23009400 menu_execute_active_handler( ??? ) ..\index.php:18
3 0.7513 24357240 call_user_func_array ( string(22), array(1) ) ..\menu.inc:348
4 0.7513 24357424 page_manager_node_view( object(stdClass)[4] ) ..\menu.inc:0
5 0.8643 25118184 ctools_context_handler_render( array(18), string(0), array(1), array(1), ??? ) ..\node_view.inc:89
6 0.9689 25673216 panels_panel_context_render( object(stdClass)[56], array(1), array(1), ??? ) ..\context-task-handler.inc:46
7 1.2215 26104488 panels_render_display( object(panels_display)[90], object(panels_renderer_standard)[96] ) ..\panel_context.inc:290
8 1.2226 26133480 panels_display->render( object(panels_renderer_standard)[96] ) ..\panels.module:1013
9 1.2241 26133776 panels_renderer_standard->render( ) ..\panels.module:688
10 1.2476 27948928 panels_renderer_standard->render_layout( ) ..\panels_renderer_standard.class.php:276
11 1.2476 27948928 panels_renderer_standard->prepare( ??? ) ..\panels_renderer_standard.class.php:300
12 1.2476 27948960 panels_renderer_standard->prepare_panes( array(4) ) ..\panels_renderer_standard.class.php:162
==============
Latest dev (02/Sept). Using a Context - Taxonomy
Comments
#1
Can you try changing 'expand' to 'explode'?
#2
I have been getting this error for weeks. I get it when i have a tagged vocab and i try to make a tax term variant for it. I work around it by changing the vocab to non tagged. where would i change expand to explode Merlin? tx.
edit: ps the error above is when i try to view a term after creating the variant. It also leads to this error in the tax term page admin page
/ctools/plugins/access/term.inc on line 141.
#3
Try this patch?
#4
Would've been nice if the submitter checked this, but I guess it'll have to do. Committed to all branches.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.