I'm sorry man :(
I'll get this issue fixed today!

-- Yehuda

On Tue, Dec 30, 2008 at 7:40 AM, phoet <[email protected]> wrote:

>
> I just tried out a little merb and i thought that i was to stupid to
> use it, or that this framework is just stupid.
>
> So now i'll have to wait until next year for my investigations ...
>
> Happy new Year!
>
> On 30 Dez., 08:00, "Yehuda Katz" <[email protected]> wrote:
> > I believe this was a bug introduced by some new caching I added. I will
> do a
> > quick release tomorrow to solve a few regressions :/
> > I hope this does not become a pattern :/
> >
> > -- Yehuda
> >
> >
> >
> > On Mon, Dec 29, 2008 at 6:42 PM, Saimon Moore <[email protected]>
> wrote:
> >
> > > Same behaviour here...
> >
> > > On Dec 30, 12:39 am, "Nicholas Orr" <[email protected]> wrote:
> > > > Yeshttp://gist.github.com/41434
> >
> > > > On Tue, Dec 30, 2008 at 10:37 AM, Kurt Schrader <[email protected]
> >
> > > wrote:
> >
> > > > > Do you have 'c[:reload_templates] = true' in your development.rb
> file?
> >
> > > > > -Kurt
> >
> > > > > On Dec 29, 2008, at 11:52 AM, cult hero wrote:
> >
> > > > > > I just upgraded to 1.0.7 and updated a project. Unless I missed
> > > > > > something, all I did was change the version number in the
> > > dependancies
> > > > > > file.
> >
> > > > > > Now, while working in development mode, if I make a change to a
> > > > > > template I have to manually restart merb for the changes to show
> up.
> > > I
> > > > > > didn't have to do this under 1.0.6.1.
> >
> > --
> > Yehuda Katz
> > Developer | Engine Yard
> > (ph) 718.877.1325
>
> >
>


-- 
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to