[MAGNOLIA-2958] (Local?) Magnolia 4.1/4.2 AdminCentral often does not display right in Firefox 3.5 Created: 26/Nov/09  Updated: 04/Aug/15  Resolved: 04/Aug/15

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.1.1, 4.2.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Will Scheidegger Assignee: Philipp Bärfuss
Resolution: Outdated Votes: 0
Labels: display, firefox
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OS X 10.6.2, Firefox 3.5.5, Magnolia 4.1.1 or 4.2.1 installed locally, accessed via http://localhost:8080/...


Attachments: JPEG File screenshot-1.jpg    
Issue Links:
relation
is related to MAGNOLIA-1959 Leopard (osx 10.5) issues Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When trying to work with Magnolia on Firefox 3.5 often half of the content is missing. Since "half of the content" usually means css and js files, this makes Magnolia pretty much useless. Here are some screenshots:

http://www.fastforward.ch/projekte/magnolia/magnolia_4_display_problems/



 Comments   
Comment by Will Scheidegger [ 26/Nov/09 ]

BTW: I don't see the problem on our Mag 4.1.1 pre-released trunk version properly installed on a server accessed via Apache

Comment by Jan Haderka [ 26/Nov/09 ]

So can you do the diff of the version that works in comparison to 4.1.1 tag?

Comment by Will Scheidegger [ 26/Nov/09 ]

diff of what? I'm not sure if the problem is situated in the admin interface module. Could also be a cache problem - at least last time (Mag 3.2?) it was a cache problem.

I will install a Magnolia 4.2.1 version this weekend on the same server (the exact same version that gives me problems here locally). Let me check first, if this works.

Comment by Jan Haderka [ 26/Nov/09 ]

Diff between your pre-release trunk copy and the 4.1.1 tag ... over all modules that make CE.

Comment by Philipp Bärfuss [ 04/Dec/09 ]

The issue is caused by a problem on OSX. While the latest version of 10.5 worked well the 10.6 series has again the same issue.

Till now we don't know what really causes the issue but we know that the following workarounds help:

  • use apache in front
  • putting only one magnolia webapp per tomcat
Comment by Jan Haderka [ 22/Apr/10 ]

Still having the same issue with 10.6.3.
The problem seems to be related to the max number of file handles allowed to be open by user. I'm not able to get over 1200 which is not enough to run 2 Magnolia instances in one tomcat.

Comment by Michael Mühlebach [ 04/Aug/15 ]

We're closing this issue as outdated as it was reported for 4.4.x or earlier versions which are no longer supported. Don't hesitate to reopen or create a new ticket in case this is still relevant and you'll experience it on 4.5.x or later versions.

Generated at Mon Feb 12 03:41:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.