We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 15759
    • 5 Posts
    Hi folks,

    fist of all i want to excuse for my poor english .......

    In our company we have to recode a huge application for one of our customers.
    In gerneral the app is an database with customers, products, etc.
    They handle their products, prices, country specific prices, shipping handling fees and so on.....
    Every reseller has its own acces to configure his specific settings and handles its data (customers, orders .......)
    This backend will be realized using CakePHP or Zend Framework - not sure at this time
    (The existing database backend uses > 100 database tables)

    After really good experiences with MODx we want to use one MODx system for each reseller.

    I did a small workaround creating an own Snippet that worked fine ....

    Is there a "MODx-like" way to realize this ?

    Greetings from germany,

    Robert


      • 22303 MODX Staff
      • 10,725 Posts
      As long as you isolate your application’s domain model (i.e. the business logic that may or may not be related to specific database tables), you should be able to present your data through MODx by developing some simple view snippets. However, this is assuming that your domain model is not burdened with presentation code, session handling, etc. You’ll want to be able to let MODx handle these views and be the main controller for your application, calling on your model code from the view scripts.

      That said, if you haven’t already chosen a framework for constructing your domain model, you might also consider something like xPDO, a sister project of MODx which is meant to help create lightweight domain models in PHP and provide CRUD scaffolding for your database tables with a minimum of effort. You end up with a basic object-oriented API for interacting with all table objects (ActiveRecord), and a simple domain model layer to use in any presentation system (like MODx). And it’s all a wrapper around the PDO data access layer that is the foundation for accessing various database engines using a single, consistent API from PHP.
        • 15759
        • 5 Posts
        Hi OpenGeek,

        thanks for your explanation and opinion.
        In fact it is planned to use xPDO as database layer inside zend framekwork.
        ZF will be used to handle the controllers/actions and the needed neccessary additions.
        (There will be a lot usage of SOAP webservices, which is now implemented in ZF 1.6)

        The only thing i’m not really sure - will it be a problem to handle sessions inside my business logic ?

        I’ll see and let you know .....

        Greeetings,

        Robert