Bug #18670
closed
alt_db_navframe.php often replaced by db_list.php without content under 4.2.0RC1 and RC2
Added by Anonymous over 16 years ago.
Updated about 11 years ago.
Description
alt_db_navframe.php often replaced by db_list.php without content under 4.2.0RC1 and RC2,
It is necessary to go "back" within the "menu" frame.
Extremely annoying, and very confusing for users less skilled.
Usually when performing some actions in the page properties, e.g., saving (and closing), etc.
Apparently some javascript problem.
I can reproduce it very often (more than 50% of cases).
It looks like it is related to Opera (I am using 9.27).
Typo3 BE was always working fine in Opera; however it is not true from v.4.2.0.
(issue imported from #M8202)
Files
can you please describe an exact way how to reproduce?
This is not for Steffen. It is a general note.
Please note that I am sponsoring a bug which didn't need to exist at all in first place, and which didn't exist in the past. So it is just someone's negligence.
Instead of creating similar problems, please focus on better job.
For Steffen:
1) Please go to Opera (e.g., the latest one).
2) Create a new page.
3) Save it.
4) And you should receive a right frame within the middle frame (without a specific content), while right frame remains as it should.
I will supply a screenshot for better understanding.
hard words. You should know that 4.2 made a big step in the BE, many frames disappeared.
This issue you describe is Opera only, and i'm not sure if it's because of some wrong JS-handling in Opera, same problem like FF3.
So all devs working on core do a good job, look to the changelog and count the fixed bugs ;-)
Dear Steffen,
I appreciate your words. And I am sure that many frames are away now. However, this is a "problem" which didn't exist, and exists now.
Yet, I am willing to put some money for fixing something which shouldn't happen in the first place.
By the way, the frames were not a problem, especially not for the backend. To try to substitute them by AJAX behaviour, is not a win situation. It is only becoming more fragile and error-prone from the future point of view (and I am not talking just about cross-browser compatibility problems).
And I would be more happy to pay (and to pay more money) for development of new, good features, than for fixing something like this.
Thanks for understanding.
Hey Tomas,
does the issue still apply to a stable 4.2 and/or the latest alpha of 4.3?
Thanks for the info!
Hi Ben,
Why do you ask me? Is it so difficult to test this?
I did two quick tests in Opera (otherwise I use Firefox for Typo3 backend, because I don't know whether I could rely on functionality in other browsers).
These two tests were without problem regarding this issue (there is another issue, but it is irrelevant for this report). I am talking about Typo3 4.2.8.
I don't use 4.3 alpha.
Kind regards, T.
- Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback for over 90 days.
Also available in: Atom
PDF