Well, it seems as if it did happen to me.
Marc Dirix wrote:
I haven't taken the time at the moment to reproduce the problem and I seriously doubt if I can. Now that the error is spotted, the module only compiles now if the error is fixed. One thing I can say though, is that I've equipped every Roxen module with a creation time stamp because I had a gut feeling before that after reloading a module and it's related code Roxen didn't always use the latest version of the code (either correct or incorrect)
In Roxen, I've seen caching to sometimes be a bit to thorougly (editing files does not clear them in cache automatically). However a Roxen restart and /or Flush Cash from the admin interface always reloads them.
Persisten cash for modules, between Roxen starts, has never happend to me.
__________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________