There was a minor error in a feature added to 0.6.8
If you had a database with pages that referenced page types that no
longer existed, you would have received errors about undefined
constants. 0.6.8 tried to address this by only loading that class if
the class was defined. This is a great way to allow you to easily
remove extensions without repercussions, but there was an oversight in
that that feature wasn't reloading in development mode.
0.6.9 Is in the works and should be out soon, but this is fixed on edge.
As for Dan and Norine Simpson's message about needing to specify the
directory for a new instance, I don't recall ever not needing to do
that. The rails command has the same requirement. But perhaps I'm
misunderstanding something.
-Jim
On Jul 29, 2008, at 9:45 AM, Anton J Aylward wrote:
Dan and Norine Simpson said the following on 28/07/08 11:46 AM:
A brand new installation seems to require specifying the name of the
directory for your installation. So, for example:
Most of us here are already using radiant and every upgrade makes me
nervous.
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
