Project

General

Profile

Actions
Copy link

Bug #25380

closed

page.meta supports http-equiv only for the key refresh

Added by Frank Nägler over 13 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
7.2 (Frontend)
Start date:
2011-03-23
Due date:
% Done:

0%

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

Description

currently the TypoScript option "page.meta" supports http-equiv meta tags only for the key "refresh".

For the IE8 Compatible meta tag (<meta http-equiv="X-UA-Compatible" content="IE=8" />) it is very important that this meta tag appears in the first lines of <head>. page.meta is the only way to add it early enough.

My patch add the TypoScript option: force_http-equiv for any meta tag, which is configured by page.meta

for example:

page.meta.X-UA-Compatible = IE=8
page.meta.X-UA-Compatible.force_http-equiv = 1

(issue imported from #M18020)

Files

meta_force_http-equiv.diff (704 Bytes) meta_force_http-equiv.diff Administrator Admin, 2011-03-23 16:10
Actions
Copy link
 #1

Updated by Todd about 12 years ago

  • Target version deleted (0)

Thanks for the helpful patch. Additionally, I would suggest changing it to use an equality test rather than isset so the typoscript value can be unset using zero.

if ($conf[$theKey . '.']['force_http-equiv'] == 1) {
$a = 'http-equiv';
}

Actions
Copy link
 #2

Updated by Mathias Schreiber almost 10 years ago

  • Description updated (diff)
  • Category deleted (Communication)
  • Target version set to 7.2 (Frontend)
  • Is Regression set to No
Actions
Copy link
 #3

Updated by Riccardo De Contardi over 9 years ago

  • Status changed from New to Closed

I close this ticket because in TYPO3 6.2 it seems that everything already works as you expect:

See the documentation: http://docs.typo3.org/typo3cms/TyposcriptReference/latest/Setup/Meta/Index.html

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
Copy link

Also available in: Atom PDF