Path

ez projects / ezjscore / forum / general / frontendcssfilelist trigger...


FrontendCSSFileList triggered on every siteaccess ?

You need to be logged in to post messages in the forums. New users may register here.

Jerome Despatis

Member since:
11 November 2008

Posts: 20

Tuesday 28 June 2011 2:47:08 pm

Hello

In an extension, I've set my design.ini with:
[StylesheetSettings]
FrontendCSSFileList[]=djgfxstock::flags
BackendCSSFileList[]=djgfxstock::flags

I have also a website with several siteaccess like domain.com/fr, domain.com/en (one siteaccess per language indeed)

Then I clear my cache, and I see that the function djgfxstock::flags is launched on backend and frontend (I'm ok with this), but it's also launched on EVERY siteaccess

I'm hardly sure that, previously ez 2011.4, this function would have been launched only one time for all siteaccess
=> I'm mistaken or logic has really changed ?
Up

Carlos Revillo

Member since:
09 January 2008

Posts: 53

Tuesday 28 June 2011 3:37:19 pm

i don't know if i really understand you well, but imho, it's normal you have it triggered in every siteaccess. if it's is your settings/design.ini and that extension is in ActiveExtensions, then normally this would happen.

So, imho, ez 2011.4 is doing it well, but previous version should work like that too... i don't think logic has changed on this. it should be another thing...


Up

André R.

Member since:
14 January 2008

Posts: 170

Wednesday 29 June 2011 9:09:59 am

The design is that FrontendCSSFileList is triggered on all front end siteaccess, how often depends on your cache-block's.

Lead Engineer eZ Publish
@: http://twitter.com/andrerom

Up

Jerome Despatis

Member since:
11 November 2008

Posts: 20

Thursday 30 June 2011 6:38:00 pm

Ok thanks,

And this logic will never change right?
Up

André R.

Member since:
14 January 2008

Posts: 170

Thursday 14 July 2011 11:13:34 am

Not in eZ Publish 4.x, but for 5.x we can re think the whole thing of course.
If you want to place it outside of the cache block on your project you can do that, but it will probably come at an performance hit, how large depends on the logic you have in those scripts.

First thing on my list for 5.x would for instance be to separate between web site wide scripts/css and pr page scripts/css so that client does not need to re download whole file if there are page variations.

Lead Engineer eZ Publish
@: http://twitter.com/andrerom

Up

You need to be logged in to post messages in the forums. New users may register here.