Solved Thanks
 

Solved Thanks

That is from a modification. Try disabling your modifications/plugins and see if you still have this problem.
Note: To temporarily disable the plugin system, edit config.php and add this line right under <?php

Solved Thanks

Remove the mod associated w/ "akspam_permissions" not disable but uninstall and see if that helps.

What usergroup is #2?

--------------- Added [DATE]1240016773[/DATE] at [TIME]1240016773[/TIME] ---------------

And... do you need to specify which usergroups can use the mod via it's options or vbulletin options? Maybe you did not specify and then when you try to make changes to the usegroup it is error'n out? Not 100% and btw which mod is that?

Edit: Some sort of anti-spam based on the name?

Solved Thanks

Wait lol... you mean you disabled them via products manager OR you did what Lynne suggested OR you uninstalled them all manually (you did not need to do that if so but spilled milk if so) ?

Go into admincp and via the Product Manager uninstall the spam mod that is for. Then edit the config and enable the mods again. See if that helps.

Solved Thanks

Well don't feel bad, just take your time and investigate it further.

Now you might have done too much but enable the mods again by deleting that code suggestion form your config file and upload it again etc.

See if that works if not come back running fingers crossed and hope for the best. ALWAYS do a DB backup @ least once a week I know it's too late for good advice but for the future eh?

You might need someone to actually look @ your sites admincp and files but be careful who you give access to.

S-MAN

the problem was, i had to remove the xml file manualy

GOOD TO HEAR!!!! Glad you stuck in there and tracked it down! Now, time to learn about backups eh? :D

S-MAN

--------------- Added [DATE]1240018454[/DATE] at [TIME]1240018454[/TIME] ---------------

BUT... you should have removed the links like I said and not all of the post contents! What if someone else in the future has the same problem and passes by this thread not knowing what you fixed via removing the xml manually.