config.cache_classes preventing omniturize from getting proper vars

[slabgorb]

Hi Javier- thanks for the code. I am using your gem in a current project, and I am having trouble only in production mode- I tracked it down to 'config.cache_classes'- if I turn this off, the gem works great, if I turn it on, every controller gets the same vars set, even though it appears to be using the proper reporter for the controller.

Any ideas as to what I am doing wrong?

thanks
Keith

[eLafo]

Hi Keith, I haven't had any issue in production mode. Which version of the gem are you using?

[slabgorb]

Thanks for replying, Javier- I am using a fork of the latest gem version (forked from master branch), on a rails 3.0 project. I have been hacking at this a bit, looking into removing the rails cache code from the meta var gem calls... that didn't seem to do it, although I may still need to do that a bit more systematically.

[slabgorb]

By the way, the inherited vars are great and very compelling.

[eLafo]

Thank you very much for the compliments, Keith :-D

I can only guess without seeing any code of yours, but It seems to me that the problem may be related to the way meta_vars gem is being used by the omniturize gem, or even that there is a bug in the meta_vars gem.

Have you defined a namespace for each controller? It occurs to me that if you are definining meta_vars with the same name and namespace -or no namespace for it matters- in different controllers, you may experiment unexpected behaviours.

In the macro has_meta_var, you can declare a default_namespace as follows:

class FooController
has_meta_var :my_meta_var, :inheritable => true, :default_namespace => 'namespace for this controller'
end

You have more info in https://github.com/eLafo/meta_vars

Once again, I am only guessing, so if you could paste some example code I will be glad to help you.