[TYPO3] extensions collide when used together

Oliver Rowlands oliver at liquidlight.co.uk
Sun Jun 15 14:00:38 CEST 2008


Hi Guido,

The simplest solution would be to not use 'error_404_handling'.

Why not simply use TYPO3's default 404 handling in your localconf.php?

$TYPO3_CONF_VARS['FE']['pageNotFound_handling_statheader'] = 'HTTP/1.x 
404 Not Found';

$TYPO3_CONF_VARS['FE']['pageNotFound_handling'] = '/my-404-page/';

In the case of a multi-domain setup:

$TYPO3_CONF_VARS['FE']['pageNotFound_handling_statheader'] = 'HTTP/1.x 
404 Not Found';

switch($_SERVER['SERVER_NAME']) {
     case 'www.domain-one.com':
         $TYPO3_CONF_VARS['FE']['pageNotFound_handling'] = 
'http://www.domain-one.com/my-404-page/';
         break;
     case 'www.domain-two.com':
         $TYPO3_CONF_VARS['FE']['pageNotFound_handling'] = 
'http://www.domain-two.com/my-404-page/';
         break;
     default:
         $TYPO3_CONF_VARS['FE']['pageNotFound_handling'] = 
'http://www.domain.com/my-404-page/';
}

Furthermore the 404 handling of 'error_404_handling' is wrong from a 
specification and SEO point of view: a 'page not found' request should 
return a '404' HTTP header code not a '302' (Temporary redirect) 
followed by a '200' (Success).

Best regards,

Oliver

G.Unger wrote:
> hi list
> 
> the extensions cr_awstat_realurl and error_404_handling do not work on 
> same instalation (T3 4.1.6).
> 
> both of them do their work as expected, as long as not installed together.
> 
> showcase:
> - installed cr_awstat_realurl on top of ics_awstats, and the section 
> where the pages path/name in awstats is shown, perfectly translates the 
> values in e.g. 
> /news/single/archive/2008/06/12/article/prinzipiell-erreichbar.html
> - installed error_404_handling, works propper and displays the errorpage
> - checked awstats in BE again, a new page is displayed -> [realurl]
> - any further click in frontend is listed as page -> [realurl]
> - uninstall/install cr_awstat_realur in extension manager, and new 
> clicks are displayed well again
> - unfortunately now the error page now is not displayed anymore, instead 
> I get the classic "Reason: Segment "xxxxxxxxx" was not a keyword for a 
> postVarSet as expected!"
> - uninstall/install error_404_handling again and it workz propper
> - unfortunately now every click is tracked as page name -> [realurl] again.
> 
> I havent got a clue where to start at :(
> 
> rgds
> GUIDO


-- 
Oliver Rowlands
:: Liquid Light ::

E - oliver at liquidlight.co.uk
W - http://www.liquidlight.co.uk

T - 00 44 (0)845 6 58 88 35
F - 00 44 (0)845 6 58 44 35


More information about the TYPO3-english mailing list