On Mon, 06 Apr 2009 23:48:46 -0400
Lance A. Brown la...@bearcircle.net wrote:
Matthew Topper said the following on 4/6/2009 7:48 PM:
Thanks, but see my latest email from this afternoon. The issue has
been resolved.
Maybe I missed it, but I didn't see a solution for your problem
On 07/04/2009, at 9:09 PM, Matthew Topper wrote:
On Mon, 06 Apr 2009 23:48:46 -0400
Lance A. Brown la...@bearcircle.net wrote:
Matthew Topper said the following on 4/6/2009 7:48 PM:
Thanks, but see my latest email from this afternoon. The issue has
been resolved.
Maybe I missed it,
Matthew Topper wrote:
On Tue, 7 Apr 2009 21:20:26 +1000
Kieren Diment kie...@diment.org wrote:
Argh. That begs the question as to why you are doing development
under apache, and not just using the built in test server for the
purpose that it's intended.
If the answer is that the dev
On Tue, Apr 7, 2009 at 9:41 AM, Ian Docherty catal...@iandocherty.com wrote:
Using Apache (already running)
You edit a controller
You switch to browser, spend minutes wondering why your change has no effect.
Slap head, switch to console
Restart apache
Switch to browser
Test changes
On Tue, Apr 07, 2009 at 07:09:55AM -0400, Matthew Topper wrote:
Maybe the email was lost somewhere as I sent it out last afternoon.
Anyway, for anyone that cares the problem was simply that I didn't
restart apache after modifying some of my controllers. So, it used the
new templates but
On Tue, Apr 7, 2009 at 10:19 AM, Lance A. Brown la...@bearcircle.net wrote:
I expect his updated controller was setting $page, not something in the
template. Therefor with the new template, but the old, still-running
controller, $page was empty, leading to the above error message.
--[Lance]
Matthew Topper said the following on 4/6/2009 7:48 PM:
Thanks, but see my latest email from this afternoon. The issue has
been resolved.
Maybe I missed it, but I didn't see a solution for your problem come
across the list...
--[Lance]
--
GPG Fingerprint: 409B A409 A38D 92BF 15D9 6EEE
