Project

General

Profile

Actions

Feature #50727

closed

Add "class" field to pages table

Added by Thomas Skierlo over 11 years ago. Updated over 4 years ago.

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

0%

Estimated time:
PHP Version:
5.3
Tags:
Complexity:
no-brainer
Sprint Focus:
Needs Decision

Description

I am missing a field “page_class” within the pages table. Remember, a class is, together with the (existing) id, the most atomic unit within all W3C specifications. With a page class, semantics could improve dramatically (decision: what is artice, aside, section...) and SVG as well as vector fonts could be used for graphical navigation – without getting (unsemantic) part of the content and without the need for sprites. Due to the fact that a field "page_class" is missing, thousands of people build graphical navigation with images drawn from media fields and they must either abuse existing fields (Alt Title, Subtitle, Alias, Layout...) or expand the pages table on their own (which I can do, and you can do, but sadly not every TYPO3 user).
My opinion: It should/must be part of the standard row of fields of the pages table. Just a short input, not connected to anything else. Simple and effective – and I'm sure it would ease the work of the semantics team dramatically. An absolute must have for the use of CSS and Javascript Frameworks - as well as HTML5.

Regards,

Thomas

Actions #1

Updated by Steffen Gebert over 11 years ago

--deleted

Actions #2

Updated by Steffen Gebert over 11 years ago

I think that's the kind of customisation, which can easily be done using a tiny extension (so tiny that it can even be created by an integrator, not even a PHP developer).

Everybody thinks that "his" field is the most important one and should be integrated into the core - and then we end up with a 200 column pages table.. so -1 from my side.

Actions #3

Updated by Philipp Gampe over 11 years ago

  • Category deleted (1050)
  • Status changed from New to Needs Feedback
  • Target version deleted (6.2.0)

In general we want to reduce the number of fields shown by default in the TYPO3 backend. This includes fields that are of little use for many websites, and fields that are specific for old functionality (CSS styled content).

Adding another random field does not seem to fit this scope. Also please see the note from Steffen.

I leave this open for a couple days, for others to comment, but I am about to reject this.

Actions #4

Updated by Thomas Skierlo over 11 years ago

Gentlemen. Just to make one thing sure. I first added the field I need to my pages table and THEN issued the feature request. Why? Because I'm trying to improve TYPO3. Are you too?

I have no problem at all if fields which are not needed are getting removed. I'm talking about a new field which might be needed, and I'm not asking for a field for my cat's birthday.

Besides that, currently other fields are added, like categories. With no documentation available until the time being.

Could have lived with a sentence like “well, I'll talk with the specialists from FE rendering or semantics. If they don't support the idea, I'll probably reject it”. But I didn't hear it. Instead I have learned, that Philip Gampe is in the position to reject any request “within a couple of days”. Do it now. I'm out of this Core issue Kindergarden – total waste of time.

Actions #5

Updated by Philipp Gampe over 11 years ago

@Thomas: First of all, I am the "Friendly Ghost" is this week. One of my task is to review and potentially close (new) issues in the issue tracker.

Second, we have a certain vision for TYPO3 CMS and we do exchange ideas, even if not all of this is public in first place.

Anyway, you fail to provide a good reason for this addition, besides "I need this" and "there are already other fields like this" which is both a "non-argument" for a serious discussion.

Third, you already good opposition in the list as well as from another another team member. If you fail to create a lobby for a feature only you need, how do you expect that this will land in core?
I leave this open so that you can create that kind of lobby, even if this is just to show that you are not the only one who needs this feature.

Forth, if you want to increase the chance to bring this to core, you have to provide a good argumentation:
  • why this is needed and what does it do
  • how does this ease the work with TYPO3
  • why can't this be easily added by extension [this is where you fail most]

You got opposition for all points already, thus if you need this, then please provide some arguments.

Actions #6

Updated by Thomas Skierlo over 11 years ago

@Philipp

Well, just to avoid that another lie is cast into concrete here:
You know and I know that my feature request had a long and detailed prologue under forum.typo3.org the day before yesterday (look for "Page Class für Navigationselemente"). You even took an unfriendly part in it, as anyone can see who is able to read German. You could have answered my question about "categories" - I asked twice and got no answer - but you never did.
I already have “my field” (the one nobody except me needs), and there is no reason at all to create a lobby. Like I said, I'm out of it here, not disturbing the Core people's “certain visions for TYPO3 CMS” anymore.

Actions #7

Updated by Alexander Opitz over 11 years ago

  • Status changed from Needs Feedback to New

@Philipp

I leave this open for a couple days, for others to comment, but I am about to reject this. <

Will there be a core member who looks into issues with the state "Needs Feedback"? No, not realy, so there won't be comments from others.

@Thomas

The problem is easy to fix, install menuclass and done. The extension has 159 downloads since 09.01.2013 and as I understand the thread on forum.typo3.org, http://forum.typo3.org/index.php?t=msg&goto=691439, it seams many users have this need. They are using own extensions, misuse other fields and so on. So an clean implementation would be fine. Then the question would be input field, select field, multi select or checkboxes? How to configure? Where to use? The so called usage scenarios. Maybe this all can get a logic, if layout X is selected then you can only select this and this class.

Would you be so nice to provide some more, detailed, usage scenarios? So this could be a feature rich change.

So I think that isn't a no-brainer and also not happening before 6.2 release.

Actions #8

Updated by Mathias Schreiber almost 10 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber

Hi Thomas,

do you think it might make more sense to come up with a set of predefined values that can be extended in order to "educate" more people towards the semantic ideas?

Actions #9

Updated by Alexander Opitz over 9 years ago

ping

Actions #10

Updated by Susanne Moog over 9 years ago

  • Sprint Focus set to PRC
Actions #11

Updated by Alexander Opitz about 9 years ago

  • Status changed from Needs Feedback to Closed
  • Assignee deleted (Mathias Schreiber)

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

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 #12

Updated by Benni Mack over 4 years ago

  • Sprint Focus changed from PRC to Needs Decision
Actions

Also available in: Atom PDF