Bug #19925
closed
IFSUB and friends are ignoring the l18n_cfg field of the page record
Added by Stefan Galinski almost 16 years ago.
Updated about 6 years ago.
Description
The l18n_cfg field is used to disable the default language record or any alternative language records which haven't a page translation. At the first glance it seems to work like expected, because the expected page records are not visible in the menu. If we have a closer look at this part, we will find out that it's badly ignored for the record states IFSUB and friends. This causes that a page record which has no visible sub pages is marked with the IFSUB state.
How to reproduce?
1) Create the following page structure:
- first parent page
- first sub page
- second parent page
- first sub page
2) Add a translation for each of the parent records
3) Set the l18n_cfg field to each of the sub pages (it's not really important which setting or combintation)
4) Create a menu with IFSUB states applied
5) Test the result in the frontend
(issue imported from #M10285)
Files
The bug report #17635 is related to this problem...
The attached patch is against TYPO3 4.2.4...
I have exactly the same error and the patch worked for me, see also Bug 0009423.
This has not yet been sent to Core List.
The attached patch is still necessary and still works in TYPO3 4.4.6
Can this be fixed in the upcoming release?
Anyone knows about 4.5?
You should still use the patch.
- Target version deleted (
0)
Why is the state of this issue Needs Feedback?
What feedback is required to get this issue solved?
Target versions should be IMHO 4.4.8, 4.5.3, 4.6.0.
- Category changed from Communication to Frontend
- Status changed from Needs Feedback to Accepted
- Target version set to 1061
No feedback is required, just someone to push it to Gerrit and some guys to review that.
After submit to master, it should also be backported to at least 4.5 and probably also the 4.4 branch. If the same patch applies to 4.3 too, would also be a candidate "while someone is at it".
- Target version changed from 1061 to 1264
The attached patch is still necessary and still works in TYPO3 4.5.3
Kind of a bummer, as the patch already exists why has it not been sent to core list yet?
Mateng, could you please just do that? Tutorial
Great! If you run into trouble, just ask on the typo3-dev or typo3-teams-core mailing list!
- Target version changed from 1264 to 1341
Patch set 1 of change I10e86761b13c61161ae3153b2b7612701e3743b7 has been pushed to the review server.
It is available at http://review.typo3.org/5265
Patch set 1 of change Iba596db44e5096d18e82757ea60a9042941719b8 has been pushed to the review server.
It is available at http://review.typo3.org/5266
Patch set 1 of change Ia988dfeb272b6c64c86c45f9d80b8b9299a09bfc has been pushed to the review server.
It is available at http://review.typo3.org/5573
Steffen Gebert wrote:
Great! If you run into trouble, just ask on the typo3-dev or typo3-teams-core mailing list!
Well, I actually ran into trouble, but didn't have the time to articulate the problems.
Thanks to Mr. Hudson for pushing this. Next time it's on me :).
- Status changed from Accepted to Under Review
Patch set 2 of change Ia988dfeb272b6c64c86c45f9d80b8b9299a09bfc has been pushed to the review server.
It is available at http://review.typo3.org/5573
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Target version deleted (
1341)
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by