Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
litespeed_wiki:cache:litemage:troubleshooting:fatal_error_uncaught_error_call_to_undefined_method [2018/01/12 21:42] Lisa Clarke Proofreading, fixing messed-up formatting |
litespeed_wiki:cache:litemage:troubleshooting:fatal_error_uncaught_error_call_to_undefined_method [2018/01/12 22:16] Jackson Zhang [Next Step: Investigate the Code In Depth] |
||
|---|---|---|---|
| Line 151: | Line 151: | ||
| <code>$this->escapeHtml</code> | <code>$this->escapeHtml</code> | ||
| - | Problem solved. Basically the steps are to locate the problematic code in the Meigee Feather theme and fix it. | + | We have disabled footer ESI in LiteMage in the first step, but we have further investigation on footer code. It has similar issue. |
| + | |||
| + | app/design/frontend/feather/default/template/page/html/footer.phtml | ||
| + | |||
| + | It uses the following line: | ||
| + | <?php echo $this->getLayout()->getMConfigResultByAlias('custom_footer_block'); ?> | ||
| + | |||
| + | Instead of calling function getMConfigResultByAlias, the user can put actual content there to avoid such issue. Since it has been covered by disabling LiteMage footer ESI, we don't change it here anymore. | ||
| + | |||
| + | |||
| + | Problem solved. Basically, the steps are to locate the problematic code in the Meigee Feather theme and fix it. | ||