Project

General

Profile

Actions

Bug #23380

closed

SysFolder and NotInMenu-Pages not visible in Pagetree

Added by Sven Juergens over 13 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-08-16
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

If you set the following configuration in UserTS options.pageTree.separateNotinmenuPages = 1
SysFilder and NotInMenu marked Pages are not visible anymore.

see attached Image

Problem is this 16px

ul.tree div.treeLinkItem {
...
height: 16px;
...
}

in typo3/sysext/t3skin/stylesheets/structure/element_tree.css

I don't know if this is set for compatibility reasons in Browsers lie IE 6/7/8, maybe someone can test it.

If this is no problem in other Browsers, remove "height: 16px;" to solve the Problem

(issue imported from #M15464)


Files

separateNotinmenuPages.gif (7.09 KB) separateNotinmenuPages.gif Administrator Admin, 2010-08-16 11:46
15464.diff (418 Bytes) 15464.diff Administrator Admin, 2010-09-15 15:05

Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Bug #23537: pageTree.separateNotinmenuPages = 1: page was hiddenClosed2010-09-14

Actions
Actions #1

Updated by Dassault Systemes over 13 years ago

I confirm the bug with typo3 4.4.2 and t3skin 4.4.0.
The fix is working (remove height:16px)
Tested in Firefox 3.5, IE6, IE7

Actions #2

Updated by Alexander Opitz over 10 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #3

Updated by Alexander Opitz about 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF