CSS Incorrect when css_fast_load=true

• Type: Bug
• Status: Closed
• Resolution: Inactive
• Affects Version/s: 6.1.1 CE GA2
• Fix Version/s: None
• Component/s: Frontend Infrastructure, Themes Infrastructure
• Labels:
  • community-verifier
  • theme.css.fast.load
• Environment: Reproducable in multiple environments including standard tomcat bundle and WAR deployment under existing Tomcat installation.

Deploying custom theme in development environment works correctly. In production environment with theme.css.fast.load=true (by default), the CSS attributes are being calculated differently. Adding "?css_fast_load=0" to the URL in production resolves the issue temporarily.

The new theme is based on the "classic" theme and rather than copy and modify the entire "custom.css", we have modified "main.css" to include "theme.css" as the last import. This technique works fine and makes version control and upgrade much easier given the minimal changes we are making to the classic theme.

theme.css

@import url(color_schemes/manl.css);

#wrapper {
    background-image: url(../images/custom/wrapper_bg.png);
    background-repeat: no-repeat;
}

#sign-in {
	top: 0;
}

#banner {
    background-image: url(../images/custom/banner_bg.png);
    background-repeat: no-repeat;
    background-position: 90% top;
}

#heading {
    height: 131px;
}

The panels below show Firebug's capture of the CSS delivered in each of the two scenarios.

main.css with ?css_fast_load=1

#wrapper {
    background: none repeat scroll 0 center transparent;
    margin: 0 auto;
    max-width: 90%;
    min-width: 960px;
    position: relative;

main.css with ?css_fast_load=0

#wrapper {
    background: none repeat scroll 0 0 transparent;
    margin: 0 auto;
    max-width: 90%;
    min-width: 960px;
    position: relative;

Note the different interpretation for the "background" tag!!! It is the "center" vertical alignment that is causing our production issue.

[Alberto Chaparro]

Hi Peter,

While we futher investigate this issue, could you try the following workaround?

• Copy the file main.css located in {theme_path}/docroot/css/ to {theme_path}

  /docroot/_diffs/css and deploy the theme (in Linux you could need execute the touch command to change the modification date)

Please, let me know if this solves your problem.

[Aniceto P Madrid (Inactive)]

Peter, Ivano
Can you tell me if this issue is stillin 6.2.0m4? Here you can download bundles http://sourceforge.net/projects/lportal/files/Liferay%20Portal/6.2.0%20M4/
Thanks

[Peter Hancox]

Hi Aniceto,

I'm out of the office until next week and not actively working on Liferay at the moment. I'll try and check for you but as yet haven't set up an environment for milestone installs so it'd be a couple of weeks at best before I can verify for you.

Apologies
Peter

[Aniceto P Madrid (Inactive)]

I'll wait.
Thanks

[Edward Gonzales (Inactive)]

Hello everyone! We are in the process of moving component "Theme" to "Theme > Dev" in LPS. Please make the necessary adjustments to your filters. Thanks!

[michele zanarotti]

Actually I'm experiencing the same exact thing with 6.2 GA1 (CE)

We have a theme inherited from classic theme.

With theme.css.fast.load = false everything works fine.
With theme.css.fast.load = true the loading is referred to the original theme, as if there where no changes in the theme. So i see the site pages messed up.

On the contrary I never experiences this on 6.1.