Craig - 03 November 2006 05:13 AM

Yes it does Martin, 260 actually

1.5.0.2?

Just when I thought I couldn’t get more confused….
A. My problem was with 1.5.0 beta 3, which definitely doesn’t have @include anywhere in Codeigniter.php.
B. 1.5.0.1 doesn’t have it either.
C. Where is 1.5.0.2, and how will it help (given point A)?
I’m going to lie down in a darkened room now.

I never tried any of the betas, but the version I downloaded, 1.5.0 (and 1.5.0.1), on the homepage certainly did have that line in /system/codeigniter/CodeIgniter.php. If it doesn’t now, Rick must have made a sneaky change

....and another thing: if you’re saying that this line was at 260, my Codeigniter.php (1.5.0.1, re-downloaded this morning) only has 259 lines. I think Rick is trying to undermine what’s left of my sanity. It won’t work, I tell you! Nyaaaaagh! Nyaaaaagh! You’ll never take me alive, boy wonder! Hahahahahahaha!

It did have a total of 260 lines.

I know… it’s bad enough having to concentrate on your own app’s controllers, models and all associated code and strucutre; but then Rick goes and changes the framework and doesn’t let us view our own errors!

Is there any update on this problem?

I’ve downloaded 1.5.0.1 again and still have no parse errors.
I could not locate the code indicated by Rick, so I also went
to lie down in a dark room.

But I have to work, and not seeing the parse errors it’s a bit like
flying with your eyes closed, very exciting but a tad risky.

Oscar Bajner - 19 November 2006 10:16 AM

Is there any update on this problem?

Not exactly, but it seems to be cropping up in different guises: see here and here.
Output buffering seems to be the consistent factor, but other than that I’m stuck. Maybe it’s the CI way of making us work harder and better: “Dare to err, o halfwit, and I shall neither forgive nor explain!”

Thanks for the update Martin.

Martin Hall - 19 November 2006 11:07 AM

“Dare to err, o halfwit, and I shall neither forgive nor explain!”

Hey! What about us 1/100wits

I know this sounds really obvious.. I noticed I wasn’t getting parse errors and after going through some of the CI error handling code, I realised that display_errors was set to Off in my php.ini file. I’ve had PHP5 installed for over a year and never noticed

Oscar, in case you missed it: Rick to the rescue. Again.

Martin, thanks, I’ve just been testing out the fix and everything is looking good!

Still, I feel a bit depressed about it all.
I struggle to find and fix the bugs in code I wrote, on My own machine.

If Rick was a mechanic, it would be like a someone saying , “I got this problem,
every time I rev the motor past 4000 rpm, and then push in the clutch twice,
the radio starts up. I drive BMW version 1.8i and the radio is a customised
Blaupunkt autotech version 2.1, can you fix it? By Friday?”

Cheers

Did that fix it for everyone? I’ve downloaded the latest copy of 1.5.0.1 which I note has things like the @ removed but still getting blank pages…

Oscar Bajner - 20 November 2006 01:47 PM

If Rick was a mechanic

Ah, but did you get the car for free and did it come with a license agreement that says ”...IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED”?

Craig - 21 November 2006 07:33 PM

Ah, but did you get the car for free and did it come with a license agreement….

I dunno, It’s not my car