Override/section problem (bug?): "Undefined index: node in ..."

Next topic

Author	Message
Lars Arne Brekken	Tuesday 08 July 2003 1:23:03 am My new site was working wonderfully. It was structured into five folders with a couple of objects in each. Then I decided to assign a section to each of the folders. My site stopped working, it seemed like the whole override system stopped working. Please note that I had no Match[section]=id in override.ini.append, the sections were only made in case they could be useful later. I was getting error messages like this: Undefined index: node in /ez/var/cache/override/override_[big ugly number] on line 678 Where 678 would be something like if ( $matchKeys['node'] == '51' ) After a lot of debugging, checking my override.ini.append etc, I gave up and removed the sections (everything is section 1 now). Now it works again. Since I don't really need sections here I can live with this, but I would like to know if anyone has experienced the same thing. Is it a feature, a bug or have I misunderstood something? Lars

Author

Message

Tuesday 08 July 2003 1:23:03 am

My new site was working wonderfully. It was structured into five folders with a couple of objects in each.

Then I decided to assign a section to each of the folders. My site stopped working, it seemed like the whole override system stopped working.

Please note that I had no Match[section]=id in override.ini.append, the sections were only made in case they could be useful later.

I was getting error messages like this:

Undefined index: node in /ez/var/cache/override/override_[big ugly number] on line 678

Where 678 would be something like
if ( $matchKeys['node'] == '51' )

After a lot of debugging, checking my override.ini.append etc, I gave up and removed the sections (everything is section 1 now).

Now it works again.

Since I don't really need sections here I can live with this, but I would like to know if anyone has experienced the same thing. Is it a feature, a bug or have I misunderstood something?

Lars