[TYPO3-dev] HMENU special = list does not take into account workspaces (bug fix)

Jigal van Hemert jigal at xs4all.nl
Fri Apr 2 19:59:49 CEST 2010


Бойчук Петро wrote:
> I've just added note and patch to the issue #5699  Sitemap Content Element
> does not honorate Workspaces [1]

Thanks for your effort!

> 1) First of all, and most important, can someone please check if this is the
> right way to fix this issue (I'm not sure how to use workspaces in TYPO3,
> but based on my researches - this is the right way, I hope)?

Testing will be done after you've done the other steps...

> 2) What should I do next if I want that fix to be included into next TYPO3
> release?

Post a message with the patch to the core list. The way to do it is 
explained in [1]

> 3) Is that the right format of patch file? Are there any guidlines for
> creating/naming patch file?

You should use a unified diff patch [2] made against trunk [3] or older 
(still supported) versions it applies to. The name usually includes the 
bug number and version: 5699_trunk.diff, 5699_4-3.diff, 5699_4-2.diff.

> 4) Maybe there is some kind of manual how to fix TYPO3 core?
[4] and the other pages in that part of the site. Read core list, read 
dev list, etc..
Core developers are quite busy, so it happens quite often that patches 
are not immediately tested and eventually they move out of sight. After 
a week you can reply to your own RFC with "REMINDER" in the body of the 
message to move it up in the list again. If you provide a clear test 
case (or point to the test case in the bug tracker) it becomes more 
likely that people find the time to test it.
There are also "bug days" [5] where developers gather on IRC to fix as 
many bugs as possible.


[1] http://typo3.org/teams/core/core-mailinglist-rules/
[2] http://typo3.org/development/bug-fixing/diff-and-patch/
[3] http://typo3.org/development/bug-fixing/using-subversion/
[4] http://typo3.org/development/bug-fixing/resolving-bugs/
[5] http://typo3.org/development/bug-fixing/bug-day/
-- 
Jigal van Hemert.




More information about the TYPO3-dev mailing list