Project

General

Profile

Actions

Task #83969

closed

Shortcut pages should show 'keywords' and 'description' fields.

Added by Raphael Graf over 6 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
Could have
Assignee:
-
Category:
Backend User Interface
Target version:
Start date:
2018-02-19
Due date:
% Done:

0%

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

Description

This can be useful (and less confusing) with a typoscript setup like the following:

meta.keywords.data = levelfield:-1, keywords, slide
meta.description.data = levelfield:-1, description, slide

Actions #1

Updated by Gerrit Code Review over 6 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55805

Actions #2

Updated by Mathias Schreiber over 6 years ago

I doubt the usefulness of inheriting SEO-related fields.
Just so I understand:
Say you have a tree structure like this:

Home [Shortcut to first subpage]
  - About us
  - Contact

Now you want to add meta keywords and a description to Home and inherit that down onto both About us and Contact?

Actions #3

Updated by Raphael Graf over 6 years ago

Mathias Schreiber wrote:

I doubt the usefulness of inheriting SEO-related fields.

I doubt the usefulness of SEO-related fields in general, but at least for keywords, this is what many sites are doing.
The keywords-example is taken from the typoscript reference:
https://docs.typo3.org/typo3cms/TyposcriptReference/Setup/Meta/Index.html?highlight=keywords

Actions #4

Updated by Gerrit Code Review over 6 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55805

Actions #5

Updated by Mathias Brodala over 6 years ago

Raphael Graf wrote:

Mathias Schreiber wrote:

I doubt the usefulness of inheriting SEO-related fields.

I doubt the usefulness of SEO-related fields in general, but at least for keywords, this is what many sites are doing.

That doesn't make it right however:

  1. Keywords are pointless unless used for internal purposes
  2. Descriptions must be unique for every single URL

So just like Mathias I don't see a use for this change.

The keywords-example is taken from the typoscript reference:
https://docs.typo3.org/typo3cms/TyposcriptReference/Setup/Meta/Index.html?highlight=keywords

Technically this example is correct, logically it's useless. ;-)

Actions #6

Updated by Gerrit Code Review over 6 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55805

Actions #7

Updated by Manuel Wohlers over 6 years ago

Mathias Brodala wrote:

  1. Keywords are pointless unless used for internal purposes
  2. Descriptions must be unique for every single URL

I don't know about a reason for multiple pages share the same description. But there may be use cases where a non-specific description is better than no description at all.
Keywords may be pointless for google & co but as you said they could be used to tag pages for whatever reason. ('internal purpose' is a reason, don't you think? ;-))

It will not hurt to have the fields available in the backend. It is easy to hide them by tsconfig anyway.

Actions #8

Updated by Georg Ringer over 6 years ago

same as possible to hide those via tsconfig it is such easy to add those fields to shortcut doktype. therefore I am for rejecting this issue

Actions #9

Updated by Georg Ringer about 6 years ago

  • Status changed from Under Review to Rejected

Rejected as this can be changed easily by an integrator

Actions

Also available in: Atom PDF