[SnakeEaterITA]

Hi everyone,

I recently updated to 4.2.5 and I started getting tons of PHP error messages:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Line 564 is

($hook = vBulletinHook::fetch_hook('process_templates_complete')) ? eval($hook) : false;

Line 60 is an empty one under

public $group_templates = array();


Do you have any idea how I could solve this problem?

[Dave]

It means that one of your plugins that is hooked into process_templates_complete has this problem on line 60 (in the hook).
My guess is that there's a declaration using =& somewhere, removing the ampersand sign should fix it.

[SnakeEaterITA]

wow thanks for the quick reply, really appreciated!

Does it mean I'd have to go through my plugins one by one, and check all of them at line 60?

If I am not wrong =& is basically a pointer? But wouldn't changing it to = change the way data is handled ?

[Dave]

Go to your AdminCP > Plugins & Products > Plugin Manager > CTRL + F and search for process_templates_complete hooks.

For each match found click on edit and look around line 60 for =& or some function that makes use of old standards. Feel free to paste line 58-62 here so we can take a look.

Changing it to =& shouldn't deal any damage, vBulletin changed all =& to = in the latest vBulletin version if I recall correctly in order to support PHP 7.

[SnakeEaterITA]

There is only one plugin that has many lines of code (the others just have just a couple)

And this is the one

Starting on line 56

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

[Dave]

I don't see anything wrong but you can try disabling the plugin which uses this hook and see if that fixes it. That way we can be certain it's this hook.

[Lynne]

When the hooks are stored in the database, ALL the hooks using the process_templates_complete location are stored 'on top of each other' (one after another). If one is only 10 lines, then the next is 70 lines, then line "60" or the error could be line 60 of the second plugin if it was stored first OR line 50 of the second plugin if it was stored second. So, you actually need to look at all the plugins using that hook location to find the problem one.