Project

General

Profile

Actions

Bug #16895

closed

Target in secondary options doesn't work

Added by Steffen Gebert almost 18 years ago. Updated over 17 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2007-01-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.1
PHP Version:
5
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When editing page properties and trying to set/change/delete a target for the page, the new target is not saved, if the secondary options are on the top frame (clicking on the icon next to Pagetitle). If the sec. options are shown within the main form, target gets saved.

(issue imported from #M4852)


Files

typo3_target.gif (4.81 KB) typo3_target.gif Administrator Admin, 2007-01-24 15:00

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #16877: typo3 not defined in jsfunc.tbe_editor.jsClosedOliver Hader2007-01-22

Actions
Actions #1

Updated by Martin Kutschker almost 18 years ago

Do other options work? I rarely use the secondary options in top frame but I think I noticed onec a failure like the one you describe.

Actions #2

Updated by Steffen Gebert almost 18 years ago

It seems that none of the text fields in secondary options works (alias, target, last change, new...)

Can anyone reproduce it? I think this might be a quite important bug to fix before release.

Actions #3

Updated by Oliver Hader almost 18 years ago

Do you possibly get any javascript errors? Did this problem exist in 4.1-beta2 or general in other versions before?

Actions #4

Updated by Steffen Gebert almost 18 years ago

I'm quite sure that this bug didn't exist in beta2.

Firefox-Error-Console tells me "typo3 is not definied in /typo3/jsfunc.tbe_editor.js:
typo3.formFieldSet(theField, evallist, is_in, checkbox, checkboxValue);

But this error occurs while activiting the secondary-options-pane. While saving, no errors occur.

The problem exists in FF and in Opera (IE not tested).

Can't you reproduce it?

Actions #5

Updated by Oliver Hader almost 18 years ago

Okay, this problem has been fixed for 4.1-RC1. Please have a look to bug-id #16877 and update your TYPO3 source using SVN or appying the patch at the mentioned bug-report.

Please give me a short feedback if the bug is fixed afterwards.

Actions #6

Updated by Oliver Hader almost 18 years ago

This bug is related to bug-id #16877 which is already fixed in SVN Trunk for TYPO3 4.1-RC1.

Actions

Also available in: Atom PDF