Update Complicated PHP Review System to Fix Lots of PHP5.6 + 7 Bugs

IMPORTANT: This project requires a very experienced PHP coder, ideally somebody who is familiar with tackling complicated systems and the shared integration of member databases/login systems between separate PHP programmes. Do not bid if you aren’t prepared for a challenge. Being familiar with vBulletin v4 is a bonus. --------- We currently use a PHP based visitor review system called Censura on our website, which was originally coded for PHP5.2 and stopped being developed by the authors at the end of 2013. The system also integrates with the popular vBulletin 4.2.5 Beta 1 discussion forum software (this already supports PHP7.0), which acts as an external member database and registration system. The review system has many directories and PHP files, which makes it quite confusing. So far the reviews system has worked perfectly up to PHP5.6, although this is only because the previous author chose to hide all of the error messages. After I re-enabled the display of errors in the review system it became clear that it has many bugs which need fixing (mostly compatibility and deprecated features that have been introduced since around PHP5.3). We expect to adopt PHP7.0 at the end of this year and obviously the bugs mean our review system won’t work at all with v7. The aim of this project is to fix all of the bugs (both in the admin system and public front end) so that the review system functions normally up to PHP7.0 (note: PHP5.6 is our current server environment but we do have a limited test for PHP7.0). I’ve written a detailed document that will be uploaded once the project is assigned to somebody. I’ll also upload a backup of the MySQL database and the review systems original setup/install files to help with resolving the bugs. I’d estimate it may take anything from 10-20 days to fix everything, depending upon your skill level. You will need to take a bit of time in order to fully understand how the system works and the way it integrates the complicated member system before you begin changing code. Try logging in and posting / editing a few reviews, have a look around the Censura admin pages, read the document I upload a few times (this is only available to the winning bidder). Get familiar with it first. I can’t stress this enough, if you dive right in you’ll get confused. ------------- Small Sample of the Errors: Strict Standards: Non-static method Censura_Controller_Front::getInstance() should not be called statically in /*******/[login to view URL] on line 16 Strict Standards: Declaration of Censura_Models_Image::update() should be compatible with Censura_Model::update($properties = false) in /*******/system/apps/Censura/Models/[login to view URL] on line 20 Warning: Cannot modify header information - headers already sent by (output started at /*******/[login to view URL]) in /*******/system/apps/Censura/Controller/[login to view URL] on line 74 Deprecated: Non-static method Censura_Controller_ApplicationRegistry::setControllerMap() should not be called statically, assuming $this from incompatible context in /*******/system/apps/Censura/Controller/[login to view URL] on line 281 Strict Standards: Only variables should be assigned by reference in /*******/system/apps/Censura/Controller/[login to view URL] on line 133 Strict Standards: Only variables should be assigned by reference in /*******/system/apps/Censura/Controller/[login to view URL] on line 327 Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /*******/system/libs/Smarty/[login to view URL] on line 270 Deprecated: Non-static method Censura_IdentityMap::getInstance() should not be called statically, assuming $this from incompatible context in /*******/system/apps/Censura/[login to view URL] on line 115 Strict Standards: Declaration of Censura_Models_Dao_Review::getAll() should be compatible with Censura_Dao::getAll($orderBy = Array, $all = false, $daoInstance = NULL) in /*******/system/apps/Censura/Models/Dao/[login to view URL] on line 766