Bug #18392
closedConstant Editor changes not saved in Internet Explorer
0%
Description
Changes made in constant Editor are not able to be saved.
(issue imported from #M7781)
Files
Updated by Steffen Kamper over 16 years ago
where? when? how?
I have no problems with saving in constant editor.
Updated by Manfred Theuermann over 16 years ago
Sorry about by bad english. I try to explain you.
I use 4.2.0 beta3 and the Quickstart package. In Template Tools (Constant Editor) for example I want to edit the first Field in Category Basic. ( Left Frame- value 170) So I klick the pencil (edit this constant) then I made my changes and klick above on save document. But nothings happen, the default value again is in the input field. I can switch to revert to default Constant with value 150 or edit value of 170. But I cant made another value
Updated by Steffen Kamper over 16 years ago
Which browser, which OS?
Do you have an JS-Error?
Updated by Manfred Theuermann over 16 years ago
Internet Explorer 7, XP- Professional, no JS-Error
Updated by Manfred Theuermann over 16 years ago
Now I´ve tried it with firefox-Browser and everything seems to be alright.
The Problems is definitiv the IE
Updated by Jeff Segars over 16 years ago
Thanks for the heads up guys. I'll look into this early next week.
Updated by Jeff Segars over 16 years ago
Just attached a one line patch that should fix the issue.
The underlying problem is that the button to save constants was changed from a regular input type=submit to an input type=image as part of the docheader improvements. The Constants Editor checks for a particular POST variable to make sure that a submit occurred, but while IE sends the variable for input type=submit, it does not send the variable for input type=image. The one line change checks for the submit_x and submit_y coordinates, which IE does send when the save button is clicked.
Updated by Jeff Segars over 16 years ago
Committed to 4.2.
FYI, this ticket is in the wrong category too (Versioning and Workspaces) and I don't seem to have the ability to change it to TYPO3 Core / Backend either.