Project

General

Profile

Actions

Feature #31303

closed

Insert Records: Ability to override header of source record

Added by Urs Braem over 13 years ago. Updated 25 days ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Frontend
Start date:
2011-10-26
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

When inserting a record, it will pick up the header from the original article.

That doesn't fit the needs in many cases, as the context for the inserted article is a different one, and a modification in the header may be needed for clarification.

The original header should be overridden by the Field currently labelled as "name" (if not empty).

An example:

Page 1:
<h1>London branch</h1>
<h2>Our partners</h2>
McKenzie
McBuffet

Page 2:
<h1>Berlin branch</h1>
<h2>Our partners</h2>
Hermann & Söhne
August & Co

Page 3:
<h1>Our global partners</h1>
<h2>Our partners</h2>
McKenzie
McBuffet
<h2>Our partners</h2>
Hermann & Söhne
August & Co

-> The h2s on Page 3 should be overrideable with a custom text to state the context:

Page 3:
<h1>Our global partners</h1>
<h2>London</h2>
McKenzie
McBuffet
<h2>Berlin</h2>
Hermann & Söhne
August & Co

One client of mine has for years been structuring his content in an odd way to escape this: he splits an article into a header and a content part, so he can later on reference only the content and place a different header before. Which leads to 3 content elements and a shortcut instead of 1 and a shortcut.

Actions #1

Updated by Mathias Schreiber about 10 years ago

  • Status changed from New to Accepted
  • Target version set to 7.2 (Frontend)
Actions #2

Updated by Urs Braem about 10 years ago

If this would be done 1:1 as I suggested it back then, it would be a very breaking change, I realize.
The "name" field shouldn't be used, rather an additional title field that comes into play when used. That would be quite nice.

Actions #3

Updated by Benni Mack almost 10 years ago

  • Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Actions #4

Updated by Susanne Moog over 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #5

Updated by Benni Mack over 9 years ago

  • Target version changed from 7.5 to 8 LTS
Actions #6

Updated by Riccardo De Contardi about 8 years ago

  • Target version changed from 8 LTS to 9.0
Actions #7

Updated by Susanne Moog over 7 years ago

  • Category changed from Content Rendering to Frontend
Actions #8

Updated by Susanne Moog about 7 years ago

  • Target version changed from 9.0 to Candidate for Major Version
Actions #9

Updated by Susanne Moog over 2 years ago

  • Sprint Focus set to On Location Sprint
Actions #10

Updated by Oliver Hader over 2 years ago

  • Sprint Focus deleted (On Location Sprint)
Actions #11

Updated by Benni Mack 25 days ago

  • Status changed from Accepted to Rejected

Hey Urs,

I am now closing this issue. To be honest: I understood the idea, but this seems very edge-casy and - in the past 10 years - nobody stepped up to pick this job. This - to me - seems to be a custom Content Type in an extension building such a logic with the headlines... this way, it can be put on extensions.typo3.org, and can be maintained separately.

I hope that's OK for you. Sorry that it took so long to get a proper answer from me! Very sorry about this!

All the best,
Benni.

Actions #12

Updated by Urs Braem 25 days ago

Hey Benni
of course, makes sense. This is outdated.
Best and thanks for the work!
Urs

Actions

Also available in: Atom PDF