Hi there, I am using Simple Machines Forum as my online community builder. I installed a mod or modification which is like a plug in to extend functionality(It was an ad generation/management plug in) so I can rotate ads on my forum. I got a fatal error when I tried to activate it. I then uninstalled the mod and got this error on my main forum's page Fatal error: Call to undefined function template_ad_position() in /home/content/m/a/a/maaxseduction/html/viplounge/Sources/Load.php(2151) : eval()'d code on line 273 You can see the image here http:// www.maaximumseduction.com/viplounge/ It is at the bottom of my forum as you can see here. How do I remove it?
How do I find out where and what that looks like? Also how do I find that line number? Is there a webmaster tool that can take me right to that line? Thanks
Try fix it with this: http://www.simplemachines.org/community/index.php?topic=381408.msg2642601#msg2642601
Uhm, seriously? By all means - we try to cater to newbies, but if you're asking those questions, you should really read up a bit on PHP... and probably also using a text-editor. You open up the file in your favorite text-editor (personally, I use Sublime Text), and use that text-editor's "go to line" function - ctrl+g in Sublime. There you'll find the function (template_ad_position() - just as it said in the error-message) - remove it. Although, if you know nothing about PHP, there might be more that needs to be removed, or some calls that surrounds it... however, if you take away that line, and there's still errors, you'll get a different error. Now, I don't know SMF, but it seems there is some rather questionable plug-in functionality, if it doesn't also remove the entries for the plugin in the template files (or whatever those files are). Did you remove the plugin via the forum-software control panel?
Yes I uninstalled it within the dashboard and then what happened was it cut off everything below my navbar. I then went to Godaddy and restored my files to a previous time stamp. However, it left that message.
You could maybe, if the error is still there, try going back even further - however, you need to set up a test-environment - never, EVER try out plugins / other functionality on a production environment - always test on a local copy, or a subdomain (dev.domain.com) or something - that way you can avoid stuff like this.