I have posted for help on a PHP forum with that little bit of the mod. Hopefully one of them will be able to help me sort it out.

I hope so, as I have a pretty close setup to what you have and can not replicate what you are getting.

Yeah I know, I have another client who is running this hack and they are running PHP 5.4 and vB 4.2.2 as well and it works just fine. I really think now that it may have something to do with the recent server upgrade/move for this client. The host he uses are horrible and could not set anything up to save their lives I think. I'm relatively sure that my dog could set it up better, but hey nothing I can do about that. :(

I'll throw out an option.

As you are on PHP 5.4.x (and not PHP 5.5.x)

In your config.php file change from

to

On the off chance regular mysql still works but mysqli does not.

Also- I have removed the file you posted. You may not redistribute whole files (or significant parts) of mods not marked as re-usable code.

Thanks but that did nothing as it was already marked as mysql and not mysqli. :( As for the file, ok.

Then did you try it as mysqli?

mysqli is the better one, if both work.

Yep since it was already in mysql I tried it as mysqli and I got the same problem. :(

See my PM...

I believe it's as simple as some missing quotes.

$formbit['value'] = $q[$formbit[id]];

Should be

$formbit['value'] = $q[$formbit['id']];

Thanks but that did not work.

I'm thinking maybe the problem is $q. It looks like it might not be set to anything at that point (although it depends on the value of $_POST['do'], which I don't know). But I suppose it could be that before it was just an unset value generating a warning, and now something else has used it as a variable (a plugin or included vb code).

That's just a guess, but it looks like $formbit should definitely be an array at that point (unless you have a plugin using hook easy_forms_view_question_start that changes it).