CF9 and Fusebox4 cache problem?

Report · Nov 11, 2009

We have a strange issue with caching I think as we are trying to upgrade to CF9.

When opening a particular page it sometimes works and sometimes doesn’t; throwing the error ‘fusebox.circuit cannot be defined’ (when it definitely is) and the debugging shows this:

17:06:57.057 - Application Exception - in D:\Web\dgmproAffiliates\fusebox4.loader.cfmx.cfm : line 97

            The specified directory D:\Web\dgmproAffiliates\parsed could not be created.

17:06:57.057 - Application Exception - in D:\Web\dgmproAffiliates\fusebox4.loader.cfmx.cfm : line 101

            The specified directory D:\Web\dgmproAffiliates\plugins could not be created.

17:06:57.057 - fusebox.forceLoadException.fuseboxXmlIsNewer - in D:\Web\dgmproAffiliates\fusebox4.loader.cfmx.cfm : line 145

            fusebox.xml is newer than it's in-memory cache.

17:06:57.057 - MissingInclude Exception - in D:\Web\dgmproAffiliates\fusebox4.runtime.cfmx.cfm : line 170

            Could not find the included template ./fusebox.init.cfm.

17:06:58.058 - Expression Exception - in D:\Web\dgmproAffiliates\fusebox4.parser.cfmx.cfm : line 117

            Element FUSEBOX.PARSEWITHCOMMENTS is undefined in APPLICATION.

But then if I refresh the page it works fine.

We have Fusebox4.

Do we need to upgrade Fusebox as this page was working fine when we were on CF6!

Anyone any idea how to fix this?

Thanks

Report · Nov 11, 2009

Hi KTMardle,

Just delete all the files from your "parsed" directory.

Give appropriate "Read/Write" permisions to the "parsed" directory.

* If you are using "Windows" Goto the properties of the "parsed" folder" and navigate to the "Security" tab and select appropriate permission options

* If you are using Unix/Linux execute "chmod 777 parsed" command.

HTH

Report · Nov 11, 2009

Thanks, but that hasn't worked.

We have another server runningwith CF6 and Fusebox4 and it doesn't have this problem!

Any other ideas?

Thanks

Report · Nov 11, 2009

Hi,

For a moment I thought like, setting 777 for parsed directory might work with this issue.

But, later when I did a search on this on FB forums, I came to know that this behaviour is a known issue, but it wont affect your application in any way.

For more info,

http://www.fusebox.org/forums/messageview.cfm?catid=27&threadid=3813&FTVAR_MSGDBTABLE=

HTH