Use modx's login and my old login system?

I currently have a website that has no content management system. However, it is built on a php/mysql based login system. Users have accounts and can login to upload photos, we fix the photos and the users log in to pay for them. We also have an admin section that allows us to actually manage our users etc.

I am looking at modx to manage the front end/cms part of the website. However, can I do that AND keep the old login system for customers/admins of our current business process?

Thanks in advance!

I am looking at modx to manage the front end/cms part of the website. However, can I do that AND keep the old login system for customers/admins of our current business process?

Greetings dwalls32 and welcome to MODx!

If I’m understanding your posting correctly, you want to keep the old login system for existing customers but add MODx in the same directory to handle the CMS component.

I have a client with a little different but similar situation. He has both MODx and WordPress in the same root directory. I put Wordpress in a separate directory (root directory/wordpress), but yeh, they coexist under the same root directory. Obviously they run from 2 different Databases. So I would assume you’ll be operating under a similar situation.

I guess you essentially will have MODx maintain the site itself and have a login form or link, for instance, on the home page directing the client to a login page enabling them to login to your current login area to upload their photos.

I hope that answers your question. If you have additional information and specifics for this project, that could help.

Good luck!

MODx is very flexible so you have a few options (I am sure that there are more):

1) do as flinx suggested, have both apps run side-by-side each doing it’s own thing.

2) integrate the custom app into the MODx site by using a combination of module (for administration) and snippets (for front end integration. A module is useful to add custom functions to the manager interface (back-end). You could also keep the administration in the front-end and not build a module, so you could have a custom administration section as well.

3) Go native, abandon you system and use MODx for everything...user, content, document management.