Fatal error issue...help?
 

Tonight when I went to check some permissions for one of my usergroups in my admincp, I couldn't access any of my usergroup settings or the "add new usergroup" sections, when I tried to do so it returned this error:
Fatal error: Cannot use string offset as an array in /home/sskies/public_html/includes/class_bitfield_builder.php on line 312

I'm not even sure what this even means?

I was able to access everything else in my admincp without problem (except the administrator permissions area, which returned the same error), but I haven't changed anything anytime recently, and I know it was working a few weeks ago. I have no idea what might be causing the problem. Does anyone have any idea what might be causing the problem or what I can do to fix it?

I'm using version 3.5.0 and I have a number of mods installed, but again, it was working fine recently and I haven't changed any files or templates or anything at all in months probably, short of adding a couple new usergroups. I think my host might have recently upgraded from php4 to php5, might this have anything to do with it?

Any help would be greatly appreciated
Thanks in advance!

This could be due to a modification not removed proper.

I haven't removed anything in months though :confused: This has just started happening within the last week or two at most.

Do a table repair.

I tried but it just sat at the "please wait" screen and didn't do anything :\

Did you make sure to check the boxes (as in Check all)? You will get that screen if you do not check any boxes, too. ;)

Haha, I'm such a ditz sometimes. I did it again, this time being sure to check all the boxes, but I'm still getting the error message when I try to access my usergroups :(

Try repairing the tables in myphpadmin

Still no luck :(

I doubt this has anything to do with table corruption. Most likely cause is a modifcation that does not work correct on your new PHP/MySQL versions.

Also please upgrade your vBulletin, the version you are using is very outdated and might also be causing problems with newer PHP/MySQL versions.

You could start by disabling modifications from your config.php and see if that solves the error.

Otherwise create a test board (duplicate of production) and start uninstalling modification on your test install until problem is solved.