Testing Scripts in CMS App Recommendation

@Warlord_evil...I would like to recommend to all site Admin and those who you have modifying or creating scripts, that they do the following to prevent situations where errant code negatively impacts the site's functions.

1. When modifying existing scripts that are referenced in source code, make a copy of the script and rename it to the filename but add "_debug" before the file extension; i.e. "Lbp_me_debug.php".
2. Create a source code test area on the server where the site code exists; i.e. "//www.lbpcentral.com/forums(and whatever your Admin login path is)/debug/".
3. Create test pages for the specific areas you are trying to debug code for. In the source code for that page, reference the new filename, so the results of modifications to that _debug file can be seen, without having an impact on the released source code for the site.
4. Once the code has been debugged, and verified functioning properly, the filename can be changed to remove the "_debug" and then replace the original file with the new modified file.

Since the "/debug" path is only accessible by Admin, and is not referenced by any released source code, there is no impact or risk to the site's released code. I bring this up as it appears the "Lbp_me.php" script has been modified, possibly in an attempt to resolve the lbp.me scraper issue. Hope this helps. :)