Classic Theme bug under SSL with Internet Explorer

[Luis Colorado, geändert vor 17 Jahren.]

Hello, everybody!

I am running Liferay under SSL, and so far it seems to run smoothly. However, when I use the classic theme with Internet Explorer 6 and 7, the animated menu (I don't know really how to call it) at the top right doesn't show the icons properly, but it instead paints solid color blocks. The menu and the animation is still functional (I still can switch communities, add portlets, and so on), but the icons are not shown.

It seems like a problem related to transparency (or the lack of it). The solid boxes are the same color of the current color scheme.

Has anybody run into this? Is there a fix in trunk or version 4.3?

Should I post a bug for this problem?

Thank you,

Luis

[David Bretzke, geändert vor 17 Jahren.]

I'm running LPP 4.2.0 under SSL as well. Running on Tomcat and all of our users use IE6. I have not seen nor heard for anyone who has seen this problem.

I like the Classic theme, but honestly dislike the AJAX menu control you are referring to...looks cool, but not intuitive to users unless they happen to rollover it.

But, no problems here under similar situation.

Dave

[Luis Colorado, geändert vor 17 Jahren.]

Thank you for replying!

Indeed... I share your opinions completely ... my peers loved that animated control, but my manager was totally annoyed by it... oh, well!

Now, regarding to the bug, I think I fixed it. Apparently the problem occurred due to the following fragment of code:

	<security-constraint>
		<web-resource-collection>
			<web-resource-name>/c/portal/protected</web-resource-name>
			<url-pattern>/*</url-pattern>
		</web-resource-collection>
		<user-data-constraint>
			<transport-guarantee>CONFIDENTIAL</transport-guarantee>
		</user-data-constraint>
	</security-constraint>
	<security-constraint>
		<web-resource-collection>
			<web-resource-name>/c/portal/protected</web-resource-name>
			<url-pattern>/*</url-pattern>
			<http-method>GET</http-method>
			<http-method>POST</http-method>
		</web-resource-collection>
		<auth-constraint>
			<role-name>users</role-name>
		</auth-constraint>
		<user-data-constraint>
			<transport-guarantee>CONFIDENTIAL</transport-guarantee>
		</user-data-constraint>
	</security-constraint>

This occurred apparently because I forgot to comment out the second security-constraint. I'm not clear about why this happened, but here's the fixed code (note the commented out code starting at line 11):

	<security-constraint>
		<web-resource-collection>
			<web-resource-name>/c/portal/protected</web-resource-name>
			<url-pattern>/*</url-pattern>
		</web-resource-collection>
		<user-data-constraint>
			<transport-guarantee>CONFIDENTIAL</transport-guarantee>
		</user-data-constraint>
	</security-constraint>
	<!--security-constraint>
		<web-resource-collection>
			<web-resource-name>/c/portal/protected</web-resource-name>
			<url-pattern>/*</url-pattern>
			<http-method>GET</http-method>
			<http-method>POST</http-method>
		</web-resource-collection>
		<auth-constraint>
			<role-name>users</role-name>
		</auth-constraint>
		<user-data-constraint>
			<transport-guarantee>CONFIDENTIAL</transport-guarantee>
		</user-data-constraint>
	</security-constraint-->

Thank you for looking!

Luis