Profile CSS Account not always load cache refresh

First of all, Boonex, could you increase the limit on a forum topic title; it is next to impossible to put in a title that means anything.

I have a little problem with a custom modification I did to my site that maybe some can help me to understand.  I added the bits and pieces necessary to place the custom css code from the profile page to the account page and my members really liked it; as it makes their account page mimic the styling they did on their profile page.  Most of the time the code loads in as it should.  However, sometimes it fails to load which I suspect is due to Dolphin refreshing the caches; does Dolphin run a cron job that clears and refreshes the caches?  When the custom css fails to load I see the key for the custom CSS displayed.  I can manually clear out the caches and then the account page once again will load in the custom CSS and work for a period of time; don't know if it is a week, two weeks, or what as I have not track the timing.

Caches are not cleared upon cron, it is cleared in the following cases:

- user clears it via admin or delete files directly via FTP or SSH

- some module reinstallation (different modules clears different caches)

- during upgrade and domain or Dolphin version change

However I've some some bug in cache generation! The problem was that if cache is empty (or cache file is missing), and cache file is accessed directly via url (without opening the page where it is used) then empty cache file is created. After that the page where cache file is used loaded without css and it looks like the page without css or js files.

http://www.boonex.com/trac/dolphin/ticket/3159

Changeset: http://www.boonex.com/trac/dolphin/changeset/17588

That could be related; although the normal css for the account page does load.  I will see the key which is something like _page_main_css or something like that; which is the key for the profile customiser which I added to the account page.  Normally I can go to admin, refresh the caches and it will reload the css that the key represents.  Today I had to flush the file caches as well.  It is a nice modification but for this little bug.

_page_main_css_

That is the key that loads in the custom css stored in the database for the profile customiser.  I added that key to the account page; adding the bits of course that gets the user ID and then replaces the key with the actual css.  This makes the account page reflects the user's profile page and they were very happy with this addition.

However, at times the key is not replaced; and the key will show up as text on the page.  I can go into the admin and clear the caches; sometimes it takes several clearing, and then I can go to the account page and the css is added as it should be.  I never see this problem with the profile page, it is only the account page where I added the profile customiser code so the account page would be the same as the profile page CSS-wise.  Since clearing the caches in the backend restores the page; and by the way, I have the cache for CSS turned OFF in the backend so it is not that, it would seem related to the cache; however, that could be unrelated although clearing caches does restore it.  It may go a week before it does this "failure".  The other day I did go in and clear the file caches as well since it did not seem to restore with an admin cache clear.

Just trying to figure out why it would "fail" at times.  My members want this added to their blog post view but I need to have it working 100%.