We are running Phpbb2 that has been modified previously by a programmer to be separated into 2 sides of a forum requiring a login to reach each side.? They have individual databases and share a few things on a combined database.? We also have a registration system that controls the access to all areas of the site including permissions to the forums.? This may have to be taken into consideration when combining the db's.? We want the db's to be combined without losing threads then upgraded to phpbb3 and be sure that our Dynamo Registration system (which has also been modified for us) interacts correctly with the upgrade
Dynamo Registration System - Modified from it's original version to allow us choose permissions manually when registration requests are received and then approved. It also was set up to communicate to our members through a newsletter and email. This does not work. Also there is intermittent problems with people who try to register by checking the appropriate boxes but when trying to approve in the admin the boxes are not checked. Somewhere it is losing the entered information but not on all requests.
Dynamo is a content hierarchy script that allows users to access certain areas of the site based on the group they are assigned. It was customized for us by a previous programmer from rent-a-coder. As far as I know and I will look again for anymore information on the previous work, there was some API code for authentication process written an then plugged into the Dynamo modules and the other scripts that were consolidated
1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement).
2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment.
b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project.
Sql, Dynamo, Phpbb2