<img alt="Liferay" height="36" src="http://cdn.www.liferay.com/osb-community-theme/images/custom/heading.png" />

Ranking: Junior Member

Mensajes: 32

Fecha de incorporación: 27 de diciembre de 2010

Hi all,

I have a problem when I modify a CSS file of a theme that I have developed. The problem is that the updates that I do to the file docroot/_diffs/css/custom.css don't appear in the pages. When I publish the new theme I see that the file webapps/mytheme-theme/css/custom.css has been updated properly in my production server. However, through Firebug I see that the CSS file doesn't include the updates that I have done.

I have included the following parameter in the file portal-ext.properties: include-and-override=portal-developer.properties. Including this parameter the theme is displayed properly, but that isn't a good solution in a production environment. If I remove the parameter include-and-override=portal-developer.properties and I restart the server, then the new CSS updates are not applied.

I have done all my tests removing my browser cache.

I have also run the following commands through Panel Control -> Server Administration:

Run the garbage collector to free up memory.
Clear content cached by this VM.
Clear content cached across the cluster.
Clear the database cache.

but my CSS updates are not reflected in my pages.

I would be grateful if somebody could help me with this issue.

RE: Liferay 6.1does NOT reload CSS changes

17 de abril de 2012 1:02

Respuesta

Oliver Bayer

Ranking: Liferay Master

Mensajes: 757

Fecha de incorporación: 18 de febrero de 2009

Hi Jose,

you should not modify theme files on your server directly. Why not? Because they are cached therefore it worked as you've deactivated the caches with the portal-developer.properties. You should make your changes in the sdk environment and then deploy the war file to your server. This way you will see all your changes immediately.

HTH Oli

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

17 de abril de 2012 3:20

Respuesta

Ranking: Junior Member

Mensajes: 32

Fecha de incorporación: 27 de diciembre de 2010

Hello Oliver,

Thank you for your help.

I'm sorry, I think that I didn't explain well the issue. The problem is that I always update my theme through the Lifery Plugins SDK and, after that, I deploy the generated war in the production server. I don't know why the changes are not reflected in my pages.

Any sugestions are welcome.

Best regards.

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

17 de abril de 2012 7:38

Respuesta

Ranking: Liferay Legend

Mensajes: 4549

Fecha de incorporación: 1 de septiembre de 2006

Because your browser is caching the CSS. Clear your browser's cache and you'll get the updated CSS.

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

17 de abril de 2012 9:23

Respuesta

Ranking: Junior Member

Mensajes: 32

Fecha de incorporación: 27 de diciembre de 2010

Hello David,

Thank you for your response, but as I said in my previous mail, I have done all my tests removing my browser cache.

Best regards.

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

17 de abril de 2012 9:26

Respuesta

Ranking: Liferay Legend

Mensajes: 4549

Fecha de incorporación: 1 de septiembre de 2006

Hmm, then are you actually using the theme on the page, or might it be referring to a different theme? Just asking, because sometimes folks aren't aware that deploying a theme and actually using it for a page aren't the same thing...

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

17 de abril de 2012 10:13

Respuesta

Alberto Chaparro

LIFERAY STAFF

Ranking: Junior Member

Mensajes: 44

Fecha de incorporación: 25 de abril de 2011

Hi Jose Luis,

Could you do the following test without the parameter include-and-override=portal-developer.properties?

Visit one page in your portal
Change your theme and deploy it
Clean your browser cache
Visit that previous page
Login in the portal
Visit that previous page

If you notice the new changes for the theme in the step 6 but not in the step 4 probably the Cache filter is caching the pages.

Let me know the results.

Best.

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

17 de abril de 2012 14:33

Respuesta

Hitoshi Ozawa

Ranking: Liferay Legend

Mensajes: 8000

Fecha de incorporación: 23 de marzo de 2010

It's just not the browser cache. If you have apache or some reverse proxy server in front of your Liferay, that may also cache your css.

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

19 de abril de 2012 1:15

Respuesta

Ranking: Junior Member

Mensajes: 32

Fecha de incorporación: 27 de diciembre de 2010

Hello Alberto,

Thank you for your help, but unfortunatelly, it didn't work.

I'm going to prepare a new testing server and I will test this issue in the new server.

Thank you!

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

19 de abril de 2012 1:23

Respuesta

Ranking: Junior Member

Mensajes: 32

Fecha de incorporación: 27 de diciembre de 2010

Hello Hitoshi,

I have an Microsoft IIS and an ISA server in front Liferay. But I have tested this problem in the local server (so I workaround ISS and ISA), and the result is the same, is said, the CSS changes are not reflected in the pages.

Thank you for your response.

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

19 de abril de 2012 2:07

Respuesta

Olaf Kock

LIFERAY STAFF

Ranking: Liferay Legend

Mensajes: 1455

