Project

General

Profile

Actions
Copy link

Bug #31470

closed

Content Element Layout -> Top Margin & Bottom Margin fields are ignored at saving record

Added by Florian Baumann over 12 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2011-10-27
Due date:
% Done:

0%

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

Description

Hello

We are currently experiencing a strange issue with a TYPO3 4.5.5 Backend. At no matter what content element the three fields Top Margin, Bottom Margin and Indentation and Frames are not written to the database after clicking the save button. The Fields just stay empty every time! It looks like TYPO3 cannot see that anything has changed.

See attached screenshot for the exact location of the fields.

What has already been tested:
- Converting the tt_content table to proper utf-8 (for some reason that wasn't) --> no success
- Initially changing the value in phpmyadmin to check whether it works at all --> no success
- Turned on sqldebug in TYPO3 install tool to track the queries done --> Could not find any corresponding update statement.

Has anyone experienced a similar behaviour in backends of v4.5.5?

Thanks a lot for inputs
Florian Baumann

Files

Download all files
gehtnet.jpg (58.4 KB) gehtnet.jpg Florian Baumann, 2011-10-31 17:30
spaceafter_spacebefore_normal.png (87.4 KB) spaceafter_spacebefore_normal.png Francois Suter, 2011-10-31 21:27
Actions
Copy link
 #1

Updated by Markus Klein over 12 years ago

Hi Florian!

Thanks for reporting.

At first I want to mention that you're using an insecure TYPO3 Core version. (http://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2011-002/)
Please update to 4.5.7.

As you say that there's no SQL query at all, can you please check if you encounter any backend (javascript) errors?
You can use the $TYPO3_CONF_VARS['BE']['debug'] setting for enabling the backend console.

Thank you.

Actions
Copy link
 #2

Updated by Francois Suter over 12 years ago

Hi Florian,

I am unable to reproduce this. There must be some extension interfering I would say. Some of things you could check (beyond what Markus already mentioned):

- do you see any error in Admin Tools > Log (if some values are not saved properly to the database, an error normally shows up there)?
- check the configuration of one of these fields in Admin Tools > Configuration (see attached screenshot showing a perfectly normal configuration)
- check the ext_tables.php files of the various extensions install and the typo3conf/extTables.php file to see if anything is affecting spaceAfter, spaceBefore and section_frame

If all else fails, try uninstalling extensions one after the other to try and find the culprit.

Actions
Copy link
 #3

Updated by Florian Baumann over 12 years ago

Hi

Sorry it took so long for my feedback. We have found the bug.

It was one of our custom extensions which modified the global TCA and still expected TYPO3 to work like an older version than 4.5. After changing the plugin based TCA file, the error was gone.

Thx a lot!

Issue can be closed.

Greets
Florian Baumann

Actions
Copy link
 #4

Updated by Stefan Galinski about 11 years ago

  • Status changed from Needs Feedback to Closed
Actions
Copy link

Also available in: Atom PDF