Opened 12 years ago

Closed 11 years ago

#1350 closed defect (duplicate)

ExtendedFileManager, IE7 Error, when changing files_url

Reported by: guest Owned by:
Priority: normal Milestone: 0.96
Component: Plugins Version: trunk
Severity: normal Keywords: ExtendedFileManager IE7


IE7 shows Error when using the ExtendedFileManager?. The List of files is empty. That occours when changing the files_dir. Firefox works fine with all settings. I tried different paths. Relativ, Absolute. With all this settings Firefox works but IE shows:

( on nightly / but the same error with final version )

Zeile: 98
Zeichen: 9
Fehler: f_url.length ist Null oder kein Objekt
Code: 0

The problem occurs too, when i use the path, i use for the images_dir or when i change

$IMConfig['resized_prefix'] = 'resized_';

Change History (3)

comment:1 Changed 12 years ago by guest

Now i know why. I seached a long time. I had a working config. And i compared them. And now i find it.

            $IMConfig['allowed_link_extensions'] = array("jpg","gif","pdf","ip","txt",

is too long.

When i change it, that there a not so many items, than it works fine.
And there is break point. When i reached the exact breakpoint, then there is an other error. In the file list is shown, that the webpage couln´t be loaded.

This produces the other error:

            $IMConfig['allowed_link_extensions'] = array("jpg","gif","pdf","ip","txt",

I don´t know if this has to do with other configuration options. But if there are less items in the declaration, then there is no error.

I hope this will help someone.

comment:2 Changed 12 years ago by guest

Now i make a new experience using firefox.


is too long than

            require_once XINHAPFAD.'contrib/php-xinha.php';

does not work. The $IMConfig information are not transported the efm.

comment:3 Changed 11 years ago by gogo

  • Resolution set to duplicate
  • Status changed from new to closed

I think I know what's happening here, you're hitting the maximum length of a URL. Your IMConfig must be VERY big and as it's passed in the URL, we have a problem there.

  • We could change to using POST, that's quite hard because the "composed" URL is passed around a lot, and we'd have to change how that works.

I'm going to dup this to that ticket because I think it will be resolved there.

Note: See TracTickets for help on using tickets.