Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script-Error with Firefox in ADE sitemap editor #76

Closed
kartobi opened this issue Sep 4, 2012 · 7 comments
Closed

Script-Error with Firefox in ADE sitemap editor #76

kartobi opened this issue Sep 4, 2012 · 7 comments

Comments

@kartobi
Copy link
Contributor

kartobi commented Sep 4, 2012

Firefox pops up an alert window "Warning: Script not responding ..." when opening the sitemap editor.

Seems only to happen when the level of my current page is four or more.

@tHerrmann
Copy link

I can not reproduce this issue, please state which Firefox version and OpenCms version you are using.

@benocms
Copy link
Contributor

benocms commented Nov 9, 2012

This problem only occurs with large sitemaps.

@tHerrmann
Copy link

Please check out OpenCms version 8.5. We did some performance enhancements on the sitemap editor for that version.

@kartobi
Copy link
Contributor Author

kartobi commented Nov 12, 2012

Uh, can't remember the firefox version two months ago. But still occurs with current version 16.0.2
OpenCms version is 8.0.4

I'll give 8.5 a try...

@ladislavovic
Copy link

I have the same problem. It is due to loading these resources:

resources/filetypes/containerpage_big.png
resources/filetypes/image_big.png
resources/filetypes/pdf_big.png

Their loading takes about 9.5 second (loading starts at the same time, it waits about 9.5 seconds and all finish at the same time).
When I write url to some of those resources directly to browser address bar, the resource is returned immediately without waiting.

OpenCms 8.0.4, Firefox 12 (CentOS) and 17.0.1 (Windows 7).

In Chrome 23 (Windows) it works properly.

@tHerrmann
Copy link

Please check if this issue remains in version 8.5.1 other wise I will close this issue.

@tHerrmann
Copy link

I assume this issue is resolved with release version 8.5.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants