[TYPO3-core] RFC: Bug 1236: 404 error while using new content wizard

Ingmar Schlecht ingmar at typo3.org
Sun Sep 10 18:37:21 CEST 2006


Sweet, works nice.

Go commit!

cheers
Ingmar

Michael Stucki schrieb:
> Hi Ingmar,
> 
>> I just noticed some funny side effects with this patch (i.e. the backend
>> suddenly displays some random website found by firefox google "I'm
>> feeling lucky" search).
> 
> Oh, thanks for noticing! You are right, my solution caused another break
> which was not the intention of course.
> 
> Interestingly nobody who tested 4.0.2-rc1 noticed this problem. Usually I
> would suggest to let this change be tested in another RC, but since nobody
> noticed at all, I think its fine to change it straight forward.
> 
> Attached are two patches:
> 
> bug_1236_post1.diff: The new patch which you can apply to your source
> bug_1236_total.diff: The actual fix after reverting the 1st change (so this
>                      is the diff to 4.0.1)
> 
> - michael
> 
>> Michael Stucki schrieb:
>>> This is a SVN patch request.
>>>
>>> Problem:
>>> Under some circumstances you can get a 404 error while using the "new
>>> content wizard".
>>>
>>> Steps to reproduce:
>>> 1. Display a page using the list module
>>> 2. Click the "Create new record" icon in the top right corner
>>> 3. Click the Pagecontent-Wizard
>>> 4. Scroll down and click "Go back"
>>> 5. You'll end up with a 404 error
>>>
>>> Solution:
>>> Change the returnUrl for the new content wizard. Replace each directory
>>> level of the path with ".."
>>>
>>> Example:
>>> If $pathToWizard is "typo3/sysext/cms/somefile.php" then the $returnUrl
>>> will be set to "../../../".
>>>
>>> It's important that the returnUrl is only changed locally ($R_URI) so
>>> $this->R_URI is not being touched! Otherwise this would cause bad
>>> side-effects.
>>>
>>> Branches:
>>> TYPO3_4-0 / Trunk
>>>
>>> Bugtracker reference:
>>> http://bugs.typo3.org/view.php?id36
>>>
>>> - michael



More information about the TYPO3-team-core mailing list