Project

General

Profile

Actions

Bug #64768

closed

Classes for tables set in RTE are not renddered in FE

Added by Harald no-lastname-given almost 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Content Rendering
Target version:
Start date:
2015-02-02
Due date:
% Done:

0%

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

Description

Since about two weeks it no longer works that classes are taken for tables in FE. Since TYPO3 currently being developed, I have been waiting for. But I think this is a mistake.

The said part of the configuration which has always worked:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

RTE.classes {
table {
name = Table: Base
}
table-striped {
name = Table: Striped rows
alternating.rows { # 0 = even, 1 = odd
startAt = 1
oddClass = row-odd
evenClass = row-even
oddHeaderClass = row-odd
evenHeaderClass = row-even
}
}
table-bordered {
name = Table: Bordered table
}
table-hover {
name = Table: Hover rows
}
table-condensed {
name = Table: Condensed table
}
........

PAGE TS CONFIG:

RTE.default {
buttons {
blockstyle.tags.table.allowedClasses := addToList(table, table-striped, table-bordered, table-hover, table-condensed)
}
proc {
allowedClasses (
table, table-striped, table-bordered, table-hover, table-condensed, table-responsive, row-odd, row-even,
)
}
........

SETUP:

  1. Allow classes to tables
    lib.parseFunc_RTE.externalBlocks.table.stdWrap.HTMLparser.tags.table.fixAttrib.class.list := addToList(table, table-striped, table-bordered, table-hover, table-condensed)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In BE (RTE), the classes are displayed. Only in the FE it is not accepted. I'm pretty sure that there's something wrong.

Thanks Harald


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #70213: Classes for tables set in RTE are not rendered in FEClosed2015-09-30

Actions
Actions #1

Updated by Stanislas Rolland almost 10 years ago

Do you mean that the classes are not rendered in the frontend?

Are they shown in the RTE in the Backend?

Actions #2

Updated by Harald no-lastname-given almost 10 years ago

Yeah right. And what is currently, I noticed only by the tables ?!

Actions #3

Updated by Stanislas Rolland almost 10 years ago

  • Subject changed from RTE: Classes for tables are not applied in FE (7.1.0-dev) to Classes for tables set in RTE are not renddered in FE
  • Category changed from RTE (rtehtmlarea + ckeditor) to Content Rendering
  • Assignee deleted (Stanislas Rolland)

Thia means that this is a content rendering issue.

Actions #4

Updated by Stanislas Rolland almost 10 years ago

Are the classes on tables still present in the RTE after saving?

Actions #5

Updated by Harald no-lastname-given almost 10 years ago

Right. The classes remain after the save in the RTE exist. But - as I said, in FE (source) does not exist!

This affects ALL classes within the table.

Actions #6

Updated by Stanislas Rolland almost 10 years ago

What value do you have for lib.parseFunc_RTE.externalBlocks.table.stdWrap.HTMLparser.tags.table.fixAttrib.class.list
when you look at the TS Object Browser on the page on which the issue arises?

Actions #7

Updated by Harald no-lastname-given almost 10 years ago

These values. The values are as I need them

lib.parseFunc_RTE.externalBlocks.table.stdWrap.HTMLparser.tags.table.fixAttrib.class.list = contenttable,table, table-striped, table-bordered, table-hover, table-condensed

Actions #8

Updated by Harald no-lastname-given over 9 years ago

Now I can pass some time.
Today I updated TYPO3 to version 7.1. This issue seems to be solved now and everything works again!?

Greetings Harald

Actions #9

Updated by Stanislas Rolland over 9 years ago

So may we close this issue?

Actions #10

Updated by Benni Mack over 9 years ago

  • Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Actions #11

Updated by Riccardo De Contardi over 9 years ago

  • Status changed from New to Closed

No feedback since a while (>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

Also available in: Atom PDF