[Millemissen]

What the h*ck does this mean?

MM

[Keith Saunders]

Thank you for your feedback and apologies for the issue.

The problem was a coding error in one of the modules compounded by the fact that I had the “Debug” setting incorrectly set which allowed all logged in user to see errors.

Whilst the problem is not yet 100% fixed, the forum will function as normal.

If we happen to get any coding errors in the future, the error message will now only be seen by me and the moderators.

[Keith Saunders]

I can confirm that the problem is now 100% fixed.

Keith..

[DJneo]

It’s just a bug in the code of the forum.

More technically it’s trying to read a variable in an array. A type of combination of grouped together variables. But instead of an Array the code gets an Boolean. (A variable that only can be yes or no)

And it’s trying to read something in an array on a certain position. But it can not. So it gives an error, and the website displays the error

[Steve at Sounds Heavenly]

Hi MM,

I have left a note for Keith to make him aware of this, I suspect it should be fairly straightforward to fix.

Kind regards, Steve.

[Millemissen]

Thanks to both of you.

It is a bit unusual and I got worried…..thinking back on the ‘errors’ that stopped the former forum.

MM

[Millemissen]

Update!

The message only appears when you are logged in.

(Thanks Keith for trying to solve this).

MM

[matador]

Thank you Keith.

And this? Just noticed it now:

[Keith Saunders]

That is part of the code debugger which only showed for me and moderators, but I have now switched it off for moderators as it lets you do things at code level..

Please confirm that you no longer see it?

[Guy]

It was there for me too, but has now disappeared. Thanks Keith!

[matador]

Also disappeared for me too.

[Author]

Posts