- Priority: 0
- Status: Closed
- Theme: Venedor
-
Assigned To:
Fred
- Private: No
- Open Date: 07.05.20, 11:07
- Opened by: ROMAIN
- Closed by: Fred
- Closed on: 08.09.20, 11:37
- Reason: Closed
- Comment: Glad to help!
Ticket #17727 - Mode Debug - BO error 500
Hi
I have a problem with the template. It’s impossible to access at the Back Office if I’m not in Debug Mode.
For example, when I click in front office on search we have this information :
This is an extract :
(1/1) ContextErrorException Notice: Undefined index: category in 424e0c577753d5bf0b306388736dca48546cf41a_2.file.product-list.tpl.php line 184 at Block_16961637245eb2c37fa24326_53885505->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_16961637245eb2c37fa24326_53885505), object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_16961637245eb2c37fa24326_53885505), object(Block_14884347915eb2a9f74755e7_49791156)) in smarty_internal_runtime_inheritance.php line 186 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_14884347915eb2a9f74755e7_49791156)) in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyDevTemplate), 'Block_14884347915eb2a9f74755e7_49791156', 'content', 2) in 572804ff0b04a7fb16ed001301078d5a7c0bb42e_2.file.layout-full-width.tpl.php line 101 at Block_16393744535eb2a9f7473a56_70496671->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248
Thanks for your help
Best regards
Comments
Could you please give me a link to a page where I can see the issue?
Yes of course : https://www.coloralpha.fr/recherche?controller=search&s=
fixed
Thank you but not totally. Indeed, when I desactive the debugmode in the backoffice the page is not available.
Could you fix that ?
I just enabled Debug mode to let you use back office. Now we need to take a look at server error logs to find out what is the reason of the issue. I’m not sure it’s relate to the theme