Project

General

Profile

Actions

Bug #17993

closed

IRRE fields give 404 alert on Safari

Added by Stefano Cecere almost 17 years ago. Updated over 16 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
-
Target version:
-
Start date:
2008-01-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

very stange

with latest trunk (2890, but checked also with 2891), only on Safari (FF works well)
whenever i click on a Inline record, an Alert with error 404 comes out (i attached screenshot)

my website in at http://localhost/mysite/

(since the alert say "http://localhost" as source)
closed the alert, it seems all had worked well (IE: the open/close of the inline field works)

(issue imported from #M7153)


Files

Picture 2.png (34.5 KB) Picture 2.png Administrator Admin, 2008-01-15 10:07
Actions #1

Updated by Oliver Hader almost 17 years ago

Does this only occour on expanding/collapsing IRRE children? Or do you get this also on creating new child records?
I could not reproduce this behaviour with Safari 3.0.4.

Actions #2

Updated by Stefano Cecere almost 17 years ago

i get the same error (without the action taking place) also creating new records

i am on 3.0.4 too.. maybe beausa i'm in localhost ?

Actions #3

Updated by Oliver Hader almost 17 years ago

The behaviour you mentioned is caused by a failed AJAX request, the this alert will popup. Could you please look into your webservers (error) logfile an tell me the URL that was called? Normally this should be http://localhost/mysite/typo3/ajax.php

I've also tested with an installation in a subdirectory like http://myhost.de/tester/typo3/ but also could not reproduce in FF, IE or Safari.

Maybe cleaning the browsers cache helps, since the old AJAX handler was typo3/alt_doc_ajax.php and was removed yesterday. Possibly this old file is still present in a cached version of t3lib/jsfunc.inline.js...

Actions #4

Updated by Stefano Cecere almost 17 years ago

yes the problem is the localhost

if i change the url from localhost to http://127.0.0.1/

everything works well.

so i think it's a Safari problem / bug. right?

stefano

Actions #5

Updated by Stefano Cecere almost 17 years ago

i did clear all Safari Cache..
and now it works correctly with http://localhost

thanks olivier

Actions #6

Updated by Oliver Hader almost 17 years ago

Puh, good to know that it's no bug of the Core ;)

Actions #7

Updated by Oliver Hader almost 17 years ago

Since this was a caching issue in local web browser, I'm closing this bug.

Actions

Also available in: Atom PDF