admin_usergroup_edit doesn't seem to be working

[Wakey]

I have thrown together a modification for a client where when a user is promoted using the promotion critera it sends them a private message informing them. As each usergroup has unique benefits each message needed to be unique so I needed to add a new field on the usergroup edit page to store and change each usergroups PM message.

I did this using the admin_usergroup_edit hook and it worked fine on my local test server but when implementing the modification on the clients server the field to enter the data refuses to display. I have installed it on 8 other forums running on a variety of hosting solutions to test and it works fine on all of them so it doesn't seem to be a code issue.


It have been trying things all day to isolate the problem and resolve it but with no luck. Has anyone encountered this kind of issue before or have any ideas of what may be causing it?

The code I'm using is below but I'm failry sure that isnt the problem

PHP Code:

print_table_header('User Promotion Notification PM Message');  
print_textarea_row('Message to send on promotion to this group', 'usergroup[pm_promotion]', $usergroup['pm_promotion']); 
print_table_break();  
print_column_style_code(array('width: 70%', 'width: 30%')); 


[kh99]

I can only think of two things offhand - check to see if there are any other plugins using that hook, maybe one of them has an error in it. Also, make sure hooks aren't disabled completely.

[Wakey]

No other plugins are assigned to the hook and I have tested a few of the other hooks and they work.

It does seem like it is that hook specifically that won't run as no matter what I put in there nothing gets displayed.

Is there any other way I can achieve the same thing without editing the usergroup.php file to hard code it?

[Wakey]

Just thought I would give you all an update. I managed to resolve this by uploading all the vBulletin files again.

Not sure what the person who setup the forum initially or updated it to the latest version did as the files the suspect files diagnostic wasn't showing any issues with any of the core files (just the usual issues relating to modification files) but that sorted it.