Project

General

Profile

Actions

Bug #41708

closed

Impossible to update Admin Panel under certain circumstances

Added by Oliver Salzburg about 12 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2012-10-08
Due date:
% Done:

0%

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

Description

Consider the following situation.

1. I have enabled Track content rendering and Display content in my admin panel.
2. This results in certain elements on my page being included in the admin panel itself. Including forms and form elements:

3. When updating the admin panel after changing some settings (for example, disabling the options mentioned above), this instead sends the embedded search form. Thus, redirecting me to the search results page and not updating my settings.

At this point I see no option to disable these settings unless I get my form out of the admin panel first...

Actions #1

Updated by Steffen Gebert about 12 years ago

  • Status changed from New to Needs Feedback

Nested <form> elements are pretty bad :-(

I'm not sure, if there's a way to avoid this. Can you imagine one?

Actions #2

Updated by Oliver Salzburg about 12 years ago

Steffen Gebert wrote:

I'm not sure, if there's a way to avoid this. Can you imagine one?

Right now I'm testing somewhat of a brute-force approach. in class.tslib_adminpanel.php:

@@ -545,7 +545,9 @@ $query . '<table class="typo3-adminPanel">' .
             $GLOBALS['TT']->printConf['flag_content'] = $this->extGetFeAdminValue('tsdebug', 'displayContent');
             $GLOBALS['TT']->printConf['flag_queries'] = $this->extGetFeAdminValue('tsdebug', 'displayQueries');

-            $out.= '<tr><td colspan="2">' . $GLOBALS['TT']->printTSlog() . '</td></tr>';
+            $tslog = $GLOBALS['TT']->printTSlog();
+      $tslog = str_replace( "<form ", "<unform ", $tslog );
+            $out.= '<tr><td colspan="2">' . $tslog . '</td></tr>';
         }

         return $out;

Works great :) The <input> elements are still rendered fine in the admin panel, they just don't affect it any longer.

Actions #3

Updated by Alexander Opitz over 11 years ago

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1)?

Actions #4

Updated by Alexander Opitz about 11 years ago

  • Status changed from Needs Feedback to Closed
  • Is Regression set to No
Actions #5

Updated by Alexander Opitz about 11 years ago

No feedback for over 90 days.

If you think, that this is the wrong decision, then please write to the mailing list typo3.teams.bugs with issue number and an explanation.

Actions

Also available in: Atom PDF