Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
litespeed_wiki:cache:litemage:troubleshooting:unable-to-redirect-404-to-search-results [2016/05/06 14:25] Michael Alegre created |
litespeed_wiki:cache:litemage:troubleshooting:unable-to-redirect-404-to-search-results [2017/05/08 13:58] (current) Lisa Clarke |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Unable To Redirect 404 Pages To Search Results ====== | + | ~~NOTOC~~ |
| + | ====== Can't Redirect 404 Pages To Search Results ====== | ||
| + | ====Problem==== | ||
| + | Some Magento extensions, such as [[https://www.magentocommerce.com/magento-connect/search-ultimate-sphinx-search.html|Mirasvit Sphinx Search Ultimate]], can redirect 404 pages to specific search results. But when LiteMage is on they can't achieve this redirection. | ||
| - | In Magento's default implementation, all 404 pages are treated as being identical with the full action name of the default "No-route Controller" being ''cms_index_noRoute''. LiteMage's default configuration will cache the output for this controller. | + | ====Cause==== |
| + | In Magento's default implementation, all 404 pages are treated as **cms_index_noRoute** (the full action name of the default No-route Controller). LiteMage's default configuration was designed with this in mind and will cache the output for this controller. As such, redirection won't work with LiteMage's default configuration. | ||
| - | If you have any extensions that change this default behavior, such as Mirasvit's Sphinx Search Ultimate which can redirect 404 pages to specific search results, you will have to change LiteMage's default configuration to not cache these pages. | + | ====Solution==== |
| + | Change LiteMage's default configuration so that it does not cache 404 pages from this controller. | ||
| - | In LiteMage's "config.xml" file under ''<default> >> <litemage> >> <default>'', change the following from | + | In LiteMage's config.xml file under **<default> >> <litemage> >> <default>**, change the following from |
| <fullcache_routes><![CDATA[cms_index_noRoute]]></fullcache_routes> | <fullcache_routes><![CDATA[cms_index_noRoute]]></fullcache_routes> | ||
| Line 13: | Line 18: | ||
| <fullcache_routes></fullcache_routes> | <fullcache_routes></fullcache_routes> | ||
| - | **Note:** This change is not available through Magento's Admin Panel and must be set through LiteMage's configuration file. As such, you will have to manually apply this change to LiteMage's "config.xml" file every time you upgrade LiteMage to a new version. | + | ====Notes==== |
| + | This change is not available through Magento's Admin Panel and must be set through LiteMage's configuration file. As such, you will have to manually apply this change to LiteMage's config.xml file every time you upgrade LiteMage to a new version. | ||