Bug #16295
closed
SQL check breaks on IE due to DOM/CSS usage
Added by Martin Kutschker over 18 years ago.
Updated almost 11 years ago.
Category:
Database API (Doctrine DBAL)
Description
The form for entering the "easy" query doesn't work at all on IE (property "display" is missing - IE doesn's support "table-row" anyway) and doesn't work reliable in Firefox (the displayed fields seldom reflect the select box setting). I have no idea how to enter data for an insert statement.
[rant]Don't use DOM when it's not necessary. Instead of a working old-school app this is a fancy non-working tool[/rant]
(issue imported from #M3754)
Hm, works fine for me in Firefox 1.5 on Linux. I'll take a closer look.
When switching back from UPDATE to some other query type, there was one field left visible. Fixed this now for Firefox, will check in MSIE.
Ok, it doesn't work at all with MSIE6. But, do I care? This is mainly a tool for my own use, that happens to be available publicly. :)
If someone wants to fix this, go ahead. I won't.
About entering data for INSERT: I added this to the manual.
If it's only an internal tool it should go (into a separate extesion). Don't clutter up the TYPO3 modules with DEBUG stuff. It's crowded enough!
See my original note why it doesn't work in IE. The easiest solution is to use a CSS class "hide" and to add remove this class when toggling visibility.
But I think the DB info (oddly named "cached info") may be of interest for more users. It could be a replacement for phpMyAdmin in the long run...
- Priority changed from -- undefined -- to Could have
- Target version deleted (
0)
- TYPO3 Version set to 3.8
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
- Status changed from Accepted to Needs Feedback
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
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.
Also available in: Atom
PDF