NOTE: This resquest had previously been made for Nucleus CMS. However, it has just been discovered that Nucleus CMS has forked, and the original platform has not had any real development in over half a year. Also, after more extensive testing inhouse, Nucleus CMS has proven FAR more complex than what we need. Therefore, Plog will be used. I developing a site using Mambo OS as my backbone. I want to use Plog as my blogging tool (located at this link: [url removed, login to view]). The successful solution will accomplish the following: 1) Mambo and Plog will share user information. Both applications will remain otherwise standalone (makes future upgrades sane). The applications can use separate logins (in other words, you don't have to integrate Mambo's login with Plog). 2) A MAJOR preference would be to have a Plog login module for Mambo so I can have this available to my users from Mambo's front page. 3) Plog has built-in multiuser multiblog capabilities, so no changes need to be made to add in that functionality. However, Plog uses a multi-form registration (needed for the user to provide the name for her blog so the system can create it). Please keep this in mind when developing your solution. When a user registers for Mambo, she should also be registered in Plog, and vice versa. I am open to the exact solution; however, the core code for both programs should remain intact. If you need to make SLIGHT changes to Nucleus mysql tables (i.e., field length), that may be acceptable. What I want is something that WORKS where I can upgrade / maintain both softwares normally (noting slight MYSQL changes the solution requires that are easily made with simple table edits ??" primarily to the USER data table). I need this solution ASAP. Feel free to ask any needed questions.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) 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 Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer 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 buyer on the site per the coder's Seller Legal Agreement).
Linux running on Apache