[TYPO3-dev] Strange issues with prefixId in TYPO3 6.2
Loek Hilgersom
loek at netcoop.nl
Mon Apr 6 17:49:16 CEST 2015
Solved, finally.
It was (of course) not the prefixId itself that caused the problem, but some
coding mistakes in extensions, combined with a change in TYPO3 core:
* Since 6.1, [FE][pageNotFoundOnCHashError] is TRUE by default (this causes
the plugin to fail as soon as you call it with some piVars set)
* one of the extensions had $pi_checkCHash = TRUE in a non-cached plugin,
* the other should have been cached but the links had no chash....
The annoying thing is, if you have a custom 404-page (with
[FE][pageNotFound_handling] = '/page-not-found'), then don't see the error.
Hope this helps someone else.
Loek
On 03-04-15 16:06, Loek Hilgersom wrote:
> Hi all,
>
> For the second time I ran into strange issues caused by having the very common line
>
> var $prefixId = 'extensionname';
>
> in pibase plugins in a 6.2 installation.
>
> It results in pages showing content from another page (usually homepage or 404),
> without being redirected, url stays the same. With Xdebug I can see that the
> plugin on the page causing the problem is not even executed. I don't see any
> errors in Apache logs or syslog.
>
> Removing the line (if it's not used), or changing the name of the variable
> solves the issue. That's good, but I have absolutely no clue why this is
> happening. Somebody with a clever idea? Something that has been changed from 4.5
> to 6.2 regarding the prefixId class variable?
>
> Thanks!
> Loek
More information about the TYPO3-dev
mailing list