Fecha de incorporación: 23 de septiembre de 2008

you can try to download the css directly from the server, see if it changed, e.g. from
http://your.server.name/your-theme/css/custom.css
Then compare it with the result of
http://your.server.name/your-theme/css/custom.css?test
The additional parameter will be ignored, but will guarantee a cache miss in case there's any cache in the line. This way you can safely rule out cache issues (or identify them). The same technique works for the minified version, but that one shouldn't be an issue, given portal-developer.properties

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

20 de abril de 2012 5:55

Respuesta

Ranking: Junior Member

Mensajes: 32

Fecha de incorporación: 27 de diciembre de 2010

I have found the problem. However, I have still another problem related with this one that I will try to solve later.

I think that the problem is related with the new 6.1 version of the plugin SDK. When I execute the task WAR through ANT, it creates a new folder called docroot/css/.saas_cache. Inside this folder I get the file main.css merged with all the css imports that I have in docroot/css/main.css.

The problem is that when I run the task WAR, if the folder docroot/css/.saas_cache already exists in the file system then the file docroot/css/.saas_cache/main.css is NOT updated with the new changes that I do in docroot/_diffs/custom.css. If before executing the task WAR I remove the folder docroot/css/.saas_cache, then the file docroot/css/.saas_cache/main.css is generated properly and when I deploy the new theme it works fine.

I work with a Windows machine, and I think that the problem maybe is caused because the .saas_cache folder starts with a dot. I believe that in a Linux machine this could work fine.

Another problem that I'm getting now is that I have made another updates in another theme and in English language the updates are not reflected but in Spanish language they are. I will try to solve this problem later, although if you have any suggestion it will be welcome.

Best regards!

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

20 de abril de 2012 6:04

Respuesta

Ranking: Liferay Legend

Mensajes: 4549

Fecha de incorporación: 1 de septiembre de 2006

Hmm, if you copy the main.css into the diffs_/css folder, would it force the update during the build?

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

20 de abril de 2012 7:59

Respuesta

Ranking: Junior Member

Mensajes: 32

Fecha de incorporación: 27 de diciembre de 2010

Hello David,

Yes, if I copy the main.css file into _diffs/css folder, it forces the update during the build.

I think that with 6.0 version this was not necessary...

Regards!!

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

20 de abril de 2012 9:27

Respuesta

Ranking: Liferay Legend

Mensajes: 4549

Fecha de incorporación: 1 de septiembre de 2006

Well, 6.0 didn't have the sass support...

I'm glad it's working now, though, and it sounds like we have a solid answer to give people if it comes up again!

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

20 de abril de 2012 9:29

Respuesta

Ken Sperow

Ranking: New Member

Mensajes: 5

Fecha de incorporación: 25 de abril de 2011

Thanks for figuring this out. I was running into this exact same issue within Linux yesterday and came across this post. I did not have this issue in 6.0.6 but it looks like the .sass-cache was being used then (at least not within our installation).

Copying main.css to the _diffs/css/ folder solved the issue for me as well.

Thanks

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

20 de abril de 2012 13:53

Respuesta

Ken Sperow

Ranking: New Member

Mensajes: 5

Fecha de incorporación: 25 de abril de 2011

I replied prematurely. Did this completely solve the issue for you? While the custom.css file within the .sass-cache directory does get updated (i.e. copied from the _diffs/css directory), the main.css file in .sass-cache/css does NOT include the updated custom.css entries from the _diffs directory. The result is that our theme is not behaving as one would expect on a production machine.

Thanks for any feedback.

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

23 de abril de 2012 0:03

Respuesta

Ranking: Junior Member

Mensajes: 32

Fecha de incorporación: 27 de diciembre de 2010

Hello Ken,

I have had to update another time my CSS, and it is working fine for me. I only copied the file main.css from MY_THEME_ROOT/docroot/css/main.css to MY_THEME_ROOT/docroot/_diffs/css/main.css, and it works.

Regards!

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

18 de mayo de 2012 17:54

Respuesta

Bill Dolan

Ranking: New Member

Mensajes: 9

Fecha de incorporación: 28 de junio de 2010

I have this same problem with CSS. I have to completely delete both old WAR file and the /docroot/css folder. Then I build and WAR and deploy and it works. Copying main.css did not work reliably for me.

The weird thing is this is just for my online environment (Liferay 6.1 CE (Paton / Build 6100 / January 6, 2012). My local environment, which is the exact same version works fine with no extra steps, just hot-deploy from eclipse and go. So the only difference is I am using the plug-in installer to deploy in the online environment.

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

1 de agosto de 2012 5:40

Respuesta

Munish Sharma

Ranking: New Member

Mensajes: 11

Fecha de incorporación: 13 de julio de 2012

hi,

Still I have the same problem, I did all the above mentioned changes in my custom theme. Complete process that i have followed:
1) I create a custom theme by Liferay IDE and provide the parent theme as "Classic" by changing in new_theme/docroot/ build.xml file by (<property name value="classic"> tab).
2) It will copy the classic theme in our newly "created theme " , we can see the changes under the docroot/css/custom.css after deploying it.
3) After that I copied the new_theme/docroot/css/custom.css file to new_theme/docroot/_diffs/css/custom.css and also copy the main.css in it.
4) Now if I am trying to change something inside the new_theme/docroot/_diffs/css/custom.css file then , its not effecting on the home page.

Plz help me ASAP.
Any sugestions are welcome...

Best Regard.

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

1 de agosto de 2012 6:27

Respuesta

Munish Sharma

Ranking: New Member

Mensajes: 11

Fecha de incorporación: 13 de julio de 2012

Hi,

Now my changes, which i did in custom.css are reflecting on the home page .
I added the simple below code inside portal-ext.properties file:

include-and-override=portal-developer.properties

Now my custom theme is working fine.

Thanks emoticon

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

23 de agosto de 2012 11:23

Respuesta

Orin Fink

Ranking: Junior Member

Mensajes: 37

Fecha de incorporación: 24 de marzo de 2010

Jose Luis Monteagudo:

I think that the problem is related with the new 6.1 version of the plugin SDK. When I execute the task WAR through ANT, it creates a new folder called docroot/css/.saas_cache. Inside this folder I get the file main.css merged with all the css imports that I have in docroot/css/main.css.

I second the notion that something has changed in the 6.1.1 (specifically 6.1.1) version of the SDK. We have been using 6.1 and building deploying just fine for 6 months. After an update to the 6.1.1 SDK, we have now had to start make sure that we delete the {theme-folder}/css, {theme-folder}/js, {theme-folder}/templates (the ones OUTSIDE of {theme-folder}/_diffs. Those are the folders that had been created from a previous ANT run. As long as those folders are removed and we run the ANT WAR against a theme directory that just has _diffs and WEB-INF in it... things seem golden. This should ensure that the newest CSS files are included in the WAR.

I think also that we have noticed this only being an issue when running the build on a server. doesn't seem to be an issue on our development environments.

Marcar como respuesta

RE: Liferay 6.1does NOT reload CSS changes

14 de septiembre de 2012 8:15

Respuesta

Theoni Zaharia

Ranking: New Member

Mensajes: 21

Fecha de incorporación: 21 de febrero de 2012

Hi all!
I experience the same problem, with an installation of liferay 6.1.1 bundled with JBoss. the thing is I cannot find the folder _diffs....It sounds a bit strange, I know, but could it be it has a different name or something in this installation?
thanks in advance!

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

14 de septiembre de 2012 8:16

Respuesta

Theoni Zaharia

Ranking: New Member

Mensajes: 21

Fecha de incorporación: 21 de febrero de 2012

Munish Sharma:

That did it for me, too, thanks!

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

6 de octubre de 2012 20:21

Respuesta

Gabriel Ramirez

Ranking: New Member

Mensajes: 1

Fecha de incorporación: 6 de octubre de 2012

The problem is a new parser for CSS's in Liferay 6.1, if your CSS has any non complaint code the entire CSS file is rejected and not included in the main.css compiled. Make sure that your CSS is well formated and you are ready to go.

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

10 de octubre de 2012 6:13

Respuesta

Marcin Maciukiewicz

Ranking: New Member

Mensajes: 24

Fecha de incorporación: 18 de julio de 2012

Is there any way to see which error prevent the css to be loaded? I've prepared totally minium modification on the custom.css extracted from the classic theme but it looks like it have been rejected by the compiler.

Or maybe I should refresh some cache?

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

10 de octubre de 2012 6:15

Respuesta

Marcin Maciukiewicz

Ranking: New Member

Mensajes: 24

Fecha de incorporación: 18 de julio de 2012

You have wrote that the css should be well formated - could you post an example of custom.css file which is compiling and correctly used by the liferay?

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

14 de enero de 2013 14:43

Respuesta

Adel Frad

Ranking: New Member

Mensajes: 19

Fecha de incorporación: 4 de agosto de 2012

Try to open the xml file build-common-theme.xml under the themes folder in your sdk and remove all the preservelastmodified="true" (or set them to false).
preservelastmodified, when true will not update the files timestamp in your theme project. Your application server will not detect the changes and redeploy the theme.

www.themeray.com

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

1 de febrero de 2013 3:51

Respuesta

Tirthal Patel

Ranking: New Member

Mensajes: 2

Fecha de incorporación: 3 de enero de 2011

I was getting the same mentioned issue. I implemented theme by extending "classic" as parent theme.

* Problem statement: I am using Liferay SDK 6.1. On windows machine, I was not getting any issue. Then I switched to Linux development environment, imported the same theme project in to Eclipse, built "war" using Liferay SDK and deployed to another Liferay Portal Server. On another server when I applied my developed custom theme, changes were not getting applied.

* Solution worked for me: Liferay SDK -> Execute clean task first and then build war.

* Why it worked? - All custom css files are always under "_diff" folder during Liferay Theme Plugins development, which may include css to override Liferay's OOTB classic theme. Then when we execute "war" build using Liferay SDK, it copies all css files under <theme-name>/css/.sass-cache and in which main.css includes all imported css files code. Due to some odd issue, main.css was not getting updated and hence not reflecting on my deployment server. So I just did "clean" task execution and then "war" build using Liferay plugin SDK. It worked for me.

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

12 de mayo de 2013 13:08

Respuesta

Konstantin Chudinov

Ranking: New Member

Mensajes: 23

Fecha de incorporación: 23 de abril de 2013

Yeah, I have the same issue. And copying main.css doesn't help. It's really annoying to delete .sass-cache folder every time, especially when I'm working on Linux, where ls -l command is not displaying this folder.
rm -rf
is only solution i've found

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

12 de mayo de 2013 23:10

Respuesta

Mirto Silvio Busico

Ranking: New Member

Mensajes: 16

Fecha de incorporación: 18 de enero de 2012

Just curious,
why you don't use

ls -la

This shows everi .* file

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

12 de mayo de 2013 23:39

Respuesta

Konstantin Chudinov

Ranking: New Member

Mensajes: 23

Fecha de incorporación: 23 de abril de 2013

Of course I can emoticon

But it is still ugly solution - everytime call linux command before deploying theme

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

15 de mayo de 2013 1:20

Respuesta

Munish Sharma

Ranking: New Member

Mensajes: 11

Fecha de incorporación: 13 de julio de 2012

Tirthal Patel:

Hello everyone,

You can try with this solution, I am sure this will work for every developer who is working with theme development :
theme.css.fast.load=false

The purpose of theme.css.fast.load property is to tell whether css should be cached or not. If it is cached, it can be loaded faster.

If you are working on theme development, you will change css code and would like to see the changes on the browser immediately .
Therefore you need to disable caching by setting theme.css.fast.load=false

Regard :
Munish Sharma

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

16 de mayo de 2013 8:34

Respuesta

Peter Dimitri

Ranking: Junior Member

Mensajes: 30

Fecha de incorporación: 9 de enero de 2013

Has anybody got this problem solved when using the "classic" theme as parent theme, without switching Liferay into developer mode? Yes, it works for me, when I enable developer mode, but that's no solution for a production server. I've tried all suggestions from above, but running "ant clean" before running "ant deploy" only works when my parent theme is the "_styled" theme.

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

16 de mayo de 2013 11:08

Respuesta

Konstantin Chudinov

Ranking: New Member

Mensajes: 23

Fecha de incorporación: 23 de abril de 2013

Peter Dimitri:

What do you mean, "developer mode" and "prodaction mode"? what the difference between them in your case?

Marcar como respuesta

RE: [SOLVED] Liferay 6.1does NOT reload CSS changes

17 de mayo de 2013 0:51

Respuesta

Peter Dimitri

Ranking: Junior Member

Mensajes: 30

Fecha de incorporación: 9 de enero de 2013

Konstantin Chudinov:

What do you mean, "developer mode" and "prodaction mode"? what the difference between them in your case?

For Information about developer mode see here: http://www.liferay.com/community/wiki/-/wiki/Main/Liferay+Developer+Mode

In nutshell, while your server is in developer mode it sends the style informations of a theme in individual files, which won't be cached by the server, whereas in production mode everything will be read from a single new main.css file, which is generated during the build process from the SDK. Of course this improves the servers performance when serving HTML pages.

Just inspect a page, themed with your custom theme with firebug. As long as the server is set to developer mode, the css you modified in your custom.css will be read from custom.css. Now switch developer mode off and restart the server (no new deployment of the theme!) and now the same css will be read from main.css

When you create a new Liferay Theme with the SDK, there will be a main.css file, which only has some @import statements in it. Here, custom.css will be loaded last, and the styles you define in custom.css will override any conflicting css statements in any css files loaded earlier. You'll find these files in /ThemeFolder/css and they will be used while the server is in developer mode.
But when you switch off developer mode, these files are ignored and instead the files from /ThemeFolder/css/.sass-cache are used, where main.css now is a mixture of the contents from your custom.css and style information of your parent theme. This MAY work, as in my case when I use the "_styled" theme as the parent theme, but there may be conflicting style information in this mixed-up file, as I'm experiencing when I use the "classic" theme as parent theme.

Because in developer mode css files won't be cached by the server, and served as individual files, this slows down the server. That's why I say it's not a solution for this problem in production servers.