We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 15510
    • 70 Posts
    I can hardly stand to wait with MODx 2 available. I know it’s beta but it has a lot of things I want. So, I took the plunge and installed it for a new web app I am working on. This is for a non-critical user base so I don’t have an issue with using a beta tool. But then, while researching how to access foreign database tables, I ran across a post from a well-known MODx community member just ten days ago stating that the

    schema is changing as we speak

    This sort of felt like stubbing one’s toe on the bed post--it really hurts and it makes you want to be more careful in the future. So, what would you do if you were just about to begin work on a big app?

    1. Build it in MODx Evo just like the good ol’ days.
    --or --
    2. Wait for MODx Revo to get out of beta so it’s not a moving target.

    I can’t afford to the time to do it twice and need some good advice.

    BTW, thanks especially to the MODx devel team. You guys are doing a great job and this is not about a lack of satisfaction with the way you’re running the project. Rather, just a search for the right balance of solution options.

    Thanks,
    kc64
      • 28215
      • 4,149 Posts
      He is correct - the schema is changing. That said, it’s only with regards to indexes and will be backwards compatible. So you should be OK.
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